From f1d67f0d9b57978b6e6caec1831450ce61ad2bcc Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 12 Jun 2024 17:39:47 +0000 Subject: [PATCH] deploy: 6877256c733f1f586fb9b4507c40c5fe5bf44091 --- 404.html | 10 +- assets/js/0058b4c6.60f0e41c.js | 1 - assets/js/0645984d.49a414ef.js | 1 - assets/js/0645984d.a8f4276b.js | 1 + assets/js/098dc4e6.10dd02c5.js | 1 - assets/js/098dc4e6.e895a85a.js | 1 + assets/js/0d7102ad.3bf1d960.js | 1 + assets/js/0df7deee.7b518820.js | 1 - assets/js/0df7deee.9699a91f.js | 1 + assets/js/10f26ab1.5fd3c153.js | 1 + assets/js/10f26ab1.d8f6ab99.js | 1 - assets/js/14b69759.0fa34992.js | 1 + assets/js/14b69759.4cb6dda2.js | 1 - assets/js/1897e797.889597f7.js | 1 + assets/js/1897e797.a5189ebb.js | 1 - assets/js/2224ae46.783d61b2.js | 1 + assets/js/2224ae46.f3cc4e4b.js | 1 - assets/js/254e3ee1.1d0a0cd9.js | 1 + assets/js/254e3ee1.89e71a31.js | 1 - assets/js/26649072.839aad2f.js | 1 + assets/js/27525b73.1a9db273.js | 1 - assets/js/27525b73.57797350.js | 1 + assets/js/2856a3e9.6cedd9a8.js | 1 - assets/js/2856a3e9.94a3fe6b.js | 1 + assets/js/2baaddb5.d409b228.js | 1 - assets/js/2baaddb5.fb0c20ca.js | 1 + assets/js/31f0b325.005710f7.js | 1 + assets/js/31f0b325.805d49fe.js | 1 - assets/js/3217192f.3749e5fb.js | 1 - assets/js/33a2184c.d317ea9c.js | 1 + assets/js/395bc0fb.05804c3d.js | 1 - assets/js/395bc0fb.a9981247.js | 1 + assets/js/3a2db09e.d000d160.js | 1 - assets/js/3a483871.398477f1.js | 1 - assets/js/3a483871.a8f87262.js | 1 + assets/js/3ce65734.d0cfde38.js | 1 - assets/js/3ce65734.da2b09c7.js | 1 + assets/js/48cc5724.66988744.js | 1 + assets/js/48cc5724.9b95328e.js | 1 - assets/js/50f28384.07b57415.js | 1 + assets/js/50f28384.c44fb4f0.js | 1 - assets/js/5243e443.389830ca.js | 1 - assets/js/5243e443.c9476cb5.js | 1 + assets/js/5440ed21.cdb4e68b.js | 1 - assets/js/5440ed21.ff303a3d.js | 1 + assets/js/560caf3c.bd452bc3.js | 1 + assets/js/59362658.906280ee.js | 1 + assets/js/59362658.dd12e8ea.js | 1 - assets/js/5e90a9b3.f62940b7.js | 1 - assets/js/63fe0935.b19a060b.js | 1 - assets/js/63fe0935.f321da39.js | 1 + assets/js/66b22c07.5886033a.js | 1 + assets/js/66b22c07.7207ff62.js | 1 - assets/js/6e164704.2afa60e6.js | 1 + assets/js/6e427521.20abbda1.js | 1 + assets/js/6e427521.349c29f1.js | 1 - assets/js/726bd3c0.683c1427.js | 1 - assets/js/726bd3c0.a48ff20e.js | 1 + assets/js/73664a40.250d7ffe.js | 1 - assets/js/73664a40.e30c8f5d.js | 1 + assets/js/7661071f.7786def8.js | 1 - assets/js/7661071f.fee017db.js | 1 + assets/js/814f3328.03a5e2e9.js | 1 + assets/js/814f3328.ba556011.js | 1 - assets/js/8389dc22.0d95d5f5.js | 1 + assets/js/8389dc22.eccc2b17.js | 1 - assets/js/851dcdeb.27d33105.js | 1 + assets/js/851dcdeb.ebc951b4.js | 1 - assets/js/86cc9362.8dd8d276.js | 1 - assets/js/86cc9362.bf26d0aa.js | 1 + assets/js/8717b14a.61162e66.js | 1 + assets/js/8717b14a.f509a579.js | 1 - assets/js/8843b0b9.17ea4325.js | 1 + assets/js/8843b0b9.bee4b4e3.js | 1 - assets/js/8acd709f.f254a944.js | 1 - assets/js/8acd709f.f97fb67c.js | 1 + assets/js/925b3f96.0c146a7d.js | 1 + assets/js/925b3f96.32f6b67d.js | 1 - assets/js/9bc6bf15.38bcf64b.js | 1 + assets/js/9bc6bf15.f3c661c2.js | 1 - assets/js/9c06b359.3fbf8174.js | 1 - assets/js/9c06b359.6515b964.js | 1 + assets/js/9e6fa7e7.84261d61.js | 1 + assets/js/a618e3e0.158299c0.js | 1 + assets/js/a618e3e0.b2684b5d.js | 1 - assets/js/a80828e2.28d37de2.js | 1 + assets/js/a80828e2.a5eb1300.js | 1 - assets/js/aabcef9f.82d66d1c.js | 1 + ...cf23e.bc0ec99a.js => acecf23e.1323fa32.js} | 2 +- assets/js/ae9ec75a.1b45b0b2.js | 1 + assets/js/ae9ec75a.c4c54758.js | 1 - assets/js/b2cb1568.44a52af5.js | 1 + assets/js/b2cb1568.f099de7c.js | 1 - assets/js/bf1307fc.113673dd.js | 1 - assets/js/c11d2165.6f42c32c.js | 1 - assets/js/c11d2165.a098c856.js | 1 + assets/js/c15d9823.2860de81.js | 1 - assets/js/cd8fd8f7.49890ea6.js | 1 + assets/js/cd8fd8f7.c9eb6ea1.js | 1 - assets/js/d85277d8.c8e6f117.js | 1 + assets/js/d9f32620.2c3364c5.js | 1 - assets/js/d9f32620.e0a03946.js | 1 + assets/js/e18cfb11.6b3ca214.js | 1 + assets/js/e18cfb11.c1b055af.js | 1 - assets/js/e273c56f.2ea068a8.js | 1 - assets/js/e273c56f.f5a0a811.js | 1 + assets/js/e5aefb32.5951bfd8.js | 1 - assets/js/e6e7a2ca.3ced26fd.js | 1 + assets/js/e6e7a2ca.592f45cb.js | 1 - assets/js/ec8f9750.7249b2c9.js | 1 + assets/js/f2eba590.c1a1ec04.js | 1 + assets/js/f2eba590.e3ea43d6.js | 1 - assets/js/f4f34a3a.41ee1bc9.js | 1 - assets/js/f4f34a3a.fe4a86c8.js | 1 + assets/js/f7adb76b.a4e31be2.js | 1 - assets/js/f7adb76b.b6121aca.js | 1 + assets/js/f81c1134.c6423362.js | 1 - assets/js/f82cd581.5ed7ba64.js | 1 - assets/js/f898e4d1.19bbffaa.js | 1 - assets/js/f898e4d1.9f6c5925.js | 1 + assets/js/main.5a2fcde4.js | 2 + ...CENSE.txt => main.5a2fcde4.js.LICENSE.txt} | 0 assets/js/main.f17cfb1f.js | 2 - assets/js/runtime~main.5adfe12d.js | 1 + assets/js/runtime~main.ef8da056.js | 1 - blog.html | 18 +-- blog/archive.html | 10 +- blog/atom.xml | 24 ++-- blog/first-blog-post.html | 10 +- blog/long-blog-post.html | 12 +- blog/mdx-blog-post.html | 12 +- blog/rss.xml | 20 +-- blog/tags.html | 10 +- blog/tags/docusaurus.html | 18 +-- blog/tags/facebook.html | 14 +-- blog/tags/hello.html | 16 +-- blog/tags/hola.html | 10 +- blog/welcome.html | 14 +-- copyright.html | 12 +- docs/next/operating-model/appendix.html | 20 +-- docs/next/operating-model/change-log.html | 18 +-- docs/next/operating-model/glossary.html | 12 +- .../how-data-space-governance.html | 84 ++++++------- .../how-data-space-operations.html | 36 +++--- .../how-life-cycle-management.html | 16 +-- .../next/operating-model/operating-model.html | 14 +-- docs/next/operating-model/outlook.html | 38 +++--- .../operating-model/what-service-map.html | 40 +++--- .../who-roles-in-the-catena-x-ecosystem.html | 52 ++++---- .../operating-model/why-introduction.html | 24 ++-- ...understanding-the-catena-x-data-space.html | 38 +++--- docs/next/search-index.json | 2 +- docs/next/standards/overview.html | 10 +- docs/next/working-model/ecosystem.html | 34 ++--- docs/next/working-model/glossary.html | 10 +- .../organizational-structure.html | 26 ++-- .../02-03-tooling.html | 22 ++-- .../overview-roles.html | 26 ++-- .../overview-roles/catena-x-roles.html | 116 +++++++++--------- .../overview-roles/tractus-x-roles.html | 26 ++-- docs/next/working-model/overview.html | 18 +-- ...03-01-process-from-idea-to-production.html | 94 +++++++------- .../03-02-Contribution-Guideline.html | 20 +-- .../03-04-Issue-Process.html | 50 ++++---- docs/operating-model/appendix.html | 20 +-- docs/operating-model/change-log.html | 18 +-- docs/operating-model/glossary.html | 12 +- .../how-data-space-governance.html | 84 ++++++------- .../how-data-space-operations.html | 36 +++--- .../how-life-cycle-management.html | 16 +-- docs/operating-model/operating-model.html | 14 +-- docs/operating-model/outlook.html | 38 +++--- docs/operating-model/what-service-map.html | 40 +++--- .../who-roles-in-the-catena-x-ecosystem.html | 52 ++++---- docs/operating-model/why-introduction.html | 24 ++-- ...understanding-the-catena-x-data-space.html | 38 +++--- docs/standards/overview.html | 10 +- docs/working-model/overview.html | 10 +- getting-started-github.html | 36 +++--- index.html | 10 +- markdown-guidelines.html | 82 ++++++------- search-index.json | 2 +- search.html | 10 +- sitemap.xml | 2 +- 184 files changed, 868 insertions(+), 868 deletions(-) delete mode 100644 assets/js/0058b4c6.60f0e41c.js delete mode 100644 assets/js/0645984d.49a414ef.js create mode 100644 assets/js/0645984d.a8f4276b.js delete mode 100644 assets/js/098dc4e6.10dd02c5.js create mode 100644 assets/js/098dc4e6.e895a85a.js create mode 100644 assets/js/0d7102ad.3bf1d960.js delete mode 100644 assets/js/0df7deee.7b518820.js create mode 100644 assets/js/0df7deee.9699a91f.js create mode 100644 assets/js/10f26ab1.5fd3c153.js delete mode 100644 assets/js/10f26ab1.d8f6ab99.js create mode 100644 assets/js/14b69759.0fa34992.js delete mode 100644 assets/js/14b69759.4cb6dda2.js create mode 100644 assets/js/1897e797.889597f7.js delete mode 100644 assets/js/1897e797.a5189ebb.js create mode 100644 assets/js/2224ae46.783d61b2.js delete mode 100644 assets/js/2224ae46.f3cc4e4b.js create mode 100644 assets/js/254e3ee1.1d0a0cd9.js delete mode 100644 assets/js/254e3ee1.89e71a31.js create mode 100644 assets/js/26649072.839aad2f.js delete mode 100644 assets/js/27525b73.1a9db273.js create mode 100644 assets/js/27525b73.57797350.js delete mode 100644 assets/js/2856a3e9.6cedd9a8.js create mode 100644 assets/js/2856a3e9.94a3fe6b.js delete mode 100644 assets/js/2baaddb5.d409b228.js create mode 100644 assets/js/2baaddb5.fb0c20ca.js create mode 100644 assets/js/31f0b325.005710f7.js delete mode 100644 assets/js/31f0b325.805d49fe.js delete mode 100644 assets/js/3217192f.3749e5fb.js create mode 100644 assets/js/33a2184c.d317ea9c.js delete mode 100644 assets/js/395bc0fb.05804c3d.js create mode 100644 assets/js/395bc0fb.a9981247.js delete mode 100644 assets/js/3a2db09e.d000d160.js delete mode 100644 assets/js/3a483871.398477f1.js create mode 100644 assets/js/3a483871.a8f87262.js delete mode 100644 assets/js/3ce65734.d0cfde38.js create mode 100644 assets/js/3ce65734.da2b09c7.js create mode 100644 assets/js/48cc5724.66988744.js delete mode 100644 assets/js/48cc5724.9b95328e.js create mode 100644 assets/js/50f28384.07b57415.js delete mode 100644 assets/js/50f28384.c44fb4f0.js delete mode 100644 assets/js/5243e443.389830ca.js create mode 100644 assets/js/5243e443.c9476cb5.js delete mode 100644 assets/js/5440ed21.cdb4e68b.js create mode 100644 assets/js/5440ed21.ff303a3d.js create mode 100644 assets/js/560caf3c.bd452bc3.js create mode 100644 assets/js/59362658.906280ee.js delete mode 100644 assets/js/59362658.dd12e8ea.js delete mode 100644 assets/js/5e90a9b3.f62940b7.js delete mode 100644 assets/js/63fe0935.b19a060b.js create mode 100644 assets/js/63fe0935.f321da39.js create mode 100644 assets/js/66b22c07.5886033a.js delete mode 100644 assets/js/66b22c07.7207ff62.js create mode 100644 assets/js/6e164704.2afa60e6.js create mode 100644 assets/js/6e427521.20abbda1.js delete mode 100644 assets/js/6e427521.349c29f1.js delete mode 100644 assets/js/726bd3c0.683c1427.js create mode 100644 assets/js/726bd3c0.a48ff20e.js delete mode 100644 assets/js/73664a40.250d7ffe.js create mode 100644 assets/js/73664a40.e30c8f5d.js delete mode 100644 assets/js/7661071f.7786def8.js create mode 100644 assets/js/7661071f.fee017db.js create mode 100644 assets/js/814f3328.03a5e2e9.js delete mode 100644 assets/js/814f3328.ba556011.js create mode 100644 assets/js/8389dc22.0d95d5f5.js delete mode 100644 assets/js/8389dc22.eccc2b17.js create mode 100644 assets/js/851dcdeb.27d33105.js delete mode 100644 assets/js/851dcdeb.ebc951b4.js delete mode 100644 assets/js/86cc9362.8dd8d276.js create mode 100644 assets/js/86cc9362.bf26d0aa.js create mode 100644 assets/js/8717b14a.61162e66.js delete mode 100644 assets/js/8717b14a.f509a579.js create mode 100644 assets/js/8843b0b9.17ea4325.js delete mode 100644 assets/js/8843b0b9.bee4b4e3.js delete mode 100644 assets/js/8acd709f.f254a944.js create mode 100644 assets/js/8acd709f.f97fb67c.js create mode 100644 assets/js/925b3f96.0c146a7d.js delete mode 100644 assets/js/925b3f96.32f6b67d.js create mode 100644 assets/js/9bc6bf15.38bcf64b.js delete mode 100644 assets/js/9bc6bf15.f3c661c2.js delete mode 100644 assets/js/9c06b359.3fbf8174.js create mode 100644 assets/js/9c06b359.6515b964.js create mode 100644 assets/js/9e6fa7e7.84261d61.js create mode 100644 assets/js/a618e3e0.158299c0.js delete mode 100644 assets/js/a618e3e0.b2684b5d.js create mode 100644 assets/js/a80828e2.28d37de2.js delete mode 100644 assets/js/a80828e2.a5eb1300.js create mode 100644 assets/js/aabcef9f.82d66d1c.js rename assets/js/{acecf23e.bc0ec99a.js => acecf23e.1323fa32.js} (57%) create mode 100644 assets/js/ae9ec75a.1b45b0b2.js delete mode 100644 assets/js/ae9ec75a.c4c54758.js create mode 100644 assets/js/b2cb1568.44a52af5.js delete mode 100644 assets/js/b2cb1568.f099de7c.js delete mode 100644 assets/js/bf1307fc.113673dd.js delete mode 100644 assets/js/c11d2165.6f42c32c.js create mode 100644 assets/js/c11d2165.a098c856.js delete mode 100644 assets/js/c15d9823.2860de81.js create mode 100644 assets/js/cd8fd8f7.49890ea6.js delete mode 100644 assets/js/cd8fd8f7.c9eb6ea1.js create mode 100644 assets/js/d85277d8.c8e6f117.js delete mode 100644 assets/js/d9f32620.2c3364c5.js create mode 100644 assets/js/d9f32620.e0a03946.js create mode 100644 assets/js/e18cfb11.6b3ca214.js delete mode 100644 assets/js/e18cfb11.c1b055af.js delete mode 100644 assets/js/e273c56f.2ea068a8.js create mode 100644 assets/js/e273c56f.f5a0a811.js delete mode 100644 assets/js/e5aefb32.5951bfd8.js create mode 100644 assets/js/e6e7a2ca.3ced26fd.js delete mode 100644 assets/js/e6e7a2ca.592f45cb.js create mode 100644 assets/js/ec8f9750.7249b2c9.js create mode 100644 assets/js/f2eba590.c1a1ec04.js delete mode 100644 assets/js/f2eba590.e3ea43d6.js delete mode 100644 assets/js/f4f34a3a.41ee1bc9.js create mode 100644 assets/js/f4f34a3a.fe4a86c8.js delete mode 100644 assets/js/f7adb76b.a4e31be2.js create mode 100644 assets/js/f7adb76b.b6121aca.js delete mode 100644 assets/js/f81c1134.c6423362.js delete mode 100644 assets/js/f82cd581.5ed7ba64.js delete mode 100644 assets/js/f898e4d1.19bbffaa.js create mode 100644 assets/js/f898e4d1.9f6c5925.js create mode 100644 assets/js/main.5a2fcde4.js rename assets/js/{main.f17cfb1f.js.LICENSE.txt => main.5a2fcde4.js.LICENSE.txt} (100%) delete mode 100644 assets/js/main.f17cfb1f.js create mode 100644 assets/js/runtime~main.5adfe12d.js delete mode 100644 assets/js/runtime~main.ef8da056.js diff --git a/404.html b/404.html index 30545cf7..f0a5559b 100644 --- a/404.html +++ b/404.html @@ -3,12 +3,12 @@ -Page Not Found | Catena-X - Library - - - +Page Not Found | Catena-X - Library + + + -
Skip to main content

Page Not Found

We could not find what you were looking for.

Please contact the owner of the site that linked you to the original URL and let them know their link is broken.

+
Skip to main content

Page Not Found

We could not find what you were looking for.

Please contact the owner of the site that linked you to the original URL and let them know their link is broken.

\ No newline at end of file diff --git a/assets/js/0058b4c6.60f0e41c.js b/assets/js/0058b4c6.60f0e41c.js deleted file mode 100644 index 7d2c1e2b..00000000 --- a/assets/js/0058b4c6.60f0e41c.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[849],{6164:e=>{e.exports=JSON.parse('{"version":{"pluginId":"default","version":"24.03","label":"24.03","banner":null,"badge":true,"noIndex":false,"className":"docs-version-24.03","isLast":true,"docsSidebars":{"sidebar_standards":[{"type":"link","label":"Overview Standards","href":"/docs/standards/overview","docId":"standards/overview","unlisted":false}],"sidebar_op_model":[{"type":"link","label":"Operating Model","href":"/docs/operating-model/operating-model/","docId":"operating-model/operating-model/operating-model","unlisted":false},{"type":"link","label":"Who: Roles in the Catena-X ecosystem","href":"/docs/operating-model/why-introduction/","docId":"operating-model/why-introduction/why-introduction","unlisted":false},{"type":"link","label":"Why: Understanding the Catena-X Data Space","href":"/docs/operating-model/why-understanding-the-catena-x-data-space/","docId":"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space","unlisted":false},{"type":"link","label":"Who: Roles in the Catena-X ecosystem","href":"/docs/operating-model/who-roles-in-the-catena-x-ecosystem/","docId":"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem","unlisted":false},{"type":"link","label":"What: Service Map","href":"/docs/operating-model/what-service-map/","docId":"operating-model/what-service-map/what-service-map","unlisted":false},{"type":"link","label":"How: Data Space Operations","href":"/docs/operating-model/how-data-space-operations/","docId":"operating-model/how-data-space-operations/how-data-space-operations","unlisted":false},{"type":"link","label":"How: Data Space Governance","href":"/docs/operating-model/how-data-space-governance/","docId":"operating-model/how-data-space-governance/how-data-space-governance","unlisted":false},{"type":"link","label":"How: Life Cycle Management","href":"/docs/operating-model/how-life-cycle-management/","docId":"operating-model/how-life-cycle-management/how-life-cycle-management","unlisted":false},{"type":"link","label":"Outlook","href":"/docs/operating-model/outlook/","docId":"operating-model/outlook/outlook","unlisted":false},{"type":"link","label":"Glossary","href":"/docs/operating-model/glossary/","docId":"operating-model/glossary/glossary","unlisted":false},{"type":"link","label":"Appendix","href":"/docs/operating-model/appendix/","docId":"operating-model/appendix/appendix","unlisted":false},{"type":"link","label":"Change Log","href":"/docs/operating-model/change-log/","docId":"operating-model/change-log/change-log","unlisted":false}],"sidebar_working_model":[{"type":"link","label":"Overview Working Model","href":"/docs/working-model/overview","docId":"working-model/overview","unlisted":false}]},"docs":{"operating-model/appendix/appendix":{"id":"operating-model/appendix/appendix","title":"Appendix","description":"Role Relationships","sidebar":"sidebar_op_model"},"operating-model/change-log/change-log":{"id":"operating-model/change-log/change-log","title":"Change Log","description":"Added","sidebar":"sidebar_op_model"},"operating-model/glossary/glossary":{"id":"operating-model/glossary/glossary","title":"Glossary","description":"| Abbreviation | Full form |","sidebar":"sidebar_op_model"},"operating-model/how-data-space-governance/how-data-space-governance":{"id":"operating-model/how-data-space-governance/how-data-space-governance","title":"How: Data Space Governance","description":"Standardization","sidebar":"sidebar_op_model"},"operating-model/how-data-space-operations/how-data-space-operations":{"id":"operating-model/how-data-space-operations/how-data-space-operations","title":"How: Data Space Operations","description":"This chapter outlines the overarching processes and premises to onboard and exchange","sidebar":"sidebar_op_model"},"operating-model/how-life-cycle-management/how-life-cycle-management":{"id":"operating-model/how-life-cycle-management/how-life-cycle-management","title":"How: Life Cycle Management","description":"Managing versions and changes of different artifacts in federated data spaces is critical to ensure compatibility, interoperability, and security. The life cycle management of the Catena-X ecosystem is coordinated by the Catena-X Association and includes the releases in the Catena-X Association and in the Eclipse Tractus-X Project (see Figure Overview Life Cycle Management). It is planned to provide quarterly releases including one major and three minor releases per year. Both releases follow calendar versioning (see CalVer), whereas their artifacts such as standards, normative documents, products, and KITs follow semantic versioning (see SemVer). To ensure backward compatibility in the future (see Chapter Backward Compatibility), versioning and passing of predefined test cases of each individual artifact is mandatory.","sidebar":"sidebar_op_model"},"operating-model/operating-model/operating-model":{"id":"operating-model/operating-model/operating-model","title":"Catena-X Operating Model","description":"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.","sidebar":"sidebar_op_model"},"operating-model/outlook/outlook":{"id":"operating-model/outlook/outlook","title":"Outlook","description":"The Catena-X Operating Model is a normative document within the regulatory framework, which is binding for all participants in the Catena-X data space. It describes the status of our data space artifacts, including roles, services, and processes along with their respective roadmaps. As Catena-X is an ongoing journey, all of these artifacts will continuously evolve to promote broader adoption and scalability, ensuring maximum interoperability, and (data) sovereignty.","sidebar":"sidebar_op_model"},"operating-model/what-service-map/what-service-map":{"id":"operating-model/what-service-map/what-service-map","title":"What: Service Map","description":"The architecture of the Catena-X Operating System (cxOS) is derived from the reference","sidebar":"sidebar_op_model"},"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem":{"id":"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem","title":"Who: Roles in the Catena-X ecosystem","description":"The Catena-X ecosystem operates on the principle of multiple distinct roles, designed to create an appealing and functional data space (see Figure Role Overview and Relationships). Participants can take on one or more roles in any combination, and multiple participants can fulfill the same role except for the CSP-B role. The CSP-B role can only exist once in the data space due to complexity and technical reasons. Provider roles receive a label through a certification or qualification process to demonstrate that they are trusted partners (see Chapter How: Life Cycle Management).","sidebar":"sidebar_op_model"},"operating-model/why-introduction/why-introduction":{"id":"operating-model/why-introduction/why-introduction","title":"Why: Introduction","description":"Relevance","sidebar":"sidebar_op_model"},"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space":{"id":"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space","title":"Why: Understanding the Catena-X Data Space","description":"Conceptual Foundations of the Catena-X Data Ecosystem","sidebar":"sidebar_op_model"},"standards/overview":{"id":"standards/overview","title":"Overview Standards","description":"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.","sidebar":"sidebar_standards"},"working-model/overview":{"id":"working-model/overview","title":"Overview Working Model","description":"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.","sidebar":"sidebar_working_model"}}}}')}}]); \ No newline at end of file diff --git a/assets/js/0645984d.49a414ef.js b/assets/js/0645984d.49a414ef.js deleted file mode 100644 index a3f8d609..00000000 --- a/assets/js/0645984d.49a414ef.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3923],{9459:(e,t,s)=>{s.r(t),s.d(t,{assets:()=>d,contentTitle:()=>r,default:()=>l,frontMatter:()=>a,metadata:()=>o,toc:()=>c});var n=s(4848),i=s(8453);const a={sidebar_position:1},r="Appendix",o={id:"operating-model/appendix/appendix",title:"Appendix",description:"Role Relationships",source:"@site/versioned_docs/version-24.03/operating-model/appendix/appendix.md",sourceDirName:"operating-model/appendix",slug:"/operating-model/appendix/",permalink:"/docs/operating-model/appendix/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Glossary",permalink:"/docs/operating-model/glossary/"},next:{title:"Change Log",permalink:"/docs/operating-model/change-log/"}},d={},c=[{value:"Role Relationships",id:"role-relationships",level:2},{value:"Data Exchange based on SSI - Next Steps",id:"data-exchange-based-on-ssi---next-steps",level:2}];function h(e){const t={em:"em",h1:"h1",h2:"h2",img:"img",p:"p",strong:"strong",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",...(0,i.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(t.h1,{id:"appendix",children:"Appendix"}),"\n",(0,n.jsx)(t.h2,{id:"role-relationships",children:"Role Relationships"}),"\n",(0,n.jsx)(t.p,{children:"Overview of mandatory (M) and optional (O) relationships between roles (release 23.09)"}),"\n",(0,n.jsxs)(t.p,{children:[(0,n.jsx)(t.img,{alt:"Role Relationships",src:s(4127).A+"",width:"1066",height:"557"}),"\n",(0,n.jsx)(t.em,{children:"Role Relationships"})]}),"\n",(0,n.jsx)(t.p,{children:"Overview of mandatory and optional relationships between roles."}),"\n",(0,n.jsxs)(t.table,{children:[(0,n.jsx)(t.thead,{children:(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.th,{children:"Relationship"}),(0,n.jsx)(t.th,{children:"Description"})]})}),(0,n.jsxs)(t.tbody,{children:[(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"IAM-Sync"}),(0,n.jsx)(t.td,{children:"The IdP is a service responsible for storing and verifying user identities. Its objective is to enable user access to all IAMs of Catena-X operators as soon as they onboard themselves and receive a user in an IAM. Achieving this requires synchronization of each IAM with every other one, a process known as Identity-Sync, which involves both regular users and technical clients."})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Integration"}),(0,n.jsx)(t.td,{children:"Technical integration is required to use Core Services Section B of the CSP-B. The other parties must have access to the services to be able to offer their services. The technical integration refers to an API. This includes documentation, access data, definition of commercial aspects and SLAs. To fully utilize Core Services B of the CSP-B, it is required to perform technical integration with the related APIs. This integration is necessary for enabling other data space participants to access the services to provide their own services. This also includes to provide documentation, access credentials, and define commercial aspects and SLAs for other related services to ensure smooth functionality."})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Onboarding"}),(0,n.jsx)(t.td,{children:"The onboarding enables either existing customers in other networks or interested parties to access the Catena-X data space (Trusted Access Point). This is the technical connection and registration of the participants. With the successful completion of the onboarding, the participant is part of Catena-X and can use the network."})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Certification"}),(0,n.jsx)(t.td,{children:"When certified by a CAB, the party is audited against the Catena-X standards. These independent third parties ensure security and in-teroperability."})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Nomination"}),(0,n.jsx)(t.td,{children:"The nomination process is designed to ensure neutrality and trustworthy execution of selected roles and tasks within the Catena-X ecosystem. The various rights and obligations of the operator are described in the Request for Tender (RFT)."})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Qualification"}),(0,n.jsx)(t.td,{children:"With the qualification, the Catena-X Association ensures that there is a uniform level of quality and service of the various providers. This creates security and trust for the users of the services."})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Trademark Rights"}),(0,n.jsx)(t.td,{children:"With the different qualifications and certifications, the respective parties receive different Catena-X labels. With these they can identify themselves and use them for illustration. The Catena-X Association holds the trademark rights to the labels and Catena-X itself"})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Use"}),(0,n.jsx)(t.td,{children:"Within Catena-X, a participant can use different offers from service providers (AP, ESP, BAP). These are certified applications. Alternatively, they can certify and operate them by themselves, but then it would not use services. The offers can be SaaS solutions or local deployments."})]})]})]}),"\n",(0,n.jsx)(t.h2,{id:"data-exchange-based-on-ssi---next-steps",children:"Data Exchange based on SSI - Next Steps"}),"\n",(0,n.jsxs)(t.p,{children:[(0,n.jsx)(t.strong,{children:"Catena-X Policies as part of the Data Exchange"}),"\n(please note the image below covers own as well as managed Wallet solutions; the credential request flow is not displayed since no changes are planned so far)"]}),"\n",(0,n.jsxs)(t.p,{children:[(0,n.jsx)(t.img,{alt:"Further development of the data exchange based on SSI",src:s(2952).A+"",width:"1106",height:"783"}),"\n",(0,n.jsx)(t.em,{children:"Further development of the data exchange based on SSI"})]})]})}function l(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,n.jsx)(t,{...e,children:(0,n.jsx)(h,{...e})}):h(e)}},2952:(e,t,s)=>{s.d(t,{A:()=>n});const n=s.p+"assets/images/further-development-of-the-data-exchange-based-on-ssi-f3a136e74f3c302de5fdf45d0886bcff.png"},4127:(e,t,s)=>{s.d(t,{A:()=>n});const n=s.p+"assets/images/role-relationships-c41cada71489356c6d8b5389b8307a54.png"},8453:(e,t,s)=>{s.d(t,{R:()=>r,x:()=>o});var n=s(6540);const i={},a=n.createContext(i);function r(e){const t=n.useContext(a);return n.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function o(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:r(e.components),n.createElement(a.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/0645984d.a8f4276b.js b/assets/js/0645984d.a8f4276b.js new file mode 100644 index 00000000..79619f92 --- /dev/null +++ b/assets/js/0645984d.a8f4276b.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3923],{9459:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>d,contentTitle:()=>r,default:()=>l,frontMatter:()=>a,metadata:()=>o,toc:()=>c});var s=n(4848),i=n(8453);const a={sidebar_position:1},r="Appendix",o={id:"operating-model/appendix/appendix",title:"Appendix",description:"Role Relationships",source:"@site/versioned_docs/version-24.03/operating-model/appendix/appendix.md",sourceDirName:"operating-model/appendix",slug:"/operating-model/appendix/",permalink:"/catenax-ev.github.io.new/docs/operating-model/appendix/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Glossary",permalink:"/catenax-ev.github.io.new/docs/operating-model/glossary/"},next:{title:"Change Log",permalink:"/catenax-ev.github.io.new/docs/operating-model/change-log/"}},d={},c=[{value:"Role Relationships",id:"role-relationships",level:2},{value:"Data Exchange based on SSI - Next Steps",id:"data-exchange-based-on-ssi---next-steps",level:2}];function h(e){const t={em:"em",h1:"h1",h2:"h2",img:"img",p:"p",strong:"strong",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",...(0,i.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsx)(t.h1,{id:"appendix",children:"Appendix"}),"\n",(0,s.jsx)(t.h2,{id:"role-relationships",children:"Role Relationships"}),"\n",(0,s.jsx)(t.p,{children:"Overview of mandatory (M) and optional (O) relationships between roles (release 23.09)"}),"\n",(0,s.jsxs)(t.p,{children:[(0,s.jsx)(t.img,{alt:"Role Relationships",src:n(4127).A+"",width:"1066",height:"557"}),"\n",(0,s.jsx)(t.em,{children:"Role Relationships"})]}),"\n",(0,s.jsx)(t.p,{children:"Overview of mandatory and optional relationships between roles."}),"\n",(0,s.jsxs)(t.table,{children:[(0,s.jsx)(t.thead,{children:(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.th,{children:"Relationship"}),(0,s.jsx)(t.th,{children:"Description"})]})}),(0,s.jsxs)(t.tbody,{children:[(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"IAM-Sync"}),(0,s.jsx)(t.td,{children:"The IdP is a service responsible for storing and verifying user identities. Its objective is to enable user access to all IAMs of Catena-X operators as soon as they onboard themselves and receive a user in an IAM. Achieving this requires synchronization of each IAM with every other one, a process known as Identity-Sync, which involves both regular users and technical clients."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Integration"}),(0,s.jsx)(t.td,{children:"Technical integration is required to use Core Services Section B of the CSP-B. The other parties must have access to the services to be able to offer their services. The technical integration refers to an API. This includes documentation, access data, definition of commercial aspects and SLAs. To fully utilize Core Services B of the CSP-B, it is required to perform technical integration with the related APIs. This integration is necessary for enabling other data space participants to access the services to provide their own services. This also includes to provide documentation, access credentials, and define commercial aspects and SLAs for other related services to ensure smooth functionality."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Onboarding"}),(0,s.jsx)(t.td,{children:"The onboarding enables either existing customers in other networks or interested parties to access the Catena-X data space (Trusted Access Point). This is the technical connection and registration of the participants. With the successful completion of the onboarding, the participant is part of Catena-X and can use the network."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Certification"}),(0,s.jsx)(t.td,{children:"When certified by a CAB, the party is audited against the Catena-X standards. These independent third parties ensure security and in-teroperability."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Nomination"}),(0,s.jsx)(t.td,{children:"The nomination process is designed to ensure neutrality and trustworthy execution of selected roles and tasks within the Catena-X ecosystem. The various rights and obligations of the operator are described in the Request for Tender (RFT)."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Qualification"}),(0,s.jsx)(t.td,{children:"With the qualification, the Catena-X Association ensures that there is a uniform level of quality and service of the various providers. This creates security and trust for the users of the services."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Trademark Rights"}),(0,s.jsx)(t.td,{children:"With the different qualifications and certifications, the respective parties receive different Catena-X labels. With these they can identify themselves and use them for illustration. The Catena-X Association holds the trademark rights to the labels and Catena-X itself"})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Use"}),(0,s.jsx)(t.td,{children:"Within Catena-X, a participant can use different offers from service providers (AP, ESP, BAP). These are certified applications. Alternatively, they can certify and operate them by themselves, but then it would not use services. The offers can be SaaS solutions or local deployments."})]})]})]}),"\n",(0,s.jsx)(t.h2,{id:"data-exchange-based-on-ssi---next-steps",children:"Data Exchange based on SSI - Next Steps"}),"\n",(0,s.jsxs)(t.p,{children:[(0,s.jsx)(t.strong,{children:"Catena-X Policies as part of the Data Exchange"}),"\n(please note the image below covers own as well as managed Wallet solutions; the credential request flow is not displayed since no changes are planned so far)"]}),"\n",(0,s.jsxs)(t.p,{children:[(0,s.jsx)(t.img,{alt:"Further development of the data exchange based on SSI",src:n(2952).A+"",width:"1106",height:"783"}),"\n",(0,s.jsx)(t.em,{children:"Further development of the data exchange based on SSI"})]})]})}function l(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,s.jsx)(t,{...e,children:(0,s.jsx)(h,{...e})}):h(e)}},2952:(e,t,n)=>{n.d(t,{A:()=>s});const s=n.p+"assets/images/further-development-of-the-data-exchange-based-on-ssi-f3a136e74f3c302de5fdf45d0886bcff.png"},4127:(e,t,n)=>{n.d(t,{A:()=>s});const s=n.p+"assets/images/role-relationships-c41cada71489356c6d8b5389b8307a54.png"},8453:(e,t,n)=>{n.d(t,{R:()=>r,x:()=>o});var s=n(6540);const i={},a=s.createContext(i);function r(e){const t=s.useContext(a);return s.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function o(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:r(e.components),s.createElement(a.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/098dc4e6.10dd02c5.js b/assets/js/098dc4e6.10dd02c5.js deleted file mode 100644 index 323eb725..00000000 --- a/assets/js/098dc4e6.10dd02c5.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3026],{3488:(e,a,t)=>{t.r(a),t.d(a,{assets:()=>c,contentTitle:()=>o,default:()=>h,frontMatter:()=>s,metadata:()=>r,toc:()=>d});var n=t(4848),i=t(8453);const s={sidebar_position:1},o="What: Service Map",r={id:"operating-model/what-service-map/what-service-map",title:"What: Service Map",description:"The architecture of the Catena-X Operating System (cxOS) is derived from the reference",source:"@site/versioned_docs/version-24.03/operating-model/what-service-map/what-service-map.md",sourceDirName:"operating-model/what-service-map",slug:"/operating-model/what-service-map/",permalink:"/docs/operating-model/what-service-map/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/docs/operating-model/who-roles-in-the-catena-x-ecosystem/"},next:{title:"How: Data Space Operations",permalink:"/docs/operating-model/how-data-space-operations/"}},c={},d=[{value:"Enablement Services",id:"enablement-services",level:2},{value:"Core Services",id:"core-services",level:2},{value:"Onboarding Services",id:"onboarding-services",level:2},{value:"Use Cases",id:"use-cases",level:2},{value:"KITs \u2013 Keep It Together",id:"kits--keep-it-together",level:3},{value:"New Use Cases and Direct Collaboration",id:"new-use-cases-and-direct-collaboration",level:3},{value:"Initiate new use case",id:"initiate-new-use-case",level:4},{value:"Direct collaboration (no multi-tier approach)",id:"direct-collaboration-no-multi-tier-approach",level:4}];function l(e){const a={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",h4:"h4",img:"img",p:"p",strong:"strong",...(0,i.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(a.h1,{id:"what-service-map",children:"What: Service Map"}),"\n",(0,n.jsxs)(a.p,{children:["The architecture of the Catena-X Operating System (cxOS) is derived from the reference\narchitectures of Industrial Data Space Association (IDSA) and Gaia-X. The cxOS consists of\nthree areas: Core, Onboarding, and Enablement Services shown in Figure ",(0,n.jsx)(a.a,{href:"/docs/operating-model/what-service-map/",children:"Service Map"}),"."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"Service Map (Deployment View)",src:t(245).A+"",width:"1641",height:"782"}),"\n",(0,n.jsx)(a.em,{children:"Service Map (Deployment View)"})]}),"\n",(0,n.jsx)(a.p,{children:"The cxOS is the technical foundation enabling business use cases to operate in a network-enabled manner across company boundaries. The operating system offers various capabilities:"}),"\n",(0,n.jsx)(a.h2,{id:"enablement-services",children:"Enablement Services"}),"\n",(0,n.jsx)(a.p,{children:"The Enablement Services are a bundle of decentral services that enable participation in the Catena-X data space. Each participant must deploy and use the enablement services to connect to the data space and enable standardized interactions based on the requirements of the respective use case. They ensure the strategic value proposition of technical/semantic interoperability and (data) sovereignty."}),"\n",(0,n.jsx)(a.p,{children:"The connector (e.g., EDC) based on the data space protocol and the identity wallet form the mandatory basis of enablement services enabling standardized technical connectivity and sovereign data exchange. All participants can use them to establish a basic connection to the data space, independent of the business use case."}),"\n",(0,n.jsx)(a.p,{children:"In addition to generic data-exchange capabilities, enabling services include context-specific service offerings. Examples are the Asset Administration Shell (AAS) as harmonized access layer for digital twins, the Decentral Digital Twin Registry (DDTR) for local discoverability of digital twins in decentral organized data spaces or the Item Relationship Service (IRS) for building data chains and iterating through a tree structure of digital twins."}),"\n",(0,n.jsxs)(a.p,{children:["Please note that there are various options for running enablement services, ranging from leveraging software-asa-service solutions to local deployments of open-source reference implementations. Further information on deployment and usage premises can be found in Chapter ",(0,n.jsx)(a.a,{href:"/docs/operating-model/how-data-space-operations/#edc-deployment-and-usage-premises",children:"EDC Deployment and Usage Premises"}),"."]}),"\n",(0,n.jsx)(a.h2,{id:"core-services",children:"Core Services"}),"\n",(0,n.jsx)(a.p,{children:"In contrast to Enablement Services, Core Services are provided and operated by Core Service providers A/B. Core services provide common accessibility and discoverability functionalities for data space participants. Examples include BPN issuer for maintaining business partner numbers, and participant information, IAM solutions for identity and access management, and discovery services to localize the address of assets in decentral organized registries across the data space. The Core Services can be divided into two areas:"}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"Core Services A"})," lists Core Services that can be operated \u201cn\u201d times in the Catena-X data space."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"Core Services B"})," lists Core Services that can only be operated once in the Catena-X data space due to business reasons or technical limitations and are therefore tendered via the nomination process of the Association."]}),"\n",(0,n.jsx)(a.p,{children:"Some of the Core Services, such as the Managed Identity Wallet, are by nature Enablement Services, but because of technical reasons they are considered Core Services B as an interim solution."}),"\n",(0,n.jsx)(a.h2,{id:"onboarding-services",children:"Onboarding Services"}),"\n",(0,n.jsxs)(a.p,{children:["The Onboarding Services are provided and operated by OSPs. Onboarding Services enable participants to onboard into the Catena-X data space. As shown in Chapter ",(0,n.jsx)(a.a,{href:"/docs/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),", the scope of Onboarding Services will change over time. The Onboarding Services can be divided into two areas:"]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"Onboarding Services"})," list the services that ensure a standardized and compliant Catena-X onboarding process (e.g., registration process)."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"External Onboarding Services"})," list the services that OSPs must integrate and use to implement a trusted onboarding process but are developed and operated by an external initiative or provider."]}),"\n",(0,n.jsx)(a.h2,{id:"use-cases",children:"Use Cases"}),"\n",(0,n.jsx)(a.p,{children:"The goal of a Catena-X use case is to solve a specific business problem and to create value for data providers and consumers. To do this, the Catena-X Association demands and promotes that use cases create Standards and KITs to enable a multi-vendor ecosystem of interoperable and compatible business applications (see: business application). Achieving network effects in the Catena-X ecosystem is critical to success and depends on the active participation of users and the creation of appealing business apps, especially for SMEs"}),"\n",(0,n.jsx)(a.h3,{id:"kits--keep-it-together",children:"KITs \u2013 Keep It Together"}),"\n",(0,n.jsxs)(a.p,{children:["KIT, short for Keep It Together, bundles all necessary resources and technical documentation designed to adopt a Catena-X use case for all data space participants (see Figure ",(0,n.jsx)(a.a,{href:"/docs/operating-model/what-service-map/#kits--keep-it-together",children:"KITs Toolbox"}),")."]}),"\n",(0,n.jsxs)(a.p,{children:["A KIT is always structured in the same way and supports the individual journey of a company joining the Catena-X data space. To ensure interoperability and data sovereignty in Catena-X use cases, adherence to a minimum set of elements is required, including semantic models for data integration and understanding, logic and schemas for value calculation, API implementation for technical communication, and access and usage policies to maintain data sovereignty. A KIT consists of various other artifacts in addition to the minimum set. A comprehensive overview of the artefacts can be found on the ",(0,n.jsx)(a.a,{href:"https://eclipse-tractusx.github.io/",children:"Tractus-X project website"}),"."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"KITs Toolbox",src:t(3410).A+"",width:"1361",height:"746"}),"\n",(0,n.jsx)(a.em,{children:"KITs Toolbox"})]}),"\n",(0,n.jsx)(a.p,{children:"DPCs that are part of the automotive value chain and strive to participate in a Catena-X use case require technical support, specifications, and tutorials. For instance, a production company may need to exchange product carbon footprint data with its partners. KITs consolidate the necessary software components, standards, access and usage policies, and code examples, ensuring these companies have everything required to successfully participate in a Catena-X use case."}),"\n",(0,n.jsx)(a.p,{children:"BAPs interested in offering a business application for a specific use case on one of the Catena-X marketplaces. These companies need to align their existing solutions with Catena-X requirements. Within a KIT, they receive guidelines and the technical support necessary for adapting their solutions to meet Catena-X conformity based on our five steps to Catena-X: Inform, connect, boost, adapt, utilize. KITs are the way forward to create a valuable multi-vendor ecosystem to promote seamless interoperability between different commercial solutions."}),"\n",(0,n.jsx)(a.h3,{id:"new-use-cases-and-direct-collaboration",children:"New Use Cases and Direct Collaboration"}),"\n",(0,n.jsx)(a.p,{children:"In addition to the first 10 use cases that have been initially developed in the Catena-X Consortium and are now governed by the Association Committees (e.g., Sustainability Committee), data space participants have the following scenarios for collaboration:"}),"\n",(0,n.jsx)(a.h4,{id:"initiate-new-use-case",children:"Initiate new use case"}),"\n",(0,n.jsx)(a.p,{children:"Any Catena-X Association member can initiate a new use case by creating a working in the Catena-X Association or expand an existing committee (whatever suits the purpose best, the final judgement is made by the Board of the Association). The goal of a committee or working group is to discuss and define a common vision, roadmap, standards, KITs, and other open-source artefacts for the use cases with focus on interoperability and data sovereignty to create multi-tier value chains for a dedicated business process."}),"\n",(0,n.jsx)(a.p,{children:"To validate the value proposition or technical specifications, a new use case can be tested in future either in a sandbox environment of the CSP-B or in the test environments of the Catena-X Association. Note that new uses cases without standards provide only limited interoperability, require individual use case policies, and cannot be certified and thus not be listed on one of the marketplaces and are therefore not supported and trusted."}),"\n",(0,n.jsx)(a.h4,{id:"direct-collaboration-no-multi-tier-approach",children:"Direct collaboration (no multi-tier approach)"}),"\n",(0,n.jsx)(a.p,{children:"The Catena-X data space also enables secure and sovereign data exchange for direct collaboration between data provider and consumer. In this scenario, the data provider and consumer are responsible for defining a bilateral semantic model, as well as appropriate usage and access policies. Alternatively, they can make use of existing usage and access policy that meets their needs. The goal of the Catena-X data space remains to always create interoperable use cases with consistent data chains. Note that direct collaboration without standards provides only limited interoperability and cannot be certified and thus not be listed on one of the marketplaces."})]})}function h(e={}){const{wrapper:a}={...(0,i.R)(),...e.components};return a?(0,n.jsx)(a,{...e,children:(0,n.jsx)(l,{...e})}):l(e)}},3410:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/kits-toolbox-6f9dbad8dd052a62be01b7abcf6ab8c7.png"},245:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/service-map-deployment-view-14a4dacf11a39f970f8d669aa3cc4af1.png"},8453:(e,a,t)=>{t.d(a,{R:()=>o,x:()=>r});var n=t(6540);const i={},s=n.createContext(i);function o(e){const a=n.useContext(s);return n.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function r(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:o(e.components),n.createElement(s.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/098dc4e6.e895a85a.js b/assets/js/098dc4e6.e895a85a.js new file mode 100644 index 00000000..36c60cbf --- /dev/null +++ b/assets/js/098dc4e6.e895a85a.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3026],{3488:(e,a,t)=>{t.r(a),t.d(a,{assets:()=>c,contentTitle:()=>o,default:()=>h,frontMatter:()=>s,metadata:()=>r,toc:()=>d});var n=t(4848),i=t(8453);const s={sidebar_position:1},o="What: Service Map",r={id:"operating-model/what-service-map/what-service-map",title:"What: Service Map",description:"The architecture of the Catena-X Operating System (cxOS) is derived from the reference",source:"@site/versioned_docs/version-24.03/operating-model/what-service-map/what-service-map.md",sourceDirName:"operating-model/what-service-map",slug:"/operating-model/what-service-map/",permalink:"/catenax-ev.github.io.new/docs/operating-model/what-service-map/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/catenax-ev.github.io.new/docs/operating-model/who-roles-in-the-catena-x-ecosystem/"},next:{title:"How: Data Space Operations",permalink:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-operations/"}},c={},d=[{value:"Enablement Services",id:"enablement-services",level:2},{value:"Core Services",id:"core-services",level:2},{value:"Onboarding Services",id:"onboarding-services",level:2},{value:"Use Cases",id:"use-cases",level:2},{value:"KITs \u2013 Keep It Together",id:"kits--keep-it-together",level:3},{value:"New Use Cases and Direct Collaboration",id:"new-use-cases-and-direct-collaboration",level:3},{value:"Initiate new use case",id:"initiate-new-use-case",level:4},{value:"Direct collaboration (no multi-tier approach)",id:"direct-collaboration-no-multi-tier-approach",level:4}];function l(e){const a={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",h4:"h4",img:"img",p:"p",strong:"strong",...(0,i.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(a.h1,{id:"what-service-map",children:"What: Service Map"}),"\n",(0,n.jsxs)(a.p,{children:["The architecture of the Catena-X Operating System (cxOS) is derived from the reference\narchitectures of Industrial Data Space Association (IDSA) and Gaia-X. The cxOS consists of\nthree areas: Core, Onboarding, and Enablement Services shown in Figure ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/what-service-map/",children:"Service Map"}),"."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"Service Map (Deployment View)",src:t(245).A+"",width:"1641",height:"782"}),"\n",(0,n.jsx)(a.em,{children:"Service Map (Deployment View)"})]}),"\n",(0,n.jsx)(a.p,{children:"The cxOS is the technical foundation enabling business use cases to operate in a network-enabled manner across company boundaries. The operating system offers various capabilities:"}),"\n",(0,n.jsx)(a.h2,{id:"enablement-services",children:"Enablement Services"}),"\n",(0,n.jsx)(a.p,{children:"The Enablement Services are a bundle of decentral services that enable participation in the Catena-X data space. Each participant must deploy and use the enablement services to connect to the data space and enable standardized interactions based on the requirements of the respective use case. They ensure the strategic value proposition of technical/semantic interoperability and (data) sovereignty."}),"\n",(0,n.jsx)(a.p,{children:"The connector (e.g., EDC) based on the data space protocol and the identity wallet form the mandatory basis of enablement services enabling standardized technical connectivity and sovereign data exchange. All participants can use them to establish a basic connection to the data space, independent of the business use case."}),"\n",(0,n.jsx)(a.p,{children:"In addition to generic data-exchange capabilities, enabling services include context-specific service offerings. Examples are the Asset Administration Shell (AAS) as harmonized access layer for digital twins, the Decentral Digital Twin Registry (DDTR) for local discoverability of digital twins in decentral organized data spaces or the Item Relationship Service (IRS) for building data chains and iterating through a tree structure of digital twins."}),"\n",(0,n.jsxs)(a.p,{children:["Please note that there are various options for running enablement services, ranging from leveraging software-asa-service solutions to local deployments of open-source reference implementations. Further information on deployment and usage premises can be found in Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-operations/#edc-deployment-and-usage-premises",children:"EDC Deployment and Usage Premises"}),"."]}),"\n",(0,n.jsx)(a.h2,{id:"core-services",children:"Core Services"}),"\n",(0,n.jsx)(a.p,{children:"In contrast to Enablement Services, Core Services are provided and operated by Core Service providers A/B. Core services provide common accessibility and discoverability functionalities for data space participants. Examples include BPN issuer for maintaining business partner numbers, and participant information, IAM solutions for identity and access management, and discovery services to localize the address of assets in decentral organized registries across the data space. The Core Services can be divided into two areas:"}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"Core Services A"})," lists Core Services that can be operated \u201cn\u201d times in the Catena-X data space."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"Core Services B"})," lists Core Services that can only be operated once in the Catena-X data space due to business reasons or technical limitations and are therefore tendered via the nomination process of the Association."]}),"\n",(0,n.jsx)(a.p,{children:"Some of the Core Services, such as the Managed Identity Wallet, are by nature Enablement Services, but because of technical reasons they are considered Core Services B as an interim solution."}),"\n",(0,n.jsx)(a.h2,{id:"onboarding-services",children:"Onboarding Services"}),"\n",(0,n.jsxs)(a.p,{children:["The Onboarding Services are provided and operated by OSPs. Onboarding Services enable participants to onboard into the Catena-X data space. As shown in Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),", the scope of Onboarding Services will change over time. The Onboarding Services can be divided into two areas:"]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"Onboarding Services"})," list the services that ensure a standardized and compliant Catena-X onboarding process (e.g., registration process)."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"External Onboarding Services"})," list the services that OSPs must integrate and use to implement a trusted onboarding process but are developed and operated by an external initiative or provider."]}),"\n",(0,n.jsx)(a.h2,{id:"use-cases",children:"Use Cases"}),"\n",(0,n.jsx)(a.p,{children:"The goal of a Catena-X use case is to solve a specific business problem and to create value for data providers and consumers. To do this, the Catena-X Association demands and promotes that use cases create Standards and KITs to enable a multi-vendor ecosystem of interoperable and compatible business applications (see: business application). Achieving network effects in the Catena-X ecosystem is critical to success and depends on the active participation of users and the creation of appealing business apps, especially for SMEs"}),"\n",(0,n.jsx)(a.h3,{id:"kits--keep-it-together",children:"KITs \u2013 Keep It Together"}),"\n",(0,n.jsxs)(a.p,{children:["KIT, short for Keep It Together, bundles all necessary resources and technical documentation designed to adopt a Catena-X use case for all data space participants (see Figure ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/what-service-map/#kits--keep-it-together",children:"KITs Toolbox"}),")."]}),"\n",(0,n.jsxs)(a.p,{children:["A KIT is always structured in the same way and supports the individual journey of a company joining the Catena-X data space. To ensure interoperability and data sovereignty in Catena-X use cases, adherence to a minimum set of elements is required, including semantic models for data integration and understanding, logic and schemas for value calculation, API implementation for technical communication, and access and usage policies to maintain data sovereignty. A KIT consists of various other artifacts in addition to the minimum set. A comprehensive overview of the artefacts can be found on the ",(0,n.jsx)(a.a,{href:"https://eclipse-tractusx.github.io/",children:"Tractus-X project website"}),"."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"KITs Toolbox",src:t(3410).A+"",width:"1361",height:"746"}),"\n",(0,n.jsx)(a.em,{children:"KITs Toolbox"})]}),"\n",(0,n.jsx)(a.p,{children:"DPCs that are part of the automotive value chain and strive to participate in a Catena-X use case require technical support, specifications, and tutorials. For instance, a production company may need to exchange product carbon footprint data with its partners. KITs consolidate the necessary software components, standards, access and usage policies, and code examples, ensuring these companies have everything required to successfully participate in a Catena-X use case."}),"\n",(0,n.jsx)(a.p,{children:"BAPs interested in offering a business application for a specific use case on one of the Catena-X marketplaces. These companies need to align their existing solutions with Catena-X requirements. Within a KIT, they receive guidelines and the technical support necessary for adapting their solutions to meet Catena-X conformity based on our five steps to Catena-X: Inform, connect, boost, adapt, utilize. KITs are the way forward to create a valuable multi-vendor ecosystem to promote seamless interoperability between different commercial solutions."}),"\n",(0,n.jsx)(a.h3,{id:"new-use-cases-and-direct-collaboration",children:"New Use Cases and Direct Collaboration"}),"\n",(0,n.jsx)(a.p,{children:"In addition to the first 10 use cases that have been initially developed in the Catena-X Consortium and are now governed by the Association Committees (e.g., Sustainability Committee), data space participants have the following scenarios for collaboration:"}),"\n",(0,n.jsx)(a.h4,{id:"initiate-new-use-case",children:"Initiate new use case"}),"\n",(0,n.jsx)(a.p,{children:"Any Catena-X Association member can initiate a new use case by creating a working in the Catena-X Association or expand an existing committee (whatever suits the purpose best, the final judgement is made by the Board of the Association). The goal of a committee or working group is to discuss and define a common vision, roadmap, standards, KITs, and other open-source artefacts for the use cases with focus on interoperability and data sovereignty to create multi-tier value chains for a dedicated business process."}),"\n",(0,n.jsx)(a.p,{children:"To validate the value proposition or technical specifications, a new use case can be tested in future either in a sandbox environment of the CSP-B or in the test environments of the Catena-X Association. Note that new uses cases without standards provide only limited interoperability, require individual use case policies, and cannot be certified and thus not be listed on one of the marketplaces and are therefore not supported and trusted."}),"\n",(0,n.jsx)(a.h4,{id:"direct-collaboration-no-multi-tier-approach",children:"Direct collaboration (no multi-tier approach)"}),"\n",(0,n.jsx)(a.p,{children:"The Catena-X data space also enables secure and sovereign data exchange for direct collaboration between data provider and consumer. In this scenario, the data provider and consumer are responsible for defining a bilateral semantic model, as well as appropriate usage and access policies. Alternatively, they can make use of existing usage and access policy that meets their needs. The goal of the Catena-X data space remains to always create interoperable use cases with consistent data chains. Note that direct collaboration without standards provides only limited interoperability and cannot be certified and thus not be listed on one of the marketplaces."})]})}function h(e={}){const{wrapper:a}={...(0,i.R)(),...e.components};return a?(0,n.jsx)(a,{...e,children:(0,n.jsx)(l,{...e})}):l(e)}},3410:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/kits-toolbox-6f9dbad8dd052a62be01b7abcf6ab8c7.png"},245:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/service-map-deployment-view-14a4dacf11a39f970f8d669aa3cc4af1.png"},8453:(e,a,t)=>{t.d(a,{R:()=>o,x:()=>r});var n=t(6540);const i={},s=n.createContext(i);function o(e){const a=n.useContext(s);return n.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function r(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:o(e.components),n.createElement(s.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/0d7102ad.3bf1d960.js b/assets/js/0d7102ad.3bf1d960.js new file mode 100644 index 00000000..dbd66a6f --- /dev/null +++ b/assets/js/0d7102ad.3bf1d960.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3738],{5248:e=>{e.exports=JSON.parse('{"version":{"pluginId":"default","version":"current","label":"Next","banner":"unreleased","badge":true,"noIndex":false,"className":"docs-version-current","isLast":false,"docsSidebars":{"sidebar_standards":[{"type":"link","label":"Overview Standards","href":"/catenax-ev.github.io.new/docs/next/standards/overview","docId":"standards/overview","unlisted":false}],"sidebar_op_model":[{"type":"link","label":"Operating Model","href":"/catenax-ev.github.io.new/docs/next/operating-model/operating-model/","docId":"operating-model/operating-model/operating-model","unlisted":false},{"type":"link","label":"Who: Roles in the Catena-X ecosystem","href":"/catenax-ev.github.io.new/docs/next/operating-model/why-introduction/","docId":"operating-model/why-introduction/why-introduction","unlisted":false},{"type":"link","label":"Why: Understanding the Catena-X Data Space","href":"/catenax-ev.github.io.new/docs/next/operating-model/why-understanding-the-catena-x-data-space/","docId":"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space","unlisted":false},{"type":"link","label":"Who: Roles in the Catena-X ecosystem","href":"/catenax-ev.github.io.new/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/","docId":"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem","unlisted":false},{"type":"link","label":"What: Service Map","href":"/catenax-ev.github.io.new/docs/next/operating-model/what-service-map/","docId":"operating-model/what-service-map/what-service-map","unlisted":false},{"type":"link","label":"How: Data Space Operations","href":"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-operations/","docId":"operating-model/how-data-space-operations/how-data-space-operations","unlisted":false},{"type":"link","label":"How: Data Space Governance","href":"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance/","docId":"operating-model/how-data-space-governance/how-data-space-governance","unlisted":false},{"type":"link","label":"How: Life Cycle Management","href":"/catenax-ev.github.io.new/docs/next/operating-model/how-life-cycle-management/","docId":"operating-model/how-life-cycle-management/how-life-cycle-management","unlisted":false},{"type":"link","label":"Outlook","href":"/catenax-ev.github.io.new/docs/next/operating-model/outlook/","docId":"operating-model/outlook/outlook","unlisted":false},{"type":"link","label":"Glossary","href":"/catenax-ev.github.io.new/docs/next/operating-model/glossary/","docId":"operating-model/glossary/glossary","unlisted":false},{"type":"link","label":"Appendix","href":"/catenax-ev.github.io.new/docs/next/operating-model/appendix/","docId":"operating-model/appendix/appendix","unlisted":false},{"type":"link","label":"Change Log","href":"/catenax-ev.github.io.new/docs/next/operating-model/change-log/","docId":"operating-model/change-log/change-log","unlisted":false}],"sidebar_working_model":[{"type":"link","label":"Overview","href":"/catenax-ev.github.io.new/docs/next/working-model/overview","docId":"working-model/overview","unlisted":false},{"type":"link","label":"Catena-X Ecosystem","href":"/catenax-ev.github.io.new/docs/next/working-model/ecosystem/","docId":"working-model/ecosystem/ecosystem","unlisted":false},{"type":"category","label":"Organizational Structure","collapsible":true,"collapsed":true,"items":[{"type":"link","label":"Tooling","href":"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/02-03-tooling","docId":"working-model/organizational-structure/02-03-tooling","unlisted":false},{"type":"category","label":"Overview roles","collapsible":true,"collapsed":true,"items":[{"type":"link","label":"Catena-X association","href":"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles","docId":"working-model/organizational-structure/overview-roles/catena-x-roles","unlisted":false},{"type":"link","label":"Tractus-X","href":"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles","docId":"working-model/organizational-structure/overview-roles/tractus-x-roles","unlisted":false}],"href":"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/"}],"href":"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/"},{"type":"category","label":"Process Structure","collapsible":true,"collapsed":true,"items":[{"type":"link","label":"Process Organization - From Idea to Release","href":"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production","docId":"working-model/process-from-idea-to-production/03-01-process-from-idea-to-production","unlisted":false},{"type":"link","label":"Tractus-X Open Source Project Contribution Guide","href":"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-02-Contribution-Guideline","docId":"working-model/process-from-idea-to-production/03-02-Contribution-Guideline","unlisted":false},{"type":"link","label":"Contribution Levels","href":"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-04-Issue-Process","docId":"working-model/process-from-idea-to-production/03-04-Issue-Process","unlisted":false}]},{"type":"link","label":"Glossary","href":"/catenax-ev.github.io.new/docs/next/working-model/glossary","docId":"working-model/glossary","unlisted":false}]},"docs":{"operating-model/appendix/appendix":{"id":"operating-model/appendix/appendix","title":"Appendix","description":"Role Relationships","sidebar":"sidebar_op_model"},"operating-model/change-log/change-log":{"id":"operating-model/change-log/change-log","title":"Change Log","description":"Added","sidebar":"sidebar_op_model"},"operating-model/glossary/glossary":{"id":"operating-model/glossary/glossary","title":"Glossary","description":"| Abbreviation | Full form |","sidebar":"sidebar_op_model"},"operating-model/how-data-space-governance/how-data-space-governance":{"id":"operating-model/how-data-space-governance/how-data-space-governance","title":"How: Data Space Governance","description":"Standardization","sidebar":"sidebar_op_model"},"operating-model/how-data-space-operations/how-data-space-operations":{"id":"operating-model/how-data-space-operations/how-data-space-operations","title":"How: Data Space Operations","description":"This chapter outlines the overarching processes and premises to onboard and exchange","sidebar":"sidebar_op_model"},"operating-model/how-life-cycle-management/how-life-cycle-management":{"id":"operating-model/how-life-cycle-management/how-life-cycle-management","title":"How: Life Cycle Management","description":"Managing versions and changes of different artifacts in federated data spaces is critical to ensure compatibility, interoperability, and security. The life cycle management of the Catena-X ecosystem is coordinated by the Catena-X Association and includes the releases in the Catena-X Association and in the Eclipse Tractus-X Project (see Figure Overview Life Cycle Management). It is planned to provide quarterly releases including one major and three minor releases per year. Both releases follow calendar versioning (see CalVer), whereas their artifacts such as standards, normative documents, products, and KITs follow semantic versioning (see SemVer). To ensure backward compatibility in the future (see Chapter Backward Compatibility), versioning and passing of predefined test cases of each individual artifact is mandatory.","sidebar":"sidebar_op_model"},"operating-model/operating-model/operating-model":{"id":"operating-model/operating-model/operating-model","title":"Catena-X Operating Model","description":"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.","sidebar":"sidebar_op_model"},"operating-model/outlook/outlook":{"id":"operating-model/outlook/outlook","title":"Outlook","description":"The Catena-X Operating Model is a normative document within the regulatory framework, which is binding for all participants in the Catena-X data space. It describes the status of our data space artifacts, including roles, services, and processes along with their respective roadmaps. As Catena-X is an ongoing journey, all of these artifacts will continuously evolve to promote broader adoption and scalability, ensuring maximum interoperability, and (data) sovereignty.","sidebar":"sidebar_op_model"},"operating-model/what-service-map/what-service-map":{"id":"operating-model/what-service-map/what-service-map","title":"What: Service Map","description":"The architecture of the Catena-X Operating System (cxOS) is derived from the reference","sidebar":"sidebar_op_model"},"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem":{"id":"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem","title":"Who: Roles in the Catena-X ecosystem","description":"The Catena-X ecosystem operates on the principle of multiple distinct roles, designed to create an appealing and functional data space (see Figure Role Overview and Relationships). Participants can take on one or more roles in any combination, and multiple participants can fulfill the same role except for the CSP-B role. The CSP-B role can only exist once in the data space due to complexity and technical reasons. Provider roles receive a label through a certification or qualification process to demonstrate that they are trusted partners (see Chapter How: Life Cycle Management).","sidebar":"sidebar_op_model"},"operating-model/why-introduction/why-introduction":{"id":"operating-model/why-introduction/why-introduction","title":"Why: Introduction","description":"Relevance","sidebar":"sidebar_op_model"},"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space":{"id":"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space","title":"Why: Understanding the Catena-X Data Space","description":"Conceptual Foundations of the Catena-X Data Ecosystem","sidebar":"sidebar_op_model"},"standards/overview":{"id":"standards/overview","title":"Overview Standards","description":"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.","sidebar":"sidebar_standards"},"working-model/ecosystem/ecosystem":{"id":"working-model/ecosystem/ecosystem","title":"Catena-X Ecosystem","description":"The Catena-X ecosystem consists of three areas","sidebar":"sidebar_working_model"},"working-model/glossary":{"id":"working-model/glossary","title":"Glossary","description":"| Abbreviation | Full form |","sidebar":"sidebar_working_model"},"working-model/organizational-structure/02-03-tooling":{"id":"working-model/organizational-structure/02-03-tooling","title":"Tooling","description":"This is just a short description about the different tools. The usage of these tools is described in the coresponding sections.","sidebar":"sidebar_working_model"},"working-model/organizational-structure/organizational-structure":{"id":"working-model/organizational-structure/organizational-structure","title":"Catena-X Organizational Structure","description":"Catena-X OrgChart","sidebar":"sidebar_working_model"},"working-model/organizational-structure/overview-roles/catena-x-roles":{"id":"working-model/organizational-structure/overview-roles/catena-x-roles","title":"Catena-X association","description":"General","sidebar":"sidebar_working_model"},"working-model/organizational-structure/overview-roles/overview-roles":{"id":"working-model/organizational-structure/overview-roles/overview-roles","title":"Overview of roles and groups","description":"Welcome to the \\"Open Source Roles\\" section of our documentation. This chapter is dedicated to providing a comprehensive overview of the various roles that are integral to the success and sustainability of our open source project. Open source projects thrive on the collaboration and contributions of a diverse and active community. Understanding the different roles within this ecosystem is crucial for both current and prospective members who wish to engage with and contribute to the project.","sidebar":"sidebar_working_model"},"working-model/organizational-structure/overview-roles/tractus-x-roles":{"id":"working-model/organizational-structure/overview-roles/tractus-x-roles","title":"Tractus-X","description":"Contributor","sidebar":"sidebar_working_model"},"working-model/overview":{"id":"working-model/overview","title":"Overview","description":"Introduction","sidebar":"sidebar_working_model"},"working-model/process-from-idea-to-production/03-01-process-from-idea-to-production":{"id":"working-model/process-from-idea-to-production/03-01-process-from-idea-to-production","title":"Process Organization - From Idea to Release","description":"Coming soon....","sidebar":"sidebar_working_model"},"working-model/process-from-idea-to-production/03-02-Contribution-Guideline":{"id":"working-model/process-from-idea-to-production/03-02-Contribution-Guideline","title":"Tractus-X Open Source Project Contribution Guide","description":"Welcome to the Tractus-X open source project! This guide is designed to help you understand how you can contribute to the Tractus-X project. There are different levels of contributions you can make, such as standard contributions, feature contributions and improvements.","sidebar":"sidebar_working_model"},"working-model/process-from-idea-to-production/03-04-Issue-Process":{"id":"working-model/process-from-idea-to-production/03-04-Issue-Process","title":"Contribution Levels","description":"Table of Contents","sidebar":"sidebar_working_model"}}}}')}}]); \ No newline at end of file diff --git a/assets/js/0df7deee.7b518820.js b/assets/js/0df7deee.7b518820.js deleted file mode 100644 index abf64869..00000000 --- a/assets/js/0df7deee.7b518820.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[297],{1318:(e,n,s)=>{s.r(n),s.d(n,{assets:()=>c,contentTitle:()=>a,default:()=>h,frontMatter:()=>r,metadata:()=>o,toc:()=>l});var i=s(4848),t=s(8453);const r={sidebar_position:1},a="Who: Roles in the Catena-X ecosystem",o={id:"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem",title:"Who: Roles in the Catena-X ecosystem",description:"The Catena-X ecosystem operates on the principle of multiple distinct roles, designed to create an appealing and functional data space (see Figure Role Overview and Relationships). Participants can take on one or more roles in any combination, and multiple participants can fulfill the same role except for the CSP-B role. The CSP-B role can only exist once in the data space due to complexity and technical reasons. Provider roles receive a label through a certification or qualification process to demonstrate that they are trusted partners (see Chapter How: Life Cycle Management).",source:"@site/docs/operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem.md",sourceDirName:"operating-model/who-roles-in-the-catena-x-ecosystem",slug:"/operating-model/who-roles-in-the-catena-x-ecosystem/",permalink:"/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Why: Understanding the Catena-X Data Space",permalink:"/docs/next/operating-model/why-understanding-the-catena-x-data-space/"},next:{title:"What: Service Map",permalink:"/docs/next/operating-model/what-service-map/"}},c={},l=[{value:"Overview of roles",id:"overview-of-roles",level:2},{value:"Detailed description of each role",id:"detailed-description-of-each-role",level:2},{value:"Core Service Provider A",id:"core-service-provider-a",level:3},{value:"Core Service Provider B",id:"core-service-provider-b",level:3},{value:"Onboarding Service Provider",id:"onboarding-service-provider",level:3},{value:"Enablement Service Provider",id:"enablement-service-provider",level:3},{value:"Business Application Provider",id:"business-application-provider",level:3},{value:"Advisory Provider",id:"advisory-provider",level:3},{value:"Data Provider/Consumer",id:"data-providerconsumer",level:3},{value:"Catena-X Association",id:"catena-x-association",level:3},{value:"Conformity Assessment Body",id:"conformity-assessment-body",level:3}];function d(e){const n={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",img:"img",li:"li",p:"p",strong:"strong",ul:"ul",...(0,t.R)(),...e.components};return(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(n.h1,{id:"who-roles-in-the-catena-x-ecosystem",children:"Who: Roles in the Catena-X ecosystem"}),"\n",(0,i.jsxs)(n.p,{children:["The Catena-X ecosystem operates on the principle of multiple distinct roles, designed to create an appealing and functional data space (see ",(0,i.jsx)(n.a,{href:"/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/#overview-of-roles",children:"Figure Role Overview and Relationships"}),"). Participants can take on one or more roles in any combination, and multiple participants can fulfill the same role except for the CSP-B role. The CSP-B role can only exist once in the data space due to complexity and technical reasons. Provider roles receive a label through a certification or qualification process to demonstrate that they are trusted partners (see Chapter ",(0,i.jsx)(n.a,{href:"/docs/next/operating-model/how-life-cycle-management/",children:"How: Life Cycle Management"}),")."]}),"\n",(0,i.jsx)(n.h2,{id:"overview-of-roles",children:"Overview of roles"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.img,{alt:"Role Overview and Relationships",src:s(7676).A+"",width:"873",height:"726"}),"\n",(0,i.jsx)(n.em,{children:"Role Overview and Relationships"})]}),"\n",(0,i.jsx)(n.h2,{id:"detailed-description-of-each-role",children:"Detailed description of each role"}),"\n",(0,i.jsxs)(n.p,{children:["Below, each role that a participant can assume in the Catena-X data spaces is described in detail, along with its assigned description, responsibilities, relationships, prerequisites, and complements. Please refer to Chapter ",(0,i.jsx)(n.a,{href:"/docs/next/operating-model/appendix/#role-relationships",children:"Role Relationships"}),". for a comprehensive overview of the relationships between these roles as well as a definition of the relationship type and Chapter ",(0,i.jsx)(n.a,{href:"/docs/next/operating-model/what-service-map/",children:"What: Service Map"})," for an overview of the Service Map."]}),"\n",(0,i.jsx)(n.h3,{id:"core-service-provider-a",children:"Core Service Provider A"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Core Service Provider A (CSP-A)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": A CSP-A is responsible for deploying, operating, and maintaining core services A according to Catena-X standards. Core Services A provide common business functionalities for all data space participants (e.g., managing marketplace offers, semantic models, or searching for business partner information)."]}),"\n",(0,i.jsx)(n.p,{children:"A CSP-A can operate various bundles of Core Services A, whereby the operation of an IAM and a marketplace is mandatory. Note that the synchronization of marketplace offers is at the discretion of a provider, who may submit and list its offer on multiple marketplaces. The CSP-A role can be taken on by multiple participants."}),"\n",(0,i.jsx)(n.p,{children:"For smooth operations, the CSP-A must provide comprehensive technical documentation, along with first, second, and third level support to facilitate integration with its services. Each CSP-A has freedom of choice regarding their business model towards their potential customers."}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["A CSP-A ",(0,i.jsx)(n.strong,{children:"must"})," implement an IAM synchronization and must integrate with\nother CSP-As."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-A ",(0,i.jsx)(n.strong,{children:"must"})," implement an IAM synchronization with an OSP."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-A ",(0,i.jsx)(n.strong,{children:"must"})," integrate with the CSP-B to be able to offer and operate its services. This includes implementing IAM synchronization and integrating with required Core Services B."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-A ",(0,i.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e.g., registration service)."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-A ",(0,i.jsx)(n.strong,{children:"must"})," accept any certified solution that wants to be listed on its marketplace in accordance with its respective terms and conditions, without discriminating against individual organizations."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"A CSP-A and its services must be certified by a CAB"}),"\n",(0,i.jsx)(n.li,{children:"A CSP-A must accept and comply with the Catena-X regulatory framework\nduring onboarding via one of the OSPs."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["Due to technical limitations, the CSP-A role currently cannot be fully assumed and executed more than once. Further details can be found in Chapter ",(0,i.jsx)(n.a,{href:"/docs/next/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"})," or can be requested during the conformity assessment."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"core-service-provider-b",children:"Core Service Provider B"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Core Service Provider B (CSP-B)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": The CSP-B is responsible for deploying, operating, and maintaining all core services section B according to Catena-X standards. Core Services B include identity and common accessibility and discoverability functionalities for all data space participants."]}),"\n",(0,i.jsx)(n.p,{children:"The CSP-B operates all Core Services B as one bundle to enable trusted participation and sovereign data exchange across all data space participants. The CSP-B role can only be taken on by one participant and is nominated by the Catena-X Association to operate and further develop the services on their behalf."}),"\n",(0,i.jsx)(n.p,{children:"For smooth operations, the CSP-B must provide comprehensive technical documentation, along with first, second, and third level support to facilitate integration with its services."}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Due to its special role, the CSP-B is responsible for:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"providing non-discriminatory access to Core Services Section B for all data space participants."}),"\n",(0,i.jsx)(n.li,{children:"coordinating the release management of Core Services B in the data space (with affected participants) based on Catena-X Association and Tractus-X releases."}),"\n",(0,i.jsx)(n.li,{children:"marketing Core Services B and managing contractual partners."}),"\n",(0,i.jsx)(n.li,{children:"issuing and revoking access of BPNs to the data space based on the country clearance list by the Catena-X Association."}),"\n",(0,i.jsx)(n.li,{children:"temporarily executing the trust anchor role and issuing verifiable credentials."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["The CSP-B ",(0,i.jsx)(n.strong,{children:"must"})," support the integration of all other data space participants to the Core Services B."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-B ",(0,i.jsx)(n.strong,{children:"must"})," implement an IAM synchronization with CSP-As and OSPs."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["A CSP-B ",(0,i.jsx)(n.strong,{children:"must"})," be nominated by the Catena-X Association."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-B ",(0,i.jsx)(n.strong,{children:"must"})," be a Catena-X Association member."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-B and its services ",(0,i.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-B ",(0,i.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework via an MoU with the Association."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["To ensure complete functionality of the data space, the CSP-B ",(0,i.jsx)(n.strong,{children:"must"})," also operate the relevant services of both the CSP-A and OSP roles."]}),"\n",(0,i.jsxs)(n.li,{children:["Further details can be found in Chapter ",(0,i.jsx)(n.a,{href:"/docs/next/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),". how Catena-X foster competition."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"onboarding-service-provider",children:"Onboarding Service Provider"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Onboarding Service Provider (OSP)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": An OSP is responsible for deploying, operating, and maintaining onboarding services according to Catena-X standards. The onboarding services enable and support data space participants to register and onboard and offboard to Catena-X data space."]}),"\n",(0,i.jsxs)(n.p,{children:["This includes organizational registration and technical integration (see Chapter ",(0,i.jsx)(n.a,{href:"/docs/next/operating-model/how-data-space-operations/#general-onboarding",children:"General Onboarding"}),"), after which an organization can fully participate in the data space. An OSP can enable new prospects and/or their existing customer base in terms of network-of-networks. To ensure maximum trust in the data space during the onboarding process, the OSP must establish a connection with the Gaia-X Digital Clearing House (GXDCH)."]}),"\n",(0,i.jsx)(n.p,{children:"For smooth operations, the OSP must provide comprehensive technical documentation, along with first, second, and third level support to facilitate integration with its services."}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["An OSP ",(0,i.jsx)(n.strong,{children:"must"})," implement an IAM synchronization with CSP-As, the CSP-B, and OSPs to provide its customers with access to the data space."]}),"\n",(0,i.jsxs)(n.li,{children:["An OSP ",(0,i.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access their identity(e. g., identity wallet) and enable data exchange."]}),"\n",(0,i.jsxs)(n.li,{children:["An OSP ",(0,i.jsx)(n.strong,{children:"must"})," integrate and use the GAIA-X Digital Clearing House to validate e. g., the Legal Person Self-Description."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["An OSP and its services ",(0,i.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,i.jsxs)(n.li,{children:["An OSP ",(0,i.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access its identity (e. g., identity wallet)"]}),"\n",(0,i.jsxs)(n.li,{children:["An OSP ",(0,i.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the other OSPs."]}),"\n",(0,i.jsxs)(n.li,{children:["An OSP ",(0,i.jsx)(n.strong,{children:"must"})," use the dedicated GAIA-X Clearing House Service nominated by the Catena-X Association."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsxs)(n.p,{children:["Due to technical limitations, the OSP role currently cannot be fully assumed and executed more than once. Further details can be found in Chapter ",(0,i.jsx)(n.a,{href:"/docs/next/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"})," or can be requested during the conformity assessment. Offboarding will be included within the upcoming releases."]}),"\n",(0,i.jsx)(n.h3,{id:"enablement-service-provider",children:"Enablement Service Provider"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Enablement Service Provider (ESP)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": An ESP is responsible for deploying, operating, and maintaining enablement services according to Catena-X standards."]}),"\n",(0,i.jsx)(n.p,{children:"An ESP can operate various bundles of decentralized services that enable sovereign\nparticipation and data exchange for data providers and consumers in the Catena-X\ndata space. An ESP can decide on the scope of its enablement service and whether\nto offer them on one or multiple of the marketplaces."}),"\n",(0,i.jsx)(n.p,{children:"In addition, ESPs can also offer non-standardized services such as automated data\nmapping, in which data is extracted from company systems and converted into\nCatena-X semantic models."}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["An ESP ",(0,i.jsx)(n.strong,{children:"can"})," use one or more CSP-A services (e. g., semantic hub)."]}),"\n",(0,i.jsxs)(n.li,{children:["An ESP ",(0,i.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access its identity (e. g., identity wallet) and enable data exchange."]}),"\n",(0,i.jsxs)(n.li,{children:["An ESP ",(0,i.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e. g., registration service)."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["An ESP and its services ",(0,i.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,i.jsxs)(n.li,{children:["An ESP ",(0,i.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsx)(n.p,{children:"n/a"}),"\n",(0,i.jsx)(n.h3,{id:"business-application-provider",children:"Business Application Provider"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Business Application Provider (BAP)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": A BAP is responsible for deploying, operating, and maintaining business applications to Catena-X standards. Business applications enable data providers and consumers to leverage different use cases and data-driven processes to solve a specific industry problem (e.g., PCF) and create business value, by using KITs and Standards for an interoperable and trusted data exchange."]}),"\n",(0,i.jsx)(n.p,{children:"A BAP can decide on the scope of its business applications and whether to offer\nthem on one or multiple of the marketplaces"}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["A BAP ",(0,i.jsx)(n.strong,{children:"can"})," use one or more CSP-A services (e. g., semantic hub)."]}),"\n",(0,i.jsxs)(n.li,{children:["A BAP ",(0,i.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access his identity (e. g., identity wallet) and enable data exchange."]}),"\n",(0,i.jsxs)(n.li,{children:["A BAP ",(0,i.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e. g., registration service)."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["A BAP and its services ",(0,i.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,i.jsxs)(n.li,{children:["A BAP ",(0,i.jsx)(n.strong,{children:"must"})," list its solution on a marketplace provided by a CSP-A."]}),"\n",(0,i.jsxs)(n.li,{children:["A BAP ",(0,i.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsx)(n.p,{children:"n/a"}),"\n",(0,i.jsx)(n.h3,{id:"advisory-provider",children:"Advisory Provider"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Advisory Provider (AP)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": An AP offers advisory services in various areas, from strategy to operations to technology or business use cases for those interested in the Catena-X data space. Providing advisory services includes topics such as onboarding guidance, business value assessment, organizational and technical enablement, but do not include the operation of technical services."]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["An AP ",(0,i.jsx)(n.strong,{children:"can"})," use one or more CSP-As if it intends to utilize specific CSP-A services such as listing an offer on a marketplace."]}),"\n",(0,i.jsxs)(n.li,{children:["An AP ",(0,i.jsx)(n.strong,{children:"can"})," integrate and use CSP-B services to access the Core Services B."]}),"\n",(0,i.jsxs)(n.li,{children:["An AP ",(0,i.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e. g., registration service)."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["An AP ",(0,i.jsx)(n.strong,{children:"must"})," be qualified by the Catena-X Association."]}),"\n",(0,i.jsxs)(n.li,{children:["An AP ",(0,i.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsx)(n.p,{children:"n/a"}),"\n",(0,i.jsx)(n.h3,{id:"data-providerconsumer",children:"Data Provider/Consumer"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Data Provider and Consumer (DPC)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": A DPC provides, consumes, and processes data to collaborate with other data space participants to solve a specific industry problem und create business value. This includes both standardized use cases and direct collaboration."]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"can"})," use the services of a CSP-A (e.g., marketplace)."]}),"\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access his identity (e. g., identity wallet) and enable data exchange."]}),"\n",(0,i.jsxs)(n.li,{children:["An DPC ",(0,i.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e.g., registration service). This can be delegated to a BAP or ESP"]}),"\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"must"})," connect with another DPC to exchange data and create value."]}),"\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"can"})," use advisory services from a qualified AP."]}),"\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"can"})," use certified enablement services from a commercial ESP (e.g., SaaS solution). Alternatively, a DPC can certify and operate its own enablement services."]}),"\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"can"})," use certified business applications from a commercial BAP (e.g., SaaS\nsolution). Alternatively, a DPC can certify and operate its own business application"]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"must"})," use certified enablement services or business applications. Alternatively, a DPC ",(0,i.jsx)(n.strong,{children:"must"})," certify its own enablement services and/or business applications by one of the CABs (as outlined in Chapter ",(0,i.jsx)(n.a,{href:"/docs/next/operating-model/how-data-space-governance/#conformity-assessment",children:"Conformity Assessment"}),")."]}),"\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs"]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsx)(n.p,{children:"n/a"}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.em,{children:"In addition to the roles in the data space, there are independent roles such as the Catena-X Association or Conformity\nAssessment Bodies (CABs) to ensure neutral, trustworthy, and secure operation of the Catena-X data space."})}),"\n",(0,i.jsx)(n.h3,{id:"catena-x-association",children:"Catena-X Association"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Catena-X Association"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": The Association is responsible for the neutral governance of the Catena-X ecosystem including the execution of nomination, standardization, qualification, and certification processes. It promotes and facilitates working groups, committees, and expert groups to discuss and align on, standards, KITs, and requirements for open-source reference implementation for the Catena-X operating system and use cases. In addition, it provides various informational resources to interested parties and Association members."]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"The Association nominates the CSP-B and CABs."}),"\n",(0,i.jsx)(n.li,{children:"The Association delegates the certification of data space participants to CABs."}),"\n",(0,i.jsx)(n.li,{children:"The Association defines the Issuer of verifiable credentials."}),"\n",(0,i.jsx)(n.li,{children:"The Association qualifies APs."}),"\n",(0,i.jsx)(n.li,{children:"The Association promotes, sponsors, and coordinates the overlying requirements of the Eclipse Tractus-X Project with a view to standardization."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsx)(n.p,{children:"n/a"}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsxs)(n.p,{children:["For the upcoming releases there will be a dedicated issuer concept in place. As of now the Association defines the Issuer (CSP-B). Further details can be found in Chapter ",(0,i.jsx)(n.a,{href:"/docs/next/operating-model/how-data-space-operations/#ssi-issuer-concept",children:"SSI Issuer Concept"}),". An outlook can be found in Chapter ",(0,i.jsx)(n.a,{href:"/docs/next/operating-model/outlook/#further-integration-of-ssi-technologies",children:"Further Integration of SSI Technologies"}),"."]}),"\n",(0,i.jsx)(n.h3,{id:"conformity-assessment-body",children:"Conformity Assessment Body"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Conformity Assessment Body (CAB)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": A CAB carries out the conformity assessment process in accordance with the Catena-X Certification Framework on behalf of the Catena-X Association. The Certification Framework consists of the certification manual and the certification catalog (derived from the (",(0,i.jsx)(n.a,{href:"https://catena-x.net/de/standard-library",children:"Catena-X standards"}),")). A CAB is nominated by the Catena-X Association to ensure an independent, trustworthy, and secure conformity assessment process."]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"A CAB is responsible for:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"creating offers for the conformity assessments."}),"\n",(0,i.jsx)(n.li,{children:"carrying out the conformity assessment process for various certification objects (e.g., provider, solutions)."}),"\n",(0,i.jsx)(n.li,{children:"informing the Catena-X Association and the certification candidate about the certification results."}),"\n",(0,i.jsx)(n.li,{children:"issuing, reissuing, and revoking of certificates on behalf of the Catena-X\nAssociation."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["The CAB ",(0,i.jsx)(n.strong,{children:"must"})," carry out the conformity assessment for all affected data space\nparticipants and their IT solutions."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"A CAB must be nominated by the Catena-X Association and comply with the Catena-X certification framework."}),"\n",(0,i.jsx)(n.li,{children:"Business model supporting adoption and offering a non-discriminating access, esp. by small and medium business."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsx)(n.p,{children:"n/a"})]})}function h(e={}){const{wrapper:n}={...(0,t.R)(),...e.components};return n?(0,i.jsx)(n,{...e,children:(0,i.jsx)(d,{...e})}):d(e)}},7676:(e,n,s)=>{s.d(n,{A:()=>i});const i=s.p+"assets/images/role-overview-and-relationships-ebdb0775319edc16372e21437aedda92.png"},8453:(e,n,s)=>{s.d(n,{R:()=>a,x:()=>o});var i=s(6540);const t={},r=i.createContext(t);function a(e){const n=i.useContext(r);return i.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function o(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(t):e.components||t:a(e.components),i.createElement(r.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/0df7deee.9699a91f.js b/assets/js/0df7deee.9699a91f.js new file mode 100644 index 00000000..c89b0258 --- /dev/null +++ b/assets/js/0df7deee.9699a91f.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[297],{1318:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>c,contentTitle:()=>a,default:()=>h,frontMatter:()=>r,metadata:()=>o,toc:()=>l});var s=i(4848),t=i(8453);const r={sidebar_position:1},a="Who: Roles in the Catena-X ecosystem",o={id:"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem",title:"Who: Roles in the Catena-X ecosystem",description:"The Catena-X ecosystem operates on the principle of multiple distinct roles, designed to create an appealing and functional data space (see Figure Role Overview and Relationships). Participants can take on one or more roles in any combination, and multiple participants can fulfill the same role except for the CSP-B role. The CSP-B role can only exist once in the data space due to complexity and technical reasons. Provider roles receive a label through a certification or qualification process to demonstrate that they are trusted partners (see Chapter How: Life Cycle Management).",source:"@site/docs/operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem.md",sourceDirName:"operating-model/who-roles-in-the-catena-x-ecosystem",slug:"/operating-model/who-roles-in-the-catena-x-ecosystem/",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Why: Understanding the Catena-X Data Space",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/why-understanding-the-catena-x-data-space/"},next:{title:"What: Service Map",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/what-service-map/"}},c={},l=[{value:"Overview of roles",id:"overview-of-roles",level:2},{value:"Detailed description of each role",id:"detailed-description-of-each-role",level:2},{value:"Core Service Provider A",id:"core-service-provider-a",level:3},{value:"Core Service Provider B",id:"core-service-provider-b",level:3},{value:"Onboarding Service Provider",id:"onboarding-service-provider",level:3},{value:"Enablement Service Provider",id:"enablement-service-provider",level:3},{value:"Business Application Provider",id:"business-application-provider",level:3},{value:"Advisory Provider",id:"advisory-provider",level:3},{value:"Data Provider/Consumer",id:"data-providerconsumer",level:3},{value:"Catena-X Association",id:"catena-x-association",level:3},{value:"Conformity Assessment Body",id:"conformity-assessment-body",level:3}];function d(e){const n={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",img:"img",li:"li",p:"p",strong:"strong",ul:"ul",...(0,t.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsx)(n.h1,{id:"who-roles-in-the-catena-x-ecosystem",children:"Who: Roles in the Catena-X ecosystem"}),"\n",(0,s.jsxs)(n.p,{children:["The Catena-X ecosystem operates on the principle of multiple distinct roles, designed to create an appealing and functional data space (see ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/#overview-of-roles",children:"Figure Role Overview and Relationships"}),"). Participants can take on one or more roles in any combination, and multiple participants can fulfill the same role except for the CSP-B role. The CSP-B role can only exist once in the data space due to complexity and technical reasons. Provider roles receive a label through a certification or qualification process to demonstrate that they are trusted partners (see Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-life-cycle-management/",children:"How: Life Cycle Management"}),")."]}),"\n",(0,s.jsx)(n.h2,{id:"overview-of-roles",children:"Overview of roles"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.img,{alt:"Role Overview and Relationships",src:i(7676).A+"",width:"873",height:"726"}),"\n",(0,s.jsx)(n.em,{children:"Role Overview and Relationships"})]}),"\n",(0,s.jsx)(n.h2,{id:"detailed-description-of-each-role",children:"Detailed description of each role"}),"\n",(0,s.jsxs)(n.p,{children:["Below, each role that a participant can assume in the Catena-X data spaces is described in detail, along with its assigned description, responsibilities, relationships, prerequisites, and complements. Please refer to Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/appendix/#role-relationships",children:"Role Relationships"}),". for a comprehensive overview of the relationships between these roles as well as a definition of the relationship type and Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/what-service-map/",children:"What: Service Map"})," for an overview of the Service Map."]}),"\n",(0,s.jsx)(n.h3,{id:"core-service-provider-a",children:"Core Service Provider A"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Core Service Provider A (CSP-A)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": A CSP-A is responsible for deploying, operating, and maintaining core services A according to Catena-X standards. Core Services A provide common business functionalities for all data space participants (e.g., managing marketplace offers, semantic models, or searching for business partner information)."]}),"\n",(0,s.jsx)(n.p,{children:"A CSP-A can operate various bundles of Core Services A, whereby the operation of an IAM and a marketplace is mandatory. Note that the synchronization of marketplace offers is at the discretion of a provider, who may submit and list its offer on multiple marketplaces. The CSP-A role can be taken on by multiple participants."}),"\n",(0,s.jsx)(n.p,{children:"For smooth operations, the CSP-A must provide comprehensive technical documentation, along with first, second, and third level support to facilitate integration with its services. Each CSP-A has freedom of choice regarding their business model towards their potential customers."}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["A CSP-A ",(0,s.jsx)(n.strong,{children:"must"})," implement an IAM synchronization and must integrate with\nother CSP-As."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-A ",(0,s.jsx)(n.strong,{children:"must"})," implement an IAM synchronization with an OSP."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-A ",(0,s.jsx)(n.strong,{children:"must"})," integrate with the CSP-B to be able to offer and operate its services. This includes implementing IAM synchronization and integrating with required Core Services B."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-A ",(0,s.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e.g., registration service)."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-A ",(0,s.jsx)(n.strong,{children:"must"})," accept any certified solution that wants to be listed on its marketplace in accordance with its respective terms and conditions, without discriminating against individual organizations."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsx)(n.li,{children:"A CSP-A and its services must be certified by a CAB"}),"\n",(0,s.jsx)(n.li,{children:"A CSP-A must accept and comply with the Catena-X regulatory framework\nduring onboarding via one of the OSPs."}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["Due to technical limitations, the CSP-A role currently cannot be fully assumed and executed more than once. Further details can be found in Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"})," or can be requested during the conformity assessment."]}),"\n"]}),"\n",(0,s.jsx)(n.h3,{id:"core-service-provider-b",children:"Core Service Provider B"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Core Service Provider B (CSP-B)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": The CSP-B is responsible for deploying, operating, and maintaining all core services section B according to Catena-X standards. Core Services B include identity and common accessibility and discoverability functionalities for all data space participants."]}),"\n",(0,s.jsx)(n.p,{children:"The CSP-B operates all Core Services B as one bundle to enable trusted participation and sovereign data exchange across all data space participants. The CSP-B role can only be taken on by one participant and is nominated by the Catena-X Association to operate and further develop the services on their behalf."}),"\n",(0,s.jsx)(n.p,{children:"For smooth operations, the CSP-B must provide comprehensive technical documentation, along with first, second, and third level support to facilitate integration with its services."}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Due to its special role, the CSP-B is responsible for:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsx)(n.li,{children:"providing non-discriminatory access to Core Services Section B for all data space participants."}),"\n",(0,s.jsx)(n.li,{children:"coordinating the release management of Core Services B in the data space (with affected participants) based on Catena-X Association and Tractus-X releases."}),"\n",(0,s.jsx)(n.li,{children:"marketing Core Services B and managing contractual partners."}),"\n",(0,s.jsx)(n.li,{children:"issuing and revoking access of BPNs to the data space based on the country clearance list by the Catena-X Association."}),"\n",(0,s.jsx)(n.li,{children:"temporarily executing the trust anchor role and issuing verifiable credentials."}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["The CSP-B ",(0,s.jsx)(n.strong,{children:"must"})," support the integration of all other data space participants to the Core Services B."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-B ",(0,s.jsx)(n.strong,{children:"must"})," implement an IAM synchronization with CSP-As and OSPs."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["A CSP-B ",(0,s.jsx)(n.strong,{children:"must"})," be nominated by the Catena-X Association."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-B ",(0,s.jsx)(n.strong,{children:"must"})," be a Catena-X Association member."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-B and its services ",(0,s.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-B ",(0,s.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework via an MoU with the Association."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["To ensure complete functionality of the data space, the CSP-B ",(0,s.jsx)(n.strong,{children:"must"})," also operate the relevant services of both the CSP-A and OSP roles."]}),"\n",(0,s.jsxs)(n.li,{children:["Further details can be found in Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),". how Catena-X foster competition."]}),"\n"]}),"\n",(0,s.jsx)(n.h3,{id:"onboarding-service-provider",children:"Onboarding Service Provider"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Onboarding Service Provider (OSP)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": An OSP is responsible for deploying, operating, and maintaining onboarding services according to Catena-X standards. The onboarding services enable and support data space participants to register and onboard and offboard to Catena-X data space."]}),"\n",(0,s.jsxs)(n.p,{children:["This includes organizational registration and technical integration (see Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-operations/#general-onboarding",children:"General Onboarding"}),"), after which an organization can fully participate in the data space. An OSP can enable new prospects and/or their existing customer base in terms of network-of-networks. To ensure maximum trust in the data space during the onboarding process, the OSP must establish a connection with the Gaia-X Digital Clearing House (GXDCH)."]}),"\n",(0,s.jsx)(n.p,{children:"For smooth operations, the OSP must provide comprehensive technical documentation, along with first, second, and third level support to facilitate integration with its services."}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["An OSP ",(0,s.jsx)(n.strong,{children:"must"})," implement an IAM synchronization with CSP-As, the CSP-B, and OSPs to provide its customers with access to the data space."]}),"\n",(0,s.jsxs)(n.li,{children:["An OSP ",(0,s.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access their identity(e. g., identity wallet) and enable data exchange."]}),"\n",(0,s.jsxs)(n.li,{children:["An OSP ",(0,s.jsx)(n.strong,{children:"must"})," integrate and use the GAIA-X Digital Clearing House to validate e. g., the Legal Person Self-Description."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["An OSP and its services ",(0,s.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,s.jsxs)(n.li,{children:["An OSP ",(0,s.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access its identity (e. g., identity wallet)"]}),"\n",(0,s.jsxs)(n.li,{children:["An OSP ",(0,s.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the other OSPs."]}),"\n",(0,s.jsxs)(n.li,{children:["An OSP ",(0,s.jsx)(n.strong,{children:"must"})," use the dedicated GAIA-X Clearing House Service nominated by the Catena-X Association."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsxs)(n.p,{children:["Due to technical limitations, the OSP role currently cannot be fully assumed and executed more than once. Further details can be found in Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"})," or can be requested during the conformity assessment. Offboarding will be included within the upcoming releases."]}),"\n",(0,s.jsx)(n.h3,{id:"enablement-service-provider",children:"Enablement Service Provider"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Enablement Service Provider (ESP)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": An ESP is responsible for deploying, operating, and maintaining enablement services according to Catena-X standards."]}),"\n",(0,s.jsx)(n.p,{children:"An ESP can operate various bundles of decentralized services that enable sovereign\nparticipation and data exchange for data providers and consumers in the Catena-X\ndata space. An ESP can decide on the scope of its enablement service and whether\nto offer them on one or multiple of the marketplaces."}),"\n",(0,s.jsx)(n.p,{children:"In addition, ESPs can also offer non-standardized services such as automated data\nmapping, in which data is extracted from company systems and converted into\nCatena-X semantic models."}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["An ESP ",(0,s.jsx)(n.strong,{children:"can"})," use one or more CSP-A services (e. g., semantic hub)."]}),"\n",(0,s.jsxs)(n.li,{children:["An ESP ",(0,s.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access its identity (e. g., identity wallet) and enable data exchange."]}),"\n",(0,s.jsxs)(n.li,{children:["An ESP ",(0,s.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e. g., registration service)."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["An ESP and its services ",(0,s.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,s.jsxs)(n.li,{children:["An ESP ",(0,s.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsx)(n.p,{children:"n/a"}),"\n",(0,s.jsx)(n.h3,{id:"business-application-provider",children:"Business Application Provider"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Business Application Provider (BAP)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": A BAP is responsible for deploying, operating, and maintaining business applications to Catena-X standards. Business applications enable data providers and consumers to leverage different use cases and data-driven processes to solve a specific industry problem (e.g., PCF) and create business value, by using KITs and Standards for an interoperable and trusted data exchange."]}),"\n",(0,s.jsx)(n.p,{children:"A BAP can decide on the scope of its business applications and whether to offer\nthem on one or multiple of the marketplaces"}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["A BAP ",(0,s.jsx)(n.strong,{children:"can"})," use one or more CSP-A services (e. g., semantic hub)."]}),"\n",(0,s.jsxs)(n.li,{children:["A BAP ",(0,s.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access his identity (e. g., identity wallet) and enable data exchange."]}),"\n",(0,s.jsxs)(n.li,{children:["A BAP ",(0,s.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e. g., registration service)."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["A BAP and its services ",(0,s.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,s.jsxs)(n.li,{children:["A BAP ",(0,s.jsx)(n.strong,{children:"must"})," list its solution on a marketplace provided by a CSP-A."]}),"\n",(0,s.jsxs)(n.li,{children:["A BAP ",(0,s.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsx)(n.p,{children:"n/a"}),"\n",(0,s.jsx)(n.h3,{id:"advisory-provider",children:"Advisory Provider"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Advisory Provider (AP)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": An AP offers advisory services in various areas, from strategy to operations to technology or business use cases for those interested in the Catena-X data space. Providing advisory services includes topics such as onboarding guidance, business value assessment, organizational and technical enablement, but do not include the operation of technical services."]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["An AP ",(0,s.jsx)(n.strong,{children:"can"})," use one or more CSP-As if it intends to utilize specific CSP-A services such as listing an offer on a marketplace."]}),"\n",(0,s.jsxs)(n.li,{children:["An AP ",(0,s.jsx)(n.strong,{children:"can"})," integrate and use CSP-B services to access the Core Services B."]}),"\n",(0,s.jsxs)(n.li,{children:["An AP ",(0,s.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e. g., registration service)."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["An AP ",(0,s.jsx)(n.strong,{children:"must"})," be qualified by the Catena-X Association."]}),"\n",(0,s.jsxs)(n.li,{children:["An AP ",(0,s.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsx)(n.p,{children:"n/a"}),"\n",(0,s.jsx)(n.h3,{id:"data-providerconsumer",children:"Data Provider/Consumer"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Data Provider and Consumer (DPC)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": A DPC provides, consumes, and processes data to collaborate with other data space participants to solve a specific industry problem und create business value. This includes both standardized use cases and direct collaboration."]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"can"})," use the services of a CSP-A (e.g., marketplace)."]}),"\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access his identity (e. g., identity wallet) and enable data exchange."]}),"\n",(0,s.jsxs)(n.li,{children:["An DPC ",(0,s.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e.g., registration service). This can be delegated to a BAP or ESP"]}),"\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"must"})," connect with another DPC to exchange data and create value."]}),"\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"can"})," use advisory services from a qualified AP."]}),"\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"can"})," use certified enablement services from a commercial ESP (e.g., SaaS solution). Alternatively, a DPC can certify and operate its own enablement services."]}),"\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"can"})," use certified business applications from a commercial BAP (e.g., SaaS\nsolution). Alternatively, a DPC can certify and operate its own business application"]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"must"})," use certified enablement services or business applications. Alternatively, a DPC ",(0,s.jsx)(n.strong,{children:"must"})," certify its own enablement services and/or business applications by one of the CABs (as outlined in Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance/#conformity-assessment",children:"Conformity Assessment"}),")."]}),"\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs"]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsx)(n.p,{children:"n/a"}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.em,{children:"In addition to the roles in the data space, there are independent roles such as the Catena-X Association or Conformity\nAssessment Bodies (CABs) to ensure neutral, trustworthy, and secure operation of the Catena-X data space."})}),"\n",(0,s.jsx)(n.h3,{id:"catena-x-association",children:"Catena-X Association"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Catena-X Association"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": The Association is responsible for the neutral governance of the Catena-X ecosystem including the execution of nomination, standardization, qualification, and certification processes. It promotes and facilitates working groups, committees, and expert groups to discuss and align on, standards, KITs, and requirements for open-source reference implementation for the Catena-X operating system and use cases. In addition, it provides various informational resources to interested parties and Association members."]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsx)(n.li,{children:"The Association nominates the CSP-B and CABs."}),"\n",(0,s.jsx)(n.li,{children:"The Association delegates the certification of data space participants to CABs."}),"\n",(0,s.jsx)(n.li,{children:"The Association defines the Issuer of verifiable credentials."}),"\n",(0,s.jsx)(n.li,{children:"The Association qualifies APs."}),"\n",(0,s.jsx)(n.li,{children:"The Association promotes, sponsors, and coordinates the overlying requirements of the Eclipse Tractus-X Project with a view to standardization."}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsx)(n.p,{children:"n/a"}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsxs)(n.p,{children:["For the upcoming releases there will be a dedicated issuer concept in place. As of now the Association defines the Issuer (CSP-B). Further details can be found in Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-operations/#ssi-issuer-concept",children:"SSI Issuer Concept"}),". An outlook can be found in Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/outlook/#further-integration-of-ssi-technologies",children:"Further Integration of SSI Technologies"}),"."]}),"\n",(0,s.jsx)(n.h3,{id:"conformity-assessment-body",children:"Conformity Assessment Body"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Conformity Assessment Body (CAB)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": A CAB carries out the conformity assessment process in accordance with the Catena-X Certification Framework on behalf of the Catena-X Association. The Certification Framework consists of the certification manual and the certification catalog (derived from the (",(0,s.jsx)(n.a,{href:"https://catena-x.net/de/standard-library",children:"Catena-X standards"}),")). A CAB is nominated by the Catena-X Association to ensure an independent, trustworthy, and secure conformity assessment process."]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"A CAB is responsible for:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsx)(n.li,{children:"creating offers for the conformity assessments."}),"\n",(0,s.jsx)(n.li,{children:"carrying out the conformity assessment process for various certification objects (e.g., provider, solutions)."}),"\n",(0,s.jsx)(n.li,{children:"informing the Catena-X Association and the certification candidate about the certification results."}),"\n",(0,s.jsx)(n.li,{children:"issuing, reissuing, and revoking of certificates on behalf of the Catena-X\nAssociation."}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["The CAB ",(0,s.jsx)(n.strong,{children:"must"})," carry out the conformity assessment for all affected data space\nparticipants and their IT solutions."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsx)(n.li,{children:"A CAB must be nominated by the Catena-X Association and comply with the Catena-X certification framework."}),"\n",(0,s.jsx)(n.li,{children:"Business model supporting adoption and offering a non-discriminating access, esp. by small and medium business."}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsx)(n.p,{children:"n/a"})]})}function h(e={}){const{wrapper:n}={...(0,t.R)(),...e.components};return n?(0,s.jsx)(n,{...e,children:(0,s.jsx)(d,{...e})}):d(e)}},7676:(e,n,i)=>{i.d(n,{A:()=>s});const s=i.p+"assets/images/role-overview-and-relationships-ebdb0775319edc16372e21437aedda92.png"},8453:(e,n,i)=>{i.d(n,{R:()=>a,x:()=>o});var s=i(6540);const t={},r=s.createContext(t);function a(e){const n=s.useContext(r);return s.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function o(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(t):e.components||t:a(e.components),s.createElement(r.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/10f26ab1.5fd3c153.js b/assets/js/10f26ab1.5fd3c153.js new file mode 100644 index 00000000..6d67f878 --- /dev/null +++ b/assets/js/10f26ab1.5fd3c153.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[2652],{4078:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>d,contentTitle:()=>r,default:()=>l,frontMatter:()=>a,metadata:()=>o,toc:()=>c});var s=n(4848),i=n(8453);const a={sidebar_position:1},r="Appendix",o={id:"operating-model/appendix/appendix",title:"Appendix",description:"Role Relationships",source:"@site/docs/operating-model/appendix/appendix.md",sourceDirName:"operating-model/appendix",slug:"/operating-model/appendix/",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/appendix/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Glossary",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/glossary/"},next:{title:"Change Log",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/change-log/"}},d={},c=[{value:"Role Relationships",id:"role-relationships",level:2},{value:"Data Exchange based on SSI - Next Steps",id:"data-exchange-based-on-ssi---next-steps",level:2}];function h(e){const t={em:"em",h1:"h1",h2:"h2",img:"img",p:"p",strong:"strong",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",...(0,i.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsx)(t.h1,{id:"appendix",children:"Appendix"}),"\n",(0,s.jsx)(t.h2,{id:"role-relationships",children:"Role Relationships"}),"\n",(0,s.jsx)(t.p,{children:"Overview of mandatory (M) and optional (O) relationships between roles (release 23.09)"}),"\n",(0,s.jsxs)(t.p,{children:[(0,s.jsx)(t.img,{alt:"Role Relationships",src:n(6442).A+"",width:"1066",height:"557"}),"\n",(0,s.jsx)(t.em,{children:"Role Relationships"})]}),"\n",(0,s.jsx)(t.p,{children:"Overview of mandatory and optional relationships between roles."}),"\n",(0,s.jsxs)(t.table,{children:[(0,s.jsx)(t.thead,{children:(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.th,{children:"Relationship"}),(0,s.jsx)(t.th,{children:"Description"})]})}),(0,s.jsxs)(t.tbody,{children:[(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"IAM-Sync"}),(0,s.jsx)(t.td,{children:"The IdP is a service responsible for storing and verifying user identities. Its objective is to enable user access to all IAMs of Catena-X operators as soon as they onboard themselves and receive a user in an IAM. Achieving this requires synchronization of each IAM with every other one, a process known as Identity-Sync, which involves both regular users and technical clients."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Integration"}),(0,s.jsx)(t.td,{children:"Technical integration is required to use Core Services Section B of the CSP-B. The other parties must have access to the services to be able to offer their services. The technical integration refers to an API. This includes documentation, access data, definition of commercial aspects and SLAs. To fully utilize Core Services B of the CSP-B, it is required to perform technical integration with the related APIs. This integration is necessary for enabling other data space participants to access the services to provide their own services. This also includes to provide documentation, access credentials, and define commercial aspects and SLAs for other related services to ensure smooth functionality."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Onboarding"}),(0,s.jsx)(t.td,{children:"The onboarding enables either existing customers in other networks or interested parties to access the Catena-X data space (Trusted Access Point). This is the technical connection and registration of the participants. With the successful completion of the onboarding, the participant is part of Catena-X and can use the network."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Certification"}),(0,s.jsx)(t.td,{children:"When certified by a CAB, the party is audited against the Catena-X standards. These independent third parties ensure security and in-teroperability."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Nomination"}),(0,s.jsx)(t.td,{children:"The nomination process is designed to ensure neutrality and trustworthy execution of selected roles and tasks within the Catena-X ecosystem. The various rights and obligations of the operator are described in the Request for Tender (RFT)."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Qualification"}),(0,s.jsx)(t.td,{children:"With the qualification, the Catena-X Association ensures that there is a uniform level of quality and service of the various providers. This creates security and trust for the users of the services."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Trademark Rights"}),(0,s.jsx)(t.td,{children:"With the different qualifications and certifications, the respective parties receive different Catena-X labels. With these they can identify themselves and use them for illustration. The Catena-X Association holds the trademark rights to the labels and Catena-X itself"})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Use"}),(0,s.jsx)(t.td,{children:"Within Catena-X, a participant can use different offers from service providers (AP, ESP, BAP). These are certified applications. Alternatively, they can certify and operate them by themselves, but then it would not use services. The offers can be SaaS solutions or local deployments."})]})]})]}),"\n",(0,s.jsx)(t.h2,{id:"data-exchange-based-on-ssi---next-steps",children:"Data Exchange based on SSI - Next Steps"}),"\n",(0,s.jsxs)(t.p,{children:[(0,s.jsx)(t.strong,{children:"Catena-X Policies as part of the Data Exchange"}),"\n(please note the image below covers own as well as managed Wallet solutions; the credential request flow is not displayed since no changes are planned so far)"]}),"\n",(0,s.jsxs)(t.p,{children:[(0,s.jsx)(t.img,{alt:"Further development of the data exchange based on SSI",src:n(4011).A+"",width:"1106",height:"783"}),"\n",(0,s.jsx)(t.em,{children:"Further development of the data exchange based on SSI"})]})]})}function l(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,s.jsx)(t,{...e,children:(0,s.jsx)(h,{...e})}):h(e)}},4011:(e,t,n)=>{n.d(t,{A:()=>s});const s=n.p+"assets/images/further-development-of-the-data-exchange-based-on-ssi-f3a136e74f3c302de5fdf45d0886bcff.png"},6442:(e,t,n)=>{n.d(t,{A:()=>s});const s=n.p+"assets/images/role-relationships-c41cada71489356c6d8b5389b8307a54.png"},8453:(e,t,n)=>{n.d(t,{R:()=>r,x:()=>o});var s=n(6540);const i={},a=s.createContext(i);function r(e){const t=s.useContext(a);return s.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function o(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:r(e.components),s.createElement(a.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/10f26ab1.d8f6ab99.js b/assets/js/10f26ab1.d8f6ab99.js deleted file mode 100644 index e3c71d24..00000000 --- a/assets/js/10f26ab1.d8f6ab99.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[2652],{4078:(e,t,s)=>{s.r(t),s.d(t,{assets:()=>d,contentTitle:()=>r,default:()=>l,frontMatter:()=>a,metadata:()=>o,toc:()=>c});var n=s(4848),i=s(8453);const a={sidebar_position:1},r="Appendix",o={id:"operating-model/appendix/appendix",title:"Appendix",description:"Role Relationships",source:"@site/docs/operating-model/appendix/appendix.md",sourceDirName:"operating-model/appendix",slug:"/operating-model/appendix/",permalink:"/docs/next/operating-model/appendix/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Glossary",permalink:"/docs/next/operating-model/glossary/"},next:{title:"Change Log",permalink:"/docs/next/operating-model/change-log/"}},d={},c=[{value:"Role Relationships",id:"role-relationships",level:2},{value:"Data Exchange based on SSI - Next Steps",id:"data-exchange-based-on-ssi---next-steps",level:2}];function h(e){const t={em:"em",h1:"h1",h2:"h2",img:"img",p:"p",strong:"strong",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",...(0,i.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(t.h1,{id:"appendix",children:"Appendix"}),"\n",(0,n.jsx)(t.h2,{id:"role-relationships",children:"Role Relationships"}),"\n",(0,n.jsx)(t.p,{children:"Overview of mandatory (M) and optional (O) relationships between roles (release 23.09)"}),"\n",(0,n.jsxs)(t.p,{children:[(0,n.jsx)(t.img,{alt:"Role Relationships",src:s(6442).A+"",width:"1066",height:"557"}),"\n",(0,n.jsx)(t.em,{children:"Role Relationships"})]}),"\n",(0,n.jsx)(t.p,{children:"Overview of mandatory and optional relationships between roles."}),"\n",(0,n.jsxs)(t.table,{children:[(0,n.jsx)(t.thead,{children:(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.th,{children:"Relationship"}),(0,n.jsx)(t.th,{children:"Description"})]})}),(0,n.jsxs)(t.tbody,{children:[(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"IAM-Sync"}),(0,n.jsx)(t.td,{children:"The IdP is a service responsible for storing and verifying user identities. Its objective is to enable user access to all IAMs of Catena-X operators as soon as they onboard themselves and receive a user in an IAM. Achieving this requires synchronization of each IAM with every other one, a process known as Identity-Sync, which involves both regular users and technical clients."})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Integration"}),(0,n.jsx)(t.td,{children:"Technical integration is required to use Core Services Section B of the CSP-B. The other parties must have access to the services to be able to offer their services. The technical integration refers to an API. This includes documentation, access data, definition of commercial aspects and SLAs. To fully utilize Core Services B of the CSP-B, it is required to perform technical integration with the related APIs. This integration is necessary for enabling other data space participants to access the services to provide their own services. This also includes to provide documentation, access credentials, and define commercial aspects and SLAs for other related services to ensure smooth functionality."})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Onboarding"}),(0,n.jsx)(t.td,{children:"The onboarding enables either existing customers in other networks or interested parties to access the Catena-X data space (Trusted Access Point). This is the technical connection and registration of the participants. With the successful completion of the onboarding, the participant is part of Catena-X and can use the network."})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Certification"}),(0,n.jsx)(t.td,{children:"When certified by a CAB, the party is audited against the Catena-X standards. These independent third parties ensure security and in-teroperability."})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Nomination"}),(0,n.jsx)(t.td,{children:"The nomination process is designed to ensure neutrality and trustworthy execution of selected roles and tasks within the Catena-X ecosystem. The various rights and obligations of the operator are described in the Request for Tender (RFT)."})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Qualification"}),(0,n.jsx)(t.td,{children:"With the qualification, the Catena-X Association ensures that there is a uniform level of quality and service of the various providers. This creates security and trust for the users of the services."})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Trademark Rights"}),(0,n.jsx)(t.td,{children:"With the different qualifications and certifications, the respective parties receive different Catena-X labels. With these they can identify themselves and use them for illustration. The Catena-X Association holds the trademark rights to the labels and Catena-X itself"})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Use"}),(0,n.jsx)(t.td,{children:"Within Catena-X, a participant can use different offers from service providers (AP, ESP, BAP). These are certified applications. Alternatively, they can certify and operate them by themselves, but then it would not use services. The offers can be SaaS solutions or local deployments."})]})]})]}),"\n",(0,n.jsx)(t.h2,{id:"data-exchange-based-on-ssi---next-steps",children:"Data Exchange based on SSI - Next Steps"}),"\n",(0,n.jsxs)(t.p,{children:[(0,n.jsx)(t.strong,{children:"Catena-X Policies as part of the Data Exchange"}),"\n(please note the image below covers own as well as managed Wallet solutions; the credential request flow is not displayed since no changes are planned so far)"]}),"\n",(0,n.jsxs)(t.p,{children:[(0,n.jsx)(t.img,{alt:"Further development of the data exchange based on SSI",src:s(4011).A+"",width:"1106",height:"783"}),"\n",(0,n.jsx)(t.em,{children:"Further development of the data exchange based on SSI"})]})]})}function l(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,n.jsx)(t,{...e,children:(0,n.jsx)(h,{...e})}):h(e)}},4011:(e,t,s)=>{s.d(t,{A:()=>n});const n=s.p+"assets/images/further-development-of-the-data-exchange-based-on-ssi-f3a136e74f3c302de5fdf45d0886bcff.png"},6442:(e,t,s)=>{s.d(t,{A:()=>n});const n=s.p+"assets/images/role-relationships-c41cada71489356c6d8b5389b8307a54.png"},8453:(e,t,s)=>{s.d(t,{R:()=>r,x:()=>o});var n=s(6540);const i={},a=n.createContext(i);function r(e){const t=n.useContext(a);return n.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function o(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:r(e.components),n.createElement(a.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/14b69759.0fa34992.js b/assets/js/14b69759.0fa34992.js new file mode 100644 index 00000000..d3083618 --- /dev/null +++ b/assets/js/14b69759.0fa34992.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[7026],{7563:(e,a,n)=>{n.r(a),n.d(a,{assets:()=>c,contentTitle:()=>r,default:()=>m,frontMatter:()=>s,metadata:()=>o,toc:()=>l});var t=n(4848),i=n(8453);const s={sidebar_position:1},r="How: Life Cycle Management",o={id:"operating-model/how-life-cycle-management/how-life-cycle-management",title:"How: Life Cycle Management",description:"Managing versions and changes of different artifacts in federated data spaces is critical to ensure compatibility, interoperability, and security. The life cycle management of the Catena-X ecosystem is coordinated by the Catena-X Association and includes the releases in the Catena-X Association and in the Eclipse Tractus-X Project (see Figure Overview Life Cycle Management). It is planned to provide quarterly releases including one major and three minor releases per year. Both releases follow calendar versioning (see CalVer), whereas their artifacts such as standards, normative documents, products, and KITs follow semantic versioning (see SemVer). To ensure backward compatibility in the future (see Chapter Backward Compatibility), versioning and passing of predefined test cases of each individual artifact is mandatory.",source:"@site/versioned_docs/version-24.03/operating-model/how-life-cycle-management/how-life-cycle-management.md",sourceDirName:"operating-model/how-life-cycle-management",slug:"/operating-model/how-life-cycle-management/",permalink:"/catenax-ev.github.io.new/docs/operating-model/how-life-cycle-management/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"How: Data Space Governance",permalink:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance/"},next:{title:"Outlook",permalink:"/catenax-ev.github.io.new/docs/operating-model/outlook/"}},c={},l=[];function d(e){const a={a:"a",em:"em",h1:"h1",img:"img",p:"p",strong:"strong",...(0,i.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(a.h1,{id:"how-life-cycle-management",children:"How: Life Cycle Management"}),"\n",(0,t.jsxs)(a.p,{children:["Managing versions and changes of different artifacts in federated data spaces is critical to ensure compatibility, interoperability, and security. The life cycle management of the Catena-X ecosystem is coordinated by the Catena-X Association and includes the releases in the Catena-X Association and in the Eclipse Tractus-X Project (see Figure ",(0,t.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-life-cycle-management/",children:"Overview Life Cycle Management"}),"). It is planned to provide quarterly releases including ",(0,t.jsx)(a.strong,{children:"one major"})," and ",(0,t.jsx)(a.strong,{children:"three minor"})," releases per year. Both releases follow calendar versioning (see ",(0,t.jsx)(a.a,{href:"https://calver.org/",children:"CalVer"}),"), whereas their artifacts such as standards, normative documents, products, and KITs follow semantic versioning (see ",(0,t.jsx)(a.a,{href:"https://semver.org/",children:"SemVer"}),"). To ensure backward compatibility in the future (see Chapter ",(0,t.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/outlook/#backward-compatibility",children:"Backward Compatibility"}),"), versioning and passing of predefined test cases of each individual artifact is mandatory."]}),"\n",(0,t.jsxs)(a.p,{children:[(0,t.jsx)(a.img,{alt:"Overview Life Cycle Management",src:n(3945).A+"",width:"1757",height:"602"}),"\n",(0,t.jsx)(a.em,{children:"Overview Life Cycle Management"})]}),"\n",(0,t.jsx)(a.p,{children:"The Catena-X Association release includes all binding and certification-relevant artifacts such as standards (e.g., API-specifications, semantic models) and normative documents for all data space participants. The Tractus-X release contains all open-source products (including services or helm charts) of the cxOS and business applications as well as KITs. In addition, there are various commercial or self-developed solutions for business applications and services following individual release cycles and versioning schemes."}),"\n",(0,t.jsx)(a.p,{children:"Both the Tractus-X release and any commercial or self developed solutions must adhere to Catena-X standards and other relevant normative documents."}),"\n",(0,t.jsxs)(a.p,{children:["Open-source products are required to fulfill the ",(0,t.jsx)(a.a,{href:"https://eclipse-tractusx.github.io/docs/release/",children:"Tractus-X release guideline(TRGs)"})," and take part in our integration tests to be part of a quarterly Tractus-X release. For critical issues (e. g., security issues), hot fixes may be released to fix a bug in the active Catena-X operating system that interrupts the normal release cycle."]})]})}function m(e={}){const{wrapper:a}={...(0,i.R)(),...e.components};return a?(0,t.jsx)(a,{...e,children:(0,t.jsx)(d,{...e})}):d(e)}},3945:(e,a,n)=>{n.d(a,{A:()=>t});const t=n.p+"assets/images/overview-life-cycle-management-dfc25bce1da282bfe1fa509d8cfe7aac.png"},8453:(e,a,n)=>{n.d(a,{R:()=>r,x:()=>o});var t=n(6540);const i={},s=t.createContext(i);function r(e){const a=t.useContext(s);return t.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function o(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:r(e.components),t.createElement(s.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/14b69759.4cb6dda2.js b/assets/js/14b69759.4cb6dda2.js deleted file mode 100644 index faeb4394..00000000 --- a/assets/js/14b69759.4cb6dda2.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[7026],{7563:(e,a,n)=>{n.r(a),n.d(a,{assets:()=>c,contentTitle:()=>r,default:()=>m,frontMatter:()=>s,metadata:()=>o,toc:()=>l});var t=n(4848),i=n(8453);const s={sidebar_position:1},r="How: Life Cycle Management",o={id:"operating-model/how-life-cycle-management/how-life-cycle-management",title:"How: Life Cycle Management",description:"Managing versions and changes of different artifacts in federated data spaces is critical to ensure compatibility, interoperability, and security. The life cycle management of the Catena-X ecosystem is coordinated by the Catena-X Association and includes the releases in the Catena-X Association and in the Eclipse Tractus-X Project (see Figure Overview Life Cycle Management). It is planned to provide quarterly releases including one major and three minor releases per year. Both releases follow calendar versioning (see CalVer), whereas their artifacts such as standards, normative documents, products, and KITs follow semantic versioning (see SemVer). To ensure backward compatibility in the future (see Chapter Backward Compatibility), versioning and passing of predefined test cases of each individual artifact is mandatory.",source:"@site/versioned_docs/version-24.03/operating-model/how-life-cycle-management/how-life-cycle-management.md",sourceDirName:"operating-model/how-life-cycle-management",slug:"/operating-model/how-life-cycle-management/",permalink:"/docs/operating-model/how-life-cycle-management/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"How: Data Space Governance",permalink:"/docs/operating-model/how-data-space-governance/"},next:{title:"Outlook",permalink:"/docs/operating-model/outlook/"}},c={},l=[];function d(e){const a={a:"a",em:"em",h1:"h1",img:"img",p:"p",strong:"strong",...(0,i.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(a.h1,{id:"how-life-cycle-management",children:"How: Life Cycle Management"}),"\n",(0,t.jsxs)(a.p,{children:["Managing versions and changes of different artifacts in federated data spaces is critical to ensure compatibility, interoperability, and security. The life cycle management of the Catena-X ecosystem is coordinated by the Catena-X Association and includes the releases in the Catena-X Association and in the Eclipse Tractus-X Project (see Figure ",(0,t.jsx)(a.a,{href:"/docs/operating-model/how-life-cycle-management/",children:"Overview Life Cycle Management"}),"). It is planned to provide quarterly releases including ",(0,t.jsx)(a.strong,{children:"one major"})," and ",(0,t.jsx)(a.strong,{children:"three minor"})," releases per year. Both releases follow calendar versioning (see ",(0,t.jsx)(a.a,{href:"https://calver.org/",children:"CalVer"}),"), whereas their artifacts such as standards, normative documents, products, and KITs follow semantic versioning (see ",(0,t.jsx)(a.a,{href:"https://semver.org/",children:"SemVer"}),"). To ensure backward compatibility in the future (see Chapter ",(0,t.jsx)(a.a,{href:"/docs/operating-model/outlook/#backward-compatibility",children:"Backward Compatibility"}),"), versioning and passing of predefined test cases of each individual artifact is mandatory."]}),"\n",(0,t.jsxs)(a.p,{children:[(0,t.jsx)(a.img,{alt:"Overview Life Cycle Management",src:n(3945).A+"",width:"1757",height:"602"}),"\n",(0,t.jsx)(a.em,{children:"Overview Life Cycle Management"})]}),"\n",(0,t.jsx)(a.p,{children:"The Catena-X Association release includes all binding and certification-relevant artifacts such as standards (e.g., API-specifications, semantic models) and normative documents for all data space participants. The Tractus-X release contains all open-source products (including services or helm charts) of the cxOS and business applications as well as KITs. In addition, there are various commercial or self-developed solutions for business applications and services following individual release cycles and versioning schemes."}),"\n",(0,t.jsx)(a.p,{children:"Both the Tractus-X release and any commercial or self developed solutions must adhere to Catena-X standards and other relevant normative documents."}),"\n",(0,t.jsxs)(a.p,{children:["Open-source products are required to fulfill the ",(0,t.jsx)(a.a,{href:"https://eclipse-tractusx.github.io/docs/release/",children:"Tractus-X release guideline(TRGs)"})," and take part in our integration tests to be part of a quarterly Tractus-X release. For critical issues (e. g., security issues), hot fixes may be released to fix a bug in the active Catena-X operating system that interrupts the normal release cycle."]})]})}function m(e={}){const{wrapper:a}={...(0,i.R)(),...e.components};return a?(0,t.jsx)(a,{...e,children:(0,t.jsx)(d,{...e})}):d(e)}},3945:(e,a,n)=>{n.d(a,{A:()=>t});const t=n.p+"assets/images/overview-life-cycle-management-dfc25bce1da282bfe1fa509d8cfe7aac.png"},8453:(e,a,n)=>{n.d(a,{R:()=>r,x:()=>o});var t=n(6540);const i={},s=t.createContext(i);function r(e){const a=t.useContext(s);return t.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function o(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:r(e.components),t.createElement(s.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/1897e797.889597f7.js b/assets/js/1897e797.889597f7.js new file mode 100644 index 00000000..b071eecc --- /dev/null +++ b/assets/js/1897e797.889597f7.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[5740],{4885:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>d,contentTitle:()=>a,default:()=>l,frontMatter:()=>i,metadata:()=>r,toc:()=>c});var s=t(4848),o=t(8453);const i={sidebar_position:1,title:"Overview Standards"},a=void 0,r={id:"standards/overview",title:"Overview Standards",description:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.",source:"@site/docs/standards/overview.md",sourceDirName:"standards",slug:"/standards/overview",permalink:"/catenax-ev.github.io.new/docs/next/standards/overview",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Overview Standards"},sidebar:"sidebar_standards"},d={},c=[];function u(e){const n={admonition:"admonition",p:"p",...(0,o.R)(),...e.components};return(0,s.jsx)(n.admonition,{type:"danger",children:(0,s.jsx)(n.p,{children:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation."})})}function l(e={}){const{wrapper:n}={...(0,o.R)(),...e.components};return n?(0,s.jsx)(n,{...e,children:(0,s.jsx)(u,{...e})}):u(e)}},8453:(e,n,t)=>{t.d(n,{R:()=>a,x:()=>r});var s=t(6540);const o={},i=s.createContext(o);function a(e){const n=s.useContext(i);return s.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function r(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(o):e.components||o:a(e.components),s.createElement(i.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/1897e797.a5189ebb.js b/assets/js/1897e797.a5189ebb.js deleted file mode 100644 index 366b669c..00000000 --- a/assets/js/1897e797.a5189ebb.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[5740],{4885:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>d,contentTitle:()=>r,default:()=>l,frontMatter:()=>i,metadata:()=>a,toc:()=>c});var s=t(4848),o=t(8453);const i={sidebar_position:1,title:"Overview Standards"},r=void 0,a={id:"standards/overview",title:"Overview Standards",description:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.",source:"@site/docs/standards/overview.md",sourceDirName:"standards",slug:"/standards/overview",permalink:"/docs/next/standards/overview",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Overview Standards"},sidebar:"sidebar_standards"},d={},c=[];function u(e){const n={admonition:"admonition",p:"p",...(0,o.R)(),...e.components};return(0,s.jsx)(n.admonition,{type:"danger",children:(0,s.jsx)(n.p,{children:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation."})})}function l(e={}){const{wrapper:n}={...(0,o.R)(),...e.components};return n?(0,s.jsx)(n,{...e,children:(0,s.jsx)(u,{...e})}):u(e)}},8453:(e,n,t)=>{t.d(n,{R:()=>r,x:()=>a});var s=t(6540);const o={},i=s.createContext(o);function r(e){const n=s.useContext(i);return s.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function a(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(o):e.components||o:r(e.components),s.createElement(i.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/2224ae46.783d61b2.js b/assets/js/2224ae46.783d61b2.js new file mode 100644 index 00000000..eb3944e7 --- /dev/null +++ b/assets/js/2224ae46.783d61b2.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[4265],{2549:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>c,contentTitle:()=>o,default:()=>h,frontMatter:()=>i,metadata:()=>d,toc:()=>l});var r=n(4848),s=n(8453);const i={sidebar_position:5,title:"Glossary"},o=void 0,d={id:"working-model/glossary",title:"Glossary",description:"| Abbreviation | Full form |",source:"@site/docs/working-model/glossary.md",sourceDirName:"working-model",slug:"/working-model/glossary",permalink:"/catenax-ev.github.io.new/docs/next/working-model/glossary",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:5,frontMatter:{sidebar_position:5,title:"Glossary"},sidebar:"sidebar_working_model",previous:{title:"Contribution Levels",permalink:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-04-Issue-Process"}},c={},l=[];function a(e){const t={table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",...(0,s.R)(),...e.components};return(0,r.jsxs)(t.table,{children:[(0,r.jsx)(t.thead,{children:(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.th,{children:"Abbreviation"}),(0,r.jsx)(t.th,{children:"Full form"})]})}),(0,r.jsxs)(t.tbody,{children:[(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"e2e"}),(0,r.jsx)(t.td,{children:"end to end"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"FOSS"}),(0,r.jsx)(t.td,{children:"Free and Open-Source Software"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"IDSA"}),(0,r.jsx)(t.td,{children:"International Data Space Association"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"OEM"}),(0,r.jsx)(t.td,{children:"Original Equipment Manufacturer"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"PR"}),(0,r.jsx)(t.td,{children:"Pull Request"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"QA"}),(0,r.jsx)(t.td,{children:"Quality Assurance"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"SIG"}),(0,r.jsx)(t.td,{children:"Special Interest Group"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"SPOC"}),(0,r.jsx)(t.td,{children:"Single Point of Contact"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"TRG"}),(0,r.jsx)(t.td,{children:"Tractus-X Release Guidelines"})]})]})]})}function h(e={}){const{wrapper:t}={...(0,s.R)(),...e.components};return t?(0,r.jsx)(t,{...e,children:(0,r.jsx)(a,{...e})}):a(e)}},8453:(e,t,n)=>{n.d(t,{R:()=>o,x:()=>d});var r=n(6540);const s={},i=r.createContext(s);function o(e){const t=r.useContext(i);return r.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function d(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:o(e.components),r.createElement(i.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/2224ae46.f3cc4e4b.js b/assets/js/2224ae46.f3cc4e4b.js deleted file mode 100644 index 6b18c4bb..00000000 --- a/assets/js/2224ae46.f3cc4e4b.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[4265],{2549:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>l,contentTitle:()=>o,default:()=>h,frontMatter:()=>i,metadata:()=>d,toc:()=>c});var r=n(4848),s=n(8453);const i={sidebar_position:5,title:"Glossary"},o=void 0,d={id:"working-model/glossary",title:"Glossary",description:"| Abbreviation | Full form |",source:"@site/docs/working-model/glossary.md",sourceDirName:"working-model",slug:"/working-model/glossary",permalink:"/docs/next/working-model/glossary",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:5,frontMatter:{sidebar_position:5,title:"Glossary"},sidebar:"sidebar_working_model",previous:{title:"Contribution Levels",permalink:"/docs/next/working-model/process-from-idea-to-production/03-04-Issue-Process"}},l={},c=[];function a(e){const t={table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",...(0,s.R)(),...e.components};return(0,r.jsxs)(t.table,{children:[(0,r.jsx)(t.thead,{children:(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.th,{children:"Abbreviation"}),(0,r.jsx)(t.th,{children:"Full form"})]})}),(0,r.jsxs)(t.tbody,{children:[(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"e2e"}),(0,r.jsx)(t.td,{children:"end to end"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"FOSS"}),(0,r.jsx)(t.td,{children:"Free and Open-Source Software"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"IDSA"}),(0,r.jsx)(t.td,{children:"International Data Space Association"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"OEM"}),(0,r.jsx)(t.td,{children:"Original Equipment Manufacturer"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"PR"}),(0,r.jsx)(t.td,{children:"Pull Request"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"QA"}),(0,r.jsx)(t.td,{children:"Quality Assurance"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"SIG"}),(0,r.jsx)(t.td,{children:"Special Interest Group"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"SPOC"}),(0,r.jsx)(t.td,{children:"Single Point of Contact"})]}),(0,r.jsxs)(t.tr,{children:[(0,r.jsx)(t.td,{children:"TRG"}),(0,r.jsx)(t.td,{children:"Tractus-X Release Guidelines"})]})]})]})}function h(e={}){const{wrapper:t}={...(0,s.R)(),...e.components};return t?(0,r.jsx)(t,{...e,children:(0,r.jsx)(a,{...e})}):a(e)}},8453:(e,t,n)=>{n.d(t,{R:()=>o,x:()=>d});var r=n(6540);const s={},i=r.createContext(s);function o(e){const t=r.useContext(i);return r.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function d(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:o(e.components),r.createElement(i.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/254e3ee1.1d0a0cd9.js b/assets/js/254e3ee1.1d0a0cd9.js new file mode 100644 index 00000000..61179f2a --- /dev/null +++ b/assets/js/254e3ee1.1d0a0cd9.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8399],{6747:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>c,contentTitle:()=>s,default:()=>u,frontMatter:()=>o,metadata:()=>r,toc:()=>d});var a=n(4848),i=n(8453);const o={sidebar_position:1},s="Why: Introduction",r={id:"operating-model/why-introduction/why-introduction",title:"Why: Introduction",description:"Relevance",source:"@site/versioned_docs/version-24.03/operating-model/why-introduction/why-introduction.md",sourceDirName:"operating-model/why-introduction",slug:"/operating-model/why-introduction/",permalink:"/catenax-ev.github.io.new/docs/operating-model/why-introduction/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Operating Model",permalink:"/catenax-ev.github.io.new/docs/operating-model/operating-model/"},next:{title:"Why: Understanding the Catena-X Data Space",permalink:"/catenax-ev.github.io.new/docs/operating-model/why-understanding-the-catena-x-data-space/"}},c={},d=[{value:"Relevance",id:"relevance",level:2},{value:"Executive Summary",id:"executive-summary",level:2},{value:"Introduction",id:"introduction",level:3},{value:"Objectives",id:"objectives",level:3},{value:"Scope",id:"scope",level:3},{value:"Document updates",id:"document-updates",level:2}];function l(e){const t={h1:"h1",h2:"h2",h3:"h3",p:"p",...(0,i.R)(),...e.components};return(0,a.jsxs)(a.Fragment,{children:[(0,a.jsx)(t.h1,{id:"why-introduction",children:"Why: Introduction"}),"\n",(0,a.jsx)(t.h2,{id:"relevance",children:"Relevance"}),"\n",(0,a.jsx)(t.p,{children:"The Catena-X Operating Model Whitepaper is a normative document of the Catena-X Association. Normative documents outline rules, guidelines, and characteristics for activities and results for all participants within the Catena-X ecosystem. The Catena-X ecosystem includes Governance,Standardization,Certification,Development and Operations. These are established by consensus among the working groups and approved by the executive board of the Catena-X Association. As part of the Catena-X regulatory framework,this document is binding for all participants of the Catena-X ecosystem. This normative document is a foundational building block, allowing all participants to collaborate within a global ecosystem."}),"\n",(0,a.jsx)(t.h2,{id:"executive-summary",children:"Executive Summary"}),"\n",(0,a.jsx)(t.h3,{id:"introduction",children:"Introduction"}),"\n",(0,a.jsx)(t.p,{children:"With Catena-X, the automotive industry is creating targets a trustworthy, collaborative, open, and secure data space to enable a data-driven value chain for their relevant business processes. All participants can be connected in business process-centric end-to-end value chains, where everyone operates on an equal playing field, has sovereign control over their data and no lock-in effects occur. Thereby, the digitalization of intercompany processes and value chains, especially those of small and medium-sized companies, can be performed on a cost effective, timely and lasting basis. Further, it secures that market participants and competitors collaborate in a compliant and trusted way."}),"\n",(0,a.jsx)(t.h3,{id:"objectives",children:"Objectives"}),"\n",(0,a.jsx)(t.p,{children:"This document defines the operating model and processes required within the Catena-X ecosystem. The operating model is linked to the concepts and values of Gaia-X and the International Data Space Association (IDSA) to create the first open and collaborative data ecosystem for the automotive value chain. Thereby, Catena-X applies these concepts and extends them by integrating automotive-specific requirements for compliance, interoperability, and security. 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."}),"\n",(0,a.jsx)(t.h3,{id:"scope",children:"Scope"}),"\n",(0,a.jsx)(t.p,{children:"The Catena-X operating model describes the entire Catena-X ecosystem, focusing on the operating environment and its roles, processes, and solutions, and how they interact. Since Catena-X is under continuous development,the document refers, where appropriate, to dynamic content that can be found on the website of the Catena-X Association."}),"\n",(0,a.jsx)(t.h2,{id:"document-updates",children:"Document updates"}),"\n",(0,a.jsx)(t.p,{children:"The Catena-X Association releases updates to its operating model in regular intervals to always guarantee a well-functioning, up-to-date framework for its data space operations. Updates are developed within the framework regulations of the Catena-X Association and require approval from the Association\u2019s executive board. Every update of this operating model will automatically be applied to all Catena-X initiatives, existing participants, as well prospects, without further notice and individual approval. An update will be communicated in due time via the Catena-X Association."})]})}function u(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,a.jsx)(t,{...e,children:(0,a.jsx)(l,{...e})}):l(e)}},8453:(e,t,n)=>{n.d(t,{R:()=>s,x:()=>r});var a=n(6540);const i={},o=a.createContext(i);function s(e){const t=a.useContext(o);return a.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function r(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:s(e.components),a.createElement(o.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/254e3ee1.89e71a31.js b/assets/js/254e3ee1.89e71a31.js deleted file mode 100644 index 0bf304cf..00000000 --- a/assets/js/254e3ee1.89e71a31.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8399],{6747:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>c,contentTitle:()=>s,default:()=>u,frontMatter:()=>o,metadata:()=>r,toc:()=>d});var a=n(4848),i=n(8453);const o={sidebar_position:1},s="Why: Introduction",r={id:"operating-model/why-introduction/why-introduction",title:"Why: Introduction",description:"Relevance",source:"@site/versioned_docs/version-24.03/operating-model/why-introduction/why-introduction.md",sourceDirName:"operating-model/why-introduction",slug:"/operating-model/why-introduction/",permalink:"/docs/operating-model/why-introduction/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Operating Model",permalink:"/docs/operating-model/operating-model/"},next:{title:"Why: Understanding the Catena-X Data Space",permalink:"/docs/operating-model/why-understanding-the-catena-x-data-space/"}},c={},d=[{value:"Relevance",id:"relevance",level:2},{value:"Executive Summary",id:"executive-summary",level:2},{value:"Introduction",id:"introduction",level:3},{value:"Objectives",id:"objectives",level:3},{value:"Scope",id:"scope",level:3},{value:"Document updates",id:"document-updates",level:2}];function l(e){const t={h1:"h1",h2:"h2",h3:"h3",p:"p",...(0,i.R)(),...e.components};return(0,a.jsxs)(a.Fragment,{children:[(0,a.jsx)(t.h1,{id:"why-introduction",children:"Why: Introduction"}),"\n",(0,a.jsx)(t.h2,{id:"relevance",children:"Relevance"}),"\n",(0,a.jsx)(t.p,{children:"The Catena-X Operating Model Whitepaper is a normative document of the Catena-X Association. Normative documents outline rules, guidelines, and characteristics for activities and results for all participants within the Catena-X ecosystem. The Catena-X ecosystem includes Governance,Standardization,Certification,Development and Operations. These are established by consensus among the working groups and approved by the executive board of the Catena-X Association. As part of the Catena-X regulatory framework,this document is binding for all participants of the Catena-X ecosystem. This normative document is a foundational building block, allowing all participants to collaborate within a global ecosystem."}),"\n",(0,a.jsx)(t.h2,{id:"executive-summary",children:"Executive Summary"}),"\n",(0,a.jsx)(t.h3,{id:"introduction",children:"Introduction"}),"\n",(0,a.jsx)(t.p,{children:"With Catena-X, the automotive industry is creating targets a trustworthy, collaborative, open, and secure data space to enable a data-driven value chain for their relevant business processes. All participants can be connected in business process-centric end-to-end value chains, where everyone operates on an equal playing field, has sovereign control over their data and no lock-in effects occur. Thereby, the digitalization of intercompany processes and value chains, especially those of small and medium-sized companies, can be performed on a cost effective, timely and lasting basis. Further, it secures that market participants and competitors collaborate in a compliant and trusted way."}),"\n",(0,a.jsx)(t.h3,{id:"objectives",children:"Objectives"}),"\n",(0,a.jsx)(t.p,{children:"This document defines the operating model and processes required within the Catena-X ecosystem. The operating model is linked to the concepts and values of Gaia-X and the International Data Space Association (IDSA) to create the first open and collaborative data ecosystem for the automotive value chain. Thereby, Catena-X applies these concepts and extends them by integrating automotive-specific requirements for compliance, interoperability, and security. 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."}),"\n",(0,a.jsx)(t.h3,{id:"scope",children:"Scope"}),"\n",(0,a.jsx)(t.p,{children:"The Catena-X operating model describes the entire Catena-X ecosystem, focusing on the operating environment and its roles, processes, and solutions, and how they interact. Since Catena-X is under continuous development,the document refers, where appropriate, to dynamic content that can be found on the website of the Catena-X Association."}),"\n",(0,a.jsx)(t.h2,{id:"document-updates",children:"Document updates"}),"\n",(0,a.jsx)(t.p,{children:"The Catena-X Association releases updates to its operating model in regular intervals to always guarantee a well-functioning, up-to-date framework for its data space operations. Updates are developed within the framework regulations of the Catena-X Association and require approval from the Association\u2019s executive board. Every update of this operating model will automatically be applied to all Catena-X initiatives, existing participants, as well prospects, without further notice and individual approval. An update will be communicated in due time via the Catena-X Association."})]})}function u(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,a.jsx)(t,{...e,children:(0,a.jsx)(l,{...e})}):l(e)}},8453:(e,t,n)=>{n.d(t,{R:()=>s,x:()=>r});var a=n(6540);const i={},o=a.createContext(i);function s(e){const t=a.useContext(o);return a.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function r(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:s(e.components),a.createElement(o.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/26649072.839aad2f.js b/assets/js/26649072.839aad2f.js new file mode 100644 index 00000000..4c0a8dfc --- /dev/null +++ b/assets/js/26649072.839aad2f.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[5077],{581:e=>{e.exports=JSON.parse('{"metadata":{"permalink":"/catenax-ev.github.io.new/blog","page":1,"postsPerPage":10,"totalPages":1,"totalCount":4,"blogDescription":"Blog","blogTitle":"Blog"}}')}}]); \ No newline at end of file diff --git a/assets/js/27525b73.1a9db273.js b/assets/js/27525b73.1a9db273.js deleted file mode 100644 index 5b329ec1..00000000 --- a/assets/js/27525b73.1a9db273.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3380],{8108:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>l,contentTitle:()=>a,default:()=>h,frontMatter:()=>r,metadata:()=>o,toc:()=>d});var i=t(4848),s=t(8453);const r={sidebar_position:1,title:"Process Organization - From Idea to Release"},a=void 0,o={id:"working-model/process-from-idea-to-production/03-01-process-from-idea-to-production",title:"Process Organization - From Idea to Release",description:"Coming soon....",source:"@site/docs/working-model/03-process-from-idea-to-production/03-01-process-from-idea-to-production.md",sourceDirName:"working-model/03-process-from-idea-to-production",slug:"/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production",permalink:"/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Process Organization - From Idea to Release"},sidebar:"sidebar_working_model",previous:{title:"Tractus-X",permalink:"/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles"},next:{title:"Tractus-X Open Source Project Contribution Guide",permalink:"/docs/next/working-model/process-from-idea-to-production/03-02-Contribution-Guideline"}},l={},d=[{value:"Tractus-X Process Overview",id:"tractus-x-process-overview",level:2},{value:"Catena-X Process Overview",id:"catena-x-process-overview",level:2},{value:"Create new feature proposal",id:"create-new-feature-proposal",level:3},{value:"Refine feature",id:"refine-feature",level:3},{value:"Validate minimal feature content",id:"validate-minimal-feature-content",level:3},{value:"Check strategic fit",id:"check-strategic-fit",level:3},{value:"Refine feature to meet DoE",id:"refine-feature-to-meet-doe",level:3},{value:"Present feature proposal in Open Refinement",id:"present-feature-proposal-in-open-refinement",level:3},{value:"Check DoE",id:"check-doe",level:3},{value:"Present feature in Open Planning",id:"present-feature-in-open-planning",level:3},{value:"Commit to feature proposal",id:"commit-to-feature-proposal",level:3},{value:"Artifacts",id:"artifacts",level:2},{value:"Process roles",id:"process-roles",level:3},{value:"Minimal feature content",id:"minimal-feature-content",level:3},{value:"Definition of Entry (DoE)",id:"definition-of-entry-doe",level:3},{value:"Open Refinement",id:"open-refinement",level:3},{value:"Open Planning",id:"open-planning",level:3},{value:"Refine and Plan",id:"refine-and-plan",level:3},{value:"Feature assignment & validation",id:"feature-assignment--validation",level:3},{value:"Feature refinement",id:"feature-refinement",level:3},{value:"Feature validation and approval",id:"feature-validation-and-approval",level:3},{value:"Open Planning meeting",id:"open-planning-meeting",level:3},{value:"Open Release Planning Meeting",id:"open-release-planning-meeting",level:2},{value:"Decision-Making by Committers",id:"decision-making-by-committers",level:3},{value:"Outcome of Open Planning",id:"outcome-of-open-planning",level:3},{value:"Feature Development",id:"feature-development",level:2},{value:"Test Management",id:"test-management",level:2},{value:"Product Tests",id:"product-tests",level:3},{value:"Release Tests",id:"release-tests",level:3},{value:"Test Beds",id:"test-beds",level:3},{value:"Defect Management",id:"defect-management",level:3},{value:"Test Artifacts",id:"test-artifacts",level:3},{value:"Release Management",id:"release-management",level:2},{value:"Purpose of Catena-X Release Management",id:"purpose-of-catena-x-release-management",level:3},{value:"Key Responsibilities",id:"key-responsibilities",level:3},{value:"Coordination with Catena-X and Tractus-X",id:"coordination-with-catena-x-and-tractus-x",level:3},{value:"Release Lifecycle",id:"release-lifecycle",level:3},{value:"Benefits of Catena-X Release Management",id:"benefits-of-catena-x-release-management",level:3},{value:"Security Mangement",id:"security-mangement",level:2},{value:"Relevant Links",id:"relevant-links",level:2},{value:"FAQs",id:"faqs",level:2}];function c(e){const n={a:"a",admonition:"admonition",em:"em",h2:"h2",h3:"h3",li:"li",ol:"ol",p:"p",strong:"strong",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",ul:"ul",...(0,s.R)(),...e.components};return(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(n.p,{children:"Coming soon...."}),"\n",(0,i.jsx)(n.h2,{id:"tractus-x-process-overview",children:"Tractus-X Process Overview"}),"\n",(0,i.jsx)(n.p,{children:"We use the Committees and Expert Groups of the Catena-X e.V. to align, develop and release Catena-X specifications and standards (candidates) - also with other initiatives in the future. We use the Eclipse Tractus-X Project (e.g., TRGs), the Eclipse Development Process to refine, plan, develop and release our implementation features."}),"\n",(0,i.jsx)(n.h2,{id:"catena-x-process-overview",children:"Catena-X Process Overview"}),"\n",(0,i.jsx)(n.p,{children:"![From idea to release item](./assets/From Idea to Release Item.drawio.svg)"}),"\n",(0,i.jsx)(n.h3,{id:"create-new-feature-proposal",children:"Create new feature proposal"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Feature Author"}),"\n",(0,i.jsx)(n.li,{children:"Description: Anybody can contribute to a use case by creating a feature proposal in Tractus X. The person creating the feature proposal is the 'Feature Author' and responsbile for the feature proposal through the process."}),"\n",(0,i.jsx)(n.li,{children:"Possible outcomes: Feature proposal created"}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"refine-feature",children:"Refine feature"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Feature Author"}),"\n",(0,i.jsx)(n.li,{children:"Description: After creating the feature proposal the feature author has to continously refine the feature until it contains the minimal feature content, so that it can be valited. This step might be obsolete if all information are added when creating the feature proposal."}),"\n",(0,i.jsx)(n.li,{children:"Possible outcomes: Submit for validation"}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"validate-minimal-feature-content",children:"Validate minimal feature content"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Topic owner (Committee or Expert Group)"}),"\n",(0,i.jsx)(n.li,{children:"Description: The topic owner is responsible to assess if the minimal feature content requirements are met by the feature proposal."}),"\n",(0,i.jsxs)(n.li,{children:["Possible outcomes:","\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Minimal feature content not complete: The feature proposal is being send back to the feature author with the request to further refine the feature proposal"}),"\n",(0,i.jsx)(n.li,{children:"Minimal feature content complete"}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"check-strategic-fit",children:"Check strategic fit"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Topic owner"}),"\n",(0,i.jsx)(n.li,{children:"Description: Once the feature proposal contains at least the minimal feature content, its strategic fit is going to be evaluated by the topic owner"}),"\n",(0,i.jsxs)(n.li,{children:["Possible outcomes:","\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Feature proposal fit strategy: If the feature proposal strategically fits it is going to be added to the Inbox."}),"\n",(0,i.jsx)(n.li,{children:"Strategic fit cant be assest: If the strategic fit cant be assest by the topic owner the feature proposal is being send back to the feature author with the request to further refine the feature proposal."}),"\n",(0,i.jsx)(n.li,{children:"Feature proposal does NOT fit: If the topic owner assess the feature proposal as not fitting the strategy, the feature proposal is going to be rejected. In this case the feature proposal is not going to be implemented."}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"refine-feature-to-meet-doe",children:"Refine feature to meet DoE"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Feature author"}),"\n",(0,i.jsx)(n.li,{children:"Description: Once the feature is validated, the feature author has to further refine the feature to meet the DoE. The refinement can be done by setting up individual refinement meetings for the feature proposal and inviting relevant people or by presenting the feature proposal in the Open Refinement. Each feature proposal has to be presented at least once in the Open Refinement so that the whole community has the chance to provide feedback."}),"\n",(0,i.jsx)(n.li,{children:"Possbile outcomes: DoE complete"}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"present-feature-proposal-in-open-refinement",children:"Present feature proposal in Open Refinement"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Feature author"}),"\n",(0,i.jsx)(n.li,{children:"Description: The feature proposal is presented in the Open Refinement to receive feedback from the community."}),"\n",(0,i.jsx)(n.li,{children:"Possible outcomes: DoE complete"}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"check-doe",children:"Check DoE"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Committers"}),"\n",(0,i.jsx)(n.li,{children:"Description: Once the DoE for a feature proposal are complete, the committers are going to assess the maturity of the feature proposal."}),"\n",(0,i.jsxs)(n.li,{children:["Possible outcomes:","\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"DoE met: If the committers assess the feature proposal mature enough, it is going to be added to the Backlog."}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"present-feature-in-open-planning",children:"Present feature in Open Planning"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Feature author"}),"\n",(0,i.jsx)(n.li,{children:"Description: The feature proposal is going to be presented in the Open Planning to be prioritized and be planned for the release."}),"\n",(0,i.jsx)(n.li,{children:"Possible outcomes: Feature proposal was presented"}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"commit-to-feature-proposal",children:"Commit to feature proposal"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Committers"}),"\n",(0,i.jsx)(n.li,{children:"Description: The committers are deciding on the scope of the upcoming release. All feature proposals presented in the Open Planning are going to be prioritized."}),"\n",(0,i.jsxs)(n.li,{children:["Possible outcomes:","\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Committed: The feature proposal gets the committment from the committers and is added to the upcoming release."}),"\n",(0,i.jsx)(n.li,{children:"Not committed: The feature proposal is not committed by the committers and wont be part of the upcoming release. The feature proposal is going to be presented again in the Open Planning for the following release."}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,i.jsx)(n.h2,{id:"artifacts",children:"Artifacts"}),"\n",(0,i.jsx)(n.h3,{id:"process-roles",children:"Process roles"}),"\n",(0,i.jsxs)(n.table,{children:[(0,i.jsx)(n.thead,{children:(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.th,{children:"Role"}),(0,i.jsx)(n.th,{children:"Description"})]})}),(0,i.jsxs)(n.tbody,{children:[(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Feature author"}),(0,i.jsx)(n.td,{children:"The feature author is going to be the primary point of contact for all questions related to a feature proposal. The feature author carries the feature proposal through the validation and refinement process."})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Topic Owner"}),(0,i.jsx)(n.td,{children:"The topic owner validates new feature proposals for a defined topic (product) to make sure feature proposals align with the strategy for it. The topic owner is usually going to be a Committee."})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Committer"}),(0,i.jsx)(n.td,{children:(0,i.jsx)(n.em,{children:"See Tractus X Committer description"})})]})]})]}),"\n",(0,i.jsx)(n.h3,{id:"minimal-feature-content",children:"Minimal feature content"}),"\n",(0,i.jsx)(n.p,{children:"The minimal feature content is a subset of the DoE. It defines the minimal information that need to be provided before a feature proposal can enter the validation and refinement process."}),"\n",(0,i.jsxs)(n.table,{children:[(0,i.jsx)(n.thead,{children:(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.th,{children:"Information"}),(0,i.jsx)(n.th,{children:"Description"})]})}),(0,i.jsxs)(n.tbody,{children:[(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Feature author"}),(0,i.jsx)(n.td,{children:"Responsbile person to carry the feature proposal through the validation and refinement process"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Description"}),(0,i.jsx)(n.td,{children:"Description of WHAT the feature proposal is about."})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Business value"}),(0,i.jsx)(n.td,{children:"Description of WHY the feature proposal is relevant."})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Acceptance criteria"}),(0,i.jsx)(n.td,{children:"Conditions that must be satisfied for the feature proposal to be accepted"})]})]})]}),"\n",(0,i.jsx)(n.h3,{id:"definition-of-entry-doe",children:"Definition of Entry (DoE)"}),"\n",(0,i.jsxs)(n.table,{children:[(0,i.jsx)(n.thead,{children:(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.th,{children:"Information"}),(0,i.jsx)(n.th,{children:"Description"})]})}),(0,i.jsxs)(n.tbody,{children:[(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Minimal feature content"}),(0,i.jsx)(n.td,{children:(0,i.jsx)(n.em,{children:"see Minimal feature content"})})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Dependencies"}),(0,i.jsx)(n.td,{children:"Dependencies with other products or issues are identified and categorized via GitHub labels"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Risks"}),(0,i.jsx)(n.td,{children:"Known rsiks are properly adressed"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Enablers"}),(0,i.jsxs)(n.td,{children:["Required enablers are defined (",(0,i.jsx)(n.em,{children:"isnt that a dependency?"}),")"]})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"High level architecture (building block view)"}),(0,i.jsx)(n.td,{})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Key dates and milestones"}),(0,i.jsx)(n.td,{children:"Key dates and milestones are defined using GitHub milestone declaration"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Testing"}),(0,i.jsx)(n.td,{children:"Test scenarios, test cases and test data are available"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Effort estimation"}),(0,i.jsx)(n.td,{children:"The effort to implement the feature is estimated (based on story points)"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Developer"}),(0,i.jsx)(n.td,{children:"Developer team for feature implementation defined"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Issues"}),(0,i.jsx)(n.td,{children:"First implementation issues are defined in the corresponding repository and linked to the feature (optional)"})]})]})]}),"\n",(0,i.jsx)(n.h3,{id:"open-refinement",children:"Open Refinement"}),"\n",(0,i.jsx)(n.p,{children:"The Open refinement is ment to..."}),"\n",(0,i.jsxs)(n.p,{children:["The Catena-X association communicates and coordiantes the open refinement and open planning meetings via the a Tractus-X ",(0,i.jsx)(n.a,{href:"https://eclipse-tractusx.github.io/blog",children:"News Page"})," and the Tractus-X ",(0,i.jsx)(n.a,{href:"https://accounts.eclipse.org/mailing-list/tractusx-dev",children:"Mailing List"}),". Feature authors must make sure to subscribe! The meetings are also be published (with meeting session and calender.ics) on the open meetings page."]}),"\n",(0,i.jsx)(n.h3,{id:"open-planning",children:"Open Planning"}),"\n",(0,i.jsx)(n.p,{children:"During the Open Planning the items for upcoming release are planned. All feature proposals that were handed in on time are going to be presented to the audience. The Open Planning is the last chance to provide feedback about the scope of the feature proposal. After the presentation of the feature proposal by the feature author, the committers are going to prioritize the feature proposal in alignment with the topic owner. A feature proposal becomes part of the upcoming release only by receiving the commitment by the committes and not by being presented in the Open Planning!"}),"\n",(0,i.jsx)(n.p,{children:"To enter the Open Plannung a feature proposal must meet the DoE X days before the Open Planning (Cut-Off)! Feature proposal that meet the DoE after the Cut-Off won't be considered in the Open Planning. This means it will likely be deferred to a future release."}),"\n",(0,i.jsxs)(n.table,{children:[(0,i.jsx)(n.thead,{children:(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.th,{children:"Tasks"}),(0,i.jsx)(n.th,{children:"Documents (e.g. Standards)"}),(0,i.jsx)(n.th,{children:"Reference Impl."}),(0,i.jsx)(n.th,{children:"Outcome"})]})}),(0,i.jsxs)(n.tbody,{children:[(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Feature Proposal"}),(0,i.jsx)(n.td,{children:"Refinement Meetings"}),(0,i.jsx)(n.td,{children:"In sig release"}),(0,i.jsx)(n.td,{children:"Proposals by C-X e.V. Overview of all feature proposals incl. acceptance criteria. (Task break down over all affected teams / dependencies.) DOE ???"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Feature Commitment"}),(0,i.jsx)(n.td,{children:"Planning Meetings"}),(0,i.jsx)(n.td,{children:"In sig release"}),(0,i.jsx)(n.td,{children:"Decision by committer group Committed, prioritized backlog for the next release. Coordination / refinement / prioritization of new ideas, business requirements, features (scope C-X only)"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{}),(0,i.jsx)(n.td,{children:"C-X association tooling"}),(0,i.jsx)(n.td,{children:"Sig-release"}),(0,i.jsx)(n.td,{children:"Priotized list of Catena-X business requirements (proposal)"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{}),(0,i.jsx)(n.td,{children:"C-X association tooling"}),(0,i.jsx)(n.td,{children:"Sig-release: Discussions, Issues"}),(0,i.jsx)(n.td,{children:"Product Priotized list of overall business requirements"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{}),(0,i.jsx)(n.td,{children:"Association meetings (e.g., roadmap)"}),(0,i.jsx)(n.td,{children:"Tractus-X open meetings (e.g., refinement, planning, \u2026)"}),(0,i.jsx)(n.td,{children:"Roadmap and issues updated (?)"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Development of Deliverable"}),(0,i.jsx)(n.td,{children:"Create (normative) documents"}),(0,i.jsx)(n.td,{children:"Create open source software / KITs"}),(0,i.jsx)(n.td,{children:"Deliverables created (Normative Documents, KITs, Reference Implementation (complies to C-X Standards))"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Review of Deliverables"}),(0,i.jsx)(n.td,{children:"Content reviews in Expert Group"}),(0,i.jsx)(n.td,{children:"Code reviews (PRs) in Tractus-X"}),(0,i.jsx)(n.td,{children:"Deliverables reviewed"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Testing of Deliverables"}),(0,i.jsx)(n.td,{children:"Member Sounding"}),(0,i.jsx)(n.td,{children:"Testing of software, test phase, test management, etc."}),(0,i.jsx)(n.td,{children:"Deliverables tested"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Release Deliverables"}),(0,i.jsx)(n.td,{children:"Quality Criteria and Style Guides"}),(0,i.jsx)(n.td,{children:"Tractus-X Release Guidelines"}),(0,i.jsx)(n.td,{children:"Deliverables released"})]})]})]}),"\n",(0,i.jsx)(n.h3,{id:"refine-and-plan",children:"Refine and Plan"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Who can propose a feature?"}),"*\nAnyone can ",(0,i.jsx)(n.strong,{children:"propose a feature"}),", including Committees, Expert Groups, and other initiatives. However, we require a dedicated feature owner for further refinement and the breakdown into implementation issues."]}),"\n",(0,i.jsx)(n.p,{children:"** There are two options regarding resource commitment:"}),"\n",(0,i.jsxs)(n.ol,{children:["\n",(0,i.jsx)(n.li,{children:"If you have dedicated developer resources, your developer team will create the implementation issues at the user story level."}),"\n",(0,i.jsx)(n.li,{children:"If you do not have dedicated developer resources, interested developers team can create the implementation issues."}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"feature-assignment--validation",children:"Feature assignment & validation"}),"\n",(0,i.jsx)(n.p,{children:"Responsible: Committee & Expert Group"}),"\n",(0,i.jsx)(n.p,{children:"Once a new feature proposal has been made for the Tractus-X project, it enters a validation phase where the Committees assigns it to the relevant Expert Group."}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Validation:"})," The Committee assignes the feature to the matching Expert Group (at least two specific contacts). The Expert Group will review the proposal to ensure it aligns with the project's goals and standards."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Request for Additional Details:"})," If the proposal lacks necessary details, the reviewing bodies may ask the author for additional information or clarification."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"feature-refinement",children:"Feature refinement"}),"\n",(0,i.jsx)(n.p,{children:"Responsible: Feature author"}),"\n",(0,i.jsx)(n.p,{children:"After being validated and initially prioritized by the Expert Group, the refinement process starts. The feature author must gather their peer group (such as experts, contributors, and committers) for example by publishing a virtual meeting invite for the feature issue to be refined."}),"\n",(0,i.jsxs)(n.p,{children:["The goal is to have features that fullfill the following ",(0,i.jsx)(n.strong,{children:"Definition of Entry (DoE)"}),":"]}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Feature author defined: The designated point of contact for any questions related to the feature during the refinement, planning and development phase (e.g., subject matter expert). Not necessarily responsible for the technical implementation of a feature."}),"\n",(0,i.jsx)(n.li,{children:"Feature desciption is available"}),"\n",(0,i.jsx)(n.li,{children:"Required enablers are defined and aligned (e.g., architecutre, infrastructure, compliance)"}),"\n",(0,i.jsx)(n.li,{children:"High-level architecture (building-block-view)"}),"\n",(0,i.jsx)(n.li,{children:"Key dates and milestones are defined using GitHub milestone declaration"}),"\n",(0,i.jsx)(n.li,{children:"Business value is defined"}),"\n",(0,i.jsx)(n.li,{children:"Test scenarios, test cases and test data are available"}),"\n",(0,i.jsx)(n.li,{children:"Accpetance criteria are defined"}),"\n",(0,i.jsx)(n.li,{children:"Feature estimation available (based on story points)"}),"\n",(0,i.jsx)(n.li,{children:"Developer team for feature implementation defined"}),"\n",(0,i.jsx)(n.li,{children:"Dependencies with other products or issues are identified and categorized via GitHub labels"}),"\n",(0,i.jsx)(n.li,{children:"Known rsiks are properly adressed"}),"\n",(0,i.jsx)(n.li,{children:"No open questions left"}),"\n",(0,i.jsx)(n.li,{children:"First implementation issues are defined in the corresponding repository and linked to the feature (optional)\n..."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"Ultimately, the decision regarding maturity is made jointly by the affected products and contributers in the open refinement meetings."}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Feature author responsibility in the refinement:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Responding to feedback:"})," The author is responsible for addressing any feedback provided by the Expert Group or Committee. This may include providing additional details or making revisions to the proposal."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Implementation issues:"})," If necessary, the author may need to create implementation issues in the repository of the corresponding product to break down the feature into manageable pieces. This aids in tracking progress and facilitates easier review."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Timely Updates:"})," The author must update the feature details within the given timeframe. Prompt responses and updates are crucial to keep the proposal moving forward."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"feature-validation-and-approval",children:"Feature validation and approval"}),"\n",(0,i.jsx)(n.p,{children:"Responsible: Feature author"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Approval for Planning:"})," Once the feature has sufficient details and meets the Definition of Done (DoE), the feature author needs to submit it to the Committee or Expert Group (specific contacts mentioned in the feature) and a committer for approval."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Status of the Feature"})," in the SIG-release repository will be set to 'Backlog' by a committer (in alignment between Expert Group, Committee and the respective feature author). This status indicates whether the feature is included in the list for open planning or not."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Continuous Communication:"})," The author should maintain close communication via the feature issue with the Expert Group and Committee throughout this process to ensure prompt resolution of any issues."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"open-planning-meeting",children:"Open Planning meeting"}),"\n",(0,i.jsx)(n.p,{children:"Responsible: Feature author"}),"\n",(0,i.jsx)(n.p,{children:"During the open planning meeting, the feature author must present the features they are responsible for, and the committers will prioritize them in alignment with the Expert Group."}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Open Planning Cut-off:"})," Features must have mandatory content from the DoE and approval (2.3) before the open planning meeting. This is a critical deadline."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Consequences of Missing Deadline:"})," If the feature does not meet the DoE or missing the approval by the open planning, it will not be included in the planning cycle. This means it will likely be deferred to a future release."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"By following this process, authors can ensure their feature proposals are considered for inclusion in the Tractus-X project's planning. It is important to be proactive, responsive, and detail-oriented to successfully navigate the post-proposal phase."}),"\n",(0,i.jsx)(n.h2,{id:"open-release-planning-meeting",children:"Open Release Planning Meeting"}),"\n",(0,i.jsx)(n.p,{children:"Once a feature is through the propose and refinement process (2.) the feature will be presented in the open planning meeting and the committer will prioritize them based on the strategic / technical fit and ressource commitment in alignment with the Expert Groups of the Catena-X association."}),"\n",(0,i.jsx)(n.p,{children:"The open release planning meeting also called Program Increment (PI) planning is a critical event in the Tractus-X project where contributors, committers, Expert Groups, and Committees come together to define the scope for the next release. This process ensures that the project's roadmap is aligned with stakeholder expectations and the project's strategic objectives. Here's how the release Planning process typically unfolds:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Attendees:"})," Contributors, committers, Expert Groups, and Committees attend the release planning meeting."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Scope Definition:"})," The main objective of this meeting is to determine the scope of the upcoming release. This involves discussing the refined features and confirming the prioritized backlog."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Priorize backlog:"})," The backlog will be reviewed to ensure that it aligns with the project's strategic direction and available resources. Before the open release planning meeting, Committees and Expert Groups can pre-prioritize the backlog. However, the final prioritization is done by the committers."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"decision-making-by-committers",children:"Decision-Making by Committers"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Realistic Scope Assessment:"})," Committers play a crucial role in the release planning process. They assess the proposed features and backlog issues to determine what is realistically achievable in the next release, considering review, maintenance, and test efforts."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Final Prioritization:"})," Committers have the final call on the prioritization of issues, ensuring that the most critical and feasible items are included in the release scope."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Resource Allocation:"})," Decisions regarding the allocation of resources, including developer time and testing infrastructure, are made to support the prioritized issues."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"outcome-of-open-planning",children:"Outcome of Open Planning"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Priortized backlog:"})," Decision by committer group Committed, prioritized backlog for the next release."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Resource commitment:"})," Teams and individuals commit to the work they will deliver, fostering accountability and setting clear expectations for the upcoming release."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Updated roadmap:"})," The project's roadmap is updated to reflect the decisions made during the release planning, providing transparency to stakeholders and the community. [TO-DO clarifiy location of the roadmap / where will this be published]"]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Decisions are documented:"})," All decisions and commitments made during the planning are documented in the decision board or directly in the comment section of a feature. [TO-DO link to the architecture decsion board]"]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Communication plan:"})," After the planning a communication via mailing-list will be done by the project lead including the relevant links and decisions."]}),"\n"]}),"\n",(0,i.jsx)(n.h2,{id:"feature-development",children:"Feature Development"}),"\n",(0,i.jsxs)(n.ol,{children:["\n",(0,i.jsx)(n.li,{children:"Sprint Planning by committer"}),"\n",(0,i.jsx)(n.li,{children:"Sprint Review by committer"}),"\n",(0,i.jsx)(n.li,{children:"Recommended: Product demo as soon as relevant feature(s) are ready to show to get feedback from the community (prototypes are also welcome)"}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"For open-source reference implementations please refer to the Eclipse Handbook and the Tractus-X release guidelines.."}),"\n",(0,i.jsx)(n.h2,{id:"test-management",children:"Test Management"}),"\n",(0,i.jsx)(n.p,{children:"The software testing of reference implementations is sponsored and coordinated by the Catena-X association. It includes the following three levels:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Level 1: Product Tests"}),"\n",(0,i.jsx)(n.li,{children:"Level 2: Release Tests"}),"\n",(0,i.jsx)(n.li,{children:"Level 3: Test Beds for 3rd Party Solutions"}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"product-tests",children:"Product Tests"}),"\n",(0,i.jsx)(n.p,{children:"Product tests include unit, regression and integration tests based on product helm charts with individual dependencies."}),"\n",(0,i.jsx)(n.p,{children:"Contributors can create pull requests (PRs) for their developed features at any time. A PR must be assigned to a feature issue committed in the open planning. To get faster code reviews, it is recommended to submit small PRs."}),"\n",(0,i.jsx)(n.p,{children:"A PR must include the feature code, adapted helm chart(s), technical documentation as well as product tests (e.g., unit tests) and product integration tests (e.g., by using helm charts or mocks). All these tests must be passed locally before the PR can be submitted."}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Hint:"})," You can find the latest versions of the product helm charts in our release changelog."]}),"\n",(0,i.jsx)(n.admonition,{type:"info",children:(0,i.jsx)(n.p,{children:"ToDo: Insert Link! Previous link was broken."})}),"\n",(0,i.jsx)(n.p,{children:"At least two committer must review the PR, including the source code, test results and the compliance with the Tractus-X release guidelines (TRGs), and approve the merging of these changes. In case there are change requests or defects that a committer cannot solve, the contributor must address these changes before merging."}),"\n",(0,i.jsx)(n.p,{children:"The PR and the related product tests are part of the open-source development process resulting in a new product (rc-)version."}),"\n",(0,i.jsx)(n.h3,{id:"release-tests",children:"Release Tests"}),"\n",(0,i.jsxs)(n.p,{children:["The release tests include e2e tests for the Catena-X operating system (cxOS) itself as well as for the cxOS with open-source applications (e.g., Trace-X) based on ",(0,i.jsx)(n.a,{href:"https://github.com/eclipse-tractusx/tractus-x-umbrella",children:"umbrella helm charts"}),". Thereby, various product combinations of umbrella helm charts are possible."]}),"\n",(0,i.jsx)(n.p,{children:"The purpose of release testing is for the feature requestor to validate the end-to-end business flow using various test executions and to confirm that the acceptance criteria have been fulfilled (business value)."}),"\n",(0,i.jsxs)(n.p,{children:["Before a product can participate in a release test, it must fulfill the following ",(0,i.jsx)(n.strong,{children:"prerequisites"}),":"]}),"\n",(0,i.jsx)(n.p,{children:"For release 24.08, Expert Groups of the Catena-X association must ..."}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["create new or refine existing e2e test cases, test data and documentation as .md-file in Tractus-X ",(0,i.jsx)(n.a,{href:"https://github.com/eclipse-tractusx/sig-testing",children:"sig-testing"}),"."]}),"\n",(0,i.jsx)(n.li,{children:"provide at least one tester for the execution of the e2e test cases (if not fully automated)."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"The Catena-X association will provide a test management team including ..."}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"a test manager that creates the test plan and report, coordinates the test execution."}),"\n",(0,i.jsx)(n.li,{children:"a DevSecOps engineer for setting up test environment infrastructure (based on the hotel budapest approach)."}),"\n",(0,i.jsx)(n.li,{children:"a DevSecOps engineer for deploying the umbrella helm chart of release candidates (supported by Tractus-X committer, if not fully automated yet)."}),"\n"]}),"\n",(0,i.jsxs)(n.p,{children:["The release tests result in a validated version of the cxOS, which is made available through quarterly Eclipse ",(0,i.jsx)(n.a,{href:"https://projects.eclipse.org/projects/automotive.tractusx",children:"Tractus-X releases"}),"."]}),"\n",(0,i.jsx)(n.h3,{id:"test-beds",children:"Test Beds"}),"\n",(0,i.jsx)(n.p,{children:"Coming soon..."}),"\n",(0,i.jsx)(n.h3,{id:"defect-management",children:"Defect Management"}),"\n",(0,i.jsxs)(n.p,{children:["Defects or unexpected behavior must be reported as bugs in the ",(0,i.jsx)(n.a,{href:"https://github.com/eclipse-tractusx/sig-release/issues/new/choose",children:"sig-release repo"}),"."]}),"\n",(0,i.jsx)(n.h3,{id:"test-artifacts",children:"Test Artifacts"}),"\n",(0,i.jsx)(n.p,{children:"There are various testing artifacts, that are either managed in Tractus-X GitHub or the Test Management Tool."}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["In ",(0,i.jsx)(n.strong,{children:"GitHub"})," we manage the different user journys and related business scenarios as .md files."]}),"\n",(0,i.jsxs)(n.li,{children:["In the ",(0,i.jsx)(n.strong,{children:"Test Management Tool"})," we manage test cases, test sets (opt.), test exectuions as well as test plans and reports."]}),"\n"]}),"\n",(0,i.jsxs)(n.table,{children:[(0,i.jsx)(n.thead,{children:(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.th,{children:"Artifact"}),(0,i.jsx)(n.th,{children:"Artifact Owner"}),(0,i.jsx)(n.th,{children:"# per Release"})]})}),(0,i.jsxs)(n.tbody,{children:[(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Test Case(s)"}),(0,i.jsx)(n.td,{children:"Product / Expert Group"}),(0,i.jsx)(n.td,{children:"n"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Test Set(s)"}),(0,i.jsx)(n.td,{children:"Product / Expert Group"}),(0,i.jsx)(n.td,{children:"n"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Test Execution(s)"}),(0,i.jsx)(n.td,{children:"Product / Expert Group"}),(0,i.jsx)(n.td,{children:"n"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Test Plan"}),(0,i.jsx)(n.td,{children:"Test Manager"}),(0,i.jsx)(n.td,{children:"1"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Test Report"}),(0,i.jsx)(n.td,{children:"Test Manager"}),(0,i.jsx)(n.td,{children:"1"})]})]})]}),"\n",(0,i.jsx)(n.h2,{id:"release-management",children:"Release Management"}),"\n",(0,i.jsxs)(n.p,{children:["Catena-X ",(0,i.jsx)(n.strong,{children:"Release Management"})," is a crucial component within the broader Catena-X ecosystem, focused on orchestrating and overseeing the release cycles of both Catena-X and Tractus-X. Here's an overview of how Catena-X Release Management operates and coordinates these releases:"]}),"\n",(0,i.jsx)(n.h3,{id:"purpose-of-catena-x-release-management",children:"Purpose of Catena-X Release Management"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Streamlining Releases"}),": Catena-X Release Management aims to streamline the process of releasing updates, upgrades, and new features for both Catena-X and Tractus-X."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Ensuring Compatibility"}),": It ensures that releases across different components are compatible and seamlessly integrate with each other."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Quality Assurance"}),": Quality assurance and testing are integral parts, ensuring that released versions meet high standards of performance, security, and reliability."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"key-responsibilities",children:"Key Responsibilities"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Release Planning"}),": This involves strategizing the timing and content of releases based on development milestones, customer feedback, and market demands."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Version Control"}),": Managing versioning across different components to maintain clarity and consistency across software, standards and deployment."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Coordination with Development Teams"}),": Collaborating closely with development teams across Expert Groups, Committees and the broader Open Source community to align on release schedules, feature prioritization, and bug fixes."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Testing and QA"}),": Overseeing comprehensive testing processes to identify and address issues before deployment (see ##Test Management)."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Documentation and Communication"}),": Ensuring that release notes, documentation, and communication channels are updated and accessible to stakeholders."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"coordination-with-catena-x-and-tractus-x",children:"Coordination with Catena-X and Tractus-X"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Catena-X Integration"}),": Coordinating releases between Catena-X and Tractus-X involves understanding the dependencies and interactions between both components of our ecosystem."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Feature Alignment"}),": Ensuring that standards developed for Catena-X and features & KITs developed for Tractus-X are aligned with overarching goals and customer requirements."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Interoperability"}),": Guaranteeing interoperability between Catena-X standards and Tractus-X features, such as reference implementations to facilitate seamless data exchange and functionality."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"release-lifecycle",children:"Release Lifecycle"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Preparation Phase"}),": Developing and communicating the overarching release timeline including relevant milestones to all stakeholders across Tractus-X and Catena-X."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Planning Phase"}),": Identifying release goals, feature prioritization, and creating a roadmap for implementation."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Development Phase"}),": Actively working with development teams to build and test new features and enhancements."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Testing and QA Phase"}),": Conducting rigorous testing, including integration testing between Catena-X and Tractus-X elements."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Deployment Phase"}),": Deploying releases to production environments while ensuring minimal disruption and downtime. While Catena-X is responsible for providing governance and guidelines for deployments, the actual deployment to productive environments lies within the responsibility of our Operating Companies and participants of the Catena-X Data Space."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Monitoring and Feedback"}),": Monitoring post-release performance, gathering feedback from users, and iterating for continuous improvement."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"benefits-of-catena-x-release-management",children:"Benefits of Catena-X Release Management"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Efficiency"}),": Streamlining release processes leads to faster time-to-market for new features and updates."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Quality Assurance"}),": Rigorous testing and QA practices enhance the overall quality and reliability of software releases."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Alignment"}),": Ensures alignment with business objectives, customer needs, and industry standards."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Risk Mitigation"}),": Proactive identification and mitigation of risks associated with releases."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"In essence, Catena-X Release Management acts as a central hub that coordinates the complex interplay between Catena-X and Tractus-X releases, ensuring smooth integration, high-quality deliverables, and customer satisfaction."}),"\n",(0,i.jsx)(n.h2,{id:"security-mangement",children:"Security Mangement"}),"\n",(0,i.jsx)(n.admonition,{type:"info",children:(0,i.jsx)(n.p,{children:"ToDo: Security, Managing and Reporting Vulnerabilities, Communication"})}),"\n",(0,i.jsx)(n.h2,{id:"relevant-links",children:"Relevant Links"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:(0,i.jsx)(n.a,{href:"https://eclipse-tractusx.github.io/community/intro",children:"Catena-X Community Introduction"})}),"\n"]}),"\n",(0,i.jsx)(n.h2,{id:"faqs",children:"FAQs"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"How are the open meetings communicated?"}),"\nThe Catena-X association will communicate and coordiante the open refinement and open planning meetings vi the a Tractus-X ",(0,i.jsx)(n.a,{href:"https://eclipse-tractusx.github.io/blog",children:"News Page"})," and the Tractus-X ",(0,i.jsx)(n.a,{href:"https://accounts.eclipse.org/mailing-list/tractusx-dev",children:"Mailing List"}),". Please make sure that you subscribe. The meetings will also be published (with meeting session and calender.ics) on the open meetings page."]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Who can propose a feature?"}),"\nAnyone can ",(0,i.jsx)(n.strong,{children:"propose a feature"}),", including Committees, Expert Groups, and other initiatives. However, we require a dedicated feature author for further refinement and the breakdown into implementation issues."]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"How to handle dependencies?"}),"\nDependencies can be discussed in our open refinement meetings as well as via our other communication channels (e.g. martix chat or bilateral sessions). Please refer to our Tractus-X ",(0,i.jsx)(n.a,{href:"https://eclipse-tractusx.github.io/community/intro",children:"communication rules"}),"."]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Who gives access to the sig-release repository to enable planning process?"}),"\nPlease refer to our Tractus-X ",(0,i.jsx)(n.a,{href:"https://eclipse-tractusx.github.io/docs/oss/getting-started",children:"Getting Started Guide"}),"."]})]})}function h(e={}){const{wrapper:n}={...(0,s.R)(),...e.components};return n?(0,i.jsx)(n,{...e,children:(0,i.jsx)(c,{...e})}):c(e)}},8453:(e,n,t)=>{t.d(n,{R:()=>a,x:()=>o});var i=t(6540);const s={},r=i.createContext(s);function a(e){const n=i.useContext(r);return i.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function o(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:a(e.components),i.createElement(r.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/27525b73.57797350.js b/assets/js/27525b73.57797350.js new file mode 100644 index 00000000..951132fb --- /dev/null +++ b/assets/js/27525b73.57797350.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3380],{8108:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>l,contentTitle:()=>a,default:()=>h,frontMatter:()=>r,metadata:()=>o,toc:()=>d});var i=t(4848),s=t(8453);const r={sidebar_position:1,title:"Process Organization - From Idea to Release"},a=void 0,o={id:"working-model/process-from-idea-to-production/03-01-process-from-idea-to-production",title:"Process Organization - From Idea to Release",description:"Coming soon....",source:"@site/docs/working-model/03-process-from-idea-to-production/03-01-process-from-idea-to-production.md",sourceDirName:"working-model/03-process-from-idea-to-production",slug:"/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production",permalink:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Process Organization - From Idea to Release"},sidebar:"sidebar_working_model",previous:{title:"Tractus-X",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles"},next:{title:"Tractus-X Open Source Project Contribution Guide",permalink:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-02-Contribution-Guideline"}},l={},d=[{value:"Tractus-X Process Overview",id:"tractus-x-process-overview",level:2},{value:"Catena-X Process Overview",id:"catena-x-process-overview",level:2},{value:"Create new feature proposal",id:"create-new-feature-proposal",level:3},{value:"Refine feature",id:"refine-feature",level:3},{value:"Validate minimal feature content",id:"validate-minimal-feature-content",level:3},{value:"Check strategic fit",id:"check-strategic-fit",level:3},{value:"Refine feature to meet DoE",id:"refine-feature-to-meet-doe",level:3},{value:"Present feature proposal in Open Refinement",id:"present-feature-proposal-in-open-refinement",level:3},{value:"Check DoE",id:"check-doe",level:3},{value:"Present feature in Open Planning",id:"present-feature-in-open-planning",level:3},{value:"Commit to feature proposal",id:"commit-to-feature-proposal",level:3},{value:"Artifacts",id:"artifacts",level:2},{value:"Process roles",id:"process-roles",level:3},{value:"Minimal feature content",id:"minimal-feature-content",level:3},{value:"Definition of Entry (DoE)",id:"definition-of-entry-doe",level:3},{value:"Open Refinement",id:"open-refinement",level:3},{value:"Open Planning",id:"open-planning",level:3},{value:"Refine and Plan",id:"refine-and-plan",level:3},{value:"Feature assignment & validation",id:"feature-assignment--validation",level:3},{value:"Feature refinement",id:"feature-refinement",level:3},{value:"Feature validation and approval",id:"feature-validation-and-approval",level:3},{value:"Open Planning meeting",id:"open-planning-meeting",level:3},{value:"Open Release Planning Meeting",id:"open-release-planning-meeting",level:2},{value:"Decision-Making by Committers",id:"decision-making-by-committers",level:3},{value:"Outcome of Open Planning",id:"outcome-of-open-planning",level:3},{value:"Feature Development",id:"feature-development",level:2},{value:"Test Management",id:"test-management",level:2},{value:"Product Tests",id:"product-tests",level:3},{value:"Release Tests",id:"release-tests",level:3},{value:"Test Beds",id:"test-beds",level:3},{value:"Defect Management",id:"defect-management",level:3},{value:"Test Artifacts",id:"test-artifacts",level:3},{value:"Release Management",id:"release-management",level:2},{value:"Purpose of Catena-X Release Management",id:"purpose-of-catena-x-release-management",level:3},{value:"Key Responsibilities",id:"key-responsibilities",level:3},{value:"Coordination with Catena-X and Tractus-X",id:"coordination-with-catena-x-and-tractus-x",level:3},{value:"Release Lifecycle",id:"release-lifecycle",level:3},{value:"Benefits of Catena-X Release Management",id:"benefits-of-catena-x-release-management",level:3},{value:"Security Mangement",id:"security-mangement",level:2},{value:"Relevant Links",id:"relevant-links",level:2},{value:"FAQs",id:"faqs",level:2}];function c(e){const n={a:"a",admonition:"admonition",em:"em",h2:"h2",h3:"h3",li:"li",ol:"ol",p:"p",strong:"strong",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",ul:"ul",...(0,s.R)(),...e.components};return(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(n.p,{children:"Coming soon...."}),"\n",(0,i.jsx)(n.h2,{id:"tractus-x-process-overview",children:"Tractus-X Process Overview"}),"\n",(0,i.jsx)(n.p,{children:"We use the Committees and Expert Groups of the Catena-X e.V. to align, develop and release Catena-X specifications and standards (candidates) - also with other initiatives in the future. We use the Eclipse Tractus-X Project (e.g., TRGs), the Eclipse Development Process to refine, plan, develop and release our implementation features."}),"\n",(0,i.jsx)(n.h2,{id:"catena-x-process-overview",children:"Catena-X Process Overview"}),"\n",(0,i.jsx)(n.p,{children:"![From idea to release item](./assets/From Idea to Release Item.drawio.svg)"}),"\n",(0,i.jsx)(n.h3,{id:"create-new-feature-proposal",children:"Create new feature proposal"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Feature Author"}),"\n",(0,i.jsx)(n.li,{children:"Description: Anybody can contribute to a use case by creating a feature proposal in Tractus X. The person creating the feature proposal is the 'Feature Author' and responsbile for the feature proposal through the process."}),"\n",(0,i.jsx)(n.li,{children:"Possible outcomes: Feature proposal created"}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"refine-feature",children:"Refine feature"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Feature Author"}),"\n",(0,i.jsx)(n.li,{children:"Description: After creating the feature proposal the feature author has to continously refine the feature until it contains the minimal feature content, so that it can be valited. This step might be obsolete if all information are added when creating the feature proposal."}),"\n",(0,i.jsx)(n.li,{children:"Possible outcomes: Submit for validation"}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"validate-minimal-feature-content",children:"Validate minimal feature content"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Topic owner (Committee or Expert Group)"}),"\n",(0,i.jsx)(n.li,{children:"Description: The topic owner is responsible to assess if the minimal feature content requirements are met by the feature proposal."}),"\n",(0,i.jsxs)(n.li,{children:["Possible outcomes:","\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Minimal feature content not complete: The feature proposal is being send back to the feature author with the request to further refine the feature proposal"}),"\n",(0,i.jsx)(n.li,{children:"Minimal feature content complete"}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"check-strategic-fit",children:"Check strategic fit"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Topic owner"}),"\n",(0,i.jsx)(n.li,{children:"Description: Once the feature proposal contains at least the minimal feature content, its strategic fit is going to be evaluated by the topic owner"}),"\n",(0,i.jsxs)(n.li,{children:["Possible outcomes:","\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Feature proposal fit strategy: If the feature proposal strategically fits it is going to be added to the Inbox."}),"\n",(0,i.jsx)(n.li,{children:"Strategic fit cant be assest: If the strategic fit cant be assest by the topic owner the feature proposal is being send back to the feature author with the request to further refine the feature proposal."}),"\n",(0,i.jsx)(n.li,{children:"Feature proposal does NOT fit: If the topic owner assess the feature proposal as not fitting the strategy, the feature proposal is going to be rejected. In this case the feature proposal is not going to be implemented."}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"refine-feature-to-meet-doe",children:"Refine feature to meet DoE"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Feature author"}),"\n",(0,i.jsx)(n.li,{children:"Description: Once the feature is validated, the feature author has to further refine the feature to meet the DoE. The refinement can be done by setting up individual refinement meetings for the feature proposal and inviting relevant people or by presenting the feature proposal in the Open Refinement. Each feature proposal has to be presented at least once in the Open Refinement so that the whole community has the chance to provide feedback."}),"\n",(0,i.jsx)(n.li,{children:"Possbile outcomes: DoE complete"}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"present-feature-proposal-in-open-refinement",children:"Present feature proposal in Open Refinement"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Feature author"}),"\n",(0,i.jsx)(n.li,{children:"Description: The feature proposal is presented in the Open Refinement to receive feedback from the community."}),"\n",(0,i.jsx)(n.li,{children:"Possible outcomes: DoE complete"}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"check-doe",children:"Check DoE"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Committers"}),"\n",(0,i.jsx)(n.li,{children:"Description: Once the DoE for a feature proposal are complete, the committers are going to assess the maturity of the feature proposal."}),"\n",(0,i.jsxs)(n.li,{children:["Possible outcomes:","\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"DoE met: If the committers assess the feature proposal mature enough, it is going to be added to the Backlog."}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"present-feature-in-open-planning",children:"Present feature in Open Planning"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Feature author"}),"\n",(0,i.jsx)(n.li,{children:"Description: The feature proposal is going to be presented in the Open Planning to be prioritized and be planned for the release."}),"\n",(0,i.jsx)(n.li,{children:"Possible outcomes: Feature proposal was presented"}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"commit-to-feature-proposal",children:"Commit to feature proposal"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Responsible: Committers"}),"\n",(0,i.jsx)(n.li,{children:"Description: The committers are deciding on the scope of the upcoming release. All feature proposals presented in the Open Planning are going to be prioritized."}),"\n",(0,i.jsxs)(n.li,{children:["Possible outcomes:","\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Committed: The feature proposal gets the committment from the committers and is added to the upcoming release."}),"\n",(0,i.jsx)(n.li,{children:"Not committed: The feature proposal is not committed by the committers and wont be part of the upcoming release. The feature proposal is going to be presented again in the Open Planning for the following release."}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,i.jsx)(n.h2,{id:"artifacts",children:"Artifacts"}),"\n",(0,i.jsx)(n.h3,{id:"process-roles",children:"Process roles"}),"\n",(0,i.jsxs)(n.table,{children:[(0,i.jsx)(n.thead,{children:(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.th,{children:"Role"}),(0,i.jsx)(n.th,{children:"Description"})]})}),(0,i.jsxs)(n.tbody,{children:[(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Feature author"}),(0,i.jsx)(n.td,{children:"The feature author is going to be the primary point of contact for all questions related to a feature proposal. The feature author carries the feature proposal through the validation and refinement process."})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Topic Owner"}),(0,i.jsx)(n.td,{children:"The topic owner validates new feature proposals for a defined topic (product) to make sure feature proposals align with the strategy for it. The topic owner is usually going to be a Committee."})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Committer"}),(0,i.jsx)(n.td,{children:(0,i.jsx)(n.em,{children:"See Tractus X Committer description"})})]})]})]}),"\n",(0,i.jsx)(n.h3,{id:"minimal-feature-content",children:"Minimal feature content"}),"\n",(0,i.jsx)(n.p,{children:"The minimal feature content is a subset of the DoE. It defines the minimal information that need to be provided before a feature proposal can enter the validation and refinement process."}),"\n",(0,i.jsxs)(n.table,{children:[(0,i.jsx)(n.thead,{children:(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.th,{children:"Information"}),(0,i.jsx)(n.th,{children:"Description"})]})}),(0,i.jsxs)(n.tbody,{children:[(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Feature author"}),(0,i.jsx)(n.td,{children:"Responsbile person to carry the feature proposal through the validation and refinement process"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Description"}),(0,i.jsx)(n.td,{children:"Description of WHAT the feature proposal is about."})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Business value"}),(0,i.jsx)(n.td,{children:"Description of WHY the feature proposal is relevant."})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Acceptance criteria"}),(0,i.jsx)(n.td,{children:"Conditions that must be satisfied for the feature proposal to be accepted"})]})]})]}),"\n",(0,i.jsx)(n.h3,{id:"definition-of-entry-doe",children:"Definition of Entry (DoE)"}),"\n",(0,i.jsxs)(n.table,{children:[(0,i.jsx)(n.thead,{children:(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.th,{children:"Information"}),(0,i.jsx)(n.th,{children:"Description"})]})}),(0,i.jsxs)(n.tbody,{children:[(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Minimal feature content"}),(0,i.jsx)(n.td,{children:(0,i.jsx)(n.em,{children:"see Minimal feature content"})})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Dependencies"}),(0,i.jsx)(n.td,{children:"Dependencies with other products or issues are identified and categorized via GitHub labels"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Risks"}),(0,i.jsx)(n.td,{children:"Known rsiks are properly adressed"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Enablers"}),(0,i.jsxs)(n.td,{children:["Required enablers are defined (",(0,i.jsx)(n.em,{children:"isnt that a dependency?"}),")"]})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"High level architecture (building block view)"}),(0,i.jsx)(n.td,{})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Key dates and milestones"}),(0,i.jsx)(n.td,{children:"Key dates and milestones are defined using GitHub milestone declaration"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Testing"}),(0,i.jsx)(n.td,{children:"Test scenarios, test cases and test data are available"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Effort estimation"}),(0,i.jsx)(n.td,{children:"The effort to implement the feature is estimated (based on story points)"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Developer"}),(0,i.jsx)(n.td,{children:"Developer team for feature implementation defined"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Issues"}),(0,i.jsx)(n.td,{children:"First implementation issues are defined in the corresponding repository and linked to the feature (optional)"})]})]})]}),"\n",(0,i.jsx)(n.h3,{id:"open-refinement",children:"Open Refinement"}),"\n",(0,i.jsx)(n.p,{children:"The Open refinement is ment to..."}),"\n",(0,i.jsxs)(n.p,{children:["The Catena-X association communicates and coordiantes the open refinement and open planning meetings via the a Tractus-X ",(0,i.jsx)(n.a,{href:"https://eclipse-tractusx.github.io/blog",children:"News Page"})," and the Tractus-X ",(0,i.jsx)(n.a,{href:"https://accounts.eclipse.org/mailing-list/tractusx-dev",children:"Mailing List"}),". Feature authors must make sure to subscribe! The meetings are also be published (with meeting session and calender.ics) on the open meetings page."]}),"\n",(0,i.jsx)(n.h3,{id:"open-planning",children:"Open Planning"}),"\n",(0,i.jsx)(n.p,{children:"During the Open Planning the items for upcoming release are planned. All feature proposals that were handed in on time are going to be presented to the audience. The Open Planning is the last chance to provide feedback about the scope of the feature proposal. After the presentation of the feature proposal by the feature author, the committers are going to prioritize the feature proposal in alignment with the topic owner. A feature proposal becomes part of the upcoming release only by receiving the commitment by the committes and not by being presented in the Open Planning!"}),"\n",(0,i.jsx)(n.p,{children:"To enter the Open Plannung a feature proposal must meet the DoE X days before the Open Planning (Cut-Off)! Feature proposal that meet the DoE after the Cut-Off won't be considered in the Open Planning. This means it will likely be deferred to a future release."}),"\n",(0,i.jsxs)(n.table,{children:[(0,i.jsx)(n.thead,{children:(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.th,{children:"Tasks"}),(0,i.jsx)(n.th,{children:"Documents (e.g. Standards)"}),(0,i.jsx)(n.th,{children:"Reference Impl."}),(0,i.jsx)(n.th,{children:"Outcome"})]})}),(0,i.jsxs)(n.tbody,{children:[(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Feature Proposal"}),(0,i.jsx)(n.td,{children:"Refinement Meetings"}),(0,i.jsx)(n.td,{children:"In sig release"}),(0,i.jsx)(n.td,{children:"Proposals by C-X e.V. Overview of all feature proposals incl. acceptance criteria. (Task break down over all affected teams / dependencies.) DOE ???"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Feature Commitment"}),(0,i.jsx)(n.td,{children:"Planning Meetings"}),(0,i.jsx)(n.td,{children:"In sig release"}),(0,i.jsx)(n.td,{children:"Decision by committer group Committed, prioritized backlog for the next release. Coordination / refinement / prioritization of new ideas, business requirements, features (scope C-X only)"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{}),(0,i.jsx)(n.td,{children:"C-X association tooling"}),(0,i.jsx)(n.td,{children:"Sig-release"}),(0,i.jsx)(n.td,{children:"Priotized list of Catena-X business requirements (proposal)"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{}),(0,i.jsx)(n.td,{children:"C-X association tooling"}),(0,i.jsx)(n.td,{children:"Sig-release: Discussions, Issues"}),(0,i.jsx)(n.td,{children:"Product Priotized list of overall business requirements"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{}),(0,i.jsx)(n.td,{children:"Association meetings (e.g., roadmap)"}),(0,i.jsx)(n.td,{children:"Tractus-X open meetings (e.g., refinement, planning, \u2026)"}),(0,i.jsx)(n.td,{children:"Roadmap and issues updated (?)"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Development of Deliverable"}),(0,i.jsx)(n.td,{children:"Create (normative) documents"}),(0,i.jsx)(n.td,{children:"Create open source software / KITs"}),(0,i.jsx)(n.td,{children:"Deliverables created (Normative Documents, KITs, Reference Implementation (complies to C-X Standards))"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Review of Deliverables"}),(0,i.jsx)(n.td,{children:"Content reviews in Expert Group"}),(0,i.jsx)(n.td,{children:"Code reviews (PRs) in Tractus-X"}),(0,i.jsx)(n.td,{children:"Deliverables reviewed"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Testing of Deliverables"}),(0,i.jsx)(n.td,{children:"Member Sounding"}),(0,i.jsx)(n.td,{children:"Testing of software, test phase, test management, etc."}),(0,i.jsx)(n.td,{children:"Deliverables tested"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Release Deliverables"}),(0,i.jsx)(n.td,{children:"Quality Criteria and Style Guides"}),(0,i.jsx)(n.td,{children:"Tractus-X Release Guidelines"}),(0,i.jsx)(n.td,{children:"Deliverables released"})]})]})]}),"\n",(0,i.jsx)(n.h3,{id:"refine-and-plan",children:"Refine and Plan"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Who can propose a feature?"}),"*\nAnyone can ",(0,i.jsx)(n.strong,{children:"propose a feature"}),", including Committees, Expert Groups, and other initiatives. However, we require a dedicated feature owner for further refinement and the breakdown into implementation issues."]}),"\n",(0,i.jsx)(n.p,{children:"** There are two options regarding resource commitment:"}),"\n",(0,i.jsxs)(n.ol,{children:["\n",(0,i.jsx)(n.li,{children:"If you have dedicated developer resources, your developer team will create the implementation issues at the user story level."}),"\n",(0,i.jsx)(n.li,{children:"If you do not have dedicated developer resources, interested developers team can create the implementation issues."}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"feature-assignment--validation",children:"Feature assignment & validation"}),"\n",(0,i.jsx)(n.p,{children:"Responsible: Committee & Expert Group"}),"\n",(0,i.jsx)(n.p,{children:"Once a new feature proposal has been made for the Tractus-X project, it enters a validation phase where the Committees assigns it to the relevant Expert Group."}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Validation:"})," The Committee assignes the feature to the matching Expert Group (at least two specific contacts). The Expert Group will review the proposal to ensure it aligns with the project's goals and standards."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Request for Additional Details:"})," If the proposal lacks necessary details, the reviewing bodies may ask the author for additional information or clarification."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"feature-refinement",children:"Feature refinement"}),"\n",(0,i.jsx)(n.p,{children:"Responsible: Feature author"}),"\n",(0,i.jsx)(n.p,{children:"After being validated and initially prioritized by the Expert Group, the refinement process starts. The feature author must gather their peer group (such as experts, contributors, and committers) for example by publishing a virtual meeting invite for the feature issue to be refined."}),"\n",(0,i.jsxs)(n.p,{children:["The goal is to have features that fullfill the following ",(0,i.jsx)(n.strong,{children:"Definition of Entry (DoE)"}),":"]}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Feature author defined: The designated point of contact for any questions related to the feature during the refinement, planning and development phase (e.g., subject matter expert). Not necessarily responsible for the technical implementation of a feature."}),"\n",(0,i.jsx)(n.li,{children:"Feature desciption is available"}),"\n",(0,i.jsx)(n.li,{children:"Required enablers are defined and aligned (e.g., architecutre, infrastructure, compliance)"}),"\n",(0,i.jsx)(n.li,{children:"High-level architecture (building-block-view)"}),"\n",(0,i.jsx)(n.li,{children:"Key dates and milestones are defined using GitHub milestone declaration"}),"\n",(0,i.jsx)(n.li,{children:"Business value is defined"}),"\n",(0,i.jsx)(n.li,{children:"Test scenarios, test cases and test data are available"}),"\n",(0,i.jsx)(n.li,{children:"Accpetance criteria are defined"}),"\n",(0,i.jsx)(n.li,{children:"Feature estimation available (based on story points)"}),"\n",(0,i.jsx)(n.li,{children:"Developer team for feature implementation defined"}),"\n",(0,i.jsx)(n.li,{children:"Dependencies with other products or issues are identified and categorized via GitHub labels"}),"\n",(0,i.jsx)(n.li,{children:"Known rsiks are properly adressed"}),"\n",(0,i.jsx)(n.li,{children:"No open questions left"}),"\n",(0,i.jsx)(n.li,{children:"First implementation issues are defined in the corresponding repository and linked to the feature (optional)\n..."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"Ultimately, the decision regarding maturity is made jointly by the affected products and contributers in the open refinement meetings."}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Feature author responsibility in the refinement:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Responding to feedback:"})," The author is responsible for addressing any feedback provided by the Expert Group or Committee. This may include providing additional details or making revisions to the proposal."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Implementation issues:"})," If necessary, the author may need to create implementation issues in the repository of the corresponding product to break down the feature into manageable pieces. This aids in tracking progress and facilitates easier review."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Timely Updates:"})," The author must update the feature details within the given timeframe. Prompt responses and updates are crucial to keep the proposal moving forward."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"feature-validation-and-approval",children:"Feature validation and approval"}),"\n",(0,i.jsx)(n.p,{children:"Responsible: Feature author"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Approval for Planning:"})," Once the feature has sufficient details and meets the Definition of Done (DoE), the feature author needs to submit it to the Committee or Expert Group (specific contacts mentioned in the feature) and a committer for approval."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Status of the Feature"})," in the SIG-release repository will be set to 'Backlog' by a committer (in alignment between Expert Group, Committee and the respective feature author). This status indicates whether the feature is included in the list for open planning or not."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Continuous Communication:"})," The author should maintain close communication via the feature issue with the Expert Group and Committee throughout this process to ensure prompt resolution of any issues."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"open-planning-meeting",children:"Open Planning meeting"}),"\n",(0,i.jsx)(n.p,{children:"Responsible: Feature author"}),"\n",(0,i.jsx)(n.p,{children:"During the open planning meeting, the feature author must present the features they are responsible for, and the committers will prioritize them in alignment with the Expert Group."}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Open Planning Cut-off:"})," Features must have mandatory content from the DoE and approval (2.3) before the open planning meeting. This is a critical deadline."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Consequences of Missing Deadline:"})," If the feature does not meet the DoE or missing the approval by the open planning, it will not be included in the planning cycle. This means it will likely be deferred to a future release."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"By following this process, authors can ensure their feature proposals are considered for inclusion in the Tractus-X project's planning. It is important to be proactive, responsive, and detail-oriented to successfully navigate the post-proposal phase."}),"\n",(0,i.jsx)(n.h2,{id:"open-release-planning-meeting",children:"Open Release Planning Meeting"}),"\n",(0,i.jsx)(n.p,{children:"Once a feature is through the propose and refinement process (2.) the feature will be presented in the open planning meeting and the committer will prioritize them based on the strategic / technical fit and ressource commitment in alignment with the Expert Groups of the Catena-X association."}),"\n",(0,i.jsx)(n.p,{children:"The open release planning meeting also called Program Increment (PI) planning is a critical event in the Tractus-X project where contributors, committers, Expert Groups, and Committees come together to define the scope for the next release. This process ensures that the project's roadmap is aligned with stakeholder expectations and the project's strategic objectives. Here's how the release Planning process typically unfolds:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Attendees:"})," Contributors, committers, Expert Groups, and Committees attend the release planning meeting."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Scope Definition:"})," The main objective of this meeting is to determine the scope of the upcoming release. This involves discussing the refined features and confirming the prioritized backlog."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Priorize backlog:"})," The backlog will be reviewed to ensure that it aligns with the project's strategic direction and available resources. Before the open release planning meeting, Committees and Expert Groups can pre-prioritize the backlog. However, the final prioritization is done by the committers."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"decision-making-by-committers",children:"Decision-Making by Committers"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Realistic Scope Assessment:"})," Committers play a crucial role in the release planning process. They assess the proposed features and backlog issues to determine what is realistically achievable in the next release, considering review, maintenance, and test efforts."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Final Prioritization:"})," Committers have the final call on the prioritization of issues, ensuring that the most critical and feasible items are included in the release scope."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Resource Allocation:"})," Decisions regarding the allocation of resources, including developer time and testing infrastructure, are made to support the prioritized issues."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"outcome-of-open-planning",children:"Outcome of Open Planning"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Priortized backlog:"})," Decision by committer group Committed, prioritized backlog for the next release."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Resource commitment:"})," Teams and individuals commit to the work they will deliver, fostering accountability and setting clear expectations for the upcoming release."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Updated roadmap:"})," The project's roadmap is updated to reflect the decisions made during the release planning, providing transparency to stakeholders and the community. [TO-DO clarifiy location of the roadmap / where will this be published]"]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Decisions are documented:"})," All decisions and commitments made during the planning are documented in the decision board or directly in the comment section of a feature. [TO-DO link to the architecture decsion board]"]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Communication plan:"})," After the planning a communication via mailing-list will be done by the project lead including the relevant links and decisions."]}),"\n"]}),"\n",(0,i.jsx)(n.h2,{id:"feature-development",children:"Feature Development"}),"\n",(0,i.jsxs)(n.ol,{children:["\n",(0,i.jsx)(n.li,{children:"Sprint Planning by committer"}),"\n",(0,i.jsx)(n.li,{children:"Sprint Review by committer"}),"\n",(0,i.jsx)(n.li,{children:"Recommended: Product demo as soon as relevant feature(s) are ready to show to get feedback from the community (prototypes are also welcome)"}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"For open-source reference implementations please refer to the Eclipse Handbook and the Tractus-X release guidelines.."}),"\n",(0,i.jsx)(n.h2,{id:"test-management",children:"Test Management"}),"\n",(0,i.jsx)(n.p,{children:"The software testing of reference implementations is sponsored and coordinated by the Catena-X association. It includes the following three levels:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Level 1: Product Tests"}),"\n",(0,i.jsx)(n.li,{children:"Level 2: Release Tests"}),"\n",(0,i.jsx)(n.li,{children:"Level 3: Test Beds for 3rd Party Solutions"}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"product-tests",children:"Product Tests"}),"\n",(0,i.jsx)(n.p,{children:"Product tests include unit, regression and integration tests based on product helm charts with individual dependencies."}),"\n",(0,i.jsx)(n.p,{children:"Contributors can create pull requests (PRs) for their developed features at any time. A PR must be assigned to a feature issue committed in the open planning. To get faster code reviews, it is recommended to submit small PRs."}),"\n",(0,i.jsx)(n.p,{children:"A PR must include the feature code, adapted helm chart(s), technical documentation as well as product tests (e.g., unit tests) and product integration tests (e.g., by using helm charts or mocks). All these tests must be passed locally before the PR can be submitted."}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Hint:"})," You can find the latest versions of the product helm charts in our release changelog."]}),"\n",(0,i.jsx)(n.admonition,{type:"info",children:(0,i.jsx)(n.p,{children:"ToDo: Insert Link! Previous link was broken."})}),"\n",(0,i.jsx)(n.p,{children:"At least two committer must review the PR, including the source code, test results and the compliance with the Tractus-X release guidelines (TRGs), and approve the merging of these changes. In case there are change requests or defects that a committer cannot solve, the contributor must address these changes before merging."}),"\n",(0,i.jsx)(n.p,{children:"The PR and the related product tests are part of the open-source development process resulting in a new product (rc-)version."}),"\n",(0,i.jsx)(n.h3,{id:"release-tests",children:"Release Tests"}),"\n",(0,i.jsxs)(n.p,{children:["The release tests include e2e tests for the Catena-X operating system (cxOS) itself as well as for the cxOS with open-source applications (e.g., Trace-X) based on ",(0,i.jsx)(n.a,{href:"https://github.com/eclipse-tractusx/tractus-x-umbrella",children:"umbrella helm charts"}),". Thereby, various product combinations of umbrella helm charts are possible."]}),"\n",(0,i.jsx)(n.p,{children:"The purpose of release testing is for the feature requestor to validate the end-to-end business flow using various test executions and to confirm that the acceptance criteria have been fulfilled (business value)."}),"\n",(0,i.jsxs)(n.p,{children:["Before a product can participate in a release test, it must fulfill the following ",(0,i.jsx)(n.strong,{children:"prerequisites"}),":"]}),"\n",(0,i.jsx)(n.p,{children:"For release 24.08, Expert Groups of the Catena-X association must ..."}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["create new or refine existing e2e test cases, test data and documentation as .md-file in Tractus-X ",(0,i.jsx)(n.a,{href:"https://github.com/eclipse-tractusx/sig-testing",children:"sig-testing"}),"."]}),"\n",(0,i.jsx)(n.li,{children:"provide at least one tester for the execution of the e2e test cases (if not fully automated)."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"The Catena-X association will provide a test management team including ..."}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"a test manager that creates the test plan and report, coordinates the test execution."}),"\n",(0,i.jsx)(n.li,{children:"a DevSecOps engineer for setting up test environment infrastructure (based on the hotel budapest approach)."}),"\n",(0,i.jsx)(n.li,{children:"a DevSecOps engineer for deploying the umbrella helm chart of release candidates (supported by Tractus-X committer, if not fully automated yet)."}),"\n"]}),"\n",(0,i.jsxs)(n.p,{children:["The release tests result in a validated version of the cxOS, which is made available through quarterly Eclipse ",(0,i.jsx)(n.a,{href:"https://projects.eclipse.org/projects/automotive.tractusx",children:"Tractus-X releases"}),"."]}),"\n",(0,i.jsx)(n.h3,{id:"test-beds",children:"Test Beds"}),"\n",(0,i.jsx)(n.p,{children:"Coming soon..."}),"\n",(0,i.jsx)(n.h3,{id:"defect-management",children:"Defect Management"}),"\n",(0,i.jsxs)(n.p,{children:["Defects or unexpected behavior must be reported as bugs in the ",(0,i.jsx)(n.a,{href:"https://github.com/eclipse-tractusx/sig-release/issues/new/choose",children:"sig-release repo"}),"."]}),"\n",(0,i.jsx)(n.h3,{id:"test-artifacts",children:"Test Artifacts"}),"\n",(0,i.jsx)(n.p,{children:"There are various testing artifacts, that are either managed in Tractus-X GitHub or the Test Management Tool."}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["In ",(0,i.jsx)(n.strong,{children:"GitHub"})," we manage the different user journys and related business scenarios as .md files."]}),"\n",(0,i.jsxs)(n.li,{children:["In the ",(0,i.jsx)(n.strong,{children:"Test Management Tool"})," we manage test cases, test sets (opt.), test exectuions as well as test plans and reports."]}),"\n"]}),"\n",(0,i.jsxs)(n.table,{children:[(0,i.jsx)(n.thead,{children:(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.th,{children:"Artifact"}),(0,i.jsx)(n.th,{children:"Artifact Owner"}),(0,i.jsx)(n.th,{children:"# per Release"})]})}),(0,i.jsxs)(n.tbody,{children:[(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Test Case(s)"}),(0,i.jsx)(n.td,{children:"Product / Expert Group"}),(0,i.jsx)(n.td,{children:"n"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Test Set(s)"}),(0,i.jsx)(n.td,{children:"Product / Expert Group"}),(0,i.jsx)(n.td,{children:"n"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Test Execution(s)"}),(0,i.jsx)(n.td,{children:"Product / Expert Group"}),(0,i.jsx)(n.td,{children:"n"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Test Plan"}),(0,i.jsx)(n.td,{children:"Test Manager"}),(0,i.jsx)(n.td,{children:"1"})]}),(0,i.jsxs)(n.tr,{children:[(0,i.jsx)(n.td,{children:"Test Report"}),(0,i.jsx)(n.td,{children:"Test Manager"}),(0,i.jsx)(n.td,{children:"1"})]})]})]}),"\n",(0,i.jsx)(n.h2,{id:"release-management",children:"Release Management"}),"\n",(0,i.jsxs)(n.p,{children:["Catena-X ",(0,i.jsx)(n.strong,{children:"Release Management"})," is a crucial component within the broader Catena-X ecosystem, focused on orchestrating and overseeing the release cycles of both Catena-X and Tractus-X. Here's an overview of how Catena-X Release Management operates and coordinates these releases:"]}),"\n",(0,i.jsx)(n.h3,{id:"purpose-of-catena-x-release-management",children:"Purpose of Catena-X Release Management"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Streamlining Releases"}),": Catena-X Release Management aims to streamline the process of releasing updates, upgrades, and new features for both Catena-X and Tractus-X."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Ensuring Compatibility"}),": It ensures that releases across different components are compatible and seamlessly integrate with each other."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Quality Assurance"}),": Quality assurance and testing are integral parts, ensuring that released versions meet high standards of performance, security, and reliability."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"key-responsibilities",children:"Key Responsibilities"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Release Planning"}),": This involves strategizing the timing and content of releases based on development milestones, customer feedback, and market demands."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Version Control"}),": Managing versioning across different components to maintain clarity and consistency across software, standards and deployment."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Coordination with Development Teams"}),": Collaborating closely with development teams across Expert Groups, Committees and the broader Open Source community to align on release schedules, feature prioritization, and bug fixes."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Testing and QA"}),": Overseeing comprehensive testing processes to identify and address issues before deployment (see ##Test Management)."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Documentation and Communication"}),": Ensuring that release notes, documentation, and communication channels are updated and accessible to stakeholders."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"coordination-with-catena-x-and-tractus-x",children:"Coordination with Catena-X and Tractus-X"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Catena-X Integration"}),": Coordinating releases between Catena-X and Tractus-X involves understanding the dependencies and interactions between both components of our ecosystem."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Feature Alignment"}),": Ensuring that standards developed for Catena-X and features & KITs developed for Tractus-X are aligned with overarching goals and customer requirements."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Interoperability"}),": Guaranteeing interoperability between Catena-X standards and Tractus-X features, such as reference implementations to facilitate seamless data exchange and functionality."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"release-lifecycle",children:"Release Lifecycle"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Preparation Phase"}),": Developing and communicating the overarching release timeline including relevant milestones to all stakeholders across Tractus-X and Catena-X."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Planning Phase"}),": Identifying release goals, feature prioritization, and creating a roadmap for implementation."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Development Phase"}),": Actively working with development teams to build and test new features and enhancements."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Testing and QA Phase"}),": Conducting rigorous testing, including integration testing between Catena-X and Tractus-X elements."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Deployment Phase"}),": Deploying releases to production environments while ensuring minimal disruption and downtime. While Catena-X is responsible for providing governance and guidelines for deployments, the actual deployment to productive environments lies within the responsibility of our Operating Companies and participants of the Catena-X Data Space."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Monitoring and Feedback"}),": Monitoring post-release performance, gathering feedback from users, and iterating for continuous improvement."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"benefits-of-catena-x-release-management",children:"Benefits of Catena-X Release Management"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Efficiency"}),": Streamlining release processes leads to faster time-to-market for new features and updates."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Quality Assurance"}),": Rigorous testing and QA practices enhance the overall quality and reliability of software releases."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Alignment"}),": Ensures alignment with business objectives, customer needs, and industry standards."]}),"\n",(0,i.jsxs)(n.li,{children:[(0,i.jsx)(n.strong,{children:"Risk Mitigation"}),": Proactive identification and mitigation of risks associated with releases."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"In essence, Catena-X Release Management acts as a central hub that coordinates the complex interplay between Catena-X and Tractus-X releases, ensuring smooth integration, high-quality deliverables, and customer satisfaction."}),"\n",(0,i.jsx)(n.h2,{id:"security-mangement",children:"Security Mangement"}),"\n",(0,i.jsx)(n.admonition,{type:"info",children:(0,i.jsx)(n.p,{children:"ToDo: Security, Managing and Reporting Vulnerabilities, Communication"})}),"\n",(0,i.jsx)(n.h2,{id:"relevant-links",children:"Relevant Links"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:(0,i.jsx)(n.a,{href:"https://eclipse-tractusx.github.io/community/intro",children:"Catena-X Community Introduction"})}),"\n"]}),"\n",(0,i.jsx)(n.h2,{id:"faqs",children:"FAQs"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"How are the open meetings communicated?"}),"\nThe Catena-X association will communicate and coordiante the open refinement and open planning meetings vi the a Tractus-X ",(0,i.jsx)(n.a,{href:"https://eclipse-tractusx.github.io/blog",children:"News Page"})," and the Tractus-X ",(0,i.jsx)(n.a,{href:"https://accounts.eclipse.org/mailing-list/tractusx-dev",children:"Mailing List"}),". Please make sure that you subscribe. The meetings will also be published (with meeting session and calender.ics) on the open meetings page."]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Who can propose a feature?"}),"\nAnyone can ",(0,i.jsx)(n.strong,{children:"propose a feature"}),", including Committees, Expert Groups, and other initiatives. However, we require a dedicated feature author for further refinement and the breakdown into implementation issues."]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"How to handle dependencies?"}),"\nDependencies can be discussed in our open refinement meetings as well as via our other communication channels (e.g. martix chat or bilateral sessions). Please refer to our Tractus-X ",(0,i.jsx)(n.a,{href:"https://eclipse-tractusx.github.io/community/intro",children:"communication rules"}),"."]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Who gives access to the sig-release repository to enable planning process?"}),"\nPlease refer to our Tractus-X ",(0,i.jsx)(n.a,{href:"https://eclipse-tractusx.github.io/docs/oss/getting-started",children:"Getting Started Guide"}),"."]})]})}function h(e={}){const{wrapper:n}={...(0,s.R)(),...e.components};return n?(0,i.jsx)(n,{...e,children:(0,i.jsx)(c,{...e})}):c(e)}},8453:(e,n,t)=>{t.d(n,{R:()=>a,x:()=>o});var i=t(6540);const s={},r=i.createContext(s);function a(e){const n=i.useContext(r);return i.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function o(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:a(e.components),i.createElement(r.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/2856a3e9.6cedd9a8.js b/assets/js/2856a3e9.6cedd9a8.js deleted file mode 100644 index 35d6a494..00000000 --- a/assets/js/2856a3e9.6cedd9a8.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9766],{4155:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>d,contentTitle:()=>r,default:()=>p,frontMatter:()=>a,metadata:()=>s,toc:()=>l});var o=t(4848),i=t(8453);const a={sidebar_position:1},r="Catena-X Operating Model",s={id:"operating-model/operating-model/operating-model",title:"Catena-X Operating Model",description:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.",source:"@site/versioned_docs/version-24.03/operating-model/operating-model/operating-model.md",sourceDirName:"operating-model/operating-model",slug:"/operating-model/operating-model/",permalink:"/docs/operating-model/operating-model/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",next:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/docs/operating-model/why-introduction/"}},d={},l=[];function c(e){const n={admonition:"admonition",em:"em",h1:"h1",img:"img",p:"p",...(0,i.R)(),...e.components};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsx)(n.h1,{id:"catena-x-operating-model",children:"Catena-X Operating Model"}),"\n",(0,o.jsx)(n.admonition,{type:"danger",children:(0,o.jsx)(n.p,{children:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation."})}),"\n",(0,o.jsxs)(n.p,{children:[(0,o.jsx)(n.img,{alt:"Operating Model",src:t(3178).A+"",width:"794",height:"948"}),"\n",(0,o.jsx)(n.em,{children:"Operating Model"})]})]})}function p(e={}){const{wrapper:n}={...(0,i.R)(),...e.components};return n?(0,o.jsx)(n,{...e,children:(0,o.jsx)(c,{...e})}):c(e)}},3178:(e,n,t)=>{t.d(n,{A:()=>o});const o=t.p+"assets/images/operating-model-bbc65b14aee53a64f303c2b891314512.png"},8453:(e,n,t)=>{t.d(n,{R:()=>r,x:()=>s});var o=t(6540);const i={},a=o.createContext(i);function r(e){const n=o.useContext(a);return o.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function s(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:r(e.components),o.createElement(a.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/2856a3e9.94a3fe6b.js b/assets/js/2856a3e9.94a3fe6b.js new file mode 100644 index 00000000..5c33ceab --- /dev/null +++ b/assets/js/2856a3e9.94a3fe6b.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9766],{4155:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>d,contentTitle:()=>r,default:()=>p,frontMatter:()=>a,metadata:()=>s,toc:()=>l});var o=t(4848),i=t(8453);const a={sidebar_position:1},r="Catena-X Operating Model",s={id:"operating-model/operating-model/operating-model",title:"Catena-X Operating Model",description:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.",source:"@site/versioned_docs/version-24.03/operating-model/operating-model/operating-model.md",sourceDirName:"operating-model/operating-model",slug:"/operating-model/operating-model/",permalink:"/catenax-ev.github.io.new/docs/operating-model/operating-model/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",next:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/catenax-ev.github.io.new/docs/operating-model/why-introduction/"}},d={},l=[];function c(e){const n={admonition:"admonition",em:"em",h1:"h1",img:"img",p:"p",...(0,i.R)(),...e.components};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsx)(n.h1,{id:"catena-x-operating-model",children:"Catena-X Operating Model"}),"\n",(0,o.jsx)(n.admonition,{type:"danger",children:(0,o.jsx)(n.p,{children:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation."})}),"\n",(0,o.jsxs)(n.p,{children:[(0,o.jsx)(n.img,{alt:"Operating Model",src:t(3178).A+"",width:"794",height:"948"}),"\n",(0,o.jsx)(n.em,{children:"Operating Model"})]})]})}function p(e={}){const{wrapper:n}={...(0,i.R)(),...e.components};return n?(0,o.jsx)(n,{...e,children:(0,o.jsx)(c,{...e})}):c(e)}},3178:(e,n,t)=>{t.d(n,{A:()=>o});const o=t.p+"assets/images/operating-model-bbc65b14aee53a64f303c2b891314512.png"},8453:(e,n,t)=>{t.d(n,{R:()=>r,x:()=>s});var o=t(6540);const i={},a=o.createContext(i);function r(e){const n=o.useContext(a);return o.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function s(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:r(e.components),o.createElement(a.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/2baaddb5.d409b228.js b/assets/js/2baaddb5.d409b228.js deleted file mode 100644 index b46d30ab..00000000 --- a/assets/js/2baaddb5.d409b228.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[5018],{4591:(e,a,t)=>{t.r(a),t.d(a,{assets:()=>d,contentTitle:()=>o,default:()=>h,frontMatter:()=>s,metadata:()=>r,toc:()=>c});var i=t(4848),n=t(8453);const s={sidebar_position:1},o="How: Data Space Governance",r={id:"operating-model/how-data-space-governance/how-data-space-governance",title:"How: Data Space Governance",description:"Standardization",source:"@site/versioned_docs/version-24.03/operating-model/how-data-space-governance/how-data-space-governance.md",sourceDirName:"operating-model/how-data-space-governance",slug:"/operating-model/how-data-space-governance/",permalink:"/docs/operating-model/how-data-space-governance/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"How: Data Space Operations",permalink:"/docs/operating-model/how-data-space-operations/"},next:{title:"How: Life Cycle Management",permalink:"/docs/operating-model/how-life-cycle-management/"}},d={},c=[{value:"Standardization",id:"standardization",level:2},{value:"Why do we standardize?",id:"why-do-we-standardize",level:3},{value:"What do we standardize?",id:"what-do-we-standardize",level:3},{value:"How do we standardize?",id:"how-do-we-standardize",level:3},{value:"Conformity Assessment",id:"conformity-assessment",level:2},{value:"Why do we certify?",id:"why-do-we-certify",level:3},{value:"What do we certify?",id:"what-do-we-certify",level:3},{value:"How do we certify?",id:"how-do-we-certify",level:3},{value:"Catena-X Labels",id:"catena-x-labels",level:3},{value:"Exceptions & Timeline for Release 23.09",id:"exceptions--timeline-for-release-2309",level:3},{value:"1. 45-day grace period to obtain valid certification after Release 3.2 (23.09)",id:"1-45-day-grace-period-to-obtain-valid-certification-after-release-32-2309",level:4},{value:"2. Certification of business applications vs. internal systems that fall under the definition of a Catena-X business application*",id:"2-certification-of-business-applications-vs-internal-systems-that-fall-under-the-definition-of-a-catena-x-business-application",level:4},{value:"3. No Catena-X Business Applications without listing on a certified CX Marketplace",id:"3-no-catena-x-business-applications-without-listing-on-a-certified-cx-marketplace",level:4},{value:"Nomination Process for unique Roles (e.g., CSP-B)",id:"nomination-process-for-unique-roles-eg-csp-b",level:2},{value:"Qualification Process",id:"qualification-process",level:2},{value:"Why do we qualify?",id:"why-do-we-qualify",level:3},{value:"Who do we qualify?",id:"who-do-we-qualify",level:3},{value:"How do we qualify?",id:"how-do-we-qualify",level:3},{value:"Regulatory Framework",id:"regulatory-framework",level:2}];function l(e){const a={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",h4:"h4",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",ul:"ul",...(0,n.R)(),...e.components};return(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(a.h1,{id:"how-data-space-governance",children:"How: Data Space Governance"}),"\n",(0,i.jsx)(a.h2,{id:"standardization",children:"Standardization"}),"\n",(0,i.jsx)(a.h3,{id:"why-do-we-standardize",children:"Why do we standardize?"}),"\n",(0,i.jsx)(a.p,{children:"The success of the digital transformation of the automotive industry critically depends on multilateral collaboration between all stakeholders along the automotive value chain. Our growing Catena-X ecosystem will enable enormous amounts of data to be integrated and collaboratively harnessed."}),"\n",(0,i.jsxs)(a.p,{children:["However, this vision is complex: companies at various stages of the automotive value chain, such as production, delivery, or logistics, often have their own IT systems to manage their data. To ensure that these complex data volumes can be sent, received, and processed smoothly across all stages of the value chain, we need one language for all players: ",(0,i.jsx)(a.strong,{children:"common standards and frameworks"}),"."]}),"\n",(0,i.jsx)(a.h3,{id:"what-do-we-standardize",children:"What do we standardize?"}),"\n",(0,i.jsx)(a.p,{children:"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."}),"\n",(0,i.jsxs)(a.p,{children:["The Catena-X Association publishes standards for generic core and enabling services as well as for domain-specific business applications (see KITs Chapter ",(0,i.jsx)(a.a,{href:"/docs/operating-model/what-service-map/#kits--keep-it-together",children:"KITs \u2013 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 ",(0,i.jsx)(a.a,{href:"https://catena-x.net/de/standard-library",children:"Catena-X standard library"}),"."]}),"\n",(0,i.jsx)(a.h3,{id:"how-do-we-standardize",children:"How do we standardize?"}),"\n",(0,i.jsxs)(a.p,{children:["Based on ",(0,i.jsx)(a.a,{href:"https://catena-x.net/fileadmin/user_upload/Vereinsdokumente/Catena-X_IP_Regelwerk_IP_Regulations.pdf",children:"Catena-X\u2019s Intellectual Property(IP)-Regulations"})," 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 ",(0,i.jsx)(a.a,{href:"/docs/operating-model/how-data-space-governance/#how-do-we-standardize",children:"Catena-X Standardization Process"}),":"]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Standardization Process",src:t(1698).A+"",width:"1492",height:"587"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Standardization Process"})]}),"\n",(0,i.jsxs)(a.p,{children:["The ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/standardisierung",children:"Catena-X standardization policy"})," provides a detailed description of how Catena-X standards are being developed including everyone involved and their respective responsibilities."]}),"\n",(0,i.jsx)(a.h2,{id:"conformity-assessment",children:"Conformity Assessment"}),"\n",(0,i.jsx)(a.h3,{id:"why-do-we-certify",children:"Why do we certify?"}),"\n",(0,i.jsx)(a.p,{children:"Cross company interactions highly rely on mutual trust. Our certifications provide trust via transparency and reliability based on our Catena-X standards. By setting up a certification process, we guarantee that our major principles are considered in every component of the network. From the core service providers to the data connectors and every single application in the network, a consistent framework was created to ensure beneficial participation for all participants in the network. A chain is only as strong as its weakest link, and to gain trust we need to ensure that all links are as strong as possible."}),"\n",(0,i.jsx)(a.h3,{id:"what-do-we-certify",children:"What do we certify?"}),"\n",(0,i.jsxs)(a.p,{children:["Catena-X certification is done in a modular, role-based way, to fulfill different requirements of participants in our ecosystem, whether IT application providers, service providers or onboarding partners. The modularity allows high flexibility and lowers the efforts and redundancies for all parties involved. Catena-X standards become mandatory for certification as soon as they have been integrated into the certification framework. The Catena-X Association aims to release an update of its certification framework simultaneously with newly released standards. The most current version can always be found on the ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/certification",children:"Catena-X website"}),"."]}),"\n",(0,i.jsx)(a.h3,{id:"how-do-we-certify",children:"How do we certify?"}),"\n",(0,i.jsxs)(a.p,{children:["An overview of the certification process is depicted in Figure ",(0,i.jsx)(a.a,{href:"/docs/operating-model/how-data-space-governance/#how-do-we-certify",children:"Catena-X Certification Process"}),".\n",(0,i.jsx)(a.img,{alt:"Catena-X Certification Process",src:t(8445).A+"",width:"1202",height:"692"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Certification Process"})]}),"\n",(0,i.jsxs)(a.p,{children:["The ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/certification",children:"Catena-X Conformity Assessment Framework Handbook"})," provides a detailed description of how Catena-X conducts conformity assessment through Conformity Assessment Bodies."]}),"\n",(0,i.jsx)(a.h3,{id:"catena-x-labels",children:"Catena-X Labels"}),"\n",(0,i.jsx)(a.p,{children:"Catena-X issues four different labels to help customers find suitable and legitimate providers for their needs. Each label is issued to the relevant role after achieving successful certification and/or qualification. Labels are associated with the offered services of the provider."}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Certified Operating Company"})," (CSP-A/CSP-B)\n",(0,i.jsx)(a.img,{alt:"Certified Operating Company",src:t(122).A+"",width:"1103",height:"568"})]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Certified Provider"})," (e.g., BAP, ESP, OSP)\n",(0,i.jsx)(a.img,{alt:"Certified Provider",src:t(8186).A+"",width:"1103",height:"567"})]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Certified Solution"})," (e.g., Business App, Service\u2026.)\n",(0,i.jsx)(a.img,{alt:"Certified Solution",src:t(4956).A+"",width:"1110",height:"563"})]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Qualified Advisor"})," (Advisory Provider)\n",(0,i.jsx)(a.img,{alt:"Qualified Advisor",src:t(4040).A+"",width:"1101",height:"563"})]}),"\n",(0,i.jsx)(a.p,{children:"Each label is obtained after successful completion of the Catena-X certification or qualification process. Details on pathways to be added."}),"\n",(0,i.jsx)(a.h3,{id:"exceptions--timeline-for-release-2309",children:"Exceptions & Timeline for Release 23.09"}),"\n",(0,i.jsx)(a.p,{children:"Release 23.09 is the official GoLive Release of the Catena-X data ecosystem. For the first time, all major components of the Catena-X data ecosystem will be available to the vast majority of the automotive value chain. To fulfil this promise to all our stakeholders while some areas of Catena-X are still under development, certain exceptions are made during this transitional period:"}),"\n",(0,i.jsx)(a.h4,{id:"1-45-day-grace-period-to-obtain-valid-certification-after-release-32-2309",children:"1. 45-day grace period to obtain valid certification after Release 3.2 (23.09)"}),"\n",(0,i.jsxs)(a.p,{children:["Catena-X will release a standard update (Release 3.2) on Sept. 28, 2023, on the Catena-X Association website. ",(0,i.jsx)(a.strong,{children:"This release will include \u201cbreaking changes\u201d as defined in the"})," ",(0,i.jsx)(a.a,{href:"https://semver.org/",children:"Semantic Versioning"}),"."]}),"\n",(0,i.jsxs)(a.p,{children:["The GoLive of the Catena-X data ecosystem (productive environment) will be ",(0,i.jsx)(a.strong,{children:"exclusively on Release 3.2"}),". This will be accompanied by an ",(0,i.jsx)(a.strong,{children:"update of the certification framework"})," (\u201cwhich role needs to have which components certified\u201d) for release 3.2."]}),"\n",(0,i.jsxs)(a.p,{children:["Each partner needs to ensure conformity to the new standards to be active in the data space. To this end, the following procedure applies: Every participant in the data space has ",(0,i.jsx)(a.strong,{children:"45 days after Sept. 28"})," (grace period) to complete their certification via a CAB or, in case of an existing certification, via free self-assessment. ",(0,i.jsx)(a.strong,{children:"Deadline is Nov. 12, 2023"})," (Sept. 28 + 45 days)."]}),"\n",(0,i.jsxs)(a.p,{children:["Cofinity-X will ",(0,i.jsx)(a.strong,{children:"allow data space registration"})," of a partner from GoLive Oct. 16 after consultation with the Association, ",(0,i.jsx)(a.strong,{children:"subject to the proviso that certification must be completed by the Nov. 12 deadline"}),". If the certificate is not proven within the 45 days, Partners must be removed from the data space at the direction of the Catena-X Association."]}),"\n",(0,i.jsxs)(a.p,{children:["Data space participants and their solutions that were already certified for Release 3.0/3.1 can use the 45-day grace period to prove their compliance to the Association via a ",(0,i.jsx)(a.strong,{children:"free self-assessment"})," and thus confirm the validity of their certificate even after release updates (up to a maximum of 12 months after initial issue). A corresponding form including confirmation of conformity with each standard required for the certificate can be requested from ",(0,i.jsx)(a.a,{href:"mailto:info@catena-x.net",children:"info@catena-x.net"}),". This does not apply to a CSP-B."]}),"\n",(0,i.jsx)(a.h4,{id:"2-certification-of-business-applications-vs-internal-systems-that-fall-under-the-definition-of-a-catena-x-business-application",children:"2. Certification of business applications vs. internal systems that fall under the definition of a Catena-X business application*"}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"A business application"})," provides specific logic and schemas defined in a Catena-X use case (e. g., data processing, transformation functions) that is applied to input data to produce an expected output. This includes the transformation of data from an input format into an output format using Catena-X semantic models (semantic interoperability) as well as the technical data exchange using standardized protocols and API-specifications (technical interoperability). This does not apply to internal systems of an organization, such as internal databases, data lakes, data pipelines (ETL) or source systems. To become operational on the Catena-X data space, a business application must comply with the corresponding standards (see Chapter ",(0,i.jsx)(a.a,{href:"/docs/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),")."]}),"\n",(0,i.jsxs)(a.p,{children:["Companies connected to Catena-X might want to ",(0,i.jsx)(a.strong,{children:"connect certain internal systems"})," including company-internal business applications to the Catena-X network. It remains, however, crucial that all participants can rely on a standardized data exchange that guarantees stable data chains built on data sovereignty and interoperability."]}),"\n",(0,i.jsx)(a.p,{children:"Consequently, the following two principles apply:"}),"\n",(0,i.jsxs)(a.ul,{children:["\n",(0,i.jsx)(a.li,{children:"Everything that is necessary to uphold a stable data chain is required to follow Catena-X standards and has to be certified by a CAB."}),"\n",(0,i.jsx)(a.li,{children:"All business applications that are either associated with the Catena-X brand and/or are offered on a Catena-X marketplace are required to follow Catena-X standards and have to be certified by a CAB."}),"\n"]}),"\n",(0,i.jsx)(a.p,{children:"If an internal system fulfills one of these two criteria, a Catena-X certification is mandatory."}),"\n",(0,i.jsx)(a.p,{children:"*For future reference, to provide a scalable way of certification, additional technical and partially automated solutions\nof assessing conformity are currently under assessment. (10 votes for, 0 against \xe0 also Steve vote for publication)"}),"\n",(0,i.jsx)(a.h4,{id:"3-no-catena-x-business-applications-without-listing-on-a-certified-cx-marketplace",children:"3. No Catena-X Business Applications without listing on a certified CX Marketplace"}),"\n",(0,i.jsx)(a.p,{children:"Catena-X is built on trust. Consequently, certified Catena-X marketplaces (CSP-A) are checking, whether services provided are coming with verified credentials to ensure that the listed offer is trustworthy and conform to Catena-X standards."}),"\n",(0,i.jsx)(a.p,{children:"To further anchor this trust, all Catena-X related business applications and services require a listing on a Catena-X certified marketplace. Catena-X does not permit operating a Catena-X solution outside of a certified Catena-X market place."}),"\n",(0,i.jsxs)(a.p,{children:["As noted in Chapter ",(0,i.jsx)(a.a,{href:"/docs/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),", as of release 23.12, Catena-X will provide the technical possibility for multiple CSP-A providers. This will foster multiple verifiers of credentials."]}),"\n",(0,i.jsx)(a.h2,{id:"nomination-process-for-unique-roles-eg-csp-b",children:"Nomination Process for unique Roles (e.g., CSP-B)"}),"\n",(0,i.jsx)(a.p,{children:"The nomination process is intended to ensure neutrality and trustworthy execution of selected roles and tasks within the Catena-X ecosystem. The Catena-X Association is responsible for the execution of the nomination process including partner selection."}),"\n",(0,i.jsxs)(a.p,{children:["The various rights and obligations of the provider are described in the Request for Tender (RFT). This is, for example, the license for operation, which can also be withdrawn in case of unfair behavior. This ensures fair awarding and safe operation of the various components. Tasks include, for example, the operation of Core Services - Section B by Core Service Providers or the certification of providers and solutions by CABs. An overview of the nomination process is depicted in Figure ",(0,i.jsx)(a.a,{href:"/docs/operating-model/how-data-space-governance/#nomination-process-for-unique-roles-eg-csp-b",children:"Catena-X Nomination Process"}),"."]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Nomination Process",src:t(9625).A+"",width:"1451",height:"652"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Nomination Process"})]}),"\n",(0,i.jsx)(a.p,{children:"The process steps of the nomination process are described in detail below."}),"\n",(0,i.jsxs)(a.table,{children:[(0,i.jsx)(a.thead,{children:(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.th,{children:"Process Step"}),(0,i.jsx)(a.th,{children:"Description"}),(0,i.jsx)(a.th,{children:"Input"}),(0,i.jsx)(a.th,{children:"Output"})]})}),(0,i.jsxs)(a.tbody,{children:[(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Create Request for Tender (RfT)"}),(0,i.jsx)(a.td,{children:"The Catena-X Association is responsible for the creation of the Request for Tender (RfT) document (e.g., for Core Services - section B)"}),(0,i.jsx)(a.td,{}),(0,i.jsx)(a.td,{children:"RfT Document(s)"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Publish RfT on Website"}),(0,i.jsxs)(a.td,{children:["The Catena-X Association is responsible for the publication and distribution of the ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/",children:"RfT Document on the website"}),"."]}),(0,i.jsx)(a.td,{children:"RfT Document(s)"}),(0,i.jsx)(a.td,{children:"RfT Document(s) RfT Event incl. Timeline RfT Template"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Create and Submit Tender for selected Core Service(s)"}),(0,i.jsx)(a.td,{children:"A provider can create and submit a tender for the published RfT."}),(0,i.jsx)(a.td,{children:"RfT Document RfT Event RfT Template"}),(0,i.jsx)(a.td,{children:"Tender"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Receive and Review Submissions"}),(0,i.jsx)(a.td,{children:"The CX Association compares the tender(s), regarding the fulfillment of the nomination criteria and creates a short list of candidates for the board."}),(0,i.jsx)(a.td,{children:"Tender(s)"}),(0,i.jsx)(a.td,{children:"Short List of Provider Candidates"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Select Provider"}),(0,i.jsx)(a.td,{children:"The board of the Association elects a provider with an absolute majority vote."}),(0,i.jsx)(a.td,{children:"Short List of Provider Candidates"}),(0,i.jsx)(a.td,{children:"Nomination of Provider"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Inform Providers"}),(0,i.jsx)(a.td,{children:"The CX Association informs all provider(s) about the result of the nomination process."}),(0,i.jsx)(a.td,{}),(0,i.jsx)(a.td,{})]})]})]}),"\n",(0,i.jsx)(a.h2,{id:"qualification-process",children:"Qualification Process"}),"\n",(0,i.jsx)(a.h3,{id:"why-do-we-qualify",children:"Why do we qualify?"}),"\n",(0,i.jsx)(a.p,{children:"On the way to creating value with Catena-X, companies may be dependent on advisory services. The quality of these advisory services is decisive for the success of the participation and thus for the success of Catena-X. Catena-X can only be successful if it succeeds in integrating large parts of the automotive value chain. We assume that this will lead to a high demand for advisory services, which must be met. These advisory services must cover the needs of small and medium-sized companies as well as the needs of large companies, which have extended integration requirements."}),"\n",(0,i.jsx)(a.p,{children:"Advisory services are hard, if not impossible, to standardize. Consequently, conformity assessment of qualified advisory services cannot take place through certification. To maintain a consistent level of quality among advisory service providers in the Catena-X data space, the Catena-X Association thus offers a qualification process that is mandatory for all advisory service providers that want to get listed in a marketplace. Advisory service providers, like all other participants active on the Catena-X data space, must adhere to the Catena-X regulatory framework and thereby confirm their full and unconditional support of our data ecosystem including its mission and standards."}),"\n",(0,i.jsx)(a.h3,{id:"who-do-we-qualify",children:"Who do we qualify?"}),"\n",(0,i.jsx)(a.p,{children:"Catena-X invites advisory service providers of all kinds to support the successful onboarding of data space participants, SMEs in particular. One of the few prerequisites is the binding commitment to provide high-quality consulting at fair and reasonable costs. Catena-X supports this endeavor with information and predefined content as well as a qualification system to prove appropriate support and consulting competencies."}),"\n",(0,i.jsx)(a.h3,{id:"how-do-we-qualify",children:"How do we qualify?"}),"\n",(0,i.jsx)(a.p,{children:"There are two ways to become a Catena-X qualified advisory service provider."}),"\n",(0,i.jsxs)(a.ol,{children:["\n",(0,i.jsx)(a.li,{children:"Qualification through training"}),"\n",(0,i.jsx)(a.li,{children:"Qualification through existing experience"}),"\n"]}),"\n",(0,i.jsxs)(a.p,{children:["For most advisory service providers, the first option applies. Qualification through existing experience is a path offered to advisory service providers that have gained experience by actively contributing to the Catena-X ecosystem either by directly accompanying companies within the Catena-X beta phase or contributing directly to the Catena-X kickstarter consortium as a listed member. An overview of the qualification process is depicted in Figure ",(0,i.jsx)(a.a,{href:"/docs/operating-model/how-data-space-governance/#how-do-we-qualify",children:"Catena-X Qualification Process"}),"."]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Qualification Process",src:t(4644).A+"",width:"1591",height:"505"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Qualification Process"})]}),"\n",(0,i.jsxs)(a.p,{children:["As of the Operating Model White Paper v.2.1, the process for qualification through training has yet to be established. It will be released on the Catena-X website as soon as it is available. Qualification through experience applies to all advisory service providers that registered for and participated in the Catena-X beta phase. If a company is interested in qualification and/or the proof of qualification, the first step is to contact the Catena-X Association via ",(0,i.jsx)(a.a,{href:"mailto:info@catena-x.net",children:"info@catena-x.net"}),". Further information and a first questionnaire to collect basic information about the company will then be made accessible."]}),"\n",(0,i.jsx)(a.h2,{id:"regulatory-framework",children:"Regulatory Framework"}),"\n",(0,i.jsxs)(a.p,{children:["The ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/governance-framework-for-data-space-operations",children:"Catena-X Regulatory Framework for data space operations"})," outlines the 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. To understand the layers of our Regulatory Framework, Catena-X uses flight levels as a metaphor (see Figure ",(0,i.jsx)(a.a,{href:"/docs/operating-model/how-data-space-governance/#regulatory-framework",children:"Catena-X Governance Framework flight levels"}),"):"]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Governance Framework flight levels",src:t(4493).A+"",width:"1701",height:"662"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Governance Framework flight levels"})]}),"\n",(0,i.jsxs)(a.p,{children:["Each higher-level cascades into the lower ones, and the lower levels align with those above. Each level comes with specific guidelines and resources but also responsibilities for participants in our data space. This Operating Model falls under the 30,000 ft level and is thus mandatory for all data space participants. Maintaining and updating our Regulatory Framework for data space operations lies within the responsibility of the Catena-X Association. All resources and normative documents included in the regulatory framework are listed on the ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/governance-framework-for-data-space-operations",children:"Catena-X website"}),"."]})]})}function h(e={}){const{wrapper:a}={...(0,n.R)(),...e.components};return a?(0,i.jsx)(a,{...e,children:(0,i.jsx)(l,{...e})}):l(e)}},8445:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-certification-process-5188b323c489dc3b8783cb25e078a8cf.png"},4493:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-governance-framework-flight-levels-eb3e47026bd2885a5180e41e529b5dd3.png"},9625:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-nomination-process-4ab5adfcbe19d906086d2c9784aad62c.png"},4644:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-qualification-process-cecb836c907111ca0c82681abea72b3c.png"},1698:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-standardization-process-df4553a1e20cbbd0726dc32b55eacb34.png"},122:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/certified-operating-company-531b11afad6c5e656d308840540013ff.png"},8186:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/certified-provider-a9f19580a33e21651b270df4075d7682.png"},4956:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/certified-solution-4cbc5006ae66d72ec0c239e75b83e29e.png"},4040:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/qualified-advisor-59653148b29b5466ff8be87dedf565a4.png"},8453:(e,a,t)=>{t.d(a,{R:()=>o,x:()=>r});var i=t(6540);const n={},s=i.createContext(n);function o(e){const a=i.useContext(s);return i.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function r(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:o(e.components),i.createElement(s.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/2baaddb5.fb0c20ca.js b/assets/js/2baaddb5.fb0c20ca.js new file mode 100644 index 00000000..79163e94 --- /dev/null +++ b/assets/js/2baaddb5.fb0c20ca.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[5018],{4591:(e,a,t)=>{t.r(a),t.d(a,{assets:()=>d,contentTitle:()=>o,default:()=>h,frontMatter:()=>s,metadata:()=>r,toc:()=>c});var i=t(4848),n=t(8453);const s={sidebar_position:1},o="How: Data Space Governance",r={id:"operating-model/how-data-space-governance/how-data-space-governance",title:"How: Data Space Governance",description:"Standardization",source:"@site/versioned_docs/version-24.03/operating-model/how-data-space-governance/how-data-space-governance.md",sourceDirName:"operating-model/how-data-space-governance",slug:"/operating-model/how-data-space-governance/",permalink:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"How: Data Space Operations",permalink:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-operations/"},next:{title:"How: Life Cycle Management",permalink:"/catenax-ev.github.io.new/docs/operating-model/how-life-cycle-management/"}},d={},c=[{value:"Standardization",id:"standardization",level:2},{value:"Why do we standardize?",id:"why-do-we-standardize",level:3},{value:"What do we standardize?",id:"what-do-we-standardize",level:3},{value:"How do we standardize?",id:"how-do-we-standardize",level:3},{value:"Conformity Assessment",id:"conformity-assessment",level:2},{value:"Why do we certify?",id:"why-do-we-certify",level:3},{value:"What do we certify?",id:"what-do-we-certify",level:3},{value:"How do we certify?",id:"how-do-we-certify",level:3},{value:"Catena-X Labels",id:"catena-x-labels",level:3},{value:"Exceptions & Timeline for Release 23.09",id:"exceptions--timeline-for-release-2309",level:3},{value:"1. 45-day grace period to obtain valid certification after Release 3.2 (23.09)",id:"1-45-day-grace-period-to-obtain-valid-certification-after-release-32-2309",level:4},{value:"2. Certification of business applications vs. internal systems that fall under the definition of a Catena-X business application*",id:"2-certification-of-business-applications-vs-internal-systems-that-fall-under-the-definition-of-a-catena-x-business-application",level:4},{value:"3. No Catena-X Business Applications without listing on a certified CX Marketplace",id:"3-no-catena-x-business-applications-without-listing-on-a-certified-cx-marketplace",level:4},{value:"Nomination Process for unique Roles (e.g., CSP-B)",id:"nomination-process-for-unique-roles-eg-csp-b",level:2},{value:"Qualification Process",id:"qualification-process",level:2},{value:"Why do we qualify?",id:"why-do-we-qualify",level:3},{value:"Who do we qualify?",id:"who-do-we-qualify",level:3},{value:"How do we qualify?",id:"how-do-we-qualify",level:3},{value:"Regulatory Framework",id:"regulatory-framework",level:2}];function l(e){const a={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",h4:"h4",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",ul:"ul",...(0,n.R)(),...e.components};return(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(a.h1,{id:"how-data-space-governance",children:"How: Data Space Governance"}),"\n",(0,i.jsx)(a.h2,{id:"standardization",children:"Standardization"}),"\n",(0,i.jsx)(a.h3,{id:"why-do-we-standardize",children:"Why do we standardize?"}),"\n",(0,i.jsx)(a.p,{children:"The success of the digital transformation of the automotive industry critically depends on multilateral collaboration between all stakeholders along the automotive value chain. Our growing Catena-X ecosystem will enable enormous amounts of data to be integrated and collaboratively harnessed."}),"\n",(0,i.jsxs)(a.p,{children:["However, this vision is complex: companies at various stages of the automotive value chain, such as production, delivery, or logistics, often have their own IT systems to manage their data. To ensure that these complex data volumes can be sent, received, and processed smoothly across all stages of the value chain, we need one language for all players: ",(0,i.jsx)(a.strong,{children:"common standards and frameworks"}),"."]}),"\n",(0,i.jsx)(a.h3,{id:"what-do-we-standardize",children:"What do we standardize?"}),"\n",(0,i.jsx)(a.p,{children:"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."}),"\n",(0,i.jsxs)(a.p,{children:["The Catena-X Association publishes standards for generic core and enabling services as well as for domain-specific business applications (see KITs Chapter ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/what-service-map/#kits--keep-it-together",children:"KITs \u2013 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 ",(0,i.jsx)(a.a,{href:"https://catena-x.net/de/standard-library",children:"Catena-X standard library"}),"."]}),"\n",(0,i.jsx)(a.h3,{id:"how-do-we-standardize",children:"How do we standardize?"}),"\n",(0,i.jsxs)(a.p,{children:["Based on ",(0,i.jsx)(a.a,{href:"https://catena-x.net/fileadmin/user_upload/Vereinsdokumente/Catena-X_IP_Regelwerk_IP_Regulations.pdf",children:"Catena-X\u2019s Intellectual Property(IP)-Regulations"})," 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 ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance/#how-do-we-standardize",children:"Catena-X Standardization Process"}),":"]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Standardization Process",src:t(1698).A+"",width:"1492",height:"587"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Standardization Process"})]}),"\n",(0,i.jsxs)(a.p,{children:["The ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/standardisierung",children:"Catena-X standardization policy"})," provides a detailed description of how Catena-X standards are being developed including everyone involved and their respective responsibilities."]}),"\n",(0,i.jsx)(a.h2,{id:"conformity-assessment",children:"Conformity Assessment"}),"\n",(0,i.jsx)(a.h3,{id:"why-do-we-certify",children:"Why do we certify?"}),"\n",(0,i.jsx)(a.p,{children:"Cross company interactions highly rely on mutual trust. Our certifications provide trust via transparency and reliability based on our Catena-X standards. By setting up a certification process, we guarantee that our major principles are considered in every component of the network. From the core service providers to the data connectors and every single application in the network, a consistent framework was created to ensure beneficial participation for all participants in the network. A chain is only as strong as its weakest link, and to gain trust we need to ensure that all links are as strong as possible."}),"\n",(0,i.jsx)(a.h3,{id:"what-do-we-certify",children:"What do we certify?"}),"\n",(0,i.jsxs)(a.p,{children:["Catena-X certification is done in a modular, role-based way, to fulfill different requirements of participants in our ecosystem, whether IT application providers, service providers or onboarding partners. The modularity allows high flexibility and lowers the efforts and redundancies for all parties involved. Catena-X standards become mandatory for certification as soon as they have been integrated into the certification framework. The Catena-X Association aims to release an update of its certification framework simultaneously with newly released standards. The most current version can always be found on the ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/certification",children:"Catena-X website"}),"."]}),"\n",(0,i.jsx)(a.h3,{id:"how-do-we-certify",children:"How do we certify?"}),"\n",(0,i.jsxs)(a.p,{children:["An overview of the certification process is depicted in Figure ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance/#how-do-we-certify",children:"Catena-X Certification Process"}),".\n",(0,i.jsx)(a.img,{alt:"Catena-X Certification Process",src:t(8445).A+"",width:"1202",height:"692"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Certification Process"})]}),"\n",(0,i.jsxs)(a.p,{children:["The ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/certification",children:"Catena-X Conformity Assessment Framework Handbook"})," provides a detailed description of how Catena-X conducts conformity assessment through Conformity Assessment Bodies."]}),"\n",(0,i.jsx)(a.h3,{id:"catena-x-labels",children:"Catena-X Labels"}),"\n",(0,i.jsx)(a.p,{children:"Catena-X issues four different labels to help customers find suitable and legitimate providers for their needs. Each label is issued to the relevant role after achieving successful certification and/or qualification. Labels are associated with the offered services of the provider."}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Certified Operating Company"})," (CSP-A/CSP-B)\n",(0,i.jsx)(a.img,{alt:"Certified Operating Company",src:t(122).A+"",width:"1103",height:"568"})]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Certified Provider"})," (e.g., BAP, ESP, OSP)\n",(0,i.jsx)(a.img,{alt:"Certified Provider",src:t(8186).A+"",width:"1103",height:"567"})]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Certified Solution"})," (e.g., Business App, Service\u2026.)\n",(0,i.jsx)(a.img,{alt:"Certified Solution",src:t(4956).A+"",width:"1110",height:"563"})]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Qualified Advisor"})," (Advisory Provider)\n",(0,i.jsx)(a.img,{alt:"Qualified Advisor",src:t(4040).A+"",width:"1101",height:"563"})]}),"\n",(0,i.jsx)(a.p,{children:"Each label is obtained after successful completion of the Catena-X certification or qualification process. Details on pathways to be added."}),"\n",(0,i.jsx)(a.h3,{id:"exceptions--timeline-for-release-2309",children:"Exceptions & Timeline for Release 23.09"}),"\n",(0,i.jsx)(a.p,{children:"Release 23.09 is the official GoLive Release of the Catena-X data ecosystem. For the first time, all major components of the Catena-X data ecosystem will be available to the vast majority of the automotive value chain. To fulfil this promise to all our stakeholders while some areas of Catena-X are still under development, certain exceptions are made during this transitional period:"}),"\n",(0,i.jsx)(a.h4,{id:"1-45-day-grace-period-to-obtain-valid-certification-after-release-32-2309",children:"1. 45-day grace period to obtain valid certification after Release 3.2 (23.09)"}),"\n",(0,i.jsxs)(a.p,{children:["Catena-X will release a standard update (Release 3.2) on Sept. 28, 2023, on the Catena-X Association website. ",(0,i.jsx)(a.strong,{children:"This release will include \u201cbreaking changes\u201d as defined in the"})," ",(0,i.jsx)(a.a,{href:"https://semver.org/",children:"Semantic Versioning"}),"."]}),"\n",(0,i.jsxs)(a.p,{children:["The GoLive of the Catena-X data ecosystem (productive environment) will be ",(0,i.jsx)(a.strong,{children:"exclusively on Release 3.2"}),". This will be accompanied by an ",(0,i.jsx)(a.strong,{children:"update of the certification framework"})," (\u201cwhich role needs to have which components certified\u201d) for release 3.2."]}),"\n",(0,i.jsxs)(a.p,{children:["Each partner needs to ensure conformity to the new standards to be active in the data space. To this end, the following procedure applies: Every participant in the data space has ",(0,i.jsx)(a.strong,{children:"45 days after Sept. 28"})," (grace period) to complete their certification via a CAB or, in case of an existing certification, via free self-assessment. ",(0,i.jsx)(a.strong,{children:"Deadline is Nov. 12, 2023"})," (Sept. 28 + 45 days)."]}),"\n",(0,i.jsxs)(a.p,{children:["Cofinity-X will ",(0,i.jsx)(a.strong,{children:"allow data space registration"})," of a partner from GoLive Oct. 16 after consultation with the Association, ",(0,i.jsx)(a.strong,{children:"subject to the proviso that certification must be completed by the Nov. 12 deadline"}),". If the certificate is not proven within the 45 days, Partners must be removed from the data space at the direction of the Catena-X Association."]}),"\n",(0,i.jsxs)(a.p,{children:["Data space participants and their solutions that were already certified for Release 3.0/3.1 can use the 45-day grace period to prove their compliance to the Association via a ",(0,i.jsx)(a.strong,{children:"free self-assessment"})," and thus confirm the validity of their certificate even after release updates (up to a maximum of 12 months after initial issue). A corresponding form including confirmation of conformity with each standard required for the certificate can be requested from ",(0,i.jsx)(a.a,{href:"mailto:info@catena-x.net",children:"info@catena-x.net"}),". This does not apply to a CSP-B."]}),"\n",(0,i.jsx)(a.h4,{id:"2-certification-of-business-applications-vs-internal-systems-that-fall-under-the-definition-of-a-catena-x-business-application",children:"2. Certification of business applications vs. internal systems that fall under the definition of a Catena-X business application*"}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"A business application"})," provides specific logic and schemas defined in a Catena-X use case (e. g., data processing, transformation functions) that is applied to input data to produce an expected output. This includes the transformation of data from an input format into an output format using Catena-X semantic models (semantic interoperability) as well as the technical data exchange using standardized protocols and API-specifications (technical interoperability). This does not apply to internal systems of an organization, such as internal databases, data lakes, data pipelines (ETL) or source systems. To become operational on the Catena-X data space, a business application must comply with the corresponding standards (see Chapter ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),")."]}),"\n",(0,i.jsxs)(a.p,{children:["Companies connected to Catena-X might want to ",(0,i.jsx)(a.strong,{children:"connect certain internal systems"})," including company-internal business applications to the Catena-X network. It remains, however, crucial that all participants can rely on a standardized data exchange that guarantees stable data chains built on data sovereignty and interoperability."]}),"\n",(0,i.jsx)(a.p,{children:"Consequently, the following two principles apply:"}),"\n",(0,i.jsxs)(a.ul,{children:["\n",(0,i.jsx)(a.li,{children:"Everything that is necessary to uphold a stable data chain is required to follow Catena-X standards and has to be certified by a CAB."}),"\n",(0,i.jsx)(a.li,{children:"All business applications that are either associated with the Catena-X brand and/or are offered on a Catena-X marketplace are required to follow Catena-X standards and have to be certified by a CAB."}),"\n"]}),"\n",(0,i.jsx)(a.p,{children:"If an internal system fulfills one of these two criteria, a Catena-X certification is mandatory."}),"\n",(0,i.jsx)(a.p,{children:"*For future reference, to provide a scalable way of certification, additional technical and partially automated solutions\nof assessing conformity are currently under assessment. (10 votes for, 0 against \xe0 also Steve vote for publication)"}),"\n",(0,i.jsx)(a.h4,{id:"3-no-catena-x-business-applications-without-listing-on-a-certified-cx-marketplace",children:"3. No Catena-X Business Applications without listing on a certified CX Marketplace"}),"\n",(0,i.jsx)(a.p,{children:"Catena-X is built on trust. Consequently, certified Catena-X marketplaces (CSP-A) are checking, whether services provided are coming with verified credentials to ensure that the listed offer is trustworthy and conform to Catena-X standards."}),"\n",(0,i.jsx)(a.p,{children:"To further anchor this trust, all Catena-X related business applications and services require a listing on a Catena-X certified marketplace. Catena-X does not permit operating a Catena-X solution outside of a certified Catena-X market place."}),"\n",(0,i.jsxs)(a.p,{children:["As noted in Chapter ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),", as of release 23.12, Catena-X will provide the technical possibility for multiple CSP-A providers. This will foster multiple verifiers of credentials."]}),"\n",(0,i.jsx)(a.h2,{id:"nomination-process-for-unique-roles-eg-csp-b",children:"Nomination Process for unique Roles (e.g., CSP-B)"}),"\n",(0,i.jsx)(a.p,{children:"The nomination process is intended to ensure neutrality and trustworthy execution of selected roles and tasks within the Catena-X ecosystem. The Catena-X Association is responsible for the execution of the nomination process including partner selection."}),"\n",(0,i.jsxs)(a.p,{children:["The various rights and obligations of the provider are described in the Request for Tender (RFT). This is, for example, the license for operation, which can also be withdrawn in case of unfair behavior. This ensures fair awarding and safe operation of the various components. Tasks include, for example, the operation of Core Services - Section B by Core Service Providers or the certification of providers and solutions by CABs. An overview of the nomination process is depicted in Figure ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance/#nomination-process-for-unique-roles-eg-csp-b",children:"Catena-X Nomination Process"}),"."]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Nomination Process",src:t(9625).A+"",width:"1451",height:"652"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Nomination Process"})]}),"\n",(0,i.jsx)(a.p,{children:"The process steps of the nomination process are described in detail below."}),"\n",(0,i.jsxs)(a.table,{children:[(0,i.jsx)(a.thead,{children:(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.th,{children:"Process Step"}),(0,i.jsx)(a.th,{children:"Description"}),(0,i.jsx)(a.th,{children:"Input"}),(0,i.jsx)(a.th,{children:"Output"})]})}),(0,i.jsxs)(a.tbody,{children:[(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Create Request for Tender (RfT)"}),(0,i.jsx)(a.td,{children:"The Catena-X Association is responsible for the creation of the Request for Tender (RfT) document (e.g., for Core Services - section B)"}),(0,i.jsx)(a.td,{}),(0,i.jsx)(a.td,{children:"RfT Document(s)"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Publish RfT on Website"}),(0,i.jsxs)(a.td,{children:["The Catena-X Association is responsible for the publication and distribution of the ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/",children:"RfT Document on the website"}),"."]}),(0,i.jsx)(a.td,{children:"RfT Document(s)"}),(0,i.jsx)(a.td,{children:"RfT Document(s) RfT Event incl. Timeline RfT Template"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Create and Submit Tender for selected Core Service(s)"}),(0,i.jsx)(a.td,{children:"A provider can create and submit a tender for the published RfT."}),(0,i.jsx)(a.td,{children:"RfT Document RfT Event RfT Template"}),(0,i.jsx)(a.td,{children:"Tender"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Receive and Review Submissions"}),(0,i.jsx)(a.td,{children:"The CX Association compares the tender(s), regarding the fulfillment of the nomination criteria and creates a short list of candidates for the board."}),(0,i.jsx)(a.td,{children:"Tender(s)"}),(0,i.jsx)(a.td,{children:"Short List of Provider Candidates"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Select Provider"}),(0,i.jsx)(a.td,{children:"The board of the Association elects a provider with an absolute majority vote."}),(0,i.jsx)(a.td,{children:"Short List of Provider Candidates"}),(0,i.jsx)(a.td,{children:"Nomination of Provider"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Inform Providers"}),(0,i.jsx)(a.td,{children:"The CX Association informs all provider(s) about the result of the nomination process."}),(0,i.jsx)(a.td,{}),(0,i.jsx)(a.td,{})]})]})]}),"\n",(0,i.jsx)(a.h2,{id:"qualification-process",children:"Qualification Process"}),"\n",(0,i.jsx)(a.h3,{id:"why-do-we-qualify",children:"Why do we qualify?"}),"\n",(0,i.jsx)(a.p,{children:"On the way to creating value with Catena-X, companies may be dependent on advisory services. The quality of these advisory services is decisive for the success of the participation and thus for the success of Catena-X. Catena-X can only be successful if it succeeds in integrating large parts of the automotive value chain. We assume that this will lead to a high demand for advisory services, which must be met. These advisory services must cover the needs of small and medium-sized companies as well as the needs of large companies, which have extended integration requirements."}),"\n",(0,i.jsx)(a.p,{children:"Advisory services are hard, if not impossible, to standardize. Consequently, conformity assessment of qualified advisory services cannot take place through certification. To maintain a consistent level of quality among advisory service providers in the Catena-X data space, the Catena-X Association thus offers a qualification process that is mandatory for all advisory service providers that want to get listed in a marketplace. Advisory service providers, like all other participants active on the Catena-X data space, must adhere to the Catena-X regulatory framework and thereby confirm their full and unconditional support of our data ecosystem including its mission and standards."}),"\n",(0,i.jsx)(a.h3,{id:"who-do-we-qualify",children:"Who do we qualify?"}),"\n",(0,i.jsx)(a.p,{children:"Catena-X invites advisory service providers of all kinds to support the successful onboarding of data space participants, SMEs in particular. One of the few prerequisites is the binding commitment to provide high-quality consulting at fair and reasonable costs. Catena-X supports this endeavor with information and predefined content as well as a qualification system to prove appropriate support and consulting competencies."}),"\n",(0,i.jsx)(a.h3,{id:"how-do-we-qualify",children:"How do we qualify?"}),"\n",(0,i.jsx)(a.p,{children:"There are two ways to become a Catena-X qualified advisory service provider."}),"\n",(0,i.jsxs)(a.ol,{children:["\n",(0,i.jsx)(a.li,{children:"Qualification through training"}),"\n",(0,i.jsx)(a.li,{children:"Qualification through existing experience"}),"\n"]}),"\n",(0,i.jsxs)(a.p,{children:["For most advisory service providers, the first option applies. Qualification through existing experience is a path offered to advisory service providers that have gained experience by actively contributing to the Catena-X ecosystem either by directly accompanying companies within the Catena-X beta phase or contributing directly to the Catena-X kickstarter consortium as a listed member. An overview of the qualification process is depicted in Figure ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance/#how-do-we-qualify",children:"Catena-X Qualification Process"}),"."]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Qualification Process",src:t(4644).A+"",width:"1591",height:"505"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Qualification Process"})]}),"\n",(0,i.jsxs)(a.p,{children:["As of the Operating Model White Paper v.2.1, the process for qualification through training has yet to be established. It will be released on the Catena-X website as soon as it is available. Qualification through experience applies to all advisory service providers that registered for and participated in the Catena-X beta phase. If a company is interested in qualification and/or the proof of qualification, the first step is to contact the Catena-X Association via ",(0,i.jsx)(a.a,{href:"mailto:info@catena-x.net",children:"info@catena-x.net"}),". Further information and a first questionnaire to collect basic information about the company will then be made accessible."]}),"\n",(0,i.jsx)(a.h2,{id:"regulatory-framework",children:"Regulatory Framework"}),"\n",(0,i.jsxs)(a.p,{children:["The ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/governance-framework-for-data-space-operations",children:"Catena-X Regulatory Framework for data space operations"})," outlines the 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. To understand the layers of our Regulatory Framework, Catena-X uses flight levels as a metaphor (see Figure ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance/#regulatory-framework",children:"Catena-X Governance Framework flight levels"}),"):"]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Governance Framework flight levels",src:t(4493).A+"",width:"1701",height:"662"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Governance Framework flight levels"})]}),"\n",(0,i.jsxs)(a.p,{children:["Each higher-level cascades into the lower ones, and the lower levels align with those above. Each level comes with specific guidelines and resources but also responsibilities for participants in our data space. This Operating Model falls under the 30,000 ft level and is thus mandatory for all data space participants. Maintaining and updating our Regulatory Framework for data space operations lies within the responsibility of the Catena-X Association. All resources and normative documents included in the regulatory framework are listed on the ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/governance-framework-for-data-space-operations",children:"Catena-X website"}),"."]})]})}function h(e={}){const{wrapper:a}={...(0,n.R)(),...e.components};return a?(0,i.jsx)(a,{...e,children:(0,i.jsx)(l,{...e})}):l(e)}},8445:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-certification-process-5188b323c489dc3b8783cb25e078a8cf.png"},4493:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-governance-framework-flight-levels-eb3e47026bd2885a5180e41e529b5dd3.png"},9625:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-nomination-process-4ab5adfcbe19d906086d2c9784aad62c.png"},4644:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-qualification-process-cecb836c907111ca0c82681abea72b3c.png"},1698:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-standardization-process-df4553a1e20cbbd0726dc32b55eacb34.png"},122:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/certified-operating-company-531b11afad6c5e656d308840540013ff.png"},8186:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/certified-provider-a9f19580a33e21651b270df4075d7682.png"},4956:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/certified-solution-4cbc5006ae66d72ec0c239e75b83e29e.png"},4040:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/qualified-advisor-59653148b29b5466ff8be87dedf565a4.png"},8453:(e,a,t)=>{t.d(a,{R:()=>o,x:()=>r});var i=t(6540);const n={},s=i.createContext(n);function o(e){const a=i.useContext(s);return i.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function r(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:o(e.components),i.createElement(s.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/31f0b325.005710f7.js b/assets/js/31f0b325.005710f7.js new file mode 100644 index 00000000..8842740a --- /dev/null +++ b/assets/js/31f0b325.005710f7.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[6559],{9110:(e,a,t)=>{t.r(a),t.d(a,{assets:()=>c,contentTitle:()=>i,default:()=>h,frontMatter:()=>o,metadata:()=>r,toc:()=>d});var n=t(4848),s=t(8453);const o={sidebar_position:1},i="Why: Understanding the Catena-X Data Space",r={id:"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space",title:"Why: Understanding the Catena-X Data Space",description:"Conceptual Foundations of the Catena-X Data Ecosystem",source:"@site/docs/operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space.md",sourceDirName:"operating-model/why-understanding-the-catena-x-data-space",slug:"/operating-model/why-understanding-the-catena-x-data-space/",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/why-understanding-the-catena-x-data-space/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/why-introduction/"},next:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/"}},c={},d=[{value:"Conceptual Foundations of the Catena-X Data Ecosystem",id:"conceptual-foundations-of-the-catena-x-data-ecosystem",level:2},{value:"The Catena-X Data Ecosystem Architecture",id:"the-catena-x-data-ecosystem-architecture",level:2}];function l(e){const a={a:"a",em:"em",h1:"h1",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",ul:"ul",...(0,s.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(a.h1,{id:"why-understanding-the-catena-x-data-space",children:"Why: Understanding the Catena-X Data Space"}),"\n",(0,n.jsx)(a.h2,{id:"conceptual-foundations-of-the-catena-x-data-ecosystem",children:"Conceptual Foundations of the Catena-X Data Ecosystem"}),"\n",(0,n.jsxs)(a.p,{children:["To comprehend the components that comprise the Catena-X operating model, it is necessary to have a basic understanding of the fundamental concepts that make up the Catena-X data ecosystem (see Figure ",(0,n.jsx)(a.a,{href:"#conceptual-foundations-of-the-catena-x-data-ecosystem",children:"Catena-X Data Ecosystem"}),"). The Catena-X data ecosystem consists of three areas: the Catena-X Automotive Network e. V., the development environment, and the operating environment."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"Catena-X Data Ecosystem",src:t(8595).A+"",width:"1127",height:"662"}),"\n",(0,n.jsx)(a.em,{children:"Catena-X Data Ecosystem"})]}),"\n",(0,n.jsxs)(a.p,{children:["The ",(0,n.jsx)(a.strong,{children:"Catena-X Automotive Network e. V."})," (in the following called \u201cCatena-X Association\u201d or \u201cthe Association\u201d) is responsible for standardization, certifications, and governance of the Catena-X ecosystem. Members can participate in committees, working groups, and expert groups to actively shape the Catena-X ecosystem. The Catena-X Association publishes standards with the goal of enabling interoperability, data-sovereignty, and security for all participants in the data space. The ecosystem participants must comply with the standards published by the Catena-X Association to work with the data space. Catena-X standards build on Gaia-X/Inter-national Data Space Association (IDSA) concepts and principles, industry standards, and best practices, among others, and extends these by automotive domain and use case-specific requirements. By certifying ecosystem participants and software components, the Catena-X Association ensures transparency and trust in the eco- system. A certification testifies, for example, that a software component is interoperable, data sovereign, and safe to use in the Catena-X data space. The Association is complemented by the ",(0,n.jsx)(a.strong,{children:"development environment"}),". The focus of the development environment is on the one hand on the creation of standardization candidates that can be submitted into the standardization process of the association. And on the other hand, the development of open-source reference implementations and other implementations for the data space. In the ",(0,n.jsx)(a.strong,{children:"operating environment"}),", the various open-source and commercial services and business applications are operated by different providers. A detailed description of the provider roles and the associated software components can be found in ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/",children:"Who: Roles in the Catena-X Ecosystem"})]})," and ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/what-service-map/",children:"What: Service Map"})]}),". All three components jointly make up the Catena-X data ecosystem. In the following chapters, the roles, responsibilities, and functions of these components are described in detail."]}),"\n",(0,n.jsx)(a.h2,{id:"the-catena-x-data-ecosystem-architecture",children:"The Catena-X Data Ecosystem Architecture"}),"\n",(0,n.jsxs)(a.p,{children:["Underlining the Catena-X data ecosystem\u2019s conceptual foundations are its individual data space components. Together, these building blocks serve as the architecture of the Catena-X data space, where each building block serves a dedicated purpose in one or several of the above-mentioned conceptual elements. An overview is depicted in Figure ",(0,n.jsx)(a.a,{href:"#the-catena-x-data-ecosystem-architecture",children:"Catena-X Data Ecosystem"})," followed by a short description of the main building blocks."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"The Catena-X Data Space",src:t(3515).A+"",width:"1034",height:"713"}),"\n",(0,n.jsx)(a.em,{children:"Catena-X Data Ecosystem"})]}),"\n",(0,n.jsx)(a.p,{children:"The global Catena-X data space is built on 5 mission-critical pillars:"}),"\n",(0,n.jsxs)(a.ul,{children:["\n",(0,n.jsxs)(a.li,{children:["a dedicated ",(0,n.jsx)(a.strong,{children:"role concept"})," covering all data space participants (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/",children:"Who: Roles in the Catena-X Ecosystem"})]}),")"]}),"\n",(0,n.jsxs)(a.li,{children:["a Service Map of foundational software services, building blocks, and standards that form the ",(0,n.jsx)(a.strong,{children:"Catena-X Operating System"})," and ",(0,n.jsx)(a.strong,{children:"Business Foundation"})," (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/what-service-map/",children:"What: Service Map"})]}),"),"]}),"\n",(0,n.jsxs)(a.li,{children:["procedures, processes, and building blocks for a trusted, scalable, and compliant ",(0,n.jsx)(a.strong,{children:"data space operation"})," (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-operations/",children:"How: Data Space Operations"})]}),"),"]}),"\n",(0,n.jsxs)(a.li,{children:["effective ",(0,n.jsx)(a.strong,{children:"data space governance"})," incl. standards, legal frameworks, (flight models) and certification (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance/",children:"How: Data Space Governance"})]}),")"]}),"\n",(0,n.jsxs)(a.li,{children:["an integrated and holistic ",(0,n.jsx)(a.strong,{children:"life cycle management ensuring compliance, interoperability"}),", and ",(0,n.jsx)(a.strong,{children:"compatibility"})," (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-life-cycle-management/",children:"How: Life Cycle Management"})]}),")"]}),"\n"]}),"\n",(0,n.jsx)(a.p,{children:"To promote adoption and collaboration, the Catena-X data space is built upon open-source principals, under the umbrella of the Eclipse Foundation. All Catena-X reference implementations and KITs are licensed under Apache 2.0 and CY BB 4.0. In order to structure and guide the development in open-source, Catena-X installed Organizational Elements (e.g., committees in the Catena-X Association), created a working group and project in Eclipse Tractus-X and defined a scalable structure for a business-oriented development and adoption of relevant artifacts and SW codes:"}),"\n",(0,n.jsxs)(a.ul,{children:["\n",(0,n.jsx)(a.li,{children:"Enablement Services"}),"\n",(0,n.jsx)(a.li,{children:"Core Services"}),"\n",(0,n.jsx)(a.li,{children:"Industry Core"}),"\n",(0,n.jsx)(a.li,{children:"and use case KITs"}),"\n"]}),"\n",(0,n.jsx)(a.p,{children:"With regard to standardization, the Catena-X Association promotes, sponsors and coordinates the overarching requirements of the Eclipse Tractus-X project. Standards are always linked, structured, and offered within those four elements."}),"\n",(0,n.jsxs)(a.p,{children:["Catena-X offers use case KITs to enable a multi-vender ecosystem of software solutions and services for each Catena-X use case. Solution and Service providers can create interoperable and data sovereign solutions and trusted services based on the Catena-X KITs and offer them on trusted marketplaces within the Catena-X Data Space (-> Core Service Provider A). The marketplaces are certified marketplaces that offer interoperable solutions from different solutions providers. The Core Services as well as marketplaces are part of the cxOS and are operated by certified operating companies (see Figure ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/what-service-map/",children:"Service Map"}),"). With this comprehensive solution portfolio, players in the automotive value chain can create business value by establishing data-driven use cases and data chains."]}),"\n",(0,n.jsx)(a.p,{children:"Trust and conformity (of Services, Offers, and potentially other non-automotive data spaces) are fundamental for Catena-X\u2019s acceptance, scalability, and value creation. Therefore, Catena-X chose and installed various neutral governance bodies \u2013 covering development and operation. The following partnerships and components in sum ensure a global data space built by best-in-class experts on trusted principles:"}),"\n",(0,n.jsxs)(a.ol,{children:["\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"Gaia-X is the basis for our overarching Trust Framework and forms the foundation for a federated, interoperable data space with trusted identities."}),"\n"]}),"\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"The International Data Space Association (IDSA) provides architecture principles that enable sovereign data exchange."}),"\n"]}),"\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"The Eclipse Foundation hosts the official open-source development project of the Catena-X ecosystem and follows the Eclipse Foundation\u2019s trusted development process."}),"\n"]}),"\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"The Catena-X Association provides industry-specific governance for the ecosystem that equally reflects the diverse interest groups within the automotive industry to serve common business needs. It also defines the vision, mission, and guiding principles for the Catena-X data space through the governance framework based on the Catena-X Statutes."}),"\n"]}),"\n"]}),"\n",(0,n.jsxs)(a.p,{children:["More specifically, in the ",(0,n.jsx)(a.strong,{children:"Catena-X operating environment"}),", the Catena-X Regulatory Framework for Data Space operations acts as a reliable mutual foundation to ensure trust, interoperability and therefore scalability. Catena-X\u2019s success largely depends on trust that every participant plays by the same, commonly set rules. By standardizing many of the relationships and agreements necessary for data exchange and bringing Catena-X use cases to life, data space participants can put their focus largely on their individual business needs rather than individual contract negotiation between business partners. Through collectively approved guidelines and templates, data exchanges on Catena-X can be seamlessly executed and operated without friction."]})]})}function h(e={}){const{wrapper:a}={...(0,s.R)(),...e.components};return a?(0,n.jsx)(a,{...e,children:(0,n.jsx)(l,{...e})}):l(e)}},8595:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/catena-x-data-ecosystem-fcef9c51f52e3f778c6034628a557cb6.png"},3515:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/the-catena-x-data-space-1ffb629fc37aca9433227da3ea2b51b9.png"},8453:(e,a,t)=>{t.d(a,{R:()=>i,x:()=>r});var n=t(6540);const s={},o=n.createContext(s);function i(e){const a=n.useContext(o);return n.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function r(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:i(e.components),n.createElement(o.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/31f0b325.805d49fe.js b/assets/js/31f0b325.805d49fe.js deleted file mode 100644 index 4efd5548..00000000 --- a/assets/js/31f0b325.805d49fe.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[6559],{9110:(e,a,t)=>{t.r(a),t.d(a,{assets:()=>c,contentTitle:()=>i,default:()=>h,frontMatter:()=>o,metadata:()=>r,toc:()=>d});var n=t(4848),s=t(8453);const o={sidebar_position:1},i="Why: Understanding the Catena-X Data Space",r={id:"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space",title:"Why: Understanding the Catena-X Data Space",description:"Conceptual Foundations of the Catena-X Data Ecosystem",source:"@site/docs/operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space.md",sourceDirName:"operating-model/why-understanding-the-catena-x-data-space",slug:"/operating-model/why-understanding-the-catena-x-data-space/",permalink:"/docs/next/operating-model/why-understanding-the-catena-x-data-space/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/docs/next/operating-model/why-introduction/"},next:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/"}},c={},d=[{value:"Conceptual Foundations of the Catena-X Data Ecosystem",id:"conceptual-foundations-of-the-catena-x-data-ecosystem",level:2},{value:"The Catena-X Data Ecosystem Architecture",id:"the-catena-x-data-ecosystem-architecture",level:2}];function l(e){const a={a:"a",em:"em",h1:"h1",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",ul:"ul",...(0,s.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(a.h1,{id:"why-understanding-the-catena-x-data-space",children:"Why: Understanding the Catena-X Data Space"}),"\n",(0,n.jsx)(a.h2,{id:"conceptual-foundations-of-the-catena-x-data-ecosystem",children:"Conceptual Foundations of the Catena-X Data Ecosystem"}),"\n",(0,n.jsxs)(a.p,{children:["To comprehend the components that comprise the Catena-X operating model, it is necessary to have a basic understanding of the fundamental concepts that make up the Catena-X data ecosystem (see Figure ",(0,n.jsx)(a.a,{href:"#conceptual-foundations-of-the-catena-x-data-ecosystem",children:"Catena-X Data Ecosystem"}),"). The Catena-X data ecosystem consists of three areas: the Catena-X Automotive Network e. V., the development environment, and the operating environment."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"Catena-X Data Ecosystem",src:t(8595).A+"",width:"1127",height:"662"}),"\n",(0,n.jsx)(a.em,{children:"Catena-X Data Ecosystem"})]}),"\n",(0,n.jsxs)(a.p,{children:["The ",(0,n.jsx)(a.strong,{children:"Catena-X Automotive Network e. V."})," (in the following called \u201cCatena-X Association\u201d or \u201cthe Association\u201d) is responsible for standardization, certifications, and governance of the Catena-X ecosystem. Members can participate in committees, working groups, and expert groups to actively shape the Catena-X ecosystem. The Catena-X Association publishes standards with the goal of enabling interoperability, data-sovereignty, and security for all participants in the data space. The ecosystem participants must comply with the standards published by the Catena-X Association to work with the data space. Catena-X standards build on Gaia-X/Inter-national Data Space Association (IDSA) concepts and principles, industry standards, and best practices, among others, and extends these by automotive domain and use case-specific requirements. By certifying ecosystem participants and software components, the Catena-X Association ensures transparency and trust in the eco- system. A certification testifies, for example, that a software component is interoperable, data sovereign, and safe to use in the Catena-X data space. The Association is complemented by the ",(0,n.jsx)(a.strong,{children:"development environment"}),". The focus of the development environment is on the one hand on the creation of standardization candidates that can be submitted into the standardization process of the association. And on the other hand, the development of open-source reference implementations and other implementations for the data space. In the ",(0,n.jsx)(a.strong,{children:"operating environment"}),", the various open-source and commercial services and business applications are operated by different providers. A detailed description of the provider roles and the associated software components can be found in ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/",children:"Who: Roles in the Catena-X Ecosystem"})]})," and ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/docs/next/operating-model/what-service-map/",children:"What: Service Map"})]}),". All three components jointly make up the Catena-X data ecosystem. In the following chapters, the roles, responsibilities, and functions of these components are described in detail."]}),"\n",(0,n.jsx)(a.h2,{id:"the-catena-x-data-ecosystem-architecture",children:"The Catena-X Data Ecosystem Architecture"}),"\n",(0,n.jsxs)(a.p,{children:["Underlining the Catena-X data ecosystem\u2019s conceptual foundations are its individual data space components. Together, these building blocks serve as the architecture of the Catena-X data space, where each building block serves a dedicated purpose in one or several of the above-mentioned conceptual elements. An overview is depicted in Figure ",(0,n.jsx)(a.a,{href:"#the-catena-x-data-ecosystem-architecture",children:"Catena-X Data Ecosystem"})," followed by a short description of the main building blocks."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"The Catena-X Data Space",src:t(3515).A+"",width:"1034",height:"713"}),"\n",(0,n.jsx)(a.em,{children:"Catena-X Data Ecosystem"})]}),"\n",(0,n.jsx)(a.p,{children:"The global Catena-X data space is built on 5 mission-critical pillars:"}),"\n",(0,n.jsxs)(a.ul,{children:["\n",(0,n.jsxs)(a.li,{children:["a dedicated ",(0,n.jsx)(a.strong,{children:"role concept"})," covering all data space participants (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/",children:"Who: Roles in the Catena-X Ecosystem"})]}),")"]}),"\n",(0,n.jsxs)(a.li,{children:["a Service Map of foundational software services, building blocks, and standards that form the ",(0,n.jsx)(a.strong,{children:"Catena-X Operating System"})," and ",(0,n.jsx)(a.strong,{children:"Business Foundation"})," (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/docs/next/operating-model/what-service-map/",children:"What: Service Map"})]}),"),"]}),"\n",(0,n.jsxs)(a.li,{children:["procedures, processes, and building blocks for a trusted, scalable, and compliant ",(0,n.jsx)(a.strong,{children:"data space operation"})," (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/docs/next/operating-model/how-data-space-operations/",children:"How: Data Space Operations"})]}),"),"]}),"\n",(0,n.jsxs)(a.li,{children:["effective ",(0,n.jsx)(a.strong,{children:"data space governance"})," incl. standards, legal frameworks, (flight models) and certification (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/docs/next/operating-model/how-data-space-governance/",children:"How: Data Space Governance"})]}),")"]}),"\n",(0,n.jsxs)(a.li,{children:["an integrated and holistic ",(0,n.jsx)(a.strong,{children:"life cycle management ensuring compliance, interoperability"}),", and ",(0,n.jsx)(a.strong,{children:"compatibility"})," (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/docs/next/operating-model/how-life-cycle-management/",children:"How: Life Cycle Management"})]}),")"]}),"\n"]}),"\n",(0,n.jsx)(a.p,{children:"To promote adoption and collaboration, the Catena-X data space is built upon open-source principals, under the umbrella of the Eclipse Foundation. All Catena-X reference implementations and KITs are licensed under Apache 2.0 and CY BB 4.0. In order to structure and guide the development in open-source, Catena-X installed Organizational Elements (e.g., committees in the Catena-X Association), created a working group and project in Eclipse Tractus-X and defined a scalable structure for a business-oriented development and adoption of relevant artifacts and SW codes:"}),"\n",(0,n.jsxs)(a.ul,{children:["\n",(0,n.jsx)(a.li,{children:"Enablement Services"}),"\n",(0,n.jsx)(a.li,{children:"Core Services"}),"\n",(0,n.jsx)(a.li,{children:"Industry Core"}),"\n",(0,n.jsx)(a.li,{children:"and use case KITs"}),"\n"]}),"\n",(0,n.jsx)(a.p,{children:"With regard to standardization, the Catena-X Association promotes, sponsors and coordinates the overarching requirements of the Eclipse Tractus-X project. Standards are always linked, structured, and offered within those four elements."}),"\n",(0,n.jsxs)(a.p,{children:["Catena-X offers use case KITs to enable a multi-vender ecosystem of software solutions and services for each Catena-X use case. Solution and Service providers can create interoperable and data sovereign solutions and trusted services based on the Catena-X KITs and offer them on trusted marketplaces within the Catena-X Data Space (-> Core Service Provider A). The marketplaces are certified marketplaces that offer interoperable solutions from different solutions providers. The Core Services as well as marketplaces are part of the cxOS and are operated by certified operating companies (see Figure ",(0,n.jsx)(a.a,{href:"/docs/next/operating-model/what-service-map/",children:"Service Map"}),"). With this comprehensive solution portfolio, players in the automotive value chain can create business value by establishing data-driven use cases and data chains."]}),"\n",(0,n.jsx)(a.p,{children:"Trust and conformity (of Services, Offers, and potentially other non-automotive data spaces) are fundamental for Catena-X\u2019s acceptance, scalability, and value creation. Therefore, Catena-X chose and installed various neutral governance bodies \u2013 covering development and operation. The following partnerships and components in sum ensure a global data space built by best-in-class experts on trusted principles:"}),"\n",(0,n.jsxs)(a.ol,{children:["\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"Gaia-X is the basis for our overarching Trust Framework and forms the foundation for a federated, interoperable data space with trusted identities."}),"\n"]}),"\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"The International Data Space Association (IDSA) provides architecture principles that enable sovereign data exchange."}),"\n"]}),"\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"The Eclipse Foundation hosts the official open-source development project of the Catena-X ecosystem and follows the Eclipse Foundation\u2019s trusted development process."}),"\n"]}),"\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"The Catena-X Association provides industry-specific governance for the ecosystem that equally reflects the diverse interest groups within the automotive industry to serve common business needs. It also defines the vision, mission, and guiding principles for the Catena-X data space through the governance framework based on the Catena-X Statutes."}),"\n"]}),"\n"]}),"\n",(0,n.jsxs)(a.p,{children:["More specifically, in the ",(0,n.jsx)(a.strong,{children:"Catena-X operating environment"}),", the Catena-X Regulatory Framework for Data Space operations acts as a reliable mutual foundation to ensure trust, interoperability and therefore scalability. Catena-X\u2019s success largely depends on trust that every participant plays by the same, commonly set rules. By standardizing many of the relationships and agreements necessary for data exchange and bringing Catena-X use cases to life, data space participants can put their focus largely on their individual business needs rather than individual contract negotiation between business partners. Through collectively approved guidelines and templates, data exchanges on Catena-X can be seamlessly executed and operated without friction."]})]})}function h(e={}){const{wrapper:a}={...(0,s.R)(),...e.components};return a?(0,n.jsx)(a,{...e,children:(0,n.jsx)(l,{...e})}):l(e)}},8595:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/catena-x-data-ecosystem-fcef9c51f52e3f778c6034628a557cb6.png"},3515:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/the-catena-x-data-space-1ffb629fc37aca9433227da3ea2b51b9.png"},8453:(e,a,t)=>{t.d(a,{R:()=>i,x:()=>r});var n=t(6540);const s={},o=n.createContext(s);function i(e){const a=n.useContext(o);return n.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function r(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:i(e.components),n.createElement(o.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/3217192f.3749e5fb.js b/assets/js/3217192f.3749e5fb.js deleted file mode 100644 index 1320bd79..00000000 --- a/assets/js/3217192f.3749e5fb.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8462],{8174:a=>{a.exports=JSON.parse('{"tag":{"label":"Docusaurus","permalink":"/blog/tags/docusaurus","description":"Docusaurus tag description","allTagsPath":"/blog/tags","count":4,"unlisted":false},"listMetadata":{"permalink":"/blog/tags/docusaurus","page":1,"postsPerPage":10,"totalPages":1,"totalCount":4,"blogDescription":"Blog","blogTitle":"Blog"}}')}}]); \ No newline at end of file diff --git a/assets/js/33a2184c.d317ea9c.js b/assets/js/33a2184c.d317ea9c.js new file mode 100644 index 00000000..25c5490d --- /dev/null +++ b/assets/js/33a2184c.d317ea9c.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9160],{2804:e=>{e.exports=JSON.parse('{"tag":{"label":"Facebook","permalink":"/catenax-ev.github.io.new/blog/tags/facebook","description":"Facebook tag description","allTagsPath":"/catenax-ev.github.io.new/blog/tags","count":1,"unlisted":false},"listMetadata":{"permalink":"/catenax-ev.github.io.new/blog/tags/facebook","page":1,"postsPerPage":10,"totalPages":1,"totalCount":1,"blogDescription":"Blog","blogTitle":"Blog"}}')}}]); \ No newline at end of file diff --git a/assets/js/395bc0fb.05804c3d.js b/assets/js/395bc0fb.05804c3d.js deleted file mode 100644 index a115ff31..00000000 --- a/assets/js/395bc0fb.05804c3d.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8031],{3379:(e,a,t)=>{t.r(a),t.d(a,{assets:()=>c,contentTitle:()=>i,default:()=>h,frontMatter:()=>o,metadata:()=>r,toc:()=>d});var n=t(4848),s=t(8453);const o={sidebar_position:1},i="Why: Understanding the Catena-X Data Space",r={id:"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space",title:"Why: Understanding the Catena-X Data Space",description:"Conceptual Foundations of the Catena-X Data Ecosystem",source:"@site/versioned_docs/version-24.03/operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space.md",sourceDirName:"operating-model/why-understanding-the-catena-x-data-space",slug:"/operating-model/why-understanding-the-catena-x-data-space/",permalink:"/docs/operating-model/why-understanding-the-catena-x-data-space/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/docs/operating-model/why-introduction/"},next:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/docs/operating-model/who-roles-in-the-catena-x-ecosystem/"}},c={},d=[{value:"Conceptual Foundations of the Catena-X Data Ecosystem",id:"conceptual-foundations-of-the-catena-x-data-ecosystem",level:2},{value:"The Catena-X Data Ecosystem Architecture",id:"the-catena-x-data-ecosystem-architecture",level:2}];function l(e){const a={a:"a",em:"em",h1:"h1",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",ul:"ul",...(0,s.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(a.h1,{id:"why-understanding-the-catena-x-data-space",children:"Why: Understanding the Catena-X Data Space"}),"\n",(0,n.jsx)(a.h2,{id:"conceptual-foundations-of-the-catena-x-data-ecosystem",children:"Conceptual Foundations of the Catena-X Data Ecosystem"}),"\n",(0,n.jsxs)(a.p,{children:["To comprehend the components that comprise the Catena-X operating model, it is necessary to have a basic understanding of the fundamental concepts that make up the Catena-X data ecosystem (see Figure ",(0,n.jsx)(a.a,{href:"#conceptual-foundations-of-the-catena-x-data-ecosystem",children:"Catena-X Data Ecosystem"}),"). The Catena-X data ecosystem consists of three areas: the Catena-X Automotive Network e. V., the development environment, and the operating environment."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"Catena-X Data Ecosystem",src:t(4874).A+"",width:"1127",height:"662"}),"\n",(0,n.jsx)(a.em,{children:"Catena-X Data Ecosystem"})]}),"\n",(0,n.jsxs)(a.p,{children:["The ",(0,n.jsx)(a.strong,{children:"Catena-X Automotive Network e. V."})," (in the following called \u201cCatena-X Association\u201d or \u201cthe Association\u201d) is responsible for standardization, certifications, and governance of the Catena-X ecosystem. Members can participate in committees, working groups, and expert groups to actively shape the Catena-X ecosystem. The Catena-X Association publishes standards with the goal of enabling interoperability, data-sovereignty, and security for all participants in the data space. The ecosystem participants must comply with the standards published by the Catena-X Association to work with the data space. Catena-X standards build on Gaia-X/Inter-national Data Space Association (IDSA) concepts and principles, industry standards, and best practices, among others, and extends these by automotive domain and use case-specific requirements. By certifying ecosystem participants and software components, the Catena-X Association ensures transparency and trust in the eco- system. A certification testifies, for example, that a software component is interoperable, data sovereign, and safe to use in the Catena-X data space. The Association is complemented by the ",(0,n.jsx)(a.strong,{children:"development environment"}),". The focus of the development environment is on the one hand on the creation of standardization candidates that can be submitted into the standardization process of the association. And on the other hand, the development of open-source reference implementations and other implementations for the data space. In the ",(0,n.jsx)(a.strong,{children:"operating environment"}),", the various open-source and commercial services and business applications are operated by different providers. A detailed description of the provider roles and the associated software components can be found in ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/docs/operating-model/who-roles-in-the-catena-x-ecosystem/",children:"Who: Roles in the Catena-X Ecosystem"})]})," and ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/docs/operating-model/what-service-map/",children:"What: Service Map"})]}),". All three components jointly make up the Catena-X data ecosystem. In the following chapters, the roles, responsibilities, and functions of these components are described in detail."]}),"\n",(0,n.jsx)(a.h2,{id:"the-catena-x-data-ecosystem-architecture",children:"The Catena-X Data Ecosystem Architecture"}),"\n",(0,n.jsxs)(a.p,{children:["Underlining the Catena-X data ecosystem\u2019s conceptual foundations are its individual data space components. Together, these building blocks serve as the architecture of the Catena-X data space, where each building block serves a dedicated purpose in one or several of the above-mentioned conceptual elements. An overview is depicted in Figure ",(0,n.jsx)(a.a,{href:"#the-catena-x-data-ecosystem-architecture",children:"Catena-X Data Ecosystem"})," followed by a short description of the main building blocks."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"The Catena-X Data Space",src:t(5074).A+"",width:"1034",height:"713"}),"\n",(0,n.jsx)(a.em,{children:"Catena-X Data Ecosystem"})]}),"\n",(0,n.jsx)(a.p,{children:"The global Catena-X data space is built on 5 mission-critical pillars:"}),"\n",(0,n.jsxs)(a.ul,{children:["\n",(0,n.jsxs)(a.li,{children:["a dedicated ",(0,n.jsx)(a.strong,{children:"role concept"})," covering all data space participants (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/docs/operating-model/who-roles-in-the-catena-x-ecosystem/",children:"Who: Roles in the Catena-X Ecosystem"})]}),")"]}),"\n",(0,n.jsxs)(a.li,{children:["a Service Map of foundational software services, building blocks, and standards that form the ",(0,n.jsx)(a.strong,{children:"Catena-X Operating System"})," and ",(0,n.jsx)(a.strong,{children:"Business Foundation"})," (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/docs/operating-model/what-service-map/",children:"What: Service Map"})]}),"),"]}),"\n",(0,n.jsxs)(a.li,{children:["procedures, processes, and building blocks for a trusted, scalable, and compliant ",(0,n.jsx)(a.strong,{children:"data space operation"})," (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/docs/operating-model/how-data-space-operations/",children:"How: Data Space Operations"})]}),"),"]}),"\n",(0,n.jsxs)(a.li,{children:["effective ",(0,n.jsx)(a.strong,{children:"data space governance"})," incl. standards, legal frameworks, (flight models) and certification (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/docs/operating-model/how-data-space-governance/",children:"How: Data Space Governance"})]}),")"]}),"\n",(0,n.jsxs)(a.li,{children:["an integrated and holistic ",(0,n.jsx)(a.strong,{children:"life cycle management ensuring compliance, interoperability"}),", and ",(0,n.jsx)(a.strong,{children:"compatibility"})," (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/docs/operating-model/how-life-cycle-management/",children:"How: Life Cycle Management"})]}),")"]}),"\n"]}),"\n",(0,n.jsx)(a.p,{children:"To promote adoption and collaboration, the Catena-X data space is built upon open-source principals, under the umbrella of the Eclipse Foundation. All Catena-X reference implementations and KITs are licensed under Apache 2.0 and CY BB 4.0. In order to structure and guide the development in open-source, Catena-X installed Organizational Elements (e.g., committees in the Catena-X Association), created a working group and project in Eclipse Tractus-X and defined a scalable structure for a business-oriented development and adoption of relevant artifacts and SW codes:"}),"\n",(0,n.jsxs)(a.ul,{children:["\n",(0,n.jsx)(a.li,{children:"Enablement Services"}),"\n",(0,n.jsx)(a.li,{children:"Core Services"}),"\n",(0,n.jsx)(a.li,{children:"Industry Core"}),"\n",(0,n.jsx)(a.li,{children:"and use case KITs"}),"\n"]}),"\n",(0,n.jsx)(a.p,{children:"With regard to standardization, the Catena-X Association promotes, sponsors and coordinates the overarching requirements of the Eclipse Tractus-X project. Standards are always linked, structured, and offered within those four elements."}),"\n",(0,n.jsxs)(a.p,{children:["Catena-X offers use case KITs to enable a multi-vender ecosystem of software solutions and services for each Catena-X use case. Solution and Service providers can create interoperable and data sovereign solutions and trusted services based on the Catena-X KITs and offer them on trusted marketplaces within the Catena-X Data Space (-> Core Service Provider A). The marketplaces are certified marketplaces that offer interoperable solutions from different solutions providers. The Core Services as well as marketplaces are part of the cxOS and are operated by certified operating companies (see Figure ",(0,n.jsx)(a.a,{href:"/docs/operating-model/what-service-map/",children:"Service Map"}),"). With this comprehensive solution portfolio, players in the automotive value chain can create business value by establishing data-driven use cases and data chains."]}),"\n",(0,n.jsx)(a.p,{children:"Trust and conformity (of Services, Offers, and potentially other non-automotive data spaces) are fundamental for Catena-X\u2019s acceptance, scalability, and value creation. Therefore, Catena-X chose and installed various neutral governance bodies \u2013 covering development and operation. The following partnerships and components in sum ensure a global data space built by best-in-class experts on trusted principles:"}),"\n",(0,n.jsxs)(a.ol,{children:["\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"Gaia-X is the basis for our overarching Trust Framework and forms the foundation for a federated, interoperable data space with trusted identities."}),"\n"]}),"\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"The International Data Space Association (IDSA) provides architecture principles that enable sovereign data exchange."}),"\n"]}),"\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"The Eclipse Foundation hosts the official open-source development project of the Catena-X ecosystem and follows the Eclipse Foundation\u2019s trusted development process."}),"\n"]}),"\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"The Catena-X Association provides industry-specific governance for the ecosystem that equally reflects the diverse interest groups within the automotive industry to serve common business needs. It also defines the vision, mission, and guiding principles for the Catena-X data space through the governance framework based on the Catena-X Statutes."}),"\n"]}),"\n"]}),"\n",(0,n.jsxs)(a.p,{children:["More specifically, in the ",(0,n.jsx)(a.strong,{children:"Catena-X operating environment"}),", the Catena-X Regulatory Framework for Data Space operations acts as a reliable mutual foundation to ensure trust, interoperability and therefore scalability. Catena-X\u2019s success largely depends on trust that every participant plays by the same, commonly set rules. By standardizing many of the relationships and agreements necessary for data exchange and bringing Catena-X use cases to life, data space participants can put their focus largely on their individual business needs rather than individual contract negotiation between business partners. Through collectively approved guidelines and templates, data exchanges on Catena-X can be seamlessly executed and operated without friction."]})]})}function h(e={}){const{wrapper:a}={...(0,s.R)(),...e.components};return a?(0,n.jsx)(a,{...e,children:(0,n.jsx)(l,{...e})}):l(e)}},4874:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/catena-x-data-ecosystem-fcef9c51f52e3f778c6034628a557cb6.png"},5074:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/the-catena-x-data-space-1ffb629fc37aca9433227da3ea2b51b9.png"},8453:(e,a,t)=>{t.d(a,{R:()=>i,x:()=>r});var n=t(6540);const s={},o=n.createContext(s);function i(e){const a=n.useContext(o);return n.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function r(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:i(e.components),n.createElement(o.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/395bc0fb.a9981247.js b/assets/js/395bc0fb.a9981247.js new file mode 100644 index 00000000..b4c9d360 --- /dev/null +++ b/assets/js/395bc0fb.a9981247.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8031],{3379:(e,a,t)=>{t.r(a),t.d(a,{assets:()=>c,contentTitle:()=>i,default:()=>h,frontMatter:()=>o,metadata:()=>r,toc:()=>d});var n=t(4848),s=t(8453);const o={sidebar_position:1},i="Why: Understanding the Catena-X Data Space",r={id:"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space",title:"Why: Understanding the Catena-X Data Space",description:"Conceptual Foundations of the Catena-X Data Ecosystem",source:"@site/versioned_docs/version-24.03/operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space.md",sourceDirName:"operating-model/why-understanding-the-catena-x-data-space",slug:"/operating-model/why-understanding-the-catena-x-data-space/",permalink:"/catenax-ev.github.io.new/docs/operating-model/why-understanding-the-catena-x-data-space/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/catenax-ev.github.io.new/docs/operating-model/why-introduction/"},next:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/catenax-ev.github.io.new/docs/operating-model/who-roles-in-the-catena-x-ecosystem/"}},c={},d=[{value:"Conceptual Foundations of the Catena-X Data Ecosystem",id:"conceptual-foundations-of-the-catena-x-data-ecosystem",level:2},{value:"The Catena-X Data Ecosystem Architecture",id:"the-catena-x-data-ecosystem-architecture",level:2}];function l(e){const a={a:"a",em:"em",h1:"h1",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",ul:"ul",...(0,s.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(a.h1,{id:"why-understanding-the-catena-x-data-space",children:"Why: Understanding the Catena-X Data Space"}),"\n",(0,n.jsx)(a.h2,{id:"conceptual-foundations-of-the-catena-x-data-ecosystem",children:"Conceptual Foundations of the Catena-X Data Ecosystem"}),"\n",(0,n.jsxs)(a.p,{children:["To comprehend the components that comprise the Catena-X operating model, it is necessary to have a basic understanding of the fundamental concepts that make up the Catena-X data ecosystem (see Figure ",(0,n.jsx)(a.a,{href:"#conceptual-foundations-of-the-catena-x-data-ecosystem",children:"Catena-X Data Ecosystem"}),"). The Catena-X data ecosystem consists of three areas: the Catena-X Automotive Network e. V., the development environment, and the operating environment."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"Catena-X Data Ecosystem",src:t(4874).A+"",width:"1127",height:"662"}),"\n",(0,n.jsx)(a.em,{children:"Catena-X Data Ecosystem"})]}),"\n",(0,n.jsxs)(a.p,{children:["The ",(0,n.jsx)(a.strong,{children:"Catena-X Automotive Network e. V."})," (in the following called \u201cCatena-X Association\u201d or \u201cthe Association\u201d) is responsible for standardization, certifications, and governance of the Catena-X ecosystem. Members can participate in committees, working groups, and expert groups to actively shape the Catena-X ecosystem. The Catena-X Association publishes standards with the goal of enabling interoperability, data-sovereignty, and security for all participants in the data space. The ecosystem participants must comply with the standards published by the Catena-X Association to work with the data space. Catena-X standards build on Gaia-X/Inter-national Data Space Association (IDSA) concepts and principles, industry standards, and best practices, among others, and extends these by automotive domain and use case-specific requirements. By certifying ecosystem participants and software components, the Catena-X Association ensures transparency and trust in the eco- system. A certification testifies, for example, that a software component is interoperable, data sovereign, and safe to use in the Catena-X data space. The Association is complemented by the ",(0,n.jsx)(a.strong,{children:"development environment"}),". The focus of the development environment is on the one hand on the creation of standardization candidates that can be submitted into the standardization process of the association. And on the other hand, the development of open-source reference implementations and other implementations for the data space. In the ",(0,n.jsx)(a.strong,{children:"operating environment"}),", the various open-source and commercial services and business applications are operated by different providers. A detailed description of the provider roles and the associated software components can be found in ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/who-roles-in-the-catena-x-ecosystem/",children:"Who: Roles in the Catena-X Ecosystem"})]})," and ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/what-service-map/",children:"What: Service Map"})]}),". All three components jointly make up the Catena-X data ecosystem. In the following chapters, the roles, responsibilities, and functions of these components are described in detail."]}),"\n",(0,n.jsx)(a.h2,{id:"the-catena-x-data-ecosystem-architecture",children:"The Catena-X Data Ecosystem Architecture"}),"\n",(0,n.jsxs)(a.p,{children:["Underlining the Catena-X data ecosystem\u2019s conceptual foundations are its individual data space components. Together, these building blocks serve as the architecture of the Catena-X data space, where each building block serves a dedicated purpose in one or several of the above-mentioned conceptual elements. An overview is depicted in Figure ",(0,n.jsx)(a.a,{href:"#the-catena-x-data-ecosystem-architecture",children:"Catena-X Data Ecosystem"})," followed by a short description of the main building blocks."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"The Catena-X Data Space",src:t(5074).A+"",width:"1034",height:"713"}),"\n",(0,n.jsx)(a.em,{children:"Catena-X Data Ecosystem"})]}),"\n",(0,n.jsx)(a.p,{children:"The global Catena-X data space is built on 5 mission-critical pillars:"}),"\n",(0,n.jsxs)(a.ul,{children:["\n",(0,n.jsxs)(a.li,{children:["a dedicated ",(0,n.jsx)(a.strong,{children:"role concept"})," covering all data space participants (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/who-roles-in-the-catena-x-ecosystem/",children:"Who: Roles in the Catena-X Ecosystem"})]}),")"]}),"\n",(0,n.jsxs)(a.li,{children:["a Service Map of foundational software services, building blocks, and standards that form the ",(0,n.jsx)(a.strong,{children:"Catena-X Operating System"})," and ",(0,n.jsx)(a.strong,{children:"Business Foundation"})," (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/what-service-map/",children:"What: Service Map"})]}),"),"]}),"\n",(0,n.jsxs)(a.li,{children:["procedures, processes, and building blocks for a trusted, scalable, and compliant ",(0,n.jsx)(a.strong,{children:"data space operation"})," (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-operations/",children:"How: Data Space Operations"})]}),"),"]}),"\n",(0,n.jsxs)(a.li,{children:["effective ",(0,n.jsx)(a.strong,{children:"data space governance"})," incl. standards, legal frameworks, (flight models) and certification (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance/",children:"How: Data Space Governance"})]}),")"]}),"\n",(0,n.jsxs)(a.li,{children:["an integrated and holistic ",(0,n.jsx)(a.strong,{children:"life cycle management ensuring compliance, interoperability"}),", and ",(0,n.jsx)(a.strong,{children:"compatibility"})," (see ",(0,n.jsxs)(a.strong,{children:["Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-life-cycle-management/",children:"How: Life Cycle Management"})]}),")"]}),"\n"]}),"\n",(0,n.jsx)(a.p,{children:"To promote adoption and collaboration, the Catena-X data space is built upon open-source principals, under the umbrella of the Eclipse Foundation. All Catena-X reference implementations and KITs are licensed under Apache 2.0 and CY BB 4.0. In order to structure and guide the development in open-source, Catena-X installed Organizational Elements (e.g., committees in the Catena-X Association), created a working group and project in Eclipse Tractus-X and defined a scalable structure for a business-oriented development and adoption of relevant artifacts and SW codes:"}),"\n",(0,n.jsxs)(a.ul,{children:["\n",(0,n.jsx)(a.li,{children:"Enablement Services"}),"\n",(0,n.jsx)(a.li,{children:"Core Services"}),"\n",(0,n.jsx)(a.li,{children:"Industry Core"}),"\n",(0,n.jsx)(a.li,{children:"and use case KITs"}),"\n"]}),"\n",(0,n.jsx)(a.p,{children:"With regard to standardization, the Catena-X Association promotes, sponsors and coordinates the overarching requirements of the Eclipse Tractus-X project. Standards are always linked, structured, and offered within those four elements."}),"\n",(0,n.jsxs)(a.p,{children:["Catena-X offers use case KITs to enable a multi-vender ecosystem of software solutions and services for each Catena-X use case. Solution and Service providers can create interoperable and data sovereign solutions and trusted services based on the Catena-X KITs and offer them on trusted marketplaces within the Catena-X Data Space (-> Core Service Provider A). The marketplaces are certified marketplaces that offer interoperable solutions from different solutions providers. The Core Services as well as marketplaces are part of the cxOS and are operated by certified operating companies (see Figure ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/operating-model/what-service-map/",children:"Service Map"}),"). With this comprehensive solution portfolio, players in the automotive value chain can create business value by establishing data-driven use cases and data chains."]}),"\n",(0,n.jsx)(a.p,{children:"Trust and conformity (of Services, Offers, and potentially other non-automotive data spaces) are fundamental for Catena-X\u2019s acceptance, scalability, and value creation. Therefore, Catena-X chose and installed various neutral governance bodies \u2013 covering development and operation. The following partnerships and components in sum ensure a global data space built by best-in-class experts on trusted principles:"}),"\n",(0,n.jsxs)(a.ol,{children:["\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"Gaia-X is the basis for our overarching Trust Framework and forms the foundation for a federated, interoperable data space with trusted identities."}),"\n"]}),"\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"The International Data Space Association (IDSA) provides architecture principles that enable sovereign data exchange."}),"\n"]}),"\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"The Eclipse Foundation hosts the official open-source development project of the Catena-X ecosystem and follows the Eclipse Foundation\u2019s trusted development process."}),"\n"]}),"\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsx)(a.p,{children:"The Catena-X Association provides industry-specific governance for the ecosystem that equally reflects the diverse interest groups within the automotive industry to serve common business needs. It also defines the vision, mission, and guiding principles for the Catena-X data space through the governance framework based on the Catena-X Statutes."}),"\n"]}),"\n"]}),"\n",(0,n.jsxs)(a.p,{children:["More specifically, in the ",(0,n.jsx)(a.strong,{children:"Catena-X operating environment"}),", the Catena-X Regulatory Framework for Data Space operations acts as a reliable mutual foundation to ensure trust, interoperability and therefore scalability. Catena-X\u2019s success largely depends on trust that every participant plays by the same, commonly set rules. By standardizing many of the relationships and agreements necessary for data exchange and bringing Catena-X use cases to life, data space participants can put their focus largely on their individual business needs rather than individual contract negotiation between business partners. Through collectively approved guidelines and templates, data exchanges on Catena-X can be seamlessly executed and operated without friction."]})]})}function h(e={}){const{wrapper:a}={...(0,s.R)(),...e.components};return a?(0,n.jsx)(a,{...e,children:(0,n.jsx)(l,{...e})}):l(e)}},4874:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/catena-x-data-ecosystem-fcef9c51f52e3f778c6034628a557cb6.png"},5074:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/the-catena-x-data-space-1ffb629fc37aca9433227da3ea2b51b9.png"},8453:(e,a,t)=>{t.d(a,{R:()=>i,x:()=>r});var n=t(6540);const s={},o=n.createContext(s);function i(e){const a=n.useContext(o);return n.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function r(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:i(e.components),n.createElement(o.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/3a2db09e.d000d160.js b/assets/js/3a2db09e.d000d160.js deleted file mode 100644 index 925ce704..00000000 --- a/assets/js/3a2db09e.d000d160.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8121],{8070:e=>{e.exports=JSON.parse('{"tags":[{"label":"Facebook","permalink":"/blog/tags/facebook","description":"Facebook tag description","count":1},{"label":"Hello","permalink":"/blog/tags/hello","description":"Hello tag description","count":2},{"label":"Docusaurus","permalink":"/blog/tags/docusaurus","description":"Docusaurus tag description","count":4},{"label":"Hola","permalink":"/blog/tags/hola","description":"Hola tag description","count":1}]}')}}]); \ No newline at end of file diff --git a/assets/js/3a483871.398477f1.js b/assets/js/3a483871.398477f1.js deleted file mode 100644 index 4afed58c..00000000 --- a/assets/js/3a483871.398477f1.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9410],{2062:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>c,contentTitle:()=>s,default:()=>u,frontMatter:()=>o,metadata:()=>r,toc:()=>d});var a=n(4848),i=n(8453);const o={sidebar_position:1},s="Why: Introduction",r={id:"operating-model/why-introduction/why-introduction",title:"Why: Introduction",description:"Relevance",source:"@site/docs/operating-model/why-introduction/why-introduction.md",sourceDirName:"operating-model/why-introduction",slug:"/operating-model/why-introduction/",permalink:"/docs/next/operating-model/why-introduction/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Operating Model",permalink:"/docs/next/operating-model/operating-model/"},next:{title:"Why: Understanding the Catena-X Data Space",permalink:"/docs/next/operating-model/why-understanding-the-catena-x-data-space/"}},c={},d=[{value:"Relevance",id:"relevance",level:2},{value:"Executive Summary",id:"executive-summary",level:2},{value:"Introduction",id:"introduction",level:3},{value:"Objectives",id:"objectives",level:3},{value:"Scope",id:"scope",level:3},{value:"Document updates",id:"document-updates",level:2}];function l(e){const t={h1:"h1",h2:"h2",h3:"h3",p:"p",...(0,i.R)(),...e.components};return(0,a.jsxs)(a.Fragment,{children:[(0,a.jsx)(t.h1,{id:"why-introduction",children:"Why: Introduction"}),"\n",(0,a.jsx)(t.h2,{id:"relevance",children:"Relevance"}),"\n",(0,a.jsx)(t.p,{children:"The Catena-X Operating Model Whitepaper is a normative document of the Catena-X Association. Normative documents outline rules, guidelines, and characteristics for activities and results for all participants within the Catena-X ecosystem. The Catena-X ecosystem includes Governance,Standardization,Certification,Development and Operations. These are established by consensus among the working groups and approved by the executive board of the Catena-X Association. As part of the Catena-X regulatory framework,this document is binding for all participants of the Catena-X ecosystem. This normative document is a foundational building block, allowing all participants to collaborate within a global ecosystem."}),"\n",(0,a.jsx)(t.h2,{id:"executive-summary",children:"Executive Summary"}),"\n",(0,a.jsx)(t.h3,{id:"introduction",children:"Introduction"}),"\n",(0,a.jsx)(t.p,{children:"With Catena-X, the automotive industry is creating targets a trustworthy, collaborative, open, and secure data space to enable a data-driven value chain for their relevant business processes. All participants can be connected in business process-centric end-to-end value chains, where everyone operates on an equal playing field, has sovereign control over their data and no lock-in effects occur. Thereby, the digitalization of intercompany processes and value chains, especially those of small and medium-sized companies, can be performed on a cost effective, timely and lasting basis. Further, it secures that market participants and competitors collaborate in a compliant and trusted way."}),"\n",(0,a.jsx)(t.h3,{id:"objectives",children:"Objectives"}),"\n",(0,a.jsx)(t.p,{children:"This document defines the operating model and processes required within the Catena-X ecosystem. The operating model is linked to the concepts and values of Gaia-X and the International Data Space Association (IDSA) to create the first open and collaborative data ecosystem for the automotive value chain. Thereby, Catena-X applies these concepts and extends them by integrating automotive-specific requirements for compliance, interoperability, and security. 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."}),"\n",(0,a.jsx)(t.h3,{id:"scope",children:"Scope"}),"\n",(0,a.jsx)(t.p,{children:"The Catena-X operating model describes the entire Catena-X ecosystem, focusing on the operating environment and its roles, processes, and solutions, and how they interact. Since Catena-X is under continuous development,the document refers, where appropriate, to dynamic content that can be found on the website of the Catena-X Association."}),"\n",(0,a.jsx)(t.h2,{id:"document-updates",children:"Document updates"}),"\n",(0,a.jsx)(t.p,{children:"The Catena-X Association releases updates to its operating model in regular intervals to always guarantee a well-functioning, up-to-date framework for its data space operations. Updates are developed within the framework regulations of the Catena-X Association and require approval from the Association\u2019s executive board. Every update of this operating model will automatically be applied to all Catena-X initiatives, existing participants, as well prospects, without further notice and individual approval. An update will be communicated in due time via the Catena-X Association."})]})}function u(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,a.jsx)(t,{...e,children:(0,a.jsx)(l,{...e})}):l(e)}},8453:(e,t,n)=>{n.d(t,{R:()=>s,x:()=>r});var a=n(6540);const i={},o=a.createContext(i);function s(e){const t=a.useContext(o);return a.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function r(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:s(e.components),a.createElement(o.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/3a483871.a8f87262.js b/assets/js/3a483871.a8f87262.js new file mode 100644 index 00000000..9208f2a9 --- /dev/null +++ b/assets/js/3a483871.a8f87262.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9410],{2062:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>c,contentTitle:()=>s,default:()=>u,frontMatter:()=>o,metadata:()=>r,toc:()=>d});var a=n(4848),i=n(8453);const o={sidebar_position:1},s="Why: Introduction",r={id:"operating-model/why-introduction/why-introduction",title:"Why: Introduction",description:"Relevance",source:"@site/docs/operating-model/why-introduction/why-introduction.md",sourceDirName:"operating-model/why-introduction",slug:"/operating-model/why-introduction/",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/why-introduction/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Operating Model",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/operating-model/"},next:{title:"Why: Understanding the Catena-X Data Space",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/why-understanding-the-catena-x-data-space/"}},c={},d=[{value:"Relevance",id:"relevance",level:2},{value:"Executive Summary",id:"executive-summary",level:2},{value:"Introduction",id:"introduction",level:3},{value:"Objectives",id:"objectives",level:3},{value:"Scope",id:"scope",level:3},{value:"Document updates",id:"document-updates",level:2}];function l(e){const t={h1:"h1",h2:"h2",h3:"h3",p:"p",...(0,i.R)(),...e.components};return(0,a.jsxs)(a.Fragment,{children:[(0,a.jsx)(t.h1,{id:"why-introduction",children:"Why: Introduction"}),"\n",(0,a.jsx)(t.h2,{id:"relevance",children:"Relevance"}),"\n",(0,a.jsx)(t.p,{children:"The Catena-X Operating Model Whitepaper is a normative document of the Catena-X Association. Normative documents outline rules, guidelines, and characteristics for activities and results for all participants within the Catena-X ecosystem. The Catena-X ecosystem includes Governance,Standardization,Certification,Development and Operations. These are established by consensus among the working groups and approved by the executive board of the Catena-X Association. As part of the Catena-X regulatory framework,this document is binding for all participants of the Catena-X ecosystem. This normative document is a foundational building block, allowing all participants to collaborate within a global ecosystem."}),"\n",(0,a.jsx)(t.h2,{id:"executive-summary",children:"Executive Summary"}),"\n",(0,a.jsx)(t.h3,{id:"introduction",children:"Introduction"}),"\n",(0,a.jsx)(t.p,{children:"With Catena-X, the automotive industry is creating targets a trustworthy, collaborative, open, and secure data space to enable a data-driven value chain for their relevant business processes. All participants can be connected in business process-centric end-to-end value chains, where everyone operates on an equal playing field, has sovereign control over their data and no lock-in effects occur. Thereby, the digitalization of intercompany processes and value chains, especially those of small and medium-sized companies, can be performed on a cost effective, timely and lasting basis. Further, it secures that market participants and competitors collaborate in a compliant and trusted way."}),"\n",(0,a.jsx)(t.h3,{id:"objectives",children:"Objectives"}),"\n",(0,a.jsx)(t.p,{children:"This document defines the operating model and processes required within the Catena-X ecosystem. The operating model is linked to the concepts and values of Gaia-X and the International Data Space Association (IDSA) to create the first open and collaborative data ecosystem for the automotive value chain. Thereby, Catena-X applies these concepts and extends them by integrating automotive-specific requirements for compliance, interoperability, and security. 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."}),"\n",(0,a.jsx)(t.h3,{id:"scope",children:"Scope"}),"\n",(0,a.jsx)(t.p,{children:"The Catena-X operating model describes the entire Catena-X ecosystem, focusing on the operating environment and its roles, processes, and solutions, and how they interact. Since Catena-X is under continuous development,the document refers, where appropriate, to dynamic content that can be found on the website of the Catena-X Association."}),"\n",(0,a.jsx)(t.h2,{id:"document-updates",children:"Document updates"}),"\n",(0,a.jsx)(t.p,{children:"The Catena-X Association releases updates to its operating model in regular intervals to always guarantee a well-functioning, up-to-date framework for its data space operations. Updates are developed within the framework regulations of the Catena-X Association and require approval from the Association\u2019s executive board. Every update of this operating model will automatically be applied to all Catena-X initiatives, existing participants, as well prospects, without further notice and individual approval. An update will be communicated in due time via the Catena-X Association."})]})}function u(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,a.jsx)(t,{...e,children:(0,a.jsx)(l,{...e})}):l(e)}},8453:(e,t,n)=>{n.d(t,{R:()=>s,x:()=>r});var a=n(6540);const i={},o=a.createContext(i);function s(e){const t=a.useContext(o);return a.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function r(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:s(e.components),a.createElement(o.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/3ce65734.d0cfde38.js b/assets/js/3ce65734.d0cfde38.js deleted file mode 100644 index 94e61e71..00000000 --- a/assets/js/3ce65734.d0cfde38.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[2825],{4990:(e,a,t)=>{t.r(a),t.d(a,{assets:()=>c,contentTitle:()=>o,default:()=>h,frontMatter:()=>s,metadata:()=>r,toc:()=>d});var n=t(4848),i=t(8453);const s={sidebar_position:1},o="What: Service Map",r={id:"operating-model/what-service-map/what-service-map",title:"What: Service Map",description:"The architecture of the Catena-X Operating System (cxOS) is derived from the reference",source:"@site/docs/operating-model/what-service-map/what-service-map.md",sourceDirName:"operating-model/what-service-map",slug:"/operating-model/what-service-map/",permalink:"/docs/next/operating-model/what-service-map/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/"},next:{title:"How: Data Space Operations",permalink:"/docs/next/operating-model/how-data-space-operations/"}},c={},d=[{value:"Enablement Services",id:"enablement-services",level:2},{value:"Core Services",id:"core-services",level:2},{value:"Onboarding Services",id:"onboarding-services",level:2},{value:"Use Cases",id:"use-cases",level:2},{value:"KITs \u2013 Keep It Together",id:"kits--keep-it-together",level:3},{value:"New Use Cases and Direct Collaboration",id:"new-use-cases-and-direct-collaboration",level:3},{value:"Initiate new use case",id:"initiate-new-use-case",level:4},{value:"Direct collaboration (no multi-tier approach)",id:"direct-collaboration-no-multi-tier-approach",level:4}];function l(e){const a={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",h4:"h4",img:"img",p:"p",strong:"strong",...(0,i.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(a.h1,{id:"what-service-map",children:"What: Service Map"}),"\n",(0,n.jsxs)(a.p,{children:["The architecture of the Catena-X Operating System (cxOS) is derived from the reference\narchitectures of Industrial Data Space Association (IDSA) and Gaia-X. The cxOS consists of\nthree areas: Core, Onboarding, and Enablement Services shown in Figure ",(0,n.jsx)(a.a,{href:"/docs/next/operating-model/what-service-map/",children:"Service Map"}),"."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"Service Map (Deployment View)",src:t(2762).A+"",width:"1641",height:"782"}),"\n",(0,n.jsx)(a.em,{children:"Service Map (Deployment View)"})]}),"\n",(0,n.jsx)(a.p,{children:"The cxOS is the technical foundation enabling business use cases to operate in a network-enabled manner across company boundaries. The operating system offers various capabilities:"}),"\n",(0,n.jsx)(a.h2,{id:"enablement-services",children:"Enablement Services"}),"\n",(0,n.jsx)(a.p,{children:"The Enablement Services are a bundle of decentral services that enable participation in the Catena-X data space. Each participant must deploy and use the enablement services to connect to the data space and enable standardized interactions based on the requirements of the respective use case. They ensure the strategic value proposition of technical/semantic interoperability and (data) sovereignty."}),"\n",(0,n.jsx)(a.p,{children:"The connector (e.g., EDC) based on the data space protocol and the identity wallet form the mandatory basis of enablement services enabling standardized technical connectivity and sovereign data exchange. All participants can use them to establish a basic connection to the data space, independent of the business use case."}),"\n",(0,n.jsx)(a.p,{children:"In addition to generic data-exchange capabilities, enabling services include context-specific service offerings. Examples are the Asset Administration Shell (AAS) as harmonized access layer for digital twins, the Decentral Digital Twin Registry (DDTR) for local discoverability of digital twins in decentral organized data spaces or the Item Relationship Service (IRS) for building data chains and iterating through a tree structure of digital twins."}),"\n",(0,n.jsxs)(a.p,{children:["Please note that there are various options for running enablement services, ranging from leveraging software-asa-service solutions to local deployments of open-source reference implementations. Further information on deployment and usage premises can be found in Chapter ",(0,n.jsx)(a.a,{href:"/docs/next/operating-model/how-data-space-operations/#edc-deployment-and-usage-premises",children:"EDC Deployment and Usage Premises"}),"."]}),"\n",(0,n.jsx)(a.h2,{id:"core-services",children:"Core Services"}),"\n",(0,n.jsx)(a.p,{children:"In contrast to Enablement Services, Core Services are provided and operated by Core Service providers A/B. Core services provide common accessibility and discoverability functionalities for data space participants. Examples include BPN issuer for maintaining business partner numbers, and participant information, IAM solutions for identity and access management, and discovery services to localize the address of assets in decentral organized registries across the data space. The Core Services can be divided into two areas:"}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"Core Services A"})," lists Core Services that can be operated \u201cn\u201d times in the Catena-X data space."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"Core Services B"})," lists Core Services that can only be operated once in the Catena-X data space due to business reasons or technical limitations and are therefore tendered via the nomination process of the Association."]}),"\n",(0,n.jsx)(a.p,{children:"Some of the Core Services, such as the Managed Identity Wallet, are by nature Enablement Services, but because of technical reasons they are considered Core Services B as an interim solution."}),"\n",(0,n.jsx)(a.h2,{id:"onboarding-services",children:"Onboarding Services"}),"\n",(0,n.jsxs)(a.p,{children:["The Onboarding Services are provided and operated by OSPs. Onboarding Services enable participants to onboard into the Catena-X data space. As shown in Chapter ",(0,n.jsx)(a.a,{href:"/docs/next/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),", the scope of Onboarding Services will change over time. The Onboarding Services can be divided into two areas:"]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"Onboarding Services"})," list the services that ensure a standardized and compliant Catena-X onboarding process (e.g., registration process)."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"External Onboarding Services"})," list the services that OSPs must integrate and use to implement a trusted onboarding process but are developed and operated by an external initiative or provider."]}),"\n",(0,n.jsx)(a.h2,{id:"use-cases",children:"Use Cases"}),"\n",(0,n.jsx)(a.p,{children:"The goal of a Catena-X use case is to solve a specific business problem and to create value for data providers and consumers. To do this, the Catena-X Association demands and promotes that use cases create Standards and KITs to enable a multi-vendor ecosystem of interoperable and compatible business applications (see: business application). Achieving network effects in the Catena-X ecosystem is critical to success and depends on the active participation of users and the creation of appealing business apps, especially for SMEs"}),"\n",(0,n.jsx)(a.h3,{id:"kits--keep-it-together",children:"KITs \u2013 Keep It Together"}),"\n",(0,n.jsxs)(a.p,{children:["KIT, short for Keep It Together, bundles all necessary resources and technical documentation designed to adopt a Catena-X use case for all data space participants (see Figure ",(0,n.jsx)(a.a,{href:"/docs/next/operating-model/what-service-map/#kits--keep-it-together",children:"KITs Toolbox"}),")."]}),"\n",(0,n.jsxs)(a.p,{children:["A KIT is always structured in the same way and supports the individual journey of a company joining the Catena-X data space. To ensure interoperability and data sovereignty in Catena-X use cases, adherence to a minimum set of elements is required, including semantic models for data integration and understanding, logic and schemas for value calculation, API implementation for technical communication, and access and usage policies to maintain data sovereignty. A KIT consists of various other artifacts in addition to the minimum set. A comprehensive overview of the artefacts can be found on the ",(0,n.jsx)(a.a,{href:"https://eclipse-tractusx.github.io/",children:"Tractus-X project website"}),"."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"KITs Toolbox",src:t(8199).A+"",width:"1361",height:"746"}),"\n",(0,n.jsx)(a.em,{children:"KITs Toolbox"})]}),"\n",(0,n.jsx)(a.p,{children:"DPCs that are part of the automotive value chain and strive to participate in a Catena-X use case require technical support, specifications, and tutorials. For instance, a production company may need to exchange product carbon footprint data with its partners. KITs consolidate the necessary software components, standards, access and usage policies, and code examples, ensuring these companies have everything required to successfully participate in a Catena-X use case."}),"\n",(0,n.jsx)(a.p,{children:"BAPs interested in offering a business application for a specific use case on one of the Catena-X marketplaces. These companies need to align their existing solutions with Catena-X requirements. Within a KIT, they receive guidelines and the technical support necessary for adapting their solutions to meet Catena-X conformity based on our five steps to Catena-X: Inform, connect, boost, adapt, utilize. KITs are the way forward to create a valuable multi-vendor ecosystem to promote seamless interoperability between different commercial solutions."}),"\n",(0,n.jsx)(a.h3,{id:"new-use-cases-and-direct-collaboration",children:"New Use Cases and Direct Collaboration"}),"\n",(0,n.jsx)(a.p,{children:"In addition to the first 10 use cases that have been initially developed in the Catena-X Consortium and are now governed by the Association Committees (e.g., Sustainability Committee), data space participants have the following scenarios for collaboration:"}),"\n",(0,n.jsx)(a.h4,{id:"initiate-new-use-case",children:"Initiate new use case"}),"\n",(0,n.jsx)(a.p,{children:"Any Catena-X Association member can initiate a new use case by creating a working in the Catena-X Association or expand an existing committee (whatever suits the purpose best, the final judgement is made by the Board of the Association). The goal of a committee or working group is to discuss and define a common vision, roadmap, standards, KITs, and other open-source artefacts for the use cases with focus on interoperability and data sovereignty to create multi-tier value chains for a dedicated business process."}),"\n",(0,n.jsx)(a.p,{children:"To validate the value proposition or technical specifications, a new use case can be tested in future either in a sandbox environment of the CSP-B or in the test environments of the Catena-X Association. Note that new uses cases without standards provide only limited interoperability, require individual use case policies, and cannot be certified and thus not be listed on one of the marketplaces and are therefore not supported and trusted."}),"\n",(0,n.jsx)(a.h4,{id:"direct-collaboration-no-multi-tier-approach",children:"Direct collaboration (no multi-tier approach)"}),"\n",(0,n.jsx)(a.p,{children:"The Catena-X data space also enables secure and sovereign data exchange for direct collaboration between data provider and consumer. In this scenario, the data provider and consumer are responsible for defining a bilateral semantic model, as well as appropriate usage and access policies. Alternatively, they can make use of existing usage and access policy that meets their needs. The goal of the Catena-X data space remains to always create interoperable use cases with consistent data chains. Note that direct collaboration without standards provides only limited interoperability and cannot be certified and thus not be listed on one of the marketplaces."})]})}function h(e={}){const{wrapper:a}={...(0,i.R)(),...e.components};return a?(0,n.jsx)(a,{...e,children:(0,n.jsx)(l,{...e})}):l(e)}},8199:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/kits-toolbox-6f9dbad8dd052a62be01b7abcf6ab8c7.png"},2762:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/service-map-deployment-view-14a4dacf11a39f970f8d669aa3cc4af1.png"},8453:(e,a,t)=>{t.d(a,{R:()=>o,x:()=>r});var n=t(6540);const i={},s=n.createContext(i);function o(e){const a=n.useContext(s);return n.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function r(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:o(e.components),n.createElement(s.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/3ce65734.da2b09c7.js b/assets/js/3ce65734.da2b09c7.js new file mode 100644 index 00000000..ea0fac97 --- /dev/null +++ b/assets/js/3ce65734.da2b09c7.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[2825],{4990:(e,a,t)=>{t.r(a),t.d(a,{assets:()=>c,contentTitle:()=>o,default:()=>h,frontMatter:()=>s,metadata:()=>r,toc:()=>d});var n=t(4848),i=t(8453);const s={sidebar_position:1},o="What: Service Map",r={id:"operating-model/what-service-map/what-service-map",title:"What: Service Map",description:"The architecture of the Catena-X Operating System (cxOS) is derived from the reference",source:"@site/docs/operating-model/what-service-map/what-service-map.md",sourceDirName:"operating-model/what-service-map",slug:"/operating-model/what-service-map/",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/what-service-map/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/"},next:{title:"How: Data Space Operations",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-operations/"}},c={},d=[{value:"Enablement Services",id:"enablement-services",level:2},{value:"Core Services",id:"core-services",level:2},{value:"Onboarding Services",id:"onboarding-services",level:2},{value:"Use Cases",id:"use-cases",level:2},{value:"KITs \u2013 Keep It Together",id:"kits--keep-it-together",level:3},{value:"New Use Cases and Direct Collaboration",id:"new-use-cases-and-direct-collaboration",level:3},{value:"Initiate new use case",id:"initiate-new-use-case",level:4},{value:"Direct collaboration (no multi-tier approach)",id:"direct-collaboration-no-multi-tier-approach",level:4}];function l(e){const a={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",h4:"h4",img:"img",p:"p",strong:"strong",...(0,i.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(a.h1,{id:"what-service-map",children:"What: Service Map"}),"\n",(0,n.jsxs)(a.p,{children:["The architecture of the Catena-X Operating System (cxOS) is derived from the reference\narchitectures of Industrial Data Space Association (IDSA) and Gaia-X. The cxOS consists of\nthree areas: Core, Onboarding, and Enablement Services shown in Figure ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/what-service-map/",children:"Service Map"}),"."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"Service Map (Deployment View)",src:t(2762).A+"",width:"1641",height:"782"}),"\n",(0,n.jsx)(a.em,{children:"Service Map (Deployment View)"})]}),"\n",(0,n.jsx)(a.p,{children:"The cxOS is the technical foundation enabling business use cases to operate in a network-enabled manner across company boundaries. The operating system offers various capabilities:"}),"\n",(0,n.jsx)(a.h2,{id:"enablement-services",children:"Enablement Services"}),"\n",(0,n.jsx)(a.p,{children:"The Enablement Services are a bundle of decentral services that enable participation in the Catena-X data space. Each participant must deploy and use the enablement services to connect to the data space and enable standardized interactions based on the requirements of the respective use case. They ensure the strategic value proposition of technical/semantic interoperability and (data) sovereignty."}),"\n",(0,n.jsx)(a.p,{children:"The connector (e.g., EDC) based on the data space protocol and the identity wallet form the mandatory basis of enablement services enabling standardized technical connectivity and sovereign data exchange. All participants can use them to establish a basic connection to the data space, independent of the business use case."}),"\n",(0,n.jsx)(a.p,{children:"In addition to generic data-exchange capabilities, enabling services include context-specific service offerings. Examples are the Asset Administration Shell (AAS) as harmonized access layer for digital twins, the Decentral Digital Twin Registry (DDTR) for local discoverability of digital twins in decentral organized data spaces or the Item Relationship Service (IRS) for building data chains and iterating through a tree structure of digital twins."}),"\n",(0,n.jsxs)(a.p,{children:["Please note that there are various options for running enablement services, ranging from leveraging software-asa-service solutions to local deployments of open-source reference implementations. Further information on deployment and usage premises can be found in Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-operations/#edc-deployment-and-usage-premises",children:"EDC Deployment and Usage Premises"}),"."]}),"\n",(0,n.jsx)(a.h2,{id:"core-services",children:"Core Services"}),"\n",(0,n.jsx)(a.p,{children:"In contrast to Enablement Services, Core Services are provided and operated by Core Service providers A/B. Core services provide common accessibility and discoverability functionalities for data space participants. Examples include BPN issuer for maintaining business partner numbers, and participant information, IAM solutions for identity and access management, and discovery services to localize the address of assets in decentral organized registries across the data space. The Core Services can be divided into two areas:"}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"Core Services A"})," lists Core Services that can be operated \u201cn\u201d times in the Catena-X data space."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"Core Services B"})," lists Core Services that can only be operated once in the Catena-X data space due to business reasons or technical limitations and are therefore tendered via the nomination process of the Association."]}),"\n",(0,n.jsx)(a.p,{children:"Some of the Core Services, such as the Managed Identity Wallet, are by nature Enablement Services, but because of technical reasons they are considered Core Services B as an interim solution."}),"\n",(0,n.jsx)(a.h2,{id:"onboarding-services",children:"Onboarding Services"}),"\n",(0,n.jsxs)(a.p,{children:["The Onboarding Services are provided and operated by OSPs. Onboarding Services enable participants to onboard into the Catena-X data space. As shown in Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),", the scope of Onboarding Services will change over time. The Onboarding Services can be divided into two areas:"]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"Onboarding Services"})," list the services that ensure a standardized and compliant Catena-X onboarding process (e.g., registration process)."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"External Onboarding Services"})," list the services that OSPs must integrate and use to implement a trusted onboarding process but are developed and operated by an external initiative or provider."]}),"\n",(0,n.jsx)(a.h2,{id:"use-cases",children:"Use Cases"}),"\n",(0,n.jsx)(a.p,{children:"The goal of a Catena-X use case is to solve a specific business problem and to create value for data providers and consumers. To do this, the Catena-X Association demands and promotes that use cases create Standards and KITs to enable a multi-vendor ecosystem of interoperable and compatible business applications (see: business application). Achieving network effects in the Catena-X ecosystem is critical to success and depends on the active participation of users and the creation of appealing business apps, especially for SMEs"}),"\n",(0,n.jsx)(a.h3,{id:"kits--keep-it-together",children:"KITs \u2013 Keep It Together"}),"\n",(0,n.jsxs)(a.p,{children:["KIT, short for Keep It Together, bundles all necessary resources and technical documentation designed to adopt a Catena-X use case for all data space participants (see Figure ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/what-service-map/#kits--keep-it-together",children:"KITs Toolbox"}),")."]}),"\n",(0,n.jsxs)(a.p,{children:["A KIT is always structured in the same way and supports the individual journey of a company joining the Catena-X data space. To ensure interoperability and data sovereignty in Catena-X use cases, adherence to a minimum set of elements is required, including semantic models for data integration and understanding, logic and schemas for value calculation, API implementation for technical communication, and access and usage policies to maintain data sovereignty. A KIT consists of various other artifacts in addition to the minimum set. A comprehensive overview of the artefacts can be found on the ",(0,n.jsx)(a.a,{href:"https://eclipse-tractusx.github.io/",children:"Tractus-X project website"}),"."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"KITs Toolbox",src:t(8199).A+"",width:"1361",height:"746"}),"\n",(0,n.jsx)(a.em,{children:"KITs Toolbox"})]}),"\n",(0,n.jsx)(a.p,{children:"DPCs that are part of the automotive value chain and strive to participate in a Catena-X use case require technical support, specifications, and tutorials. For instance, a production company may need to exchange product carbon footprint data with its partners. KITs consolidate the necessary software components, standards, access and usage policies, and code examples, ensuring these companies have everything required to successfully participate in a Catena-X use case."}),"\n",(0,n.jsx)(a.p,{children:"BAPs interested in offering a business application for a specific use case on one of the Catena-X marketplaces. These companies need to align their existing solutions with Catena-X requirements. Within a KIT, they receive guidelines and the technical support necessary for adapting their solutions to meet Catena-X conformity based on our five steps to Catena-X: Inform, connect, boost, adapt, utilize. KITs are the way forward to create a valuable multi-vendor ecosystem to promote seamless interoperability between different commercial solutions."}),"\n",(0,n.jsx)(a.h3,{id:"new-use-cases-and-direct-collaboration",children:"New Use Cases and Direct Collaboration"}),"\n",(0,n.jsx)(a.p,{children:"In addition to the first 10 use cases that have been initially developed in the Catena-X Consortium and are now governed by the Association Committees (e.g., Sustainability Committee), data space participants have the following scenarios for collaboration:"}),"\n",(0,n.jsx)(a.h4,{id:"initiate-new-use-case",children:"Initiate new use case"}),"\n",(0,n.jsx)(a.p,{children:"Any Catena-X Association member can initiate a new use case by creating a working in the Catena-X Association or expand an existing committee (whatever suits the purpose best, the final judgement is made by the Board of the Association). The goal of a committee or working group is to discuss and define a common vision, roadmap, standards, KITs, and other open-source artefacts for the use cases with focus on interoperability and data sovereignty to create multi-tier value chains for a dedicated business process."}),"\n",(0,n.jsx)(a.p,{children:"To validate the value proposition or technical specifications, a new use case can be tested in future either in a sandbox environment of the CSP-B or in the test environments of the Catena-X Association. Note that new uses cases without standards provide only limited interoperability, require individual use case policies, and cannot be certified and thus not be listed on one of the marketplaces and are therefore not supported and trusted."}),"\n",(0,n.jsx)(a.h4,{id:"direct-collaboration-no-multi-tier-approach",children:"Direct collaboration (no multi-tier approach)"}),"\n",(0,n.jsx)(a.p,{children:"The Catena-X data space also enables secure and sovereign data exchange for direct collaboration between data provider and consumer. In this scenario, the data provider and consumer are responsible for defining a bilateral semantic model, as well as appropriate usage and access policies. Alternatively, they can make use of existing usage and access policy that meets their needs. The goal of the Catena-X data space remains to always create interoperable use cases with consistent data chains. Note that direct collaboration without standards provides only limited interoperability and cannot be certified and thus not be listed on one of the marketplaces."})]})}function h(e={}){const{wrapper:a}={...(0,i.R)(),...e.components};return a?(0,n.jsx)(a,{...e,children:(0,n.jsx)(l,{...e})}):l(e)}},8199:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/kits-toolbox-6f9dbad8dd052a62be01b7abcf6ab8c7.png"},2762:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/service-map-deployment-view-14a4dacf11a39f970f8d669aa3cc4af1.png"},8453:(e,a,t)=>{t.d(a,{R:()=>o,x:()=>r});var n=t(6540);const i={},s=n.createContext(i);function o(e){const a=n.useContext(s);return n.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function r(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:o(e.components),n.createElement(s.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/48cc5724.66988744.js b/assets/js/48cc5724.66988744.js new file mode 100644 index 00000000..2033d7ba --- /dev/null +++ b/assets/js/48cc5724.66988744.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[855],{72:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>a,contentTitle:()=>r,default:()=>u,frontMatter:()=>o,metadata:()=>l,toc:()=>c});var t=i(4848),s=i(8453);const o={},r="How to Work with GitHub",l={type:"mdx",permalink:"/catenax-ev.github.io.new/getting-started-github",source:"@site/src/pages/getting-started-github.md",title:"How to Work with GitHub",description:"GitHub is a powerful platform for version control, collaboration, and project management. Whether you're a beginner or an experienced developer, understanding how to effectively use GitHub is essential. This guide provides an overview of common GitHub workflows and best practices.",frontMatter:{},unlisted:!1},a={},c=[{value:"Getting Started",id:"getting-started",level:2},{value:"Creating a Repository",id:"creating-a-repository",level:2},{value:"Cloning a Repository",id:"cloning-a-repository",level:2},{value:"Making Changes",id:"making-changes",level:2},{value:"Branching",id:"branching",level:2},{value:"Committing Changes",id:"committing-changes",level:2},{value:"Pushing Changes",id:"pushing-changes",level:2},{value:"Pull Requests",id:"pull-requests",level:2},{value:"Managing Issues",id:"managing-issues",level:2},{value:"Collaborating with Others",id:"collaborating-with-others",level:2},{value:"GitHub Pages",id:"github-pages",level:2},{value:"GitHub Actions",id:"github-actions",level:2}];function h(e){const n={a:"a",code:"code",h1:"h1",h2:"h2",hr:"hr",li:"li",ol:"ol",p:"p",pre:"pre",ul:"ul",...(0,s.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(n.h1,{id:"how-to-work-with-github",children:"How to Work with GitHub"}),"\n",(0,t.jsx)(n.p,{children:"GitHub is a powerful platform for version control, collaboration, and project management. Whether you're a beginner or an experienced developer, understanding how to effectively use GitHub is essential. This guide provides an overview of common GitHub workflows and best practices."}),"\n",(0,t.jsx)(n.h2,{id:"getting-started",children:"Getting Started"}),"\n",(0,t.jsxs)(n.p,{children:["To get started with GitHub, you'll need to create an account on ",(0,t.jsx)(n.a,{href:"https://github.com/",children:"GitHub"}),". Once you've signed up, you can start using GitHub to host your code repositories and collaborate with others."]}),"\n",(0,t.jsx)(n.h2,{id:"creating-a-repository",children:"Creating a Repository"}),"\n",(0,t.jsx)(n.p,{children:"To create a new repository on GitHub:"}),"\n",(0,t.jsxs)(n.ol,{children:["\n",(0,t.jsx)(n.li,{children:"Navigate to your GitHub profile."}),"\n",(0,t.jsx)(n.li,{children:'Click on the "New" button.'}),"\n",(0,t.jsx)(n.li,{children:"Fill in the repository name, description, and other details."}),"\n",(0,t.jsx)(n.li,{children:"Choose visibility settings (public/private)."}),"\n",(0,t.jsx)(n.li,{children:'Click "Create repository".'}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"cloning-a-repository",children:"Cloning a Repository"}),"\n",(0,t.jsx)(n.p,{children:"To clone a repository to your local machine:"}),"\n",(0,t.jsx)(n.pre,{children:(0,t.jsx)(n.code,{className:"language-bash",children:"git clone \n"})}),"\n",(0,t.jsx)(n.h2,{id:"making-changes",children:"Making Changes"}),"\n",(0,t.jsxs)(n.ol,{children:["\n",(0,t.jsxs)(n.li,{children:["Make sure you're in the right branch (",(0,t.jsx)(n.code,{children:"git checkout "}),")."]}),"\n",(0,t.jsx)(n.li,{children:"Make your changes to the files."}),"\n",(0,t.jsx)(n.li,{children:"Save the changes."}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"branching",children:"Branching"}),"\n",(0,t.jsx)(n.p,{children:"Branches allow you to work on different features or fixes without affecting the main codebase."}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:["Create a new branch: ",(0,t.jsx)(n.code,{children:"git checkout -b "})]}),"\n",(0,t.jsxs)(n.li,{children:["Switch to an existing branch: ",(0,t.jsx)(n.code,{children:"git checkout "})]}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"committing-changes",children:"Committing Changes"}),"\n",(0,t.jsx)(n.p,{children:"After making changes, commit them to your local repository:"}),"\n",(0,t.jsx)(n.pre,{children:(0,t.jsx)(n.code,{className:"language-bash",children:'git add .\ngit commit -m "Descriptive commit message"\n'})}),"\n",(0,t.jsx)(n.h2,{id:"pushing-changes",children:"Pushing Changes"}),"\n",(0,t.jsx)(n.p,{children:"To push your changes to the remote repository:"}),"\n",(0,t.jsx)(n.pre,{children:(0,t.jsx)(n.code,{className:"language-bash",children:"git push origin \n"})}),"\n",(0,t.jsx)(n.h2,{id:"pull-requests",children:"Pull Requests"}),"\n",(0,t.jsx)(n.p,{children:"Pull requests are used to propose changes to a repository. To create a pull request:"}),"\n",(0,t.jsxs)(n.ol,{children:["\n",(0,t.jsx)(n.li,{children:"Navigate to the repository on GitHub."}),"\n",(0,t.jsx)(n.li,{children:'Click on the "Pull requests" tab.'}),"\n",(0,t.jsx)(n.li,{children:'Click on the "New pull request" button.'}),"\n",(0,t.jsx)(n.li,{children:"Select the branches you want to merge."}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"managing-issues",children:"Managing Issues"}),"\n",(0,t.jsx)(n.p,{children:"GitHub Issues are used to track tasks, enhancements, and bugs. To create an issue:"}),"\n",(0,t.jsxs)(n.ol,{children:["\n",(0,t.jsx)(n.li,{children:"Navigate to the repository on GitHub."}),"\n",(0,t.jsx)(n.li,{children:'Click on the "Issues" tab.'}),"\n",(0,t.jsx)(n.li,{children:'Click on the "New issue" button.'}),"\n",(0,t.jsx)(n.li,{children:"Fill in the details and submit."}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"collaborating-with-others",children:"Collaborating with Others"}),"\n",(0,t.jsx)(n.p,{children:"GitHub enables collaboration with team members and contributors through:"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Pull requests"}),"\n",(0,t.jsx)(n.li,{children:"Code reviews"}),"\n",(0,t.jsx)(n.li,{children:"Issue tracking"}),"\n",(0,t.jsx)(n.li,{children:"Project boards"}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"github-pages",children:"GitHub Pages"}),"\n",(0,t.jsx)(n.p,{children:"GitHub Pages allows you to host static websites directly from your GitHub repository."}),"\n",(0,t.jsx)(n.h2,{id:"github-actions",children:"GitHub Actions"}),"\n",(0,t.jsx)(n.p,{children:"GitHub Actions automate workflows such as testing, building, and deploying your code."}),"\n",(0,t.jsx)(n.hr,{}),"\n",(0,t.jsx)(n.p,{children:"This guide covers the basics of working with GitHub. Explore GitHub's documentation and resources to dive deeper into specific features and workflows."})]})}function u(e={}){const{wrapper:n}={...(0,s.R)(),...e.components};return n?(0,t.jsx)(n,{...e,children:(0,t.jsx)(h,{...e})}):h(e)}},8453:(e,n,i)=>{i.d(n,{R:()=>r,x:()=>l});var t=i(6540);const s={},o=t.createContext(s);function r(e){const n=t.useContext(o);return t.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function l(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:r(e.components),t.createElement(o.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/48cc5724.9b95328e.js b/assets/js/48cc5724.9b95328e.js deleted file mode 100644 index 439f14a6..00000000 --- a/assets/js/48cc5724.9b95328e.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[855],{72:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>a,contentTitle:()=>r,default:()=>d,frontMatter:()=>o,metadata:()=>l,toc:()=>c});var t=i(4848),s=i(8453);const o={},r="How to Work with GitHub",l={type:"mdx",permalink:"/getting-started-github",source:"@site/src/pages/getting-started-github.md",title:"How to Work with GitHub",description:"GitHub is a powerful platform for version control, collaboration, and project management. Whether you're a beginner or an experienced developer, understanding how to effectively use GitHub is essential. This guide provides an overview of common GitHub workflows and best practices.",frontMatter:{},unlisted:!1},a={},c=[{value:"Getting Started",id:"getting-started",level:2},{value:"Creating a Repository",id:"creating-a-repository",level:2},{value:"Cloning a Repository",id:"cloning-a-repository",level:2},{value:"Making Changes",id:"making-changes",level:2},{value:"Branching",id:"branching",level:2},{value:"Committing Changes",id:"committing-changes",level:2},{value:"Pushing Changes",id:"pushing-changes",level:2},{value:"Pull Requests",id:"pull-requests",level:2},{value:"Managing Issues",id:"managing-issues",level:2},{value:"Collaborating with Others",id:"collaborating-with-others",level:2},{value:"GitHub Pages",id:"github-pages",level:2},{value:"GitHub Actions",id:"github-actions",level:2}];function h(e){const n={a:"a",code:"code",h1:"h1",h2:"h2",hr:"hr",li:"li",ol:"ol",p:"p",pre:"pre",ul:"ul",...(0,s.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(n.h1,{id:"how-to-work-with-github",children:"How to Work with GitHub"}),"\n",(0,t.jsx)(n.p,{children:"GitHub is a powerful platform for version control, collaboration, and project management. Whether you're a beginner or an experienced developer, understanding how to effectively use GitHub is essential. This guide provides an overview of common GitHub workflows and best practices."}),"\n",(0,t.jsx)(n.h2,{id:"getting-started",children:"Getting Started"}),"\n",(0,t.jsxs)(n.p,{children:["To get started with GitHub, you'll need to create an account on ",(0,t.jsx)(n.a,{href:"https://github.com/",children:"GitHub"}),". Once you've signed up, you can start using GitHub to host your code repositories and collaborate with others."]}),"\n",(0,t.jsx)(n.h2,{id:"creating-a-repository",children:"Creating a Repository"}),"\n",(0,t.jsx)(n.p,{children:"To create a new repository on GitHub:"}),"\n",(0,t.jsxs)(n.ol,{children:["\n",(0,t.jsx)(n.li,{children:"Navigate to your GitHub profile."}),"\n",(0,t.jsx)(n.li,{children:'Click on the "New" button.'}),"\n",(0,t.jsx)(n.li,{children:"Fill in the repository name, description, and other details."}),"\n",(0,t.jsx)(n.li,{children:"Choose visibility settings (public/private)."}),"\n",(0,t.jsx)(n.li,{children:'Click "Create repository".'}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"cloning-a-repository",children:"Cloning a Repository"}),"\n",(0,t.jsx)(n.p,{children:"To clone a repository to your local machine:"}),"\n",(0,t.jsx)(n.pre,{children:(0,t.jsx)(n.code,{className:"language-bash",children:"git clone \n"})}),"\n",(0,t.jsx)(n.h2,{id:"making-changes",children:"Making Changes"}),"\n",(0,t.jsxs)(n.ol,{children:["\n",(0,t.jsxs)(n.li,{children:["Make sure you're in the right branch (",(0,t.jsx)(n.code,{children:"git checkout "}),")."]}),"\n",(0,t.jsx)(n.li,{children:"Make your changes to the files."}),"\n",(0,t.jsx)(n.li,{children:"Save the changes."}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"branching",children:"Branching"}),"\n",(0,t.jsx)(n.p,{children:"Branches allow you to work on different features or fixes without affecting the main codebase."}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:["Create a new branch: ",(0,t.jsx)(n.code,{children:"git checkout -b "})]}),"\n",(0,t.jsxs)(n.li,{children:["Switch to an existing branch: ",(0,t.jsx)(n.code,{children:"git checkout "})]}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"committing-changes",children:"Committing Changes"}),"\n",(0,t.jsx)(n.p,{children:"After making changes, commit them to your local repository:"}),"\n",(0,t.jsx)(n.pre,{children:(0,t.jsx)(n.code,{className:"language-bash",children:'git add .\ngit commit -m "Descriptive commit message"\n'})}),"\n",(0,t.jsx)(n.h2,{id:"pushing-changes",children:"Pushing Changes"}),"\n",(0,t.jsx)(n.p,{children:"To push your changes to the remote repository:"}),"\n",(0,t.jsx)(n.pre,{children:(0,t.jsx)(n.code,{className:"language-bash",children:"git push origin \n"})}),"\n",(0,t.jsx)(n.h2,{id:"pull-requests",children:"Pull Requests"}),"\n",(0,t.jsx)(n.p,{children:"Pull requests are used to propose changes to a repository. To create a pull request:"}),"\n",(0,t.jsxs)(n.ol,{children:["\n",(0,t.jsx)(n.li,{children:"Navigate to the repository on GitHub."}),"\n",(0,t.jsx)(n.li,{children:'Click on the "Pull requests" tab.'}),"\n",(0,t.jsx)(n.li,{children:'Click on the "New pull request" button.'}),"\n",(0,t.jsx)(n.li,{children:"Select the branches you want to merge."}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"managing-issues",children:"Managing Issues"}),"\n",(0,t.jsx)(n.p,{children:"GitHub Issues are used to track tasks, enhancements, and bugs. To create an issue:"}),"\n",(0,t.jsxs)(n.ol,{children:["\n",(0,t.jsx)(n.li,{children:"Navigate to the repository on GitHub."}),"\n",(0,t.jsx)(n.li,{children:'Click on the "Issues" tab.'}),"\n",(0,t.jsx)(n.li,{children:'Click on the "New issue" button.'}),"\n",(0,t.jsx)(n.li,{children:"Fill in the details and submit."}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"collaborating-with-others",children:"Collaborating with Others"}),"\n",(0,t.jsx)(n.p,{children:"GitHub enables collaboration with team members and contributors through:"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Pull requests"}),"\n",(0,t.jsx)(n.li,{children:"Code reviews"}),"\n",(0,t.jsx)(n.li,{children:"Issue tracking"}),"\n",(0,t.jsx)(n.li,{children:"Project boards"}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"github-pages",children:"GitHub Pages"}),"\n",(0,t.jsx)(n.p,{children:"GitHub Pages allows you to host static websites directly from your GitHub repository."}),"\n",(0,t.jsx)(n.h2,{id:"github-actions",children:"GitHub Actions"}),"\n",(0,t.jsx)(n.p,{children:"GitHub Actions automate workflows such as testing, building, and deploying your code."}),"\n",(0,t.jsx)(n.hr,{}),"\n",(0,t.jsx)(n.p,{children:"This guide covers the basics of working with GitHub. Explore GitHub's documentation and resources to dive deeper into specific features and workflows."})]})}function d(e={}){const{wrapper:n}={...(0,s.R)(),...e.components};return n?(0,t.jsx)(n,{...e,children:(0,t.jsx)(h,{...e})}):h(e)}},8453:(e,n,i)=>{i.d(n,{R:()=>r,x:()=>l});var t=i(6540);const s={},o=t.createContext(s);function r(e){const n=t.useContext(o);return t.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function l(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:r(e.components),t.createElement(o.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/50f28384.07b57415.js b/assets/js/50f28384.07b57415.js new file mode 100644 index 00000000..64499324 --- /dev/null +++ b/assets/js/50f28384.07b57415.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3095],{1339:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>d,contentTitle:()=>s,default:()=>h,frontMatter:()=>r,metadata:()=>o,toc:()=>l});var t=i(4848),a=i(8453);const r={sidebar_position:1},s="Change Log",o={id:"operating-model/change-log/change-log",title:"Change Log",description:"Added",source:"@site/versioned_docs/version-24.03/operating-model/change-log/change-log.md",sourceDirName:"operating-model/change-log",slug:"/operating-model/change-log/",permalink:"/catenax-ev.github.io.new/docs/operating-model/change-log/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Appendix",permalink:"/catenax-ev.github.io.new/docs/operating-model/appendix/"}},d={},l=[{value:"Added",id:"added",level:2},{value:"Changed/Updated",id:"changedupdated",level:2},{value:"Unchanged",id:"unchanged",level:2}];function c(e){const n={h1:"h1",h2:"h2",li:"li",ul:"ul",...(0,a.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(n.h1,{id:"change-log",children:"Change Log"}),"\n",(0,t.jsx)(n.h2,{id:"added",children:"Added"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Role: Catena-X Automotive Network e.V."}),"\n",(0,t.jsx)(n.li,{children:"Service Map: Onboarding Service Category"}),"\n",(0,t.jsxs)(n.li,{children:["Data Space Operations: Providing information, guidelines, and premises on how to participate and exchange data in the data space:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"General Onboarding Process"}),"\n",(0,t.jsx)(n.li,{children:"Gaia-X Compliance"}),"\n",(0,t.jsx)(n.li,{children:"SSI Issuer Concept"}),"\n",(0,t.jsx)(n.li,{children:"Data Exchange based on SSI"}),"\n",(0,t.jsx)(n.li,{children:"EDC Deployment and Usage Premises"}),"\n"]}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["Life Cycle Management:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Versioning"}),"\n",(0,t.jsx)(n.li,{children:"Backward Compatibility"}),"\n"]}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["Data Space Governance:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Qualification Process"}),"\n",(0,t.jsx)(n.li,{children:"Exceptions"}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"changedupdated",children:"Changed/Updated"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Introduction: clarity and readability improvements"}),"\n",(0,t.jsxs)(n.li,{children:["Roles:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Re-naming of consulting provider to advisory provider"}),"\n",(0,t.jsx)(n.li,{children:"Detailing the description of all roles with responsibilities, respective relationships, prerequisites, and complements"}),"\n"]}),"\n"]}),"\n",(0,t.jsx)(n.li,{children:"Service Map: Update of service map according to Tractus-X release 23.09"}),"\n",(0,t.jsx)(n.li,{children:"Standardization process: reference provided to standardization policy that details the Catena-X standardization process further"}),"\n",(0,t.jsx)(n.li,{children:"Certification process: reference provided to Conformity Assessment Framework that details the Catena-X certification process further"}),"\n",(0,t.jsx)(n.li,{children:"Labels: Removed distinguishing factors between Certified Operating Company and Certified Partner"}),"\n",(0,t.jsx)(n.li,{children:"Outlook: updated according to release 23.09"}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"unchanged",children:"Unchanged"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Nomination Process"}),"\n"]})]})}function h(e={}){const{wrapper:n}={...(0,a.R)(),...e.components};return n?(0,t.jsx)(n,{...e,children:(0,t.jsx)(c,{...e})}):c(e)}},8453:(e,n,i)=>{i.d(n,{R:()=>s,x:()=>o});var t=i(6540);const a={},r=t.createContext(a);function s(e){const n=t.useContext(r);return t.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function o(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(a):e.components||a:s(e.components),t.createElement(r.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/50f28384.c44fb4f0.js b/assets/js/50f28384.c44fb4f0.js deleted file mode 100644 index 357ae4c8..00000000 --- a/assets/js/50f28384.c44fb4f0.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3095],{1339:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>d,contentTitle:()=>s,default:()=>h,frontMatter:()=>a,metadata:()=>o,toc:()=>l});var t=i(4848),r=i(8453);const a={sidebar_position:1},s="Change Log",o={id:"operating-model/change-log/change-log",title:"Change Log",description:"Added",source:"@site/versioned_docs/version-24.03/operating-model/change-log/change-log.md",sourceDirName:"operating-model/change-log",slug:"/operating-model/change-log/",permalink:"/docs/operating-model/change-log/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Appendix",permalink:"/docs/operating-model/appendix/"}},d={},l=[{value:"Added",id:"added",level:2},{value:"Changed/Updated",id:"changedupdated",level:2},{value:"Unchanged",id:"unchanged",level:2}];function c(e){const n={h1:"h1",h2:"h2",li:"li",ul:"ul",...(0,r.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(n.h1,{id:"change-log",children:"Change Log"}),"\n",(0,t.jsx)(n.h2,{id:"added",children:"Added"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Role: Catena-X Automotive Network e.V."}),"\n",(0,t.jsx)(n.li,{children:"Service Map: Onboarding Service Category"}),"\n",(0,t.jsxs)(n.li,{children:["Data Space Operations: Providing information, guidelines, and premises on how to participate and exchange data in the data space:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"General Onboarding Process"}),"\n",(0,t.jsx)(n.li,{children:"Gaia-X Compliance"}),"\n",(0,t.jsx)(n.li,{children:"SSI Issuer Concept"}),"\n",(0,t.jsx)(n.li,{children:"Data Exchange based on SSI"}),"\n",(0,t.jsx)(n.li,{children:"EDC Deployment and Usage Premises"}),"\n"]}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["Life Cycle Management:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Versioning"}),"\n",(0,t.jsx)(n.li,{children:"Backward Compatibility"}),"\n"]}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["Data Space Governance:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Qualification Process"}),"\n",(0,t.jsx)(n.li,{children:"Exceptions"}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"changedupdated",children:"Changed/Updated"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Introduction: clarity and readability improvements"}),"\n",(0,t.jsxs)(n.li,{children:["Roles:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Re-naming of consulting provider to advisory provider"}),"\n",(0,t.jsx)(n.li,{children:"Detailing the description of all roles with responsibilities, respective relationships, prerequisites, and complements"}),"\n"]}),"\n"]}),"\n",(0,t.jsx)(n.li,{children:"Service Map: Update of service map according to Tractus-X release 23.09"}),"\n",(0,t.jsx)(n.li,{children:"Standardization process: reference provided to standardization policy that details the Catena-X standardization process further"}),"\n",(0,t.jsx)(n.li,{children:"Certification process: reference provided to Conformity Assessment Framework that details the Catena-X certification process further"}),"\n",(0,t.jsx)(n.li,{children:"Labels: Removed distinguishing factors between Certified Operating Company and Certified Partner"}),"\n",(0,t.jsx)(n.li,{children:"Outlook: updated according to release 23.09"}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"unchanged",children:"Unchanged"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Nomination Process"}),"\n"]})]})}function h(e={}){const{wrapper:n}={...(0,r.R)(),...e.components};return n?(0,t.jsx)(n,{...e,children:(0,t.jsx)(c,{...e})}):c(e)}},8453:(e,n,i)=>{i.d(n,{R:()=>s,x:()=>o});var t=i(6540);const r={},a=t.createContext(r);function s(e){const n=t.useContext(a);return t.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function o(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(r):e.components||r:s(e.components),t.createElement(a.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/5243e443.389830ca.js b/assets/js/5243e443.389830ca.js deleted file mode 100644 index 9870cb3e..00000000 --- a/assets/js/5243e443.389830ca.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[1941],{6832:(e,r,t)=>{t.r(r),t.d(r,{assets:()=>c,contentTitle:()=>i,default:()=>a,frontMatter:()=>d,metadata:()=>l,toc:()=>o});var s=t(4848),n=t(8453);const d={sidebar_position:1},i="Glossary",l={id:"operating-model/glossary/glossary",title:"Glossary",description:"| Abbreviation | Full form |",source:"@site/docs/operating-model/glossary/glossary.md",sourceDirName:"operating-model/glossary",slug:"/operating-model/glossary/",permalink:"/docs/next/operating-model/glossary/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Outlook",permalink:"/docs/next/operating-model/outlook/"},next:{title:"Appendix",permalink:"/docs/next/operating-model/appendix/"}},c={},o=[];function h(e){const r={h1:"h1",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",...(0,n.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsx)(r.h1,{id:"glossary",children:"Glossary"}),"\n",(0,s.jsxs)(r.table,{children:[(0,s.jsx)(r.thead,{children:(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.th,{children:"Abbreviation"}),(0,s.jsx)(r.th,{children:"Full form"})]})}),(0,s.jsxs)(r.tbody,{children:[(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"AAS"}),(0,s.jsx)(r.td,{children:"Asset Administration Shell"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"AP"}),(0,s.jsx)(r.td,{children:"Advisory Provider"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"API"}),(0,s.jsx)(r.td,{children:"Application Programming Interfaces"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"BAP"}),(0,s.jsx)(r.td,{children:"Business Application Provider"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"BPN(BPNL, BPNA, BPNS)"}),(0,s.jsx)(r.td,{children:"Business Partner Number (Legal Entities, Addresses, Sites)"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CAB"}),(0,s.jsx)(r.td,{children:"Conformity Assessment Body"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CAC"}),(0,s.jsx)(r.td,{children:"Conformity Assessment Criteria"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"COTS"}),(0,s.jsx)(r.td,{children:"Commercial-off-the-Shelf (Software)"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CSP-A"}),(0,s.jsx)(r.td,{children:"Core Service Provider A"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CSP-B"}),(0,s.jsx)(r.td,{children:"Core Service Provider B"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"cxOS"}),(0,s.jsx)(r.td,{children:"Catena-X Operating System"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"DAPS"}),(0,s.jsx)(r.td,{children:"Dynamic Attribute Provisioning Service"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"DDTR"}),(0,s.jsx)(r.td,{children:"Decentralized Digital Twin Registry"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"DSSC"}),(0,s.jsx)(r.td,{children:"Data Space Support Center"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"EDC"}),(0,s.jsx)(r.td,{children:"Eclipse Data Space Components"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"EDWG"}),(0,s.jsx)(r.td,{children:"Eclipse Data Space Working Group"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"ETL"}),(0,s.jsx)(r.td,{children:"Extract, Transform, Load (Process)"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"GXDCH"}),(0,s.jsx)(r.td,{children:"Gaia-X Digital Clearing House"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"IAM"}),(0,s.jsx)(r.td,{children:"Identity and Access Management"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"IDSA"}),(0,s.jsx)(r.td,{children:"International Data Spaces Association"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"IRS"}),(0,s.jsx)(r.td,{children:"Item Relationship Service"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"MIW"}),(0,s.jsx)(r.td,{children:"Managed Identity Wallet"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"PCF"}),(0,s.jsx)(r.td,{children:"Product Carbon Footprint"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"RfT"}),(0,s.jsx)(r.td,{children:"Request for Tender"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"SaaS"}),(0,s.jsx)(r.td,{children:"Software-as-a-Service"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"SSI"}),(0,s.jsx)(r.td,{children:"Self-Sovereign Identity"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"TRG"}),(0,s.jsx)(r.td,{children:"Tractus-X Release Guideline"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"OSP"}),(0,s.jsx)(r.td,{children:"Onboarding Service Provider"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"VC"}),(0,s.jsx)(r.td,{children:"Verifiable Credential"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"VP"}),(0,s.jsx)(r.td,{children:"Verifiable Presentation"})]})]})]})]})}function a(e={}){const{wrapper:r}={...(0,n.R)(),...e.components};return r?(0,s.jsx)(r,{...e,children:(0,s.jsx)(h,{...e})}):h(e)}},8453:(e,r,t)=>{t.d(r,{R:()=>i,x:()=>l});var s=t(6540);const n={},d=s.createContext(n);function i(e){const r=s.useContext(d);return s.useMemo((function(){return"function"==typeof e?e(r):{...r,...e}}),[r,e])}function l(e){let r;return r=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:i(e.components),s.createElement(d.Provider,{value:r},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/5243e443.c9476cb5.js b/assets/js/5243e443.c9476cb5.js new file mode 100644 index 00000000..023fee57 --- /dev/null +++ b/assets/js/5243e443.c9476cb5.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[1941],{6832:(e,r,t)=>{t.r(r),t.d(r,{assets:()=>c,contentTitle:()=>d,default:()=>h,frontMatter:()=>i,metadata:()=>l,toc:()=>o});var s=t(4848),n=t(8453);const i={sidebar_position:1},d="Glossary",l={id:"operating-model/glossary/glossary",title:"Glossary",description:"| Abbreviation | Full form |",source:"@site/docs/operating-model/glossary/glossary.md",sourceDirName:"operating-model/glossary",slug:"/operating-model/glossary/",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/glossary/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Outlook",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/outlook/"},next:{title:"Appendix",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/appendix/"}},c={},o=[];function a(e){const r={h1:"h1",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",...(0,n.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsx)(r.h1,{id:"glossary",children:"Glossary"}),"\n",(0,s.jsxs)(r.table,{children:[(0,s.jsx)(r.thead,{children:(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.th,{children:"Abbreviation"}),(0,s.jsx)(r.th,{children:"Full form"})]})}),(0,s.jsxs)(r.tbody,{children:[(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"AAS"}),(0,s.jsx)(r.td,{children:"Asset Administration Shell"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"AP"}),(0,s.jsx)(r.td,{children:"Advisory Provider"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"API"}),(0,s.jsx)(r.td,{children:"Application Programming Interfaces"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"BAP"}),(0,s.jsx)(r.td,{children:"Business Application Provider"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"BPN(BPNL, BPNA, BPNS)"}),(0,s.jsx)(r.td,{children:"Business Partner Number (Legal Entities, Addresses, Sites)"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CAB"}),(0,s.jsx)(r.td,{children:"Conformity Assessment Body"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CAC"}),(0,s.jsx)(r.td,{children:"Conformity Assessment Criteria"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"COTS"}),(0,s.jsx)(r.td,{children:"Commercial-off-the-Shelf (Software)"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CSP-A"}),(0,s.jsx)(r.td,{children:"Core Service Provider A"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CSP-B"}),(0,s.jsx)(r.td,{children:"Core Service Provider B"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"cxOS"}),(0,s.jsx)(r.td,{children:"Catena-X Operating System"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"DAPS"}),(0,s.jsx)(r.td,{children:"Dynamic Attribute Provisioning Service"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"DDTR"}),(0,s.jsx)(r.td,{children:"Decentralized Digital Twin Registry"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"DSSC"}),(0,s.jsx)(r.td,{children:"Data Space Support Center"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"EDC"}),(0,s.jsx)(r.td,{children:"Eclipse Data Space Components"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"EDWG"}),(0,s.jsx)(r.td,{children:"Eclipse Data Space Working Group"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"ETL"}),(0,s.jsx)(r.td,{children:"Extract, Transform, Load (Process)"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"GXDCH"}),(0,s.jsx)(r.td,{children:"Gaia-X Digital Clearing House"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"IAM"}),(0,s.jsx)(r.td,{children:"Identity and Access Management"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"IDSA"}),(0,s.jsx)(r.td,{children:"International Data Spaces Association"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"IRS"}),(0,s.jsx)(r.td,{children:"Item Relationship Service"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"MIW"}),(0,s.jsx)(r.td,{children:"Managed Identity Wallet"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"PCF"}),(0,s.jsx)(r.td,{children:"Product Carbon Footprint"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"RfT"}),(0,s.jsx)(r.td,{children:"Request for Tender"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"SaaS"}),(0,s.jsx)(r.td,{children:"Software-as-a-Service"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"SSI"}),(0,s.jsx)(r.td,{children:"Self-Sovereign Identity"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"TRG"}),(0,s.jsx)(r.td,{children:"Tractus-X Release Guideline"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"OSP"}),(0,s.jsx)(r.td,{children:"Onboarding Service Provider"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"VC"}),(0,s.jsx)(r.td,{children:"Verifiable Credential"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"VP"}),(0,s.jsx)(r.td,{children:"Verifiable Presentation"})]})]})]})]})}function h(e={}){const{wrapper:r}={...(0,n.R)(),...e.components};return r?(0,s.jsx)(r,{...e,children:(0,s.jsx)(a,{...e})}):a(e)}},8453:(e,r,t)=>{t.d(r,{R:()=>d,x:()=>l});var s=t(6540);const n={},i=s.createContext(n);function d(e){const r=s.useContext(i);return s.useMemo((function(){return"function"==typeof e?e(r):{...r,...e}}),[r,e])}function l(e){let r;return r=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:d(e.components),s.createElement(i.Provider,{value:r},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/5440ed21.cdb4e68b.js b/assets/js/5440ed21.cdb4e68b.js deleted file mode 100644 index a9a918b1..00000000 --- a/assets/js/5440ed21.cdb4e68b.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9520],{672:(e,n,s)=>{s.r(n),s.d(n,{assets:()=>c,contentTitle:()=>a,default:()=>h,frontMatter:()=>r,metadata:()=>o,toc:()=>l});var i=s(4848),t=s(8453);const r={sidebar_position:1},a="Who: Roles in the Catena-X ecosystem",o={id:"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem",title:"Who: Roles in the Catena-X ecosystem",description:"The Catena-X ecosystem operates on the principle of multiple distinct roles, designed to create an appealing and functional data space (see Figure Role Overview and Relationships). Participants can take on one or more roles in any combination, and multiple participants can fulfill the same role except for the CSP-B role. The CSP-B role can only exist once in the data space due to complexity and technical reasons. Provider roles receive a label through a certification or qualification process to demonstrate that they are trusted partners (see Chapter How: Life Cycle Management).",source:"@site/versioned_docs/version-24.03/operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem.md",sourceDirName:"operating-model/who-roles-in-the-catena-x-ecosystem",slug:"/operating-model/who-roles-in-the-catena-x-ecosystem/",permalink:"/docs/operating-model/who-roles-in-the-catena-x-ecosystem/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Why: Understanding the Catena-X Data Space",permalink:"/docs/operating-model/why-understanding-the-catena-x-data-space/"},next:{title:"What: Service Map",permalink:"/docs/operating-model/what-service-map/"}},c={},l=[{value:"Overview of roles",id:"overview-of-roles",level:2},{value:"Detailed description of each role",id:"detailed-description-of-each-role",level:2},{value:"Core Service Provider A",id:"core-service-provider-a",level:3},{value:"Core Service Provider B",id:"core-service-provider-b",level:3},{value:"Onboarding Service Provider",id:"onboarding-service-provider",level:3},{value:"Enablement Service Provider",id:"enablement-service-provider",level:3},{value:"Business Application Provider",id:"business-application-provider",level:3},{value:"Advisory Provider",id:"advisory-provider",level:3},{value:"Data Provider/Consumer",id:"data-providerconsumer",level:3},{value:"Catena-X Association",id:"catena-x-association",level:3},{value:"Conformity Assessment Body",id:"conformity-assessment-body",level:3}];function d(e){const n={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",img:"img",li:"li",p:"p",strong:"strong",ul:"ul",...(0,t.R)(),...e.components};return(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(n.h1,{id:"who-roles-in-the-catena-x-ecosystem",children:"Who: Roles in the Catena-X ecosystem"}),"\n",(0,i.jsxs)(n.p,{children:["The Catena-X ecosystem operates on the principle of multiple distinct roles, designed to create an appealing and functional data space (see ",(0,i.jsx)(n.a,{href:"/docs/operating-model/who-roles-in-the-catena-x-ecosystem/#overview-of-roles",children:"Figure Role Overview and Relationships"}),"). Participants can take on one or more roles in any combination, and multiple participants can fulfill the same role except for the CSP-B role. The CSP-B role can only exist once in the data space due to complexity and technical reasons. Provider roles receive a label through a certification or qualification process to demonstrate that they are trusted partners (see Chapter ",(0,i.jsx)(n.a,{href:"/docs/operating-model/how-life-cycle-management/",children:"How: Life Cycle Management"}),")."]}),"\n",(0,i.jsx)(n.h2,{id:"overview-of-roles",children:"Overview of roles"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.img,{alt:"Role Overview and Relationships",src:s(8481).A+"",width:"873",height:"726"}),"\n",(0,i.jsx)(n.em,{children:"Role Overview and Relationships"})]}),"\n",(0,i.jsx)(n.h2,{id:"detailed-description-of-each-role",children:"Detailed description of each role"}),"\n",(0,i.jsxs)(n.p,{children:["Below, each role that a participant can assume in the Catena-X data spaces is described in detail, along with its assigned description, responsibilities, relationships, prerequisites, and complements. Please refer to Chapter ",(0,i.jsx)(n.a,{href:"/docs/operating-model/appendix/#role-relationships",children:"Role Relationships"}),". for a comprehensive overview of the relationships between these roles as well as a definition of the relationship type and Chapter ",(0,i.jsx)(n.a,{href:"/docs/operating-model/what-service-map/",children:"What: Service Map"})," for an overview of the Service Map."]}),"\n",(0,i.jsx)(n.h3,{id:"core-service-provider-a",children:"Core Service Provider A"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Core Service Provider A (CSP-A)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": A CSP-A is responsible for deploying, operating, and maintaining core services A according to Catena-X standards. Core Services A provide common business functionalities for all data space participants (e.g., managing marketplace offers, semantic models, or searching for business partner information)."]}),"\n",(0,i.jsx)(n.p,{children:"A CSP-A can operate various bundles of Core Services A, whereby the operation of an IAM and a marketplace is mandatory. Note that the synchronization of marketplace offers is at the discretion of a provider, who may submit and list its offer on multiple marketplaces. The CSP-A role can be taken on by multiple participants."}),"\n",(0,i.jsx)(n.p,{children:"For smooth operations, the CSP-A must provide comprehensive technical documentation, along with first, second, and third level support to facilitate integration with its services. Each CSP-A has freedom of choice regarding their business model towards their potential customers."}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["A CSP-A ",(0,i.jsx)(n.strong,{children:"must"})," implement an IAM synchronization and must integrate with\nother CSP-As."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-A ",(0,i.jsx)(n.strong,{children:"must"})," implement an IAM synchronization with an OSP."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-A ",(0,i.jsx)(n.strong,{children:"must"})," integrate with the CSP-B to be able to offer and operate its services. This includes implementing IAM synchronization and integrating with required Core Services B."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-A ",(0,i.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e.g., registration service)."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-A ",(0,i.jsx)(n.strong,{children:"must"})," accept any certified solution that wants to be listed on its marketplace in accordance with its respective terms and conditions, without discriminating against individual organizations."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"A CSP-A and its services must be certified by a CAB"}),"\n",(0,i.jsx)(n.li,{children:"A CSP-A must accept and comply with the Catena-X regulatory framework\nduring onboarding via one of the OSPs."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["Due to technical limitations, the CSP-A role currently cannot be fully assumed and executed more than once. Further details can be found in Chapter ",(0,i.jsx)(n.a,{href:"/docs/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"})," or can be requested during the conformity assessment."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"core-service-provider-b",children:"Core Service Provider B"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Core Service Provider B (CSP-B)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": The CSP-B is responsible for deploying, operating, and maintaining all core services section B according to Catena-X standards. Core Services B include identity and common accessibility and discoverability functionalities for all data space participants."]}),"\n",(0,i.jsx)(n.p,{children:"The CSP-B operates all Core Services B as one bundle to enable trusted participation and sovereign data exchange across all data space participants. The CSP-B role can only be taken on by one participant and is nominated by the Catena-X Association to operate and further develop the services on their behalf."}),"\n",(0,i.jsx)(n.p,{children:"For smooth operations, the CSP-B must provide comprehensive technical documentation, along with first, second, and third level support to facilitate integration with its services."}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Due to its special role, the CSP-B is responsible for:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"providing non-discriminatory access to Core Services Section B for all data space participants."}),"\n",(0,i.jsx)(n.li,{children:"coordinating the release management of Core Services B in the data space (with affected participants) based on Catena-X Association and Tractus-X releases."}),"\n",(0,i.jsx)(n.li,{children:"marketing Core Services B and managing contractual partners."}),"\n",(0,i.jsx)(n.li,{children:"issuing and revoking access of BPNs to the data space based on the country clearance list by the Catena-X Association."}),"\n",(0,i.jsx)(n.li,{children:"temporarily executing the trust anchor role and issuing verifiable credentials."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["The CSP-B ",(0,i.jsx)(n.strong,{children:"must"})," support the integration of all other data space participants to the Core Services B."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-B ",(0,i.jsx)(n.strong,{children:"must"})," implement an IAM synchronization with CSP-As and OSPs."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["A CSP-B ",(0,i.jsx)(n.strong,{children:"must"})," be nominated by the Catena-X Association."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-B ",(0,i.jsx)(n.strong,{children:"must"})," be a Catena-X Association member."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-B and its services ",(0,i.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,i.jsxs)(n.li,{children:["A CSP-B ",(0,i.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework via an MoU with the Association."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["To ensure complete functionality of the data space, the CSP-B ",(0,i.jsx)(n.strong,{children:"must"})," also operate the relevant services of both the CSP-A and OSP roles."]}),"\n",(0,i.jsxs)(n.li,{children:["Further details can be found in Chapter ",(0,i.jsx)(n.a,{href:"/docs/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),". how Catena-X foster competition."]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"onboarding-service-provider",children:"Onboarding Service Provider"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Onboarding Service Provider (OSP)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": An OSP is responsible for deploying, operating, and maintaining onboarding services according to Catena-X standards. The onboarding services enable and support data space participants to register and onboard and offboard to Catena-X data space."]}),"\n",(0,i.jsxs)(n.p,{children:["This includes organizational registration and technical integration (see Chapter ",(0,i.jsx)(n.a,{href:"/docs/operating-model/how-data-space-operations/#general-onboarding",children:"General Onboarding"}),"), after which an organization can fully participate in the data space. An OSP can enable new prospects and/or their existing customer base in terms of network-of-networks. To ensure maximum trust in the data space during the onboarding process, the OSP must establish a connection with the Gaia-X Digital Clearing House (GXDCH)."]}),"\n",(0,i.jsx)(n.p,{children:"For smooth operations, the OSP must provide comprehensive technical documentation, along with first, second, and third level support to facilitate integration with its services."}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["An OSP ",(0,i.jsx)(n.strong,{children:"must"})," implement an IAM synchronization with CSP-As, the CSP-B, and OSPs to provide its customers with access to the data space."]}),"\n",(0,i.jsxs)(n.li,{children:["An OSP ",(0,i.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access their identity(e. g., identity wallet) and enable data exchange."]}),"\n",(0,i.jsxs)(n.li,{children:["An OSP ",(0,i.jsx)(n.strong,{children:"must"})," integrate and use the GAIA-X Digital Clearing House to validate e. g., the Legal Person Self-Description."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["An OSP and its services ",(0,i.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,i.jsxs)(n.li,{children:["An OSP ",(0,i.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access its identity (e. g., identity wallet)"]}),"\n",(0,i.jsxs)(n.li,{children:["An OSP ",(0,i.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the other OSPs."]}),"\n",(0,i.jsxs)(n.li,{children:["An OSP ",(0,i.jsx)(n.strong,{children:"must"})," use the dedicated GAIA-X Clearing House Service nominated by the Catena-X Association."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsxs)(n.p,{children:["Due to technical limitations, the OSP role currently cannot be fully assumed and executed more than once. Further details can be found in Chapter ",(0,i.jsx)(n.a,{href:"/docs/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"})," or can be requested during the conformity assessment. Offboarding will be included within the upcoming releases."]}),"\n",(0,i.jsx)(n.h3,{id:"enablement-service-provider",children:"Enablement Service Provider"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Enablement Service Provider (ESP)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": An ESP is responsible for deploying, operating, and maintaining enablement services according to Catena-X standards."]}),"\n",(0,i.jsx)(n.p,{children:"An ESP can operate various bundles of decentralized services that enable sovereign\nparticipation and data exchange for data providers and consumers in the Catena-X\ndata space. An ESP can decide on the scope of its enablement service and whether\nto offer them on one or multiple of the marketplaces."}),"\n",(0,i.jsx)(n.p,{children:"In addition, ESPs can also offer non-standardized services such as automated data\nmapping, in which data is extracted from company systems and converted into\nCatena-X semantic models."}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["An ESP ",(0,i.jsx)(n.strong,{children:"can"})," use one or more CSP-A services (e. g., semantic hub)."]}),"\n",(0,i.jsxs)(n.li,{children:["An ESP ",(0,i.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access its identity (e. g., identity wallet) and enable data exchange."]}),"\n",(0,i.jsxs)(n.li,{children:["An ESP ",(0,i.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e. g., registration service)."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["An ESP and its services ",(0,i.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,i.jsxs)(n.li,{children:["An ESP ",(0,i.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsx)(n.p,{children:"n/a"}),"\n",(0,i.jsx)(n.h3,{id:"business-application-provider",children:"Business Application Provider"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Business Application Provider (BAP)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": A BAP is responsible for deploying, operating, and maintaining business applications to Catena-X standards. Business applications enable data providers and consumers to leverage different use cases and data-driven processes to solve a specific industry problem (e.g., PCF) and create business value, by using KITs and Standards for an interoperable and trusted data exchange."]}),"\n",(0,i.jsx)(n.p,{children:"A BAP can decide on the scope of its business applications and whether to offer\nthem on one or multiple of the marketplaces"}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["A BAP ",(0,i.jsx)(n.strong,{children:"can"})," use one or more CSP-A services (e. g., semantic hub)."]}),"\n",(0,i.jsxs)(n.li,{children:["A BAP ",(0,i.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access his identity (e. g., identity wallet) and enable data exchange."]}),"\n",(0,i.jsxs)(n.li,{children:["A BAP ",(0,i.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e. g., registration service)."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["A BAP and its services ",(0,i.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,i.jsxs)(n.li,{children:["A BAP ",(0,i.jsx)(n.strong,{children:"must"})," list its solution on a marketplace provided by a CSP-A."]}),"\n",(0,i.jsxs)(n.li,{children:["A BAP ",(0,i.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsx)(n.p,{children:"n/a"}),"\n",(0,i.jsx)(n.h3,{id:"advisory-provider",children:"Advisory Provider"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Advisory Provider (AP)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": An AP offers advisory services in various areas, from strategy to operations to technology or business use cases for those interested in the Catena-X data space. Providing advisory services includes topics such as onboarding guidance, business value assessment, organizational and technical enablement, but do not include the operation of technical services."]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["An AP ",(0,i.jsx)(n.strong,{children:"can"})," use one or more CSP-As if it intends to utilize specific CSP-A services such as listing an offer on a marketplace."]}),"\n",(0,i.jsxs)(n.li,{children:["An AP ",(0,i.jsx)(n.strong,{children:"can"})," integrate and use CSP-B services to access the Core Services B."]}),"\n",(0,i.jsxs)(n.li,{children:["An AP ",(0,i.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e. g., registration service)."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["An AP ",(0,i.jsx)(n.strong,{children:"must"})," be qualified by the Catena-X Association."]}),"\n",(0,i.jsxs)(n.li,{children:["An AP ",(0,i.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsx)(n.p,{children:"n/a"}),"\n",(0,i.jsx)(n.h3,{id:"data-providerconsumer",children:"Data Provider/Consumer"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Data Provider and Consumer (DPC)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": A DPC provides, consumes, and processes data to collaborate with other data space participants to solve a specific industry problem und create business value. This includes both standardized use cases and direct collaboration."]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"can"})," use the services of a CSP-A (e.g., marketplace)."]}),"\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access his identity (e. g., identity wallet) and enable data exchange."]}),"\n",(0,i.jsxs)(n.li,{children:["An DPC ",(0,i.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e.g., registration service). This can be delegated to a BAP or ESP"]}),"\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"must"})," connect with another DPC to exchange data and create value."]}),"\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"can"})," use advisory services from a qualified AP."]}),"\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"can"})," use certified enablement services from a commercial ESP (e.g., SaaS solution). Alternatively, a DPC can certify and operate its own enablement services."]}),"\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"can"})," use certified business applications from a commercial BAP (e.g., SaaS\nsolution). Alternatively, a DPC can certify and operate its own business application"]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"must"})," use certified enablement services or business applications. Alternatively, a DPC ",(0,i.jsx)(n.strong,{children:"must"})," certify its own enablement services and/or business applications by one of the CABs (as outlined in Chapter ",(0,i.jsx)(n.a,{href:"/docs/operating-model/how-data-space-governance/#conformity-assessment",children:"Conformity Assessment"}),")."]}),"\n",(0,i.jsxs)(n.li,{children:["A DPC ",(0,i.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs"]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsx)(n.p,{children:"n/a"}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.em,{children:"In addition to the roles in the data space, there are independent roles such as the Catena-X Association or Conformity\nAssessment Bodies (CABs) to ensure neutral, trustworthy, and secure operation of the Catena-X data space."})}),"\n",(0,i.jsx)(n.h3,{id:"catena-x-association",children:"Catena-X Association"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Catena-X Association"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": The Association is responsible for the neutral governance of the Catena-X ecosystem including the execution of nomination, standardization, qualification, and certification processes. It promotes and facilitates working groups, committees, and expert groups to discuss and align on, standards, KITs, and requirements for open-source reference implementation for the Catena-X operating system and use cases. In addition, it provides various informational resources to interested parties and Association members."]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"The Association nominates the CSP-B and CABs."}),"\n",(0,i.jsx)(n.li,{children:"The Association delegates the certification of data space participants to CABs."}),"\n",(0,i.jsx)(n.li,{children:"The Association defines the Issuer of verifiable credentials."}),"\n",(0,i.jsx)(n.li,{children:"The Association qualifies APs."}),"\n",(0,i.jsx)(n.li,{children:"The Association promotes, sponsors, and coordinates the overlying requirements of the Eclipse Tractus-X Project with a view to standardization."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsx)(n.p,{children:"n/a"}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsxs)(n.p,{children:["For the upcoming releases there will be a dedicated issuer concept in place. As of now the Association defines the Issuer (CSP-B). Further details can be found in Chapter ",(0,i.jsx)(n.a,{href:"/docs/operating-model/how-data-space-operations/#ssi-issuer-concept",children:"SSI Issuer Concept"}),". An outlook can be found in Chapter ",(0,i.jsx)(n.a,{href:"/docs/operating-model/outlook/#further-integration-of-ssi-technologies",children:"Further Integration of SSI Technologies"}),"."]}),"\n",(0,i.jsx)(n.h3,{id:"conformity-assessment-body",children:"Conformity Assessment Body"}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Role:"})," Conformity Assessment Body (CAB)"]}),"\n",(0,i.jsxs)(n.p,{children:[(0,i.jsx)(n.strong,{children:"Description/Responsibilities"}),": A CAB carries out the conformity assessment process in accordance with the Catena-X Certification Framework on behalf of the Catena-X Association. The Certification Framework consists of the certification manual and the certification catalog (derived from the (",(0,i.jsx)(n.a,{href:"https://catena-x.net/de/standard-library",children:"Catena-X standards"}),")). A CAB is nominated by the Catena-X Association to ensure an independent, trustworthy, and secure conformity assessment process."]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"A CAB is responsible for:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"creating offers for the conformity assessments."}),"\n",(0,i.jsx)(n.li,{children:"carrying out the conformity assessment process for various certification objects (e.g., provider, solutions)."}),"\n",(0,i.jsx)(n.li,{children:"informing the Catena-X Association and the certification candidate about the certification results."}),"\n",(0,i.jsx)(n.li,{children:"issuing, reissuing, and revoking of certificates on behalf of the Catena-X\nAssociation."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["The CAB ",(0,i.jsx)(n.strong,{children:"must"})," carry out the conformity assessment for all affected data space\nparticipants and their IT solutions."]}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"A CAB must be nominated by the Catena-X Association and comply with the Catena-X certification framework."}),"\n",(0,i.jsx)(n.li,{children:"Business model supporting adoption and offering a non-discriminating access, esp. by small and medium business."}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,i.jsx)(n.p,{children:"n/a"})]})}function h(e={}){const{wrapper:n}={...(0,t.R)(),...e.components};return n?(0,i.jsx)(n,{...e,children:(0,i.jsx)(d,{...e})}):d(e)}},8481:(e,n,s)=>{s.d(n,{A:()=>i});const i=s.p+"assets/images/role-overview-and-relationships-ebdb0775319edc16372e21437aedda92.png"},8453:(e,n,s)=>{s.d(n,{R:()=>a,x:()=>o});var i=s(6540);const t={},r=i.createContext(t);function a(e){const n=i.useContext(r);return i.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function o(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(t):e.components||t:a(e.components),i.createElement(r.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/5440ed21.ff303a3d.js b/assets/js/5440ed21.ff303a3d.js new file mode 100644 index 00000000..109e874c --- /dev/null +++ b/assets/js/5440ed21.ff303a3d.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9520],{672:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>c,contentTitle:()=>a,default:()=>h,frontMatter:()=>r,metadata:()=>o,toc:()=>l});var s=i(4848),t=i(8453);const r={sidebar_position:1},a="Who: Roles in the Catena-X ecosystem",o={id:"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem",title:"Who: Roles in the Catena-X ecosystem",description:"The Catena-X ecosystem operates on the principle of multiple distinct roles, designed to create an appealing and functional data space (see Figure Role Overview and Relationships). Participants can take on one or more roles in any combination, and multiple participants can fulfill the same role except for the CSP-B role. The CSP-B role can only exist once in the data space due to complexity and technical reasons. Provider roles receive a label through a certification or qualification process to demonstrate that they are trusted partners (see Chapter How: Life Cycle Management).",source:"@site/versioned_docs/version-24.03/operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem.md",sourceDirName:"operating-model/who-roles-in-the-catena-x-ecosystem",slug:"/operating-model/who-roles-in-the-catena-x-ecosystem/",permalink:"/catenax-ev.github.io.new/docs/operating-model/who-roles-in-the-catena-x-ecosystem/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Why: Understanding the Catena-X Data Space",permalink:"/catenax-ev.github.io.new/docs/operating-model/why-understanding-the-catena-x-data-space/"},next:{title:"What: Service Map",permalink:"/catenax-ev.github.io.new/docs/operating-model/what-service-map/"}},c={},l=[{value:"Overview of roles",id:"overview-of-roles",level:2},{value:"Detailed description of each role",id:"detailed-description-of-each-role",level:2},{value:"Core Service Provider A",id:"core-service-provider-a",level:3},{value:"Core Service Provider B",id:"core-service-provider-b",level:3},{value:"Onboarding Service Provider",id:"onboarding-service-provider",level:3},{value:"Enablement Service Provider",id:"enablement-service-provider",level:3},{value:"Business Application Provider",id:"business-application-provider",level:3},{value:"Advisory Provider",id:"advisory-provider",level:3},{value:"Data Provider/Consumer",id:"data-providerconsumer",level:3},{value:"Catena-X Association",id:"catena-x-association",level:3},{value:"Conformity Assessment Body",id:"conformity-assessment-body",level:3}];function d(e){const n={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",img:"img",li:"li",p:"p",strong:"strong",ul:"ul",...(0,t.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsx)(n.h1,{id:"who-roles-in-the-catena-x-ecosystem",children:"Who: Roles in the Catena-X ecosystem"}),"\n",(0,s.jsxs)(n.p,{children:["The Catena-X ecosystem operates on the principle of multiple distinct roles, designed to create an appealing and functional data space (see ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/who-roles-in-the-catena-x-ecosystem/#overview-of-roles",children:"Figure Role Overview and Relationships"}),"). Participants can take on one or more roles in any combination, and multiple participants can fulfill the same role except for the CSP-B role. The CSP-B role can only exist once in the data space due to complexity and technical reasons. Provider roles receive a label through a certification or qualification process to demonstrate that they are trusted partners (see Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-life-cycle-management/",children:"How: Life Cycle Management"}),")."]}),"\n",(0,s.jsx)(n.h2,{id:"overview-of-roles",children:"Overview of roles"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.img,{alt:"Role Overview and Relationships",src:i(8481).A+"",width:"873",height:"726"}),"\n",(0,s.jsx)(n.em,{children:"Role Overview and Relationships"})]}),"\n",(0,s.jsx)(n.h2,{id:"detailed-description-of-each-role",children:"Detailed description of each role"}),"\n",(0,s.jsxs)(n.p,{children:["Below, each role that a participant can assume in the Catena-X data spaces is described in detail, along with its assigned description, responsibilities, relationships, prerequisites, and complements. Please refer to Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/appendix/#role-relationships",children:"Role Relationships"}),". for a comprehensive overview of the relationships between these roles as well as a definition of the relationship type and Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/what-service-map/",children:"What: Service Map"})," for an overview of the Service Map."]}),"\n",(0,s.jsx)(n.h3,{id:"core-service-provider-a",children:"Core Service Provider A"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Core Service Provider A (CSP-A)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": A CSP-A is responsible for deploying, operating, and maintaining core services A according to Catena-X standards. Core Services A provide common business functionalities for all data space participants (e.g., managing marketplace offers, semantic models, or searching for business partner information)."]}),"\n",(0,s.jsx)(n.p,{children:"A CSP-A can operate various bundles of Core Services A, whereby the operation of an IAM and a marketplace is mandatory. Note that the synchronization of marketplace offers is at the discretion of a provider, who may submit and list its offer on multiple marketplaces. The CSP-A role can be taken on by multiple participants."}),"\n",(0,s.jsx)(n.p,{children:"For smooth operations, the CSP-A must provide comprehensive technical documentation, along with first, second, and third level support to facilitate integration with its services. Each CSP-A has freedom of choice regarding their business model towards their potential customers."}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["A CSP-A ",(0,s.jsx)(n.strong,{children:"must"})," implement an IAM synchronization and must integrate with\nother CSP-As."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-A ",(0,s.jsx)(n.strong,{children:"must"})," implement an IAM synchronization with an OSP."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-A ",(0,s.jsx)(n.strong,{children:"must"})," integrate with the CSP-B to be able to offer and operate its services. This includes implementing IAM synchronization and integrating with required Core Services B."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-A ",(0,s.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e.g., registration service)."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-A ",(0,s.jsx)(n.strong,{children:"must"})," accept any certified solution that wants to be listed on its marketplace in accordance with its respective terms and conditions, without discriminating against individual organizations."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsx)(n.li,{children:"A CSP-A and its services must be certified by a CAB"}),"\n",(0,s.jsx)(n.li,{children:"A CSP-A must accept and comply with the Catena-X regulatory framework\nduring onboarding via one of the OSPs."}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["Due to technical limitations, the CSP-A role currently cannot be fully assumed and executed more than once. Further details can be found in Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"})," or can be requested during the conformity assessment."]}),"\n"]}),"\n",(0,s.jsx)(n.h3,{id:"core-service-provider-b",children:"Core Service Provider B"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Core Service Provider B (CSP-B)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": The CSP-B is responsible for deploying, operating, and maintaining all core services section B according to Catena-X standards. Core Services B include identity and common accessibility and discoverability functionalities for all data space participants."]}),"\n",(0,s.jsx)(n.p,{children:"The CSP-B operates all Core Services B as one bundle to enable trusted participation and sovereign data exchange across all data space participants. The CSP-B role can only be taken on by one participant and is nominated by the Catena-X Association to operate and further develop the services on their behalf."}),"\n",(0,s.jsx)(n.p,{children:"For smooth operations, the CSP-B must provide comprehensive technical documentation, along with first, second, and third level support to facilitate integration with its services."}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Due to its special role, the CSP-B is responsible for:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsx)(n.li,{children:"providing non-discriminatory access to Core Services Section B for all data space participants."}),"\n",(0,s.jsx)(n.li,{children:"coordinating the release management of Core Services B in the data space (with affected participants) based on Catena-X Association and Tractus-X releases."}),"\n",(0,s.jsx)(n.li,{children:"marketing Core Services B and managing contractual partners."}),"\n",(0,s.jsx)(n.li,{children:"issuing and revoking access of BPNs to the data space based on the country clearance list by the Catena-X Association."}),"\n",(0,s.jsx)(n.li,{children:"temporarily executing the trust anchor role and issuing verifiable credentials."}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["The CSP-B ",(0,s.jsx)(n.strong,{children:"must"})," support the integration of all other data space participants to the Core Services B."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-B ",(0,s.jsx)(n.strong,{children:"must"})," implement an IAM synchronization with CSP-As and OSPs."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["A CSP-B ",(0,s.jsx)(n.strong,{children:"must"})," be nominated by the Catena-X Association."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-B ",(0,s.jsx)(n.strong,{children:"must"})," be a Catena-X Association member."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-B and its services ",(0,s.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,s.jsxs)(n.li,{children:["A CSP-B ",(0,s.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework via an MoU with the Association."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["To ensure complete functionality of the data space, the CSP-B ",(0,s.jsx)(n.strong,{children:"must"})," also operate the relevant services of both the CSP-A and OSP roles."]}),"\n",(0,s.jsxs)(n.li,{children:["Further details can be found in Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),". how Catena-X foster competition."]}),"\n"]}),"\n",(0,s.jsx)(n.h3,{id:"onboarding-service-provider",children:"Onboarding Service Provider"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Onboarding Service Provider (OSP)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": An OSP is responsible for deploying, operating, and maintaining onboarding services according to Catena-X standards. The onboarding services enable and support data space participants to register and onboard and offboard to Catena-X data space."]}),"\n",(0,s.jsxs)(n.p,{children:["This includes organizational registration and technical integration (see Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-operations/#general-onboarding",children:"General Onboarding"}),"), after which an organization can fully participate in the data space. An OSP can enable new prospects and/or their existing customer base in terms of network-of-networks. To ensure maximum trust in the data space during the onboarding process, the OSP must establish a connection with the Gaia-X Digital Clearing House (GXDCH)."]}),"\n",(0,s.jsx)(n.p,{children:"For smooth operations, the OSP must provide comprehensive technical documentation, along with first, second, and third level support to facilitate integration with its services."}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["An OSP ",(0,s.jsx)(n.strong,{children:"must"})," implement an IAM synchronization with CSP-As, the CSP-B, and OSPs to provide its customers with access to the data space."]}),"\n",(0,s.jsxs)(n.li,{children:["An OSP ",(0,s.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access their identity(e. g., identity wallet) and enable data exchange."]}),"\n",(0,s.jsxs)(n.li,{children:["An OSP ",(0,s.jsx)(n.strong,{children:"must"})," integrate and use the GAIA-X Digital Clearing House to validate e. g., the Legal Person Self-Description."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["An OSP and its services ",(0,s.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,s.jsxs)(n.li,{children:["An OSP ",(0,s.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access its identity (e. g., identity wallet)"]}),"\n",(0,s.jsxs)(n.li,{children:["An OSP ",(0,s.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the other OSPs."]}),"\n",(0,s.jsxs)(n.li,{children:["An OSP ",(0,s.jsx)(n.strong,{children:"must"})," use the dedicated GAIA-X Clearing House Service nominated by the Catena-X Association."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsxs)(n.p,{children:["Due to technical limitations, the OSP role currently cannot be fully assumed and executed more than once. Further details can be found in Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"})," or can be requested during the conformity assessment. Offboarding will be included within the upcoming releases."]}),"\n",(0,s.jsx)(n.h3,{id:"enablement-service-provider",children:"Enablement Service Provider"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Enablement Service Provider (ESP)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": An ESP is responsible for deploying, operating, and maintaining enablement services according to Catena-X standards."]}),"\n",(0,s.jsx)(n.p,{children:"An ESP can operate various bundles of decentralized services that enable sovereign\nparticipation and data exchange for data providers and consumers in the Catena-X\ndata space. An ESP can decide on the scope of its enablement service and whether\nto offer them on one or multiple of the marketplaces."}),"\n",(0,s.jsx)(n.p,{children:"In addition, ESPs can also offer non-standardized services such as automated data\nmapping, in which data is extracted from company systems and converted into\nCatena-X semantic models."}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["An ESP ",(0,s.jsx)(n.strong,{children:"can"})," use one or more CSP-A services (e. g., semantic hub)."]}),"\n",(0,s.jsxs)(n.li,{children:["An ESP ",(0,s.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access its identity (e. g., identity wallet) and enable data exchange."]}),"\n",(0,s.jsxs)(n.li,{children:["An ESP ",(0,s.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e. g., registration service)."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["An ESP and its services ",(0,s.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,s.jsxs)(n.li,{children:["An ESP ",(0,s.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsx)(n.p,{children:"n/a"}),"\n",(0,s.jsx)(n.h3,{id:"business-application-provider",children:"Business Application Provider"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Business Application Provider (BAP)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": A BAP is responsible for deploying, operating, and maintaining business applications to Catena-X standards. Business applications enable data providers and consumers to leverage different use cases and data-driven processes to solve a specific industry problem (e.g., PCF) and create business value, by using KITs and Standards for an interoperable and trusted data exchange."]}),"\n",(0,s.jsx)(n.p,{children:"A BAP can decide on the scope of its business applications and whether to offer\nthem on one or multiple of the marketplaces"}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["A BAP ",(0,s.jsx)(n.strong,{children:"can"})," use one or more CSP-A services (e. g., semantic hub)."]}),"\n",(0,s.jsxs)(n.li,{children:["A BAP ",(0,s.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access his identity (e. g., identity wallet) and enable data exchange."]}),"\n",(0,s.jsxs)(n.li,{children:["A BAP ",(0,s.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e. g., registration service)."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["A BAP and its services ",(0,s.jsx)(n.strong,{children:"must"})," be certified by a CAB."]}),"\n",(0,s.jsxs)(n.li,{children:["A BAP ",(0,s.jsx)(n.strong,{children:"must"})," list its solution on a marketplace provided by a CSP-A."]}),"\n",(0,s.jsxs)(n.li,{children:["A BAP ",(0,s.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsx)(n.p,{children:"n/a"}),"\n",(0,s.jsx)(n.h3,{id:"advisory-provider",children:"Advisory Provider"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Advisory Provider (AP)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": An AP offers advisory services in various areas, from strategy to operations to technology or business use cases for those interested in the Catena-X data space. Providing advisory services includes topics such as onboarding guidance, business value assessment, organizational and technical enablement, but do not include the operation of technical services."]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["An AP ",(0,s.jsx)(n.strong,{children:"can"})," use one or more CSP-As if it intends to utilize specific CSP-A services such as listing an offer on a marketplace."]}),"\n",(0,s.jsxs)(n.li,{children:["An AP ",(0,s.jsx)(n.strong,{children:"can"})," integrate and use CSP-B services to access the Core Services B."]}),"\n",(0,s.jsxs)(n.li,{children:["An AP ",(0,s.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e. g., registration service)."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["An AP ",(0,s.jsx)(n.strong,{children:"must"})," be qualified by the Catena-X Association."]}),"\n",(0,s.jsxs)(n.li,{children:["An AP ",(0,s.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsx)(n.p,{children:"n/a"}),"\n",(0,s.jsx)(n.h3,{id:"data-providerconsumer",children:"Data Provider/Consumer"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Data Provider and Consumer (DPC)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": A DPC provides, consumes, and processes data to collaborate with other data space participants to solve a specific industry problem und create business value. This includes both standardized use cases and direct collaboration."]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"can"})," use the services of a CSP-A (e.g., marketplace)."]}),"\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"must"})," integrate and use CSP-B services to access his identity (e. g., identity wallet) and enable data exchange."]}),"\n",(0,s.jsxs)(n.li,{children:["An DPC ",(0,s.jsx)(n.strong,{children:"must"})," use the services of one of the OSPs to register and onboard itself to the data space (e.g., registration service). This can be delegated to a BAP or ESP"]}),"\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"must"})," connect with another DPC to exchange data and create value."]}),"\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"can"})," use advisory services from a qualified AP."]}),"\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"can"})," use certified enablement services from a commercial ESP (e.g., SaaS solution). Alternatively, a DPC can certify and operate its own enablement services."]}),"\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"can"})," use certified business applications from a commercial BAP (e.g., SaaS\nsolution). Alternatively, a DPC can certify and operate its own business application"]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"must"})," use certified enablement services or business applications. Alternatively, a DPC ",(0,s.jsx)(n.strong,{children:"must"})," certify its own enablement services and/or business applications by one of the CABs (as outlined in Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance/#conformity-assessment",children:"Conformity Assessment"}),")."]}),"\n",(0,s.jsxs)(n.li,{children:["A DPC ",(0,s.jsx)(n.strong,{children:"must"})," accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs"]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsx)(n.p,{children:"n/a"}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.em,{children:"In addition to the roles in the data space, there are independent roles such as the Catena-X Association or Conformity\nAssessment Bodies (CABs) to ensure neutral, trustworthy, and secure operation of the Catena-X data space."})}),"\n",(0,s.jsx)(n.h3,{id:"catena-x-association",children:"Catena-X Association"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Catena-X Association"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": The Association is responsible for the neutral governance of the Catena-X ecosystem including the execution of nomination, standardization, qualification, and certification processes. It promotes and facilitates working groups, committees, and expert groups to discuss and align on, standards, KITs, and requirements for open-source reference implementation for the Catena-X operating system and use cases. In addition, it provides various informational resources to interested parties and Association members."]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsx)(n.li,{children:"The Association nominates the CSP-B and CABs."}),"\n",(0,s.jsx)(n.li,{children:"The Association delegates the certification of data space participants to CABs."}),"\n",(0,s.jsx)(n.li,{children:"The Association defines the Issuer of verifiable credentials."}),"\n",(0,s.jsx)(n.li,{children:"The Association qualifies APs."}),"\n",(0,s.jsx)(n.li,{children:"The Association promotes, sponsors, and coordinates the overlying requirements of the Eclipse Tractus-X Project with a view to standardization."}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsx)(n.p,{children:"n/a"}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsxs)(n.p,{children:["For the upcoming releases there will be a dedicated issuer concept in place. As of now the Association defines the Issuer (CSP-B). Further details can be found in Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-operations/#ssi-issuer-concept",children:"SSI Issuer Concept"}),". An outlook can be found in Chapter ",(0,s.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/outlook/#further-integration-of-ssi-technologies",children:"Further Integration of SSI Technologies"}),"."]}),"\n",(0,s.jsx)(n.h3,{id:"conformity-assessment-body",children:"Conformity Assessment Body"}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Role:"})," Conformity Assessment Body (CAB)"]}),"\n",(0,s.jsxs)(n.p,{children:[(0,s.jsx)(n.strong,{children:"Description/Responsibilities"}),": A CAB carries out the conformity assessment process in accordance with the Catena-X Certification Framework on behalf of the Catena-X Association. The Certification Framework consists of the certification manual and the certification catalog (derived from the (",(0,s.jsx)(n.a,{href:"https://catena-x.net/de/standard-library",children:"Catena-X standards"}),")). A CAB is nominated by the Catena-X Association to ensure an independent, trustworthy, and secure conformity assessment process."]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"A CAB is responsible for:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsx)(n.li,{children:"creating offers for the conformity assessments."}),"\n",(0,s.jsx)(n.li,{children:"carrying out the conformity assessment process for various certification objects (e.g., provider, solutions)."}),"\n",(0,s.jsx)(n.li,{children:"informing the Catena-X Association and the certification candidate about the certification results."}),"\n",(0,s.jsx)(n.li,{children:"issuing, reissuing, and revoking of certificates on behalf of the Catena-X\nAssociation."}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Relationships:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:["The CAB ",(0,s.jsx)(n.strong,{children:"must"})," carry out the conformity assessment for all affected data space\nparticipants and their IT solutions."]}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Prerequisites:"})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsx)(n.li,{children:"A CAB must be nominated by the Catena-X Association and comply with the Catena-X certification framework."}),"\n",(0,s.jsx)(n.li,{children:"Business model supporting adoption and offering a non-discriminating access, esp. by small and medium business."}),"\n"]}),"\n",(0,s.jsx)(n.p,{children:(0,s.jsx)(n.strong,{children:"Limitations Release 23.09:"})}),"\n",(0,s.jsx)(n.p,{children:"n/a"})]})}function h(e={}){const{wrapper:n}={...(0,t.R)(),...e.components};return n?(0,s.jsx)(n,{...e,children:(0,s.jsx)(d,{...e})}):d(e)}},8481:(e,n,i)=>{i.d(n,{A:()=>s});const s=i.p+"assets/images/role-overview-and-relationships-ebdb0775319edc16372e21437aedda92.png"},8453:(e,n,i)=>{i.d(n,{R:()=>a,x:()=>o});var s=i(6540);const t={},r=s.createContext(t);function a(e){const n=s.useContext(r);return s.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function o(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(t):e.components||t:a(e.components),s.createElement(r.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/560caf3c.bd452bc3.js b/assets/js/560caf3c.bd452bc3.js new file mode 100644 index 00000000..0f27eadd --- /dev/null +++ b/assets/js/560caf3c.bd452bc3.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[6230],{2807:a=>{a.exports=JSON.parse('{"tag":{"label":"Docusaurus","permalink":"/catenax-ev.github.io.new/blog/tags/docusaurus","description":"Docusaurus tag description","allTagsPath":"/catenax-ev.github.io.new/blog/tags","count":4,"unlisted":false},"listMetadata":{"permalink":"/catenax-ev.github.io.new/blog/tags/docusaurus","page":1,"postsPerPage":10,"totalPages":1,"totalCount":4,"blogDescription":"Blog","blogTitle":"Blog"}}')}}]); \ No newline at end of file diff --git a/assets/js/59362658.906280ee.js b/assets/js/59362658.906280ee.js new file mode 100644 index 00000000..83c8210b --- /dev/null +++ b/assets/js/59362658.906280ee.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9325],{1180:(e,t,o)=>{o.r(t),o.d(t,{assets:()=>c,contentTitle:()=>a,default:()=>p,frontMatter:()=>r,metadata:()=>i,toc:()=>u});var s=o(4848),n=o(8453);const r={slug:"mdx-blog-post",title:"MDX Blog Post",authors:["slorber"],tags:["docusaurus"]},a=void 0,i={permalink:"/catenax-ev.github.io.new/blog/mdx-blog-post",source:"@site/blog/2021-08-01-mdx-blog-post.mdx",title:"MDX Blog Post",description:"Blog posts support Docusaurus Markdown features, such as MDX.",date:"2021-08-01T00:00:00.000Z",tags:[{inline:!1,label:"Docusaurus",permalink:"/catenax-ev.github.io.new/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:.175,hasTruncateMarker:!1,authors:[{name:"S\xe9bastien Lorber",title:"Docusaurus maintainer",url:"https://sebastienlorber.com",imageURL:"https://github.com/slorber.png",key:"slorber"}],frontMatter:{slug:"mdx-blog-post",title:"MDX Blog Post",authors:["slorber"],tags:["docusaurus"]},unlisted:!1,prevItem:{title:"Welcome",permalink:"/catenax-ev.github.io.new/blog/welcome"},nextItem:{title:"Long Blog Post",permalink:"/catenax-ev.github.io.new/blog/long-blog-post"}},c={authorsImageUrls:[void 0]},u=[];function l(e){const t={a:"a",admonition:"admonition",code:"code",p:"p",pre:"pre",...(0,n.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsxs)(t.p,{children:["Blog posts support ",(0,s.jsx)(t.a,{href:"https://docusaurus.io/docs/markdown-features",children:"Docusaurus Markdown features"}),", such as ",(0,s.jsx)(t.a,{href:"https://mdxjs.com/",children:"MDX"}),"."]}),"\n",(0,s.jsxs)(t.admonition,{type:"tip",children:[(0,s.jsx)(t.p,{children:"Use the power of React to create interactive blog posts."}),(0,s.jsx)(t.pre,{children:(0,s.jsx)(t.code,{className:"language-js",children:"\n"})}),(0,s.jsx)("button",{onClick:()=>alert("button clicked!"),children:"Click me!"})]})]})}function p(e={}){const{wrapper:t}={...(0,n.R)(),...e.components};return t?(0,s.jsx)(t,{...e,children:(0,s.jsx)(l,{...e})}):l(e)}},8453:(e,t,o)=>{o.d(t,{R:()=>a,x:()=>i});var s=o(6540);const n={},r=s.createContext(n);function a(e){const t=s.useContext(r);return s.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function i(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:a(e.components),s.createElement(r.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/59362658.dd12e8ea.js b/assets/js/59362658.dd12e8ea.js deleted file mode 100644 index 190b2c51..00000000 --- a/assets/js/59362658.dd12e8ea.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9325],{1180:(t,e,o)=>{o.r(e),o.d(e,{assets:()=>u,contentTitle:()=>a,default:()=>p,frontMatter:()=>r,metadata:()=>c,toc:()=>i});var s=o(4848),n=o(8453);const r={slug:"mdx-blog-post",title:"MDX Blog Post",authors:["slorber"],tags:["docusaurus"]},a=void 0,c={permalink:"/blog/mdx-blog-post",source:"@site/blog/2021-08-01-mdx-blog-post.mdx",title:"MDX Blog Post",description:"Blog posts support Docusaurus Markdown features, such as MDX.",date:"2021-08-01T00:00:00.000Z",tags:[{inline:!1,label:"Docusaurus",permalink:"/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:.175,hasTruncateMarker:!1,authors:[{name:"S\xe9bastien Lorber",title:"Docusaurus maintainer",url:"https://sebastienlorber.com",imageURL:"https://github.com/slorber.png",key:"slorber"}],frontMatter:{slug:"mdx-blog-post",title:"MDX Blog Post",authors:["slorber"],tags:["docusaurus"]},unlisted:!1,prevItem:{title:"Welcome",permalink:"/blog/welcome"},nextItem:{title:"Long Blog Post",permalink:"/blog/long-blog-post"}},u={authorsImageUrls:[void 0]},i=[];function l(t){const e={a:"a",admonition:"admonition",code:"code",p:"p",pre:"pre",...(0,n.R)(),...t.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsxs)(e.p,{children:["Blog posts support ",(0,s.jsx)(e.a,{href:"https://docusaurus.io/docs/markdown-features",children:"Docusaurus Markdown features"}),", such as ",(0,s.jsx)(e.a,{href:"https://mdxjs.com/",children:"MDX"}),"."]}),"\n",(0,s.jsxs)(e.admonition,{type:"tip",children:[(0,s.jsx)(e.p,{children:"Use the power of React to create interactive blog posts."}),(0,s.jsx)(e.pre,{children:(0,s.jsx)(e.code,{className:"language-js",children:"\n"})}),(0,s.jsx)("button",{onClick:()=>alert("button clicked!"),children:"Click me!"})]})]})}function p(t={}){const{wrapper:e}={...(0,n.R)(),...t.components};return e?(0,s.jsx)(e,{...t,children:(0,s.jsx)(l,{...t})}):l(t)}},8453:(t,e,o)=>{o.d(e,{R:()=>a,x:()=>c});var s=o(6540);const n={},r=s.createContext(n);function a(t){const e=s.useContext(r);return s.useMemo((function(){return"function"==typeof t?t(e):{...e,...t}}),[e,t])}function c(t){let e;return e=t.disableParentContext?"function"==typeof t.components?t.components(n):t.components||n:a(t.components),s.createElement(r.Provider,{value:e},t.children)}}}]); \ No newline at end of file diff --git a/assets/js/5e90a9b3.f62940b7.js b/assets/js/5e90a9b3.f62940b7.js deleted file mode 100644 index 05bc879b..00000000 --- a/assets/js/5e90a9b3.f62940b7.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8025],{7134:a=>{a.exports=JSON.parse('{"tag":{"label":"Hola","permalink":"/blog/tags/hola","description":"Hola tag description","allTagsPath":"/blog/tags","count":1,"unlisted":false},"listMetadata":{"permalink":"/blog/tags/hola","page":1,"postsPerPage":10,"totalPages":1,"totalCount":1,"blogDescription":"Blog","blogTitle":"Blog"}}')}}]); \ No newline at end of file diff --git a/assets/js/63fe0935.b19a060b.js b/assets/js/63fe0935.b19a060b.js deleted file mode 100644 index 17ab2858..00000000 --- a/assets/js/63fe0935.b19a060b.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[6144],{1314:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>l,contentTitle:()=>o,default:()=>u,frontMatter:()=>a,metadata:()=>s,toc:()=>c});var i=t(4848),r=t(8453);const a={sidebar_position:1},o="Catena-X Organizational Structure",s={id:"working-model/organizational-structure/organizational-structure",title:"Catena-X Organizational Structure",description:"Catena-X OrgChart",source:"@site/docs/working-model/02-organizational-structure/02-organizational-structure.md",sourceDirName:"working-model/02-organizational-structure",slug:"/working-model/organizational-structure/",permalink:"/docs/next/working-model/organizational-structure/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_working_model",previous:{title:"Catena-X Ecosystem",permalink:"/docs/next/working-model/ecosystem/"},next:{title:"Tooling",permalink:"/docs/next/working-model/organizational-structure/02-03-tooling"}},l={},c=[{value:"Structural Organization",id:"structural-organization",level:2},{value:"Catena-X Automotive Network e.V",id:"catena-x-automotive-network-ev",level:3},{value:"Eclipse Tractus-X Project",id:"eclipse-tractus-x-project",level:3},{value:"Other Initiatives",id:"other-initiatives",level:3}];function d(e){const n={a:"a",admonition:"admonition",h1:"h1",h2:"h2",h3:"h3",img:"img",li:"li",p:"p",ul:"ul",...(0,r.R)(),...e.components};return(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(n.h1,{id:"catena-x-organizational-structure",children:"Catena-X Organizational Structure"}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Catena-X OrgChart",src:t(8804).A+""})}),"\n",(0,i.jsx)(n.h2,{id:"structural-organization",children:"Structural Organization"}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Structual Process Organization",src:t(46).A+""})}),"\n",(0,i.jsx)(n.h3,{id:"catena-x-automotive-network-ev",children:"Catena-X Automotive Network e.V"}),"\n",(0,i.jsx)(n.admonition,{type:"info",children:(0,i.jsx)(n.p,{children:"ToDo: Michael\nUpdate Grafik nach dem 01.04. mit Update von Jan"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Catena-X is structured along Committees and Expert Groups"}),"\n",(0,i.jsxs)(n.li,{children:["Committees and Expert Groups are mapped to products or use cases","\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Role of Catena-X Association"}),"\n",(0,i.jsx)(n.li,{children:"Rolle der Mitarbeiter innerhalb im Verein (z.B. Expert Groups, Committees)"}),"\n",(0,i.jsx)(n.li,{children:"The Catena-X Automotive Network e.V. promotes, sponsors, and coordinates the overlying requirements of the Eclipse Tractus-X Project."}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,i.jsxs)(n.p,{children:["Committees and Expert Groups are advertised, selected, and established on the basis of a \u201crequirement\u201d. The application phases are similar and the distributors are always the Catena-X members. More information can be found ",(0,i.jsx)(n.a,{href:"/docs/next/working-model/organizational-structure/overview-roles/",children:"here"}),"."]}),"\n",(0,i.jsx)(n.p,{children:"To get a better overview of the given Committees and Expert Groups, there will be a SharePoint page within the member area. Information about:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"The groups"}),"\n",(0,i.jsx)(n.li,{children:"Purpose"}),"\n",(0,i.jsx)(n.li,{children:"Member"}),"\n",(0,i.jsx)(n.li,{children:"Important meetings"}),"\n",(0,i.jsx)(n.li,{children:"Milestones"}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"Can be found there."}),"\n",(0,i.jsx)(n.admonition,{type:"info",children:(0,i.jsx)(n.p,{children:"The sharepoint pages can only be accessed by association members."})}),"\n",(0,i.jsx)(n.h3,{id:"eclipse-tractus-x-project",children:"Eclipse Tractus-X Project"}),"\n",(0,i.jsx)(n.admonition,{type:"info",children:(0,i.jsx)(n.p,{children:"ToDo: Michael"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Tractus-X is structured along products (repos) or use cases"}),"\n",(0,i.jsx)(n.li,{children:"Committers / Contributors are mapped to products or use cases"}),"\n",(0,i.jsx)(n.li,{children:"Each contributor can propose features in sig-release"}),"\n",(0,i.jsx)(n.li,{children:"Committers make the decision which features will be committed in the next release"}),"\n",(0,i.jsxs)(n.li,{children:["Outcome:","\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Planning: Committed, periodized backlog for a release"}),"\n",(0,i.jsx)(n.li,{children:"Release: Release Train"}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"other-initiatives",children:"Other Initiatives"}),"\n",(0,i.jsx)(n.admonition,{type:"info",children:(0,i.jsx)(n.p,{children:"ToDo: Michael"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["Other initiatives (such as M-X) can use our processes to propose...","\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Feature proposals"}),"\n",(0,i.jsx)(n.li,{children:"Standardization candidates (?)"}),"\n"]}),"\n"]}),"\n"]})]})}function u(e={}){const{wrapper:n}={...(0,r.R)(),...e.components};return n?(0,i.jsx)(n,{...e,children:(0,i.jsx)(d,{...e})}):d(e)}},8804:(e,n,t)=>{t.d(n,{A:()=>i});const i=t.p+"assets/images/CX-Org-Chart.drawio-dec484457a650af4b5dae9aedc795e0f.svg"},46:(e,n,t)=>{t.d(n,{A:()=>i});const i=t.p+"assets/images/structual-process-organization.drawio-c59648c003e14f05c2b9d55ef16fdda5.svg"},8453:(e,n,t)=>{t.d(n,{R:()=>o,x:()=>s});var i=t(6540);const r={},a=i.createContext(r);function o(e){const n=i.useContext(a);return i.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function s(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(r):e.components||r:o(e.components),i.createElement(a.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/63fe0935.f321da39.js b/assets/js/63fe0935.f321da39.js new file mode 100644 index 00000000..9b8e30b3 --- /dev/null +++ b/assets/js/63fe0935.f321da39.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[6144],{1314:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>l,contentTitle:()=>o,default:()=>u,frontMatter:()=>a,metadata:()=>s,toc:()=>c});var i=t(4848),r=t(8453);const a={sidebar_position:1},o="Catena-X Organizational Structure",s={id:"working-model/organizational-structure/organizational-structure",title:"Catena-X Organizational Structure",description:"Catena-X OrgChart",source:"@site/docs/working-model/02-organizational-structure/02-organizational-structure.md",sourceDirName:"working-model/02-organizational-structure",slug:"/working-model/organizational-structure/",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_working_model",previous:{title:"Catena-X Ecosystem",permalink:"/catenax-ev.github.io.new/docs/next/working-model/ecosystem/"},next:{title:"Tooling",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/02-03-tooling"}},l={},c=[{value:"Structural Organization",id:"structural-organization",level:2},{value:"Catena-X Automotive Network e.V",id:"catena-x-automotive-network-ev",level:3},{value:"Eclipse Tractus-X Project",id:"eclipse-tractus-x-project",level:3},{value:"Other Initiatives",id:"other-initiatives",level:3}];function d(e){const n={a:"a",admonition:"admonition",h1:"h1",h2:"h2",h3:"h3",img:"img",li:"li",p:"p",ul:"ul",...(0,r.R)(),...e.components};return(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(n.h1,{id:"catena-x-organizational-structure",children:"Catena-X Organizational Structure"}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Catena-X OrgChart",src:t(8804).A+""})}),"\n",(0,i.jsx)(n.h2,{id:"structural-organization",children:"Structural Organization"}),"\n",(0,i.jsx)(n.p,{children:(0,i.jsx)(n.img,{alt:"Structual Process Organization",src:t(46).A+""})}),"\n",(0,i.jsx)(n.h3,{id:"catena-x-automotive-network-ev",children:"Catena-X Automotive Network e.V"}),"\n",(0,i.jsx)(n.admonition,{type:"info",children:(0,i.jsx)(n.p,{children:"ToDo: Michael\nUpdate Grafik nach dem 01.04. mit Update von Jan"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Catena-X is structured along Committees and Expert Groups"}),"\n",(0,i.jsxs)(n.li,{children:["Committees and Expert Groups are mapped to products or use cases","\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Role of Catena-X Association"}),"\n",(0,i.jsx)(n.li,{children:"Rolle der Mitarbeiter innerhalb im Verein (z.B. Expert Groups, Committees)"}),"\n",(0,i.jsx)(n.li,{children:"The Catena-X Automotive Network e.V. promotes, sponsors, and coordinates the overlying requirements of the Eclipse Tractus-X Project."}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,i.jsxs)(n.p,{children:["Committees and Expert Groups are advertised, selected, and established on the basis of a \u201crequirement\u201d. The application phases are similar and the distributors are always the Catena-X members. More information can be found ",(0,i.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/",children:"here"}),"."]}),"\n",(0,i.jsx)(n.p,{children:"To get a better overview of the given Committees and Expert Groups, there will be a SharePoint page within the member area. Information about:"}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"The groups"}),"\n",(0,i.jsx)(n.li,{children:"Purpose"}),"\n",(0,i.jsx)(n.li,{children:"Member"}),"\n",(0,i.jsx)(n.li,{children:"Important meetings"}),"\n",(0,i.jsx)(n.li,{children:"Milestones"}),"\n"]}),"\n",(0,i.jsx)(n.p,{children:"Can be found there."}),"\n",(0,i.jsx)(n.admonition,{type:"info",children:(0,i.jsx)(n.p,{children:"The sharepoint pages can only be accessed by association members."})}),"\n",(0,i.jsx)(n.h3,{id:"eclipse-tractus-x-project",children:"Eclipse Tractus-X Project"}),"\n",(0,i.jsx)(n.admonition,{type:"info",children:(0,i.jsx)(n.p,{children:"ToDo: Michael"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Tractus-X is structured along products (repos) or use cases"}),"\n",(0,i.jsx)(n.li,{children:"Committers / Contributors are mapped to products or use cases"}),"\n",(0,i.jsx)(n.li,{children:"Each contributor can propose features in sig-release"}),"\n",(0,i.jsx)(n.li,{children:"Committers make the decision which features will be committed in the next release"}),"\n",(0,i.jsxs)(n.li,{children:["Outcome:","\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Planning: Committed, periodized backlog for a release"}),"\n",(0,i.jsx)(n.li,{children:"Release: Release Train"}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,i.jsx)(n.h3,{id:"other-initiatives",children:"Other Initiatives"}),"\n",(0,i.jsx)(n.admonition,{type:"info",children:(0,i.jsx)(n.p,{children:"ToDo: Michael"})}),"\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsxs)(n.li,{children:["Other initiatives (such as M-X) can use our processes to propose...","\n",(0,i.jsxs)(n.ul,{children:["\n",(0,i.jsx)(n.li,{children:"Feature proposals"}),"\n",(0,i.jsx)(n.li,{children:"Standardization candidates (?)"}),"\n"]}),"\n"]}),"\n"]})]})}function u(e={}){const{wrapper:n}={...(0,r.R)(),...e.components};return n?(0,i.jsx)(n,{...e,children:(0,i.jsx)(d,{...e})}):d(e)}},8804:(e,n,t)=>{t.d(n,{A:()=>i});const i=t.p+"assets/images/CX-Org-Chart.drawio-dec484457a650af4b5dae9aedc795e0f.svg"},46:(e,n,t)=>{t.d(n,{A:()=>i});const i=t.p+"assets/images/structual-process-organization.drawio-c59648c003e14f05c2b9d55ef16fdda5.svg"},8453:(e,n,t)=>{t.d(n,{R:()=>o,x:()=>s});var i=t(6540);const r={},a=i.createContext(r);function o(e){const n=i.useContext(a);return i.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function s(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(r):e.components||r:o(e.components),i.createElement(a.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/66b22c07.5886033a.js b/assets/js/66b22c07.5886033a.js new file mode 100644 index 00000000..84fa41c8 --- /dev/null +++ b/assets/js/66b22c07.5886033a.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9457],{6486:(e,a,t)=>{t.r(a),t.d(a,{assets:()=>c,contentTitle:()=>r,default:()=>m,frontMatter:()=>s,metadata:()=>o,toc:()=>l});var n=t(4848),i=t(8453);const s={sidebar_position:1},r="How: Life Cycle Management",o={id:"operating-model/how-life-cycle-management/how-life-cycle-management",title:"How: Life Cycle Management",description:"Managing versions and changes of different artifacts in federated data spaces is critical to ensure compatibility, interoperability, and security. The life cycle management of the Catena-X ecosystem is coordinated by the Catena-X Association and includes the releases in the Catena-X Association and in the Eclipse Tractus-X Project (see Figure Overview Life Cycle Management). It is planned to provide quarterly releases including one major and three minor releases per year. Both releases follow calendar versioning (see CalVer), whereas their artifacts such as standards, normative documents, products, and KITs follow semantic versioning (see SemVer). To ensure backward compatibility in the future (see Chapter Backward Compatibility), versioning and passing of predefined test cases of each individual artifact is mandatory.",source:"@site/docs/operating-model/how-life-cycle-management/how-life-cycle-management.md",sourceDirName:"operating-model/how-life-cycle-management",slug:"/operating-model/how-life-cycle-management/",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/how-life-cycle-management/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"How: Data Space Governance",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance/"},next:{title:"Outlook",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/outlook/"}},c={},l=[];function d(e){const a={a:"a",em:"em",h1:"h1",img:"img",p:"p",strong:"strong",...(0,i.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(a.h1,{id:"how-life-cycle-management",children:"How: Life Cycle Management"}),"\n",(0,n.jsxs)(a.p,{children:["Managing versions and changes of different artifacts in federated data spaces is critical to ensure compatibility, interoperability, and security. The life cycle management of the Catena-X ecosystem is coordinated by the Catena-X Association and includes the releases in the Catena-X Association and in the Eclipse Tractus-X Project (see Figure ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-life-cycle-management/",children:"Overview Life Cycle Management"}),"). It is planned to provide quarterly releases including ",(0,n.jsx)(a.strong,{children:"one major"})," and ",(0,n.jsx)(a.strong,{children:"three minor"})," releases per year. Both releases follow calendar versioning (see ",(0,n.jsx)(a.a,{href:"https://calver.org/",children:"CalVer"}),"), whereas their artifacts such as standards, normative documents, products, and KITs follow semantic versioning (see ",(0,n.jsx)(a.a,{href:"https://semver.org/",children:"SemVer"}),"). To ensure backward compatibility in the future (see Chapter ",(0,n.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/outlook/#backward-compatibility",children:"Backward Compatibility"}),"), versioning and passing of predefined test cases of each individual artifact is mandatory."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"Overview Life Cycle Management",src:t(1162).A+"",width:"1757",height:"602"}),"\n",(0,n.jsx)(a.em,{children:"Overview Life Cycle Management"})]}),"\n",(0,n.jsx)(a.p,{children:"The Catena-X Association release includes all binding and certification-relevant artifacts such as standards (e.g., API-specifications, semantic models) and normative documents for all data space participants. The Tractus-X release contains all open-source products (including services or helm charts) of the cxOS and business applications as well as KITs. In addition, there are various commercial or self-developed solutions for business applications and services following individual release cycles and versioning schemes."}),"\n",(0,n.jsx)(a.p,{children:"Both the Tractus-X release and any commercial or self developed solutions must adhere to Catena-X standards and other relevant normative documents."}),"\n",(0,n.jsxs)(a.p,{children:["Open-source products are required to fulfill the ",(0,n.jsx)(a.a,{href:"https://eclipse-tractusx.github.io/docs/release/",children:"Tractus-X release guideline(TRGs)"})," and take part in our integration tests to be part of a quarterly Tractus-X release. For critical issues (e. g., security issues), hot fixes may be released to fix a bug in the active Catena-X operating system that interrupts the normal release cycle."]})]})}function m(e={}){const{wrapper:a}={...(0,i.R)(),...e.components};return a?(0,n.jsx)(a,{...e,children:(0,n.jsx)(d,{...e})}):d(e)}},1162:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/overview-life-cycle-management-dfc25bce1da282bfe1fa509d8cfe7aac.png"},8453:(e,a,t)=>{t.d(a,{R:()=>r,x:()=>o});var n=t(6540);const i={},s=n.createContext(i);function r(e){const a=n.useContext(s);return n.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function o(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:r(e.components),n.createElement(s.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/66b22c07.7207ff62.js b/assets/js/66b22c07.7207ff62.js deleted file mode 100644 index 776a9a98..00000000 --- a/assets/js/66b22c07.7207ff62.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9457],{6486:(e,a,t)=>{t.r(a),t.d(a,{assets:()=>c,contentTitle:()=>r,default:()=>m,frontMatter:()=>s,metadata:()=>o,toc:()=>l});var n=t(4848),i=t(8453);const s={sidebar_position:1},r="How: Life Cycle Management",o={id:"operating-model/how-life-cycle-management/how-life-cycle-management",title:"How: Life Cycle Management",description:"Managing versions and changes of different artifacts in federated data spaces is critical to ensure compatibility, interoperability, and security. The life cycle management of the Catena-X ecosystem is coordinated by the Catena-X Association and includes the releases in the Catena-X Association and in the Eclipse Tractus-X Project (see Figure Overview Life Cycle Management). It is planned to provide quarterly releases including one major and three minor releases per year. Both releases follow calendar versioning (see CalVer), whereas their artifacts such as standards, normative documents, products, and KITs follow semantic versioning (see SemVer). To ensure backward compatibility in the future (see Chapter Backward Compatibility), versioning and passing of predefined test cases of each individual artifact is mandatory.",source:"@site/docs/operating-model/how-life-cycle-management/how-life-cycle-management.md",sourceDirName:"operating-model/how-life-cycle-management",slug:"/operating-model/how-life-cycle-management/",permalink:"/docs/next/operating-model/how-life-cycle-management/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"How: Data Space Governance",permalink:"/docs/next/operating-model/how-data-space-governance/"},next:{title:"Outlook",permalink:"/docs/next/operating-model/outlook/"}},c={},l=[];function d(e){const a={a:"a",em:"em",h1:"h1",img:"img",p:"p",strong:"strong",...(0,i.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(a.h1,{id:"how-life-cycle-management",children:"How: Life Cycle Management"}),"\n",(0,n.jsxs)(a.p,{children:["Managing versions and changes of different artifacts in federated data spaces is critical to ensure compatibility, interoperability, and security. The life cycle management of the Catena-X ecosystem is coordinated by the Catena-X Association and includes the releases in the Catena-X Association and in the Eclipse Tractus-X Project (see Figure ",(0,n.jsx)(a.a,{href:"/docs/next/operating-model/how-life-cycle-management/",children:"Overview Life Cycle Management"}),"). It is planned to provide quarterly releases including ",(0,n.jsx)(a.strong,{children:"one major"})," and ",(0,n.jsx)(a.strong,{children:"three minor"})," releases per year. Both releases follow calendar versioning (see ",(0,n.jsx)(a.a,{href:"https://calver.org/",children:"CalVer"}),"), whereas their artifacts such as standards, normative documents, products, and KITs follow semantic versioning (see ",(0,n.jsx)(a.a,{href:"https://semver.org/",children:"SemVer"}),"). To ensure backward compatibility in the future (see Chapter ",(0,n.jsx)(a.a,{href:"/docs/next/operating-model/outlook/#backward-compatibility",children:"Backward Compatibility"}),"), versioning and passing of predefined test cases of each individual artifact is mandatory."]}),"\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.img,{alt:"Overview Life Cycle Management",src:t(1162).A+"",width:"1757",height:"602"}),"\n",(0,n.jsx)(a.em,{children:"Overview Life Cycle Management"})]}),"\n",(0,n.jsx)(a.p,{children:"The Catena-X Association release includes all binding and certification-relevant artifacts such as standards (e.g., API-specifications, semantic models) and normative documents for all data space participants. The Tractus-X release contains all open-source products (including services or helm charts) of the cxOS and business applications as well as KITs. In addition, there are various commercial or self-developed solutions for business applications and services following individual release cycles and versioning schemes."}),"\n",(0,n.jsx)(a.p,{children:"Both the Tractus-X release and any commercial or self developed solutions must adhere to Catena-X standards and other relevant normative documents."}),"\n",(0,n.jsxs)(a.p,{children:["Open-source products are required to fulfill the ",(0,n.jsx)(a.a,{href:"https://eclipse-tractusx.github.io/docs/release/",children:"Tractus-X release guideline(TRGs)"})," and take part in our integration tests to be part of a quarterly Tractus-X release. For critical issues (e. g., security issues), hot fixes may be released to fix a bug in the active Catena-X operating system that interrupts the normal release cycle."]})]})}function m(e={}){const{wrapper:a}={...(0,i.R)(),...e.components};return a?(0,n.jsx)(a,{...e,children:(0,n.jsx)(d,{...e})}):d(e)}},1162:(e,a,t)=>{t.d(a,{A:()=>n});const n=t.p+"assets/images/overview-life-cycle-management-dfc25bce1da282bfe1fa509d8cfe7aac.png"},8453:(e,a,t)=>{t.d(a,{R:()=>r,x:()=>o});var n=t(6540);const i={},s=n.createContext(i);function r(e){const a=n.useContext(s);return n.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function o(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:r(e.components),n.createElement(s.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/6e164704.2afa60e6.js b/assets/js/6e164704.2afa60e6.js new file mode 100644 index 00000000..5a0bc781 --- /dev/null +++ b/assets/js/6e164704.2afa60e6.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[4926],{7957:e=>{e.exports=JSON.parse('{"version":{"pluginId":"default","version":"24.03","label":"24.03","banner":null,"badge":true,"noIndex":false,"className":"docs-version-24.03","isLast":true,"docsSidebars":{"sidebar_standards":[{"type":"link","label":"Overview Standards","href":"/catenax-ev.github.io.new/docs/standards/overview","docId":"standards/overview","unlisted":false}],"sidebar_op_model":[{"type":"link","label":"Operating Model","href":"/catenax-ev.github.io.new/docs/operating-model/operating-model/","docId":"operating-model/operating-model/operating-model","unlisted":false},{"type":"link","label":"Who: Roles in the Catena-X ecosystem","href":"/catenax-ev.github.io.new/docs/operating-model/why-introduction/","docId":"operating-model/why-introduction/why-introduction","unlisted":false},{"type":"link","label":"Why: Understanding the Catena-X Data Space","href":"/catenax-ev.github.io.new/docs/operating-model/why-understanding-the-catena-x-data-space/","docId":"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space","unlisted":false},{"type":"link","label":"Who: Roles in the Catena-X ecosystem","href":"/catenax-ev.github.io.new/docs/operating-model/who-roles-in-the-catena-x-ecosystem/","docId":"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem","unlisted":false},{"type":"link","label":"What: Service Map","href":"/catenax-ev.github.io.new/docs/operating-model/what-service-map/","docId":"operating-model/what-service-map/what-service-map","unlisted":false},{"type":"link","label":"How: Data Space Operations","href":"/catenax-ev.github.io.new/docs/operating-model/how-data-space-operations/","docId":"operating-model/how-data-space-operations/how-data-space-operations","unlisted":false},{"type":"link","label":"How: Data Space Governance","href":"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance/","docId":"operating-model/how-data-space-governance/how-data-space-governance","unlisted":false},{"type":"link","label":"How: Life Cycle Management","href":"/catenax-ev.github.io.new/docs/operating-model/how-life-cycle-management/","docId":"operating-model/how-life-cycle-management/how-life-cycle-management","unlisted":false},{"type":"link","label":"Outlook","href":"/catenax-ev.github.io.new/docs/operating-model/outlook/","docId":"operating-model/outlook/outlook","unlisted":false},{"type":"link","label":"Glossary","href":"/catenax-ev.github.io.new/docs/operating-model/glossary/","docId":"operating-model/glossary/glossary","unlisted":false},{"type":"link","label":"Appendix","href":"/catenax-ev.github.io.new/docs/operating-model/appendix/","docId":"operating-model/appendix/appendix","unlisted":false},{"type":"link","label":"Change Log","href":"/catenax-ev.github.io.new/docs/operating-model/change-log/","docId":"operating-model/change-log/change-log","unlisted":false}],"sidebar_working_model":[{"type":"link","label":"Overview Working Model","href":"/catenax-ev.github.io.new/docs/working-model/overview","docId":"working-model/overview","unlisted":false}]},"docs":{"operating-model/appendix/appendix":{"id":"operating-model/appendix/appendix","title":"Appendix","description":"Role Relationships","sidebar":"sidebar_op_model"},"operating-model/change-log/change-log":{"id":"operating-model/change-log/change-log","title":"Change Log","description":"Added","sidebar":"sidebar_op_model"},"operating-model/glossary/glossary":{"id":"operating-model/glossary/glossary","title":"Glossary","description":"| Abbreviation | Full form |","sidebar":"sidebar_op_model"},"operating-model/how-data-space-governance/how-data-space-governance":{"id":"operating-model/how-data-space-governance/how-data-space-governance","title":"How: Data Space Governance","description":"Standardization","sidebar":"sidebar_op_model"},"operating-model/how-data-space-operations/how-data-space-operations":{"id":"operating-model/how-data-space-operations/how-data-space-operations","title":"How: Data Space Operations","description":"This chapter outlines the overarching processes and premises to onboard and exchange","sidebar":"sidebar_op_model"},"operating-model/how-life-cycle-management/how-life-cycle-management":{"id":"operating-model/how-life-cycle-management/how-life-cycle-management","title":"How: Life Cycle Management","description":"Managing versions and changes of different artifacts in federated data spaces is critical to ensure compatibility, interoperability, and security. The life cycle management of the Catena-X ecosystem is coordinated by the Catena-X Association and includes the releases in the Catena-X Association and in the Eclipse Tractus-X Project (see Figure Overview Life Cycle Management). It is planned to provide quarterly releases including one major and three minor releases per year. Both releases follow calendar versioning (see CalVer), whereas their artifacts such as standards, normative documents, products, and KITs follow semantic versioning (see SemVer). To ensure backward compatibility in the future (see Chapter Backward Compatibility), versioning and passing of predefined test cases of each individual artifact is mandatory.","sidebar":"sidebar_op_model"},"operating-model/operating-model/operating-model":{"id":"operating-model/operating-model/operating-model","title":"Catena-X Operating Model","description":"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.","sidebar":"sidebar_op_model"},"operating-model/outlook/outlook":{"id":"operating-model/outlook/outlook","title":"Outlook","description":"The Catena-X Operating Model is a normative document within the regulatory framework, which is binding for all participants in the Catena-X data space. It describes the status of our data space artifacts, including roles, services, and processes along with their respective roadmaps. As Catena-X is an ongoing journey, all of these artifacts will continuously evolve to promote broader adoption and scalability, ensuring maximum interoperability, and (data) sovereignty.","sidebar":"sidebar_op_model"},"operating-model/what-service-map/what-service-map":{"id":"operating-model/what-service-map/what-service-map","title":"What: Service Map","description":"The architecture of the Catena-X Operating System (cxOS) is derived from the reference","sidebar":"sidebar_op_model"},"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem":{"id":"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem","title":"Who: Roles in the Catena-X ecosystem","description":"The Catena-X ecosystem operates on the principle of multiple distinct roles, designed to create an appealing and functional data space (see Figure Role Overview and Relationships). Participants can take on one or more roles in any combination, and multiple participants can fulfill the same role except for the CSP-B role. The CSP-B role can only exist once in the data space due to complexity and technical reasons. Provider roles receive a label through a certification or qualification process to demonstrate that they are trusted partners (see Chapter How: Life Cycle Management).","sidebar":"sidebar_op_model"},"operating-model/why-introduction/why-introduction":{"id":"operating-model/why-introduction/why-introduction","title":"Why: Introduction","description":"Relevance","sidebar":"sidebar_op_model"},"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space":{"id":"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space","title":"Why: Understanding the Catena-X Data Space","description":"Conceptual Foundations of the Catena-X Data Ecosystem","sidebar":"sidebar_op_model"},"standards/overview":{"id":"standards/overview","title":"Overview Standards","description":"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.","sidebar":"sidebar_standards"},"working-model/overview":{"id":"working-model/overview","title":"Overview Working Model","description":"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.","sidebar":"sidebar_working_model"}}}}')}}]); \ No newline at end of file diff --git a/assets/js/6e427521.20abbda1.js b/assets/js/6e427521.20abbda1.js new file mode 100644 index 00000000..c73fa5d9 --- /dev/null +++ b/assets/js/6e427521.20abbda1.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[7177],{8803:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>c,contentTitle:()=>a,default:()=>p,frontMatter:()=>i,metadata:()=>s,toc:()=>d});var r=n(4848),o=n(8453);const i={},a="COPYRIGHT & TRADEMARKS",s={type:"mdx",permalink:"/catenax-ev.github.io.new/copyright",source:"@site/src/pages/copyright.md",title:"COPYRIGHT & TRADEMARKS",description:"Any and all rights to the present document or parts of it, including but not limited under copyright",frontMatter:{},unlisted:!1},c={},d=[];function h(e){const t={h1:"h1",p:"p",...(0,o.R)(),...e.components};return(0,r.jsxs)(r.Fragment,{children:[(0,r.jsx)(t.h1,{id:"copyright--trademarks",children:"COPYRIGHT & TRADEMARKS"}),"\n",(0,r.jsx)(t.p,{children:"Any and all rights to the present document or parts of it, including but not limited under copyright\nlaw, are owned by Catena-X and its licensors."}),"\n",(0,r.jsx)(t.p,{children:"The contents of this document shall not be copied, modified, distributed, displayed, made publicly\navailable or otherwise be publicly communicated, in whole or in part, for any purposes, without the\nprior authorization by Catena-X, and nothing herein confers any right or license to do so."}),"\n",(0,r.jsx)(t.p,{children:"The present document may include trademarks or trade names which are registered by their owners. Catena-X\nclaims no ownership of these except for any which are indicated as being the property of Catena-X, and\nconveys no right to use or reproduce any such trademark or trade name contained herein. Mention of any\nthird-party trademarks in the present document does not constitute an endorsement by Catena-X of products,\nservices or organizations associated with those trademarks."}),"\n",(0,r.jsx)(t.p,{children:"\u201cCATENA-X\u201d is a trademark owned by Catena-X registered for its benefit and the benefit of its members.\nUsing or reproducing this trademark or the trade name of Catena-X is expressly prohibited.\nNo express or implied license to any intellectual property rights in the present document or parts\nthereof, or relating to the use of its contents, or mentioned in the present document is granted herein.\nThe copyright and the foregoing restrictions extend to reproduction in all media.\n\xa9 Catena-X Automotive Network e.V. All rights reserved."})]})}function p(e={}){const{wrapper:t}={...(0,o.R)(),...e.components};return t?(0,r.jsx)(t,{...e,children:(0,r.jsx)(h,{...e})}):h(e)}},8453:(e,t,n)=>{n.d(t,{R:()=>a,x:()=>s});var r=n(6540);const o={},i=r.createContext(o);function a(e){const t=r.useContext(i);return r.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function s(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(o):e.components||o:a(e.components),r.createElement(i.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/6e427521.349c29f1.js b/assets/js/6e427521.349c29f1.js deleted file mode 100644 index 747d8949..00000000 --- a/assets/js/6e427521.349c29f1.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[7177],{8803:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>c,contentTitle:()=>a,default:()=>p,frontMatter:()=>i,metadata:()=>s,toc:()=>d});var r=n(4848),o=n(8453);const i={},a="COPYRIGHT & TRADEMARKS",s={type:"mdx",permalink:"/copyright",source:"@site/src/pages/copyright.md",title:"COPYRIGHT & TRADEMARKS",description:"Any and all rights to the present document or parts of it, including but not limited under copyright",frontMatter:{},unlisted:!1},c={},d=[];function h(e){const t={h1:"h1",p:"p",...(0,o.R)(),...e.components};return(0,r.jsxs)(r.Fragment,{children:[(0,r.jsx)(t.h1,{id:"copyright--trademarks",children:"COPYRIGHT & TRADEMARKS"}),"\n",(0,r.jsx)(t.p,{children:"Any and all rights to the present document or parts of it, including but not limited under copyright\nlaw, are owned by Catena-X and its licensors."}),"\n",(0,r.jsx)(t.p,{children:"The contents of this document shall not be copied, modified, distributed, displayed, made publicly\navailable or otherwise be publicly communicated, in whole or in part, for any purposes, without the\nprior authorization by Catena-X, and nothing herein confers any right or license to do so."}),"\n",(0,r.jsx)(t.p,{children:"The present document may include trademarks or trade names which are registered by their owners. Catena-X\nclaims no ownership of these except for any which are indicated as being the property of Catena-X, and\nconveys no right to use or reproduce any such trademark or trade name contained herein. Mention of any\nthird-party trademarks in the present document does not constitute an endorsement by Catena-X of products,\nservices or organizations associated with those trademarks."}),"\n",(0,r.jsx)(t.p,{children:"\u201cCATENA-X\u201d is a trademark owned by Catena-X registered for its benefit and the benefit of its members.\nUsing or reproducing this trademark or the trade name of Catena-X is expressly prohibited.\nNo express or implied license to any intellectual property rights in the present document or parts\nthereof, or relating to the use of its contents, or mentioned in the present document is granted herein.\nThe copyright and the foregoing restrictions extend to reproduction in all media.\n\xa9 Catena-X Automotive Network e.V. All rights reserved."})]})}function p(e={}){const{wrapper:t}={...(0,o.R)(),...e.components};return t?(0,r.jsx)(t,{...e,children:(0,r.jsx)(h,{...e})}):h(e)}},8453:(e,t,n)=>{n.d(t,{R:()=>a,x:()=>s});var r=n(6540);const o={},i=r.createContext(o);function a(e){const t=r.useContext(i);return r.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function s(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(o):e.components||o:a(e.components),r.createElement(i.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/726bd3c0.683c1427.js b/assets/js/726bd3c0.683c1427.js deleted file mode 100644 index 5284c90c..00000000 --- a/assets/js/726bd3c0.683c1427.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8254],{7718:(e,t,i)=>{i.r(t),i.d(t,{assets:()=>l,contentTitle:()=>s,default:()=>h,frontMatter:()=>o,metadata:()=>r,toc:()=>c});var n=i(4848),a=i(8453);const o={sidebar_position:1},s="Outlook",r={id:"operating-model/outlook/outlook",title:"Outlook",description:"The Catena-X Operating Model is a normative document within the regulatory framework, which is binding for all participants in the Catena-X data space. It describes the status of our data space artifacts, including roles, services, and processes along with their respective roadmaps. As Catena-X is an ongoing journey, all of these artifacts will continuously evolve to promote broader adoption and scalability, ensuring maximum interoperability, and (data) sovereignty.",source:"@site/docs/operating-model/outlook/outlook.md",sourceDirName:"operating-model/outlook",slug:"/operating-model/outlook/",permalink:"/docs/next/operating-model/outlook/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"How: Life Cycle Management",permalink:"/docs/next/operating-model/how-life-cycle-management/"},next:{title:"Glossary",permalink:"/docs/next/operating-model/glossary/"}},l={},c=[{value:"Industry Core",id:"industry-core",level:2},{value:"Increase Decentralization of Core Services",id:"increase-decentralization-of-core-services",level:2},{value:"Release v23.09",id:"release-v2309",level:3},{value:"Release v23.12 (planned)",id:"release-v2312-planned",level:3},{value:"Releases 2024 (planned)",id:"releases-2024-planned",level:3},{value:"Further Integration of SSI Technologies",id:"further-integration-of-ssi-technologies",level:2},{value:"Data Space Interoperability",id:"data-space-interoperability",level:2},{value:"Backward Compatibility",id:"backward-compatibility",level:2},{value:"Sanctions",id:"sanctions",level:2}];function d(e){const t={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",img:"img",li:"li",p:"p",strong:"strong",ul:"ul",...(0,a.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(t.h1,{id:"outlook",children:"Outlook"}),"\n",(0,n.jsx)(t.p,{children:"The Catena-X Operating Model is a normative document within the regulatory framework, which is binding for all participants in the Catena-X data space. It describes the status of our data space artifacts, including roles, services, and processes along with their respective roadmaps. As Catena-X is an ongoing journey, all of these artifacts will continuously evolve to promote broader adoption and scalability, ensuring maximum interoperability, and (data) sovereignty."}),"\n",(0,n.jsx)(t.h2,{id:"industry-core",children:"Industry Core"}),"\n",(0,n.jsx)(t.p,{children:"The Industry Core aims to reduce the complexity of multi-tier connections within the decentralized Catena-X data space and to act as an enabler for data-driven use cases like tracking a product carbon footprint (PCF) value or circular economy. Reusing common components and standards (especially data provisioning of digital twins of parts) across different use cases promotes efficiency and interoperability. To enable onboarding for corporations that have different legal entities, concepts for a corporate BPNL are also created. This enables a simple participation via a company-group-wide BPNL. The industry core fosters the realization of seamless data chains, with one use case benefiting from another. As a result, cross-domain network effects and n-tier use cases become possible."}),"\n",(0,n.jsx)(t.h2,{id:"increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),"\n",(0,n.jsxs)(t.p,{children:["Catena-X follows a business-oriented decentralization approach that aims to achieve interoperability and data sovereignty while balancing manageability of complexity, and technical maturity. Therefore, Core Services B will gradually transition into onboarding services or Core Services A, if appropriate. Please find below the timeline for the upcoming decentralization of Core Services B (see Figure ",(0,n.jsx)(t.a,{href:"/docs/next/operating-model/outlook/#increase-decentralization-of-core-services",children:"Timeline for further Decentralization"}),")."]}),"\n",(0,n.jsxs)(t.p,{children:[(0,n.jsx)(t.img,{alt:"Timeline for further Decentralization",src:i(4749).A+"",width:"991",height:"731"}),"\n",(0,n.jsx)(t.em,{children:"Timeline for further Decentralization"})]}),"\n",(0,n.jsx)(t.h3,{id:"release-v2309",children:"Release v23.09"}),"\n",(0,n.jsx)(t.p,{children:"Due to organizational and technical limitations, the services associated with the CSP-A and OSP roles can only be operated once and must therefore temporarily be offered by the nominated CSP-B."}),"\n",(0,n.jsx)(t.h3,{id:"release-v2312-planned",children:"Release v23.12 (planned)"}),"\n",(0,n.jsx)(t.p,{children:"With the introduction of new identity synchronization functions, multiple CSP-A and OSP can operate the corresponding services and collaborate. In addition, there will be new CSP-B services such as the Policy and Credential Hub."}),"\n",(0,n.jsx)(t.h3,{id:"releases-2024-planned",children:"Releases 2024 (planned)"}),"\n",(0,n.jsx)(t.p,{children:"With an increasing decentralization of services, Core Services B are shifted step by step to Core Services A and the decentralized portfolio of Onboarding Service Provider likewise increases. For future releases, committees, expert, and working groups will be coordinated to develop a detailed decentralization roadmap under the supervision of the Catena-X Association."}),"\n",(0,n.jsx)(t.h2,{id:"further-integration-of-ssi-technologies",children:"Further Integration of SSI Technologies"}),"\n",(0,n.jsxs)(t.p,{children:["To realize the Catena-X vision of a decentralized data space, we will further develop our SSI technologies. Future releases will enable the use of both managed identity wallets and self-provisioned identity wallets. To enable the technical enforcement of policies, it is planned to introduce a policy hub and policy code templates to also provide the information transparently to the participants. This also includes the decentralization of the issuer service and logging functionality for agreements. To further strengthen trust in the data space, we will introduce the option to define various root trust anchors (e.g., the Catena-X Association). This will also allow the identity wallet to be decentralized and allow multiple issuers. In addition, a chain of trust will be established to prove that a given credential comes from a trusted source according to the Catena-X Governance Framework. The concept is still under development and will be released in one of the next versions (by May 2024). While developing this concept, the concepts of the Policy Hub and the Certifications Hub will also be concretized. An illustration of this can be found in Chapter ",(0,n.jsx)(t.a,{href:"/docs/next/operating-model/appendix/#data-exchange-based-on-ssi---next-steps",children:"Data Exchange based on SSI - Next Steps"}),"."]}),"\n",(0,n.jsx)(t.h2,{id:"data-space-interoperability",children:"Data Space Interoperability"}),"\n",(0,n.jsx)(t.p,{children:"The Catena-X Association is committed to promote and engage in various initiatives that focus on creating common guidelines and standards to ensure interoperability with other data space initiatives. Initiatives such as the Data Space Support Centre (DSSC) and Manufacturing-X will help establish an interoperable data space across different industry sectors. Furthermore, the Catena-X Association will drive technical initiatives, such as the Eclipse Tractus-X project and the Eclipse Dataspace Working Group (EDWG), which aim to align a common technical foundation, certification procedures and test/ security requirements."}),"\n",(0,n.jsx)(t.h2,{id:"backward-compatibility",children:"Backward Compatibility"}),"\n",(0,n.jsxs)(t.p,{children:["The vision of the Catena-X data space is to provide seamless data access and creation of data chains across multi-tier value chains. Initially, the data space can be operated and evolved by deployment of dedicated, synchronized releases (see Chapter ",(0,n.jsx)(t.a,{href:"/docs/next/operating-model/how-data-space-governance/",children:"How: Data Space Governance"}),"). While initially, dedicated, synchronized releases (see Chapter ",(0,n.jsx)(t.a,{href:"/docs/next/operating-model/how-data-space-governance/",children:"How: Data Space Governance"}),") may suffice, our goal of involving thousands of partners makes it impossible to maintain the same technical components across the board. To overcome this challenge, we must ensure that the release and upgrade of dedicated components can be executed independently, without causing disruptions in the network connectivity and data chains."]}),"\n",(0,n.jsx)(t.p,{children:"To achieve this in areas such as APIs, semantic models, and procedural specifications, the Catena-X Association promotes and supports adherence to the following principles:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Continuous revising of standards"})," to ensure compatibility between different versions and releases."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Developing technical specifications"})," and ",(0,n.jsx)(t.strong,{children:"reference implementations"})," in Eclipse Tractus-X that follow the required standards to lay the technical foundation."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Coordinating"})," closely with different ",(0,n.jsx)(t.strong,{children:"operators"})," to execute rollout and implementation of the different versions and releases."]}),"\n"]}),"\n",(0,n.jsx)(t.h2,{id:"sanctions",children:"Sanctions"}),"\n",(0,n.jsx)(t.p,{children:"Following its GoLive, the Catena-X data space will grow in participants and complexity. Consequently, ensuring compliance of all participants with established rules, regulations, and standards becomes increasingly relevant."}),"\n",(0,n.jsx)(t.p,{children:"Moving forward, concepts of imposing restrictions or penalties on individuals, organizations, or entities that engage in actions or behaviors that are deemed harmful, illegal, or unethical within the context of data management, privacy, and security will be evaluated and developed. These sanctions will aim to deter, correct, or punish noncompliant behavior, thereby safeguarding data integrity, protecting individual rights, and maintaining the trust and credibility of the data ecosystem."})]})}function h(e={}){const{wrapper:t}={...(0,a.R)(),...e.components};return t?(0,n.jsx)(t,{...e,children:(0,n.jsx)(d,{...e})}):d(e)}},4749:(e,t,i)=>{i.d(t,{A:()=>n});const n=i.p+"assets/images/timeline-for-further-decentralization-1eff7b5a80c5ea1f5d6a99c537793c48.png"},8453:(e,t,i)=>{i.d(t,{R:()=>s,x:()=>r});var n=i(6540);const a={},o=n.createContext(a);function s(e){const t=n.useContext(o);return n.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function r(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(a):e.components||a:s(e.components),n.createElement(o.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/726bd3c0.a48ff20e.js b/assets/js/726bd3c0.a48ff20e.js new file mode 100644 index 00000000..c0968a28 --- /dev/null +++ b/assets/js/726bd3c0.a48ff20e.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8254],{7718:(e,t,i)=>{i.r(t),i.d(t,{assets:()=>l,contentTitle:()=>s,default:()=>h,frontMatter:()=>o,metadata:()=>r,toc:()=>c});var n=i(4848),a=i(8453);const o={sidebar_position:1},s="Outlook",r={id:"operating-model/outlook/outlook",title:"Outlook",description:"The Catena-X Operating Model is a normative document within the regulatory framework, which is binding for all participants in the Catena-X data space. It describes the status of our data space artifacts, including roles, services, and processes along with their respective roadmaps. As Catena-X is an ongoing journey, all of these artifacts will continuously evolve to promote broader adoption and scalability, ensuring maximum interoperability, and (data) sovereignty.",source:"@site/docs/operating-model/outlook/outlook.md",sourceDirName:"operating-model/outlook",slug:"/operating-model/outlook/",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/outlook/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"How: Life Cycle Management",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/how-life-cycle-management/"},next:{title:"Glossary",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/glossary/"}},l={},c=[{value:"Industry Core",id:"industry-core",level:2},{value:"Increase Decentralization of Core Services",id:"increase-decentralization-of-core-services",level:2},{value:"Release v23.09",id:"release-v2309",level:3},{value:"Release v23.12 (planned)",id:"release-v2312-planned",level:3},{value:"Releases 2024 (planned)",id:"releases-2024-planned",level:3},{value:"Further Integration of SSI Technologies",id:"further-integration-of-ssi-technologies",level:2},{value:"Data Space Interoperability",id:"data-space-interoperability",level:2},{value:"Backward Compatibility",id:"backward-compatibility",level:2},{value:"Sanctions",id:"sanctions",level:2}];function d(e){const t={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",img:"img",li:"li",p:"p",strong:"strong",ul:"ul",...(0,a.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(t.h1,{id:"outlook",children:"Outlook"}),"\n",(0,n.jsx)(t.p,{children:"The Catena-X Operating Model is a normative document within the regulatory framework, which is binding for all participants in the Catena-X data space. It describes the status of our data space artifacts, including roles, services, and processes along with their respective roadmaps. As Catena-X is an ongoing journey, all of these artifacts will continuously evolve to promote broader adoption and scalability, ensuring maximum interoperability, and (data) sovereignty."}),"\n",(0,n.jsx)(t.h2,{id:"industry-core",children:"Industry Core"}),"\n",(0,n.jsx)(t.p,{children:"The Industry Core aims to reduce the complexity of multi-tier connections within the decentralized Catena-X data space and to act as an enabler for data-driven use cases like tracking a product carbon footprint (PCF) value or circular economy. Reusing common components and standards (especially data provisioning of digital twins of parts) across different use cases promotes efficiency and interoperability. To enable onboarding for corporations that have different legal entities, concepts for a corporate BPNL are also created. This enables a simple participation via a company-group-wide BPNL. The industry core fosters the realization of seamless data chains, with one use case benefiting from another. As a result, cross-domain network effects and n-tier use cases become possible."}),"\n",(0,n.jsx)(t.h2,{id:"increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),"\n",(0,n.jsxs)(t.p,{children:["Catena-X follows a business-oriented decentralization approach that aims to achieve interoperability and data sovereignty while balancing manageability of complexity, and technical maturity. Therefore, Core Services B will gradually transition into onboarding services or Core Services A, if appropriate. Please find below the timeline for the upcoming decentralization of Core Services B (see Figure ",(0,n.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/outlook/#increase-decentralization-of-core-services",children:"Timeline for further Decentralization"}),")."]}),"\n",(0,n.jsxs)(t.p,{children:[(0,n.jsx)(t.img,{alt:"Timeline for further Decentralization",src:i(4749).A+"",width:"991",height:"731"}),"\n",(0,n.jsx)(t.em,{children:"Timeline for further Decentralization"})]}),"\n",(0,n.jsx)(t.h3,{id:"release-v2309",children:"Release v23.09"}),"\n",(0,n.jsx)(t.p,{children:"Due to organizational and technical limitations, the services associated with the CSP-A and OSP roles can only be operated once and must therefore temporarily be offered by the nominated CSP-B."}),"\n",(0,n.jsx)(t.h3,{id:"release-v2312-planned",children:"Release v23.12 (planned)"}),"\n",(0,n.jsx)(t.p,{children:"With the introduction of new identity synchronization functions, multiple CSP-A and OSP can operate the corresponding services and collaborate. In addition, there will be new CSP-B services such as the Policy and Credential Hub."}),"\n",(0,n.jsx)(t.h3,{id:"releases-2024-planned",children:"Releases 2024 (planned)"}),"\n",(0,n.jsx)(t.p,{children:"With an increasing decentralization of services, Core Services B are shifted step by step to Core Services A and the decentralized portfolio of Onboarding Service Provider likewise increases. For future releases, committees, expert, and working groups will be coordinated to develop a detailed decentralization roadmap under the supervision of the Catena-X Association."}),"\n",(0,n.jsx)(t.h2,{id:"further-integration-of-ssi-technologies",children:"Further Integration of SSI Technologies"}),"\n",(0,n.jsxs)(t.p,{children:["To realize the Catena-X vision of a decentralized data space, we will further develop our SSI technologies. Future releases will enable the use of both managed identity wallets and self-provisioned identity wallets. To enable the technical enforcement of policies, it is planned to introduce a policy hub and policy code templates to also provide the information transparently to the participants. This also includes the decentralization of the issuer service and logging functionality for agreements. To further strengthen trust in the data space, we will introduce the option to define various root trust anchors (e.g., the Catena-X Association). This will also allow the identity wallet to be decentralized and allow multiple issuers. In addition, a chain of trust will be established to prove that a given credential comes from a trusted source according to the Catena-X Governance Framework. The concept is still under development and will be released in one of the next versions (by May 2024). While developing this concept, the concepts of the Policy Hub and the Certifications Hub will also be concretized. An illustration of this can be found in Chapter ",(0,n.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/appendix/#data-exchange-based-on-ssi---next-steps",children:"Data Exchange based on SSI - Next Steps"}),"."]}),"\n",(0,n.jsx)(t.h2,{id:"data-space-interoperability",children:"Data Space Interoperability"}),"\n",(0,n.jsx)(t.p,{children:"The Catena-X Association is committed to promote and engage in various initiatives that focus on creating common guidelines and standards to ensure interoperability with other data space initiatives. Initiatives such as the Data Space Support Centre (DSSC) and Manufacturing-X will help establish an interoperable data space across different industry sectors. Furthermore, the Catena-X Association will drive technical initiatives, such as the Eclipse Tractus-X project and the Eclipse Dataspace Working Group (EDWG), which aim to align a common technical foundation, certification procedures and test/ security requirements."}),"\n",(0,n.jsx)(t.h2,{id:"backward-compatibility",children:"Backward Compatibility"}),"\n",(0,n.jsxs)(t.p,{children:["The vision of the Catena-X data space is to provide seamless data access and creation of data chains across multi-tier value chains. Initially, the data space can be operated and evolved by deployment of dedicated, synchronized releases (see Chapter ",(0,n.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance/",children:"How: Data Space Governance"}),"). While initially, dedicated, synchronized releases (see Chapter ",(0,n.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance/",children:"How: Data Space Governance"}),") may suffice, our goal of involving thousands of partners makes it impossible to maintain the same technical components across the board. To overcome this challenge, we must ensure that the release and upgrade of dedicated components can be executed independently, without causing disruptions in the network connectivity and data chains."]}),"\n",(0,n.jsx)(t.p,{children:"To achieve this in areas such as APIs, semantic models, and procedural specifications, the Catena-X Association promotes and supports adherence to the following principles:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Continuous revising of standards"})," to ensure compatibility between different versions and releases."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Developing technical specifications"})," and ",(0,n.jsx)(t.strong,{children:"reference implementations"})," in Eclipse Tractus-X that follow the required standards to lay the technical foundation."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Coordinating"})," closely with different ",(0,n.jsx)(t.strong,{children:"operators"})," to execute rollout and implementation of the different versions and releases."]}),"\n"]}),"\n",(0,n.jsx)(t.h2,{id:"sanctions",children:"Sanctions"}),"\n",(0,n.jsx)(t.p,{children:"Following its GoLive, the Catena-X data space will grow in participants and complexity. Consequently, ensuring compliance of all participants with established rules, regulations, and standards becomes increasingly relevant."}),"\n",(0,n.jsx)(t.p,{children:"Moving forward, concepts of imposing restrictions or penalties on individuals, organizations, or entities that engage in actions or behaviors that are deemed harmful, illegal, or unethical within the context of data management, privacy, and security will be evaluated and developed. These sanctions will aim to deter, correct, or punish noncompliant behavior, thereby safeguarding data integrity, protecting individual rights, and maintaining the trust and credibility of the data ecosystem."})]})}function h(e={}){const{wrapper:t}={...(0,a.R)(),...e.components};return t?(0,n.jsx)(t,{...e,children:(0,n.jsx)(d,{...e})}):d(e)}},4749:(e,t,i)=>{i.d(t,{A:()=>n});const n=i.p+"assets/images/timeline-for-further-decentralization-1eff7b5a80c5ea1f5d6a99c537793c48.png"},8453:(e,t,i)=>{i.d(t,{R:()=>s,x:()=>r});var n=i(6540);const a={},o=n.createContext(a);function s(e){const t=n.useContext(o);return n.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function r(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(a):e.components||a:s(e.components),n.createElement(o.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/73664a40.250d7ffe.js b/assets/js/73664a40.250d7ffe.js deleted file mode 100644 index 40bb2753..00000000 --- a/assets/js/73664a40.250d7ffe.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[1972],{9581:(e,s,i)=>{i.r(s),i.d(s,{assets:()=>m,contentTitle:()=>u,default:()=>a,frontMatter:()=>n,metadata:()=>r,toc:()=>l});var t=i(4848),o=i(8453);const n={slug:"long-blog-post",title:"Long Blog Post",authors:"endi",tags:["hello","docusaurus"]},u=void 0,r={permalink:"/blog/long-blog-post",source:"@site/blog/2019-05-29-long-blog-post.md",title:"Long Blog Post",description:"This is the summary of a very long blog post,",date:"2019-05-29T00:00:00.000Z",tags:[{inline:!1,label:"Hello",permalink:"/blog/tags/hello",description:"Hello tag description"},{inline:!1,label:"Docusaurus",permalink:"/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:2.05,hasTruncateMarker:!0,authors:[{name:"Endilie Yacop Sucipto",title:"Maintainer of Docusaurus",url:"https://github.com/endiliey",imageURL:"https://github.com/endiliey.png",key:"endi"}],frontMatter:{slug:"long-blog-post",title:"Long Blog Post",authors:"endi",tags:["hello","docusaurus"]},unlisted:!1,prevItem:{title:"MDX Blog Post",permalink:"/blog/mdx-blog-post"},nextItem:{title:"First Blog Post",permalink:"/blog/first-blog-post"}},m={authorsImageUrls:[void 0]},l=[];function c(e){const s={code:"code",p:"p",...(0,o.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(s.p,{children:"This is the summary of a very long blog post,"}),"\n",(0,t.jsxs)(s.p,{children:["Use a ",(0,t.jsx)(s.code,{children:"\x3c!--"})," ",(0,t.jsx)(s.code,{children:"truncate"})," ",(0,t.jsx)(s.code,{children:"--\x3e"})," comment to limit blog post size in the list view."]}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"})]})}function a(e={}){const{wrapper:s}={...(0,o.R)(),...e.components};return s?(0,t.jsx)(s,{...e,children:(0,t.jsx)(c,{...e})}):c(e)}},8453:(e,s,i)=>{i.d(s,{R:()=>u,x:()=>r});var t=i(6540);const o={},n=t.createContext(o);function u(e){const s=t.useContext(n);return t.useMemo((function(){return"function"==typeof e?e(s):{...s,...e}}),[s,e])}function r(e){let s;return s=e.disableParentContext?"function"==typeof e.components?e.components(o):e.components||o:u(e.components),t.createElement(n.Provider,{value:s},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/73664a40.e30c8f5d.js b/assets/js/73664a40.e30c8f5d.js new file mode 100644 index 00000000..c50569c6 --- /dev/null +++ b/assets/js/73664a40.e30c8f5d.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[1972],{9581:(e,s,i)=>{i.r(s),i.d(s,{assets:()=>m,contentTitle:()=>u,default:()=>a,frontMatter:()=>n,metadata:()=>r,toc:()=>l});var t=i(4848),o=i(8453);const n={slug:"long-blog-post",title:"Long Blog Post",authors:"endi",tags:["hello","docusaurus"]},u=void 0,r={permalink:"/catenax-ev.github.io.new/blog/long-blog-post",source:"@site/blog/2019-05-29-long-blog-post.md",title:"Long Blog Post",description:"This is the summary of a very long blog post,",date:"2019-05-29T00:00:00.000Z",tags:[{inline:!1,label:"Hello",permalink:"/catenax-ev.github.io.new/blog/tags/hello",description:"Hello tag description"},{inline:!1,label:"Docusaurus",permalink:"/catenax-ev.github.io.new/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:2.05,hasTruncateMarker:!0,authors:[{name:"Endilie Yacop Sucipto",title:"Maintainer of Docusaurus",url:"https://github.com/endiliey",imageURL:"https://github.com/endiliey.png",key:"endi"}],frontMatter:{slug:"long-blog-post",title:"Long Blog Post",authors:"endi",tags:["hello","docusaurus"]},unlisted:!1,prevItem:{title:"MDX Blog Post",permalink:"/catenax-ev.github.io.new/blog/mdx-blog-post"},nextItem:{title:"First Blog Post",permalink:"/catenax-ev.github.io.new/blog/first-blog-post"}},m={authorsImageUrls:[void 0]},l=[];function c(e){const s={code:"code",p:"p",...(0,o.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(s.p,{children:"This is the summary of a very long blog post,"}),"\n",(0,t.jsxs)(s.p,{children:["Use a ",(0,t.jsx)(s.code,{children:"\x3c!--"})," ",(0,t.jsx)(s.code,{children:"truncate"})," ",(0,t.jsx)(s.code,{children:"--\x3e"})," comment to limit blog post size in the list view."]}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}),"\n",(0,t.jsx)(s.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"})]})}function a(e={}){const{wrapper:s}={...(0,o.R)(),...e.components};return s?(0,t.jsx)(s,{...e,children:(0,t.jsx)(c,{...e})}):c(e)}},8453:(e,s,i)=>{i.d(s,{R:()=>u,x:()=>r});var t=i(6540);const o={},n=t.createContext(o);function u(e){const s=t.useContext(n);return t.useMemo((function(){return"function"==typeof e?e(s):{...s,...e}}),[s,e])}function r(e){let s;return s=e.disableParentContext?"function"==typeof e.components?e.components(o):e.components||o:u(e.components),t.createElement(n.Provider,{value:s},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/7661071f.7786def8.js b/assets/js/7661071f.7786def8.js deleted file mode 100644 index e74a722a..00000000 --- a/assets/js/7661071f.7786def8.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8737],{4137:(e,o,n)=>{n.r(o),n.d(o,{assets:()=>i,contentTitle:()=>l,default:()=>d,frontMatter:()=>r,metadata:()=>a,toc:()=>c});var s=n(4848),t=n(8453);const r={slug:"welcome",title:"Welcome",authors:["slorber","yangshun"],tags:["facebook","hello","docusaurus"]},l=void 0,a={permalink:"/blog/welcome",source:"@site/blog/2021-08-26-welcome/index.md",title:"Welcome",description:"Docusaurus blogging features are powered by the blog plugin.",date:"2021-08-26T00:00:00.000Z",tags:[{inline:!1,label:"Facebook",permalink:"/blog/tags/facebook",description:"Facebook tag description"},{inline:!1,label:"Hello",permalink:"/blog/tags/hello",description:"Hello tag description"},{inline:!1,label:"Docusaurus",permalink:"/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:.405,hasTruncateMarker:!1,authors:[{name:"S\xe9bastien Lorber",title:"Docusaurus maintainer",url:"https://sebastienlorber.com",imageURL:"https://github.com/slorber.png",key:"slorber"},{name:"Yangshun Tay",title:"Front End Engineer @ Facebook",url:"https://github.com/yangshun",imageURL:"https://github.com/yangshun.png",key:"yangshun"}],frontMatter:{slug:"welcome",title:"Welcome",authors:["slorber","yangshun"],tags:["facebook","hello","docusaurus"]},unlisted:!1,nextItem:{title:"MDX Blog Post",permalink:"/blog/mdx-blog-post"}},i={authorsImageUrls:[void 0,void 0]},c=[];function u(e){const o={a:"a",code:"code",img:"img",li:"li",p:"p",strong:"strong",ul:"ul",...(0,t.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsxs)(o.p,{children:[(0,s.jsx)(o.a,{href:"https://docusaurus.io/docs/blog",children:"Docusaurus blogging features"})," are powered by the ",(0,s.jsx)(o.a,{href:"https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog",children:"blog plugin"}),"."]}),"\n",(0,s.jsxs)(o.p,{children:["Simply add Markdown files (or folders) to the ",(0,s.jsx)(o.code,{children:"blog"})," directory."]}),"\n",(0,s.jsxs)(o.p,{children:["Regular blog authors can be added to ",(0,s.jsx)(o.code,{children:"authors.yml"}),"."]}),"\n",(0,s.jsx)(o.p,{children:"The blog post date can be extracted from filenames, such as:"}),"\n",(0,s.jsxs)(o.ul,{children:["\n",(0,s.jsx)(o.li,{children:(0,s.jsx)(o.code,{children:"2019-05-30-welcome.md"})}),"\n",(0,s.jsx)(o.li,{children:(0,s.jsx)(o.code,{children:"2019-05-30-welcome/index.md"})}),"\n"]}),"\n",(0,s.jsx)(o.p,{children:"A blog post folder can be convenient to co-locate blog post images:"}),"\n",(0,s.jsx)(o.p,{children:(0,s.jsx)(o.img,{alt:"Docusaurus Plushie",src:n(9465).A+"",width:"1500",height:"500"})}),"\n",(0,s.jsx)(o.p,{children:"The blog supports tags as well!"}),"\n",(0,s.jsxs)(o.p,{children:[(0,s.jsx)(o.strong,{children:"And if you don't want a blog"}),": just delete this directory, and use ",(0,s.jsx)(o.code,{children:"blog: false"})," in your Docusaurus config."]})]})}function d(e={}){const{wrapper:o}={...(0,t.R)(),...e.components};return o?(0,s.jsx)(o,{...e,children:(0,s.jsx)(u,{...e})}):u(e)}},9465:(e,o,n)=>{n.d(o,{A:()=>s});const s=n.p+"assets/images/docusaurus-plushie-banner-a60f7593abca1e3eef26a9afa244e4fb.jpeg"},8453:(e,o,n)=>{n.d(o,{R:()=>l,x:()=>a});var s=n(6540);const t={},r=s.createContext(t);function l(e){const o=s.useContext(r);return s.useMemo((function(){return"function"==typeof e?e(o):{...o,...e}}),[o,e])}function a(e){let o;return o=e.disableParentContext?"function"==typeof e.components?e.components(t):e.components||t:l(e.components),s.createElement(r.Provider,{value:o},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/7661071f.fee017db.js b/assets/js/7661071f.fee017db.js new file mode 100644 index 00000000..354b7dfc --- /dev/null +++ b/assets/js/7661071f.fee017db.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8737],{4137:(e,o,n)=>{n.r(o),n.d(o,{assets:()=>l,contentTitle:()=>i,default:()=>d,frontMatter:()=>a,metadata:()=>r,toc:()=>c});var t=n(4848),s=n(8453);const a={slug:"welcome",title:"Welcome",authors:["slorber","yangshun"],tags:["facebook","hello","docusaurus"]},i=void 0,r={permalink:"/catenax-ev.github.io.new/blog/welcome",source:"@site/blog/2021-08-26-welcome/index.md",title:"Welcome",description:"Docusaurus blogging features are powered by the blog plugin.",date:"2021-08-26T00:00:00.000Z",tags:[{inline:!1,label:"Facebook",permalink:"/catenax-ev.github.io.new/blog/tags/facebook",description:"Facebook tag description"},{inline:!1,label:"Hello",permalink:"/catenax-ev.github.io.new/blog/tags/hello",description:"Hello tag description"},{inline:!1,label:"Docusaurus",permalink:"/catenax-ev.github.io.new/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:.405,hasTruncateMarker:!1,authors:[{name:"S\xe9bastien Lorber",title:"Docusaurus maintainer",url:"https://sebastienlorber.com",imageURL:"https://github.com/slorber.png",key:"slorber"},{name:"Yangshun Tay",title:"Front End Engineer @ Facebook",url:"https://github.com/yangshun",imageURL:"https://github.com/yangshun.png",key:"yangshun"}],frontMatter:{slug:"welcome",title:"Welcome",authors:["slorber","yangshun"],tags:["facebook","hello","docusaurus"]},unlisted:!1,nextItem:{title:"MDX Blog Post",permalink:"/catenax-ev.github.io.new/blog/mdx-blog-post"}},l={authorsImageUrls:[void 0,void 0]},c=[];function u(e){const o={a:"a",code:"code",img:"img",li:"li",p:"p",strong:"strong",ul:"ul",...(0,s.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsxs)(o.p,{children:[(0,t.jsx)(o.a,{href:"https://docusaurus.io/docs/blog",children:"Docusaurus blogging features"})," are powered by the ",(0,t.jsx)(o.a,{href:"https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog",children:"blog plugin"}),"."]}),"\n",(0,t.jsxs)(o.p,{children:["Simply add Markdown files (or folders) to the ",(0,t.jsx)(o.code,{children:"blog"})," directory."]}),"\n",(0,t.jsxs)(o.p,{children:["Regular blog authors can be added to ",(0,t.jsx)(o.code,{children:"authors.yml"}),"."]}),"\n",(0,t.jsx)(o.p,{children:"The blog post date can be extracted from filenames, such as:"}),"\n",(0,t.jsxs)(o.ul,{children:["\n",(0,t.jsx)(o.li,{children:(0,t.jsx)(o.code,{children:"2019-05-30-welcome.md"})}),"\n",(0,t.jsx)(o.li,{children:(0,t.jsx)(o.code,{children:"2019-05-30-welcome/index.md"})}),"\n"]}),"\n",(0,t.jsx)(o.p,{children:"A blog post folder can be convenient to co-locate blog post images:"}),"\n",(0,t.jsx)(o.p,{children:(0,t.jsx)(o.img,{alt:"Docusaurus Plushie",src:n(9465).A+"",width:"1500",height:"500"})}),"\n",(0,t.jsx)(o.p,{children:"The blog supports tags as well!"}),"\n",(0,t.jsxs)(o.p,{children:[(0,t.jsx)(o.strong,{children:"And if you don't want a blog"}),": just delete this directory, and use ",(0,t.jsx)(o.code,{children:"blog: false"})," in your Docusaurus config."]})]})}function d(e={}){const{wrapper:o}={...(0,s.R)(),...e.components};return o?(0,t.jsx)(o,{...e,children:(0,t.jsx)(u,{...e})}):u(e)}},9465:(e,o,n)=>{n.d(o,{A:()=>t});const t=n.p+"assets/images/docusaurus-plushie-banner-a60f7593abca1e3eef26a9afa244e4fb.jpeg"},8453:(e,o,n)=>{n.d(o,{R:()=>i,x:()=>r});var t=n(6540);const s={},a=t.createContext(s);function i(e){const o=t.useContext(a);return t.useMemo((function(){return"function"==typeof e?e(o):{...o,...e}}),[o,e])}function r(e){let o;return o=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:i(e.components),t.createElement(a.Provider,{value:o},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/814f3328.03a5e2e9.js b/assets/js/814f3328.03a5e2e9.js new file mode 100644 index 00000000..ed99c855 --- /dev/null +++ b/assets/js/814f3328.03a5e2e9.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[7472],{5513:e=>{e.exports=JSON.parse('{"title":"Recent posts","items":[{"title":"Welcome","permalink":"/catenax-ev.github.io.new/blog/welcome","unlisted":false},{"title":"MDX Blog Post","permalink":"/catenax-ev.github.io.new/blog/mdx-blog-post","unlisted":false},{"title":"Long Blog Post","permalink":"/catenax-ev.github.io.new/blog/long-blog-post","unlisted":false},{"title":"First Blog Post","permalink":"/catenax-ev.github.io.new/blog/first-blog-post","unlisted":false}]}')}}]); \ No newline at end of file diff --git a/assets/js/814f3328.ba556011.js b/assets/js/814f3328.ba556011.js deleted file mode 100644 index 2790a12a..00000000 --- a/assets/js/814f3328.ba556011.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[7472],{5513:e=>{e.exports=JSON.parse('{"title":"Recent posts","items":[{"title":"Welcome","permalink":"/blog/welcome","unlisted":false},{"title":"MDX Blog Post","permalink":"/blog/mdx-blog-post","unlisted":false},{"title":"Long Blog Post","permalink":"/blog/long-blog-post","unlisted":false},{"title":"First Blog Post","permalink":"/blog/first-blog-post","unlisted":false}]}')}}]); \ No newline at end of file diff --git a/assets/js/8389dc22.0d95d5f5.js b/assets/js/8389dc22.0d95d5f5.js new file mode 100644 index 00000000..971aa50a --- /dev/null +++ b/assets/js/8389dc22.0d95d5f5.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[94],{5206:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>c,contentTitle:()=>o,default:()=>h,frontMatter:()=>s,metadata:()=>r,toc:()=>d});var a=t(4848),i=t(8453);const s={sidebar_position:1},o="How: Data Space Operations",r={id:"operating-model/how-data-space-operations/how-data-space-operations",title:"How: Data Space Operations",description:"This chapter outlines the overarching processes and premises to onboard and exchange",source:"@site/docs/operating-model/how-data-space-operations/how-data-space-operations.md",sourceDirName:"operating-model/how-data-space-operations",slug:"/operating-model/how-data-space-operations/",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-operations/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"What: Service Map",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/what-service-map/"},next:{title:"How: Data Space Governance",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance/"}},c={},d=[{value:"General Onboarding",id:"general-onboarding",level:2},{value:"Gaia-X Compliance",id:"gaia-x-compliance",level:2},{value:"SSI Issuer Concept",id:"ssi-issuer-concept",level:2},{value:"Data Exchange based on SSI",id:"data-exchange-based-on-ssi",level:2},{value:"EDC Deployment and Usage Premises",id:"edc-deployment-and-usage-premises",level:2}];function l(e){const n={a:"a",em:"em",h1:"h1",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",ul:"ul",...(0,i.R)(),...e.components};return(0,a.jsxs)(a.Fragment,{children:[(0,a.jsx)(n.h1,{id:"how-data-space-operations",children:"How: Data Space Operations"}),"\n",(0,a.jsx)(n.p,{children:"This chapter outlines the overarching processes and premises to onboard and exchange\ndata in the Catena-X data space. This includes the general onboarding process that all\nparticipants must complete to join the Catena-X data space. It involves registration and\ntechnical integration, as well as compliance with the regulatory framework and verification\nthrough the Gaia-X Digital Clearing House. The introduction of Self Sovereign Identities (SSI)\nin Tractus-X Release 23.09 updates the process for offering, exchanging, and using data,\nwhile the chapter also covers EDC deployment and usage premises and available support\noptions for participants."}),"\n",(0,a.jsx)(n.h2,{id:"general-onboarding",children:"General Onboarding"}),"\n",(0,a.jsxs)(n.p,{children:["To participate in the data space, all participants must complete the general registration process, which involves registration and can be extended by the technical integration (see Figure ",(0,a.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-operations/#general-onboarding",children:"General Onboarding Process"}),")."]}),"\n",(0,a.jsxs)(n.p,{children:[(0,a.jsx)(n.img,{alt:"General Onboarding Process",src:t(4478).A+"",width:"1465",height:"692"}),"\n",(0,a.jsx)(n.em,{children:"General Onboarding Process"})]}),"\n",(0,a.jsxs)(n.p,{children:["During ",(0,a.jsx)(n.strong,{children:"registration"}),", all participants must fill out their company data, select their data space role, and agree to the regulatory framework via one of the OSPs (see Chapter ",(0,a.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/#onboarding-service-provider",children:"Onboarding Service Provider"}),"). A BPNL (if not yet existing) as well as a Managed Wallet Tenant with BPNL Credential and CX membership Credential are created as part of the registration approval process, which is owned/managed by the operation company. Each participant can collect their identity proofs, certificates and other verifiable information, rights, or services in its identity wallet."]}),"\n",(0,a.jsxs)(n.p,{children:["During ",(0,a.jsx)(n.strong,{children:"technical integration"}),", the technical user creation and registration of the connectors are essential to enable the company communication with the data space. The technical user enables the customer company to connect the connector with the wallet and the connector registration is needed to ensure that the connector can get found by other data space members."]}),"\n",(0,a.jsxs)(n.p,{children:["The self-descriptions of newly registered legal entities and connectors are validated by the GXDCH (see Chapter ",(0,a.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-operations/#gaia-x-compliance",children:"Gaia-X Compliance"}),"). This involves signing and issuing credentials to the identity wallet of a DPC, providing proof of Gaia-X compliance and legal entity notarization. Detailed information about the Standard CX-0006 in the ",(0,a.jsx)(n.a,{href:"https://catena-x.net/de/standard-library",children:"Standard Library"})," of the Catena-X Association."]}),"\n",(0,a.jsx)(n.h2,{id:"gaia-x-compliance",children:"Gaia-X Compliance"}),"\n",(0,a.jsx)(n.p,{children:"The Gaia-X Digital Clearing House (GXDCH) is an external service that maximizes trust within the Catena-X data space and interoperability with other data space initiatives based on the Gaia-X Trust Framework. The GXDCH enables the validation of legal entities, ensures Gaia-X compliance, and creates an eIDAS conform digital signature (SelfDescription) 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, every OSP must connect to the GXDCH. OSP candidates can request more information during conformity assessment."}),"\n",(0,a.jsx)(n.h2,{id:"ssi-issuer-concept",children:"SSI Issuer Concept"}),"\n",(0,a.jsxs)(n.p,{children:["The Tractus-X Release 23.09 initiates the introduction of Self Sovereign Identities (SSI), replacing the Dynamic Attribute Provisioning Service (DAPS). The current release and version of SSI allows only one issuer and one centrally managed identity wallet operated by the CSP-B (see Chapter ",(0,a.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/what-service-map/",children:"What: Service Map"}),"). This also includes the revocation of issued certificates. This is done in cooperation with the Catena-X Association e.g., in case of conscious violation of legal and technical framework. With the 23.09. Release the CSP-B is the single issuer authority of Catena-X credentials. Multi-issuer concept is planned in the following releases. The BPNL can be found on the Catena-X Association website and the portal of the CSP-B. This concept will evolve in future releases, the details of which can be found in Chapter ",(0,a.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/outlook/#further-integration-of-ssi-technologies",children:"Further Integration of SSI Technologies"}),"."]}),"\n",(0,a.jsx)(n.h2,{id:"data-exchange-based-on-ssi",children:"Data Exchange based on SSI"}),"\n",(0,a.jsxs)(n.p,{children:["With the introduction of Self Sovereign Identities (SSI) in the Tractus-X Release 23.09, the processes to participate in a use case as well as offer, exchange, and use data are updated as follows (see Figure ",(0,a.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-operations/#data-exchange-based-on-ssi",children:"Data Exchange Process"}),"):"]}),"\n",(0,a.jsxs)(n.p,{children:[(0,a.jsx)(n.img,{alt:"Data Exchange Process",src:t(2224).A+"",width:"1037",height:"781"}),"\n",(0,a.jsx)(n.em,{children:"Data Exchange Process"})]}),"\n",(0,a.jsxs)(n.ol,{children:["\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Participant signs pre-defined use case framework conditions and requests credential via CSP-B"})}),"\n",(0,a.jsx)(n.p,{children:"The data consumer must sign and upload the respective use case framework conditions to request the use case participation credential."}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Issuer validates request and issues credential"})}),"\n",(0,a.jsx)(n.p,{children:"The request from the participant (e.g., data consumer) is sent to the issuer (operator) for validation (frame version and existing signature) and confirmation, which triggers the creation of the VC."}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Requests credential"})}),"\n",(0,a.jsx)(n.p,{children:"The customer EDC calls the MIW to retrieve the verified summary credentials, requests the signature and retrieves the verified presentation with the summary credential."}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Query catalogue/offers"})}),"\n",(0,a.jsx)(n.p,{children:"With the query of the data provider catalog, the consumer EDC submits the request with the VP in the request header. Upon successful validation, the issuer generates the verified credential using the MIW component and stores it in the wallet tenant of the customer company wallet. is recreated containing both the previous credentials and the newly added credential."}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Submit catalog"})}),"\n",(0,a.jsx)(n.p,{children:"The received offer catalog request and the submitted customer VP are validated by the provider EDC. All data offers where the data access policies set by the provider match the verified credentials owned by the data consumer are sent to the customer. Any data offers that require verified credentials that the data consumer does not have will not be sent/published to the data consumer."}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Manual checking of data offering policies"})}),"\n",(0,a.jsx)(n.p,{children:"Configured data offer policies must be manually checked by the data consumer."}),"\n",(0,a.jsxs)(n.ul,{children:["\n",(0,a.jsx)(n.li,{children:"If a purpose is specified, the purpose must be validated internally by the data consumer. The purpose may refer to an individual contract concluded between the data consumer and the data provider. The data consumer must review the contract and decide whether the policies are acceptable for the specific data offering based on the established policies (see next step 7)."}),"\n",(0,a.jsx)(n.li,{children:"If no purpose is specified, the negotiation can start immediately, as the access and usage policies are automatically technically enforced and validated by the EDCs."}),"\n"]}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Decision on the purpose of the data offer"})}),"\n",(0,a.jsx)(n.p,{children:"Based on step 6 individual data contract validation, the data consumer must decide whether to proceed with the negotiation or whether to disagree with the individual purpose. If there is disagreement, the negotiation should not be started. If there is consent, the data consumer can start the negotiation."}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Contract negotiation"})}),"\n",(0,a.jsx)(n.p,{children:"The data consumer starts the contract negotiation by sending a request for an agreement/contract"}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Contract conclusion/success"})}),"\n",(0,a.jsx)(n.p,{children:"The EDC of the data provider receives the negotiation requests, validates the access and usage policies of the specific data offer requested by the data provider, and matches it with the VP of the data consumer. If the data consumer has all relevant credentials, the agreement is successfully concluded, and an agreement log is stored in both EDCs."}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Data transfer"})}),"\n",(0,a.jsx)(n.p,{children:"Data transmission/access by the data consumer can take place as long as the contract is active."}),"\n"]}),"\n"]}),"\n",(0,a.jsx)(n.h2,{id:"edc-deployment-and-usage-premises",children:"EDC Deployment and Usage Premises"}),"\n",(0,a.jsx)(n.p,{children:"Each data space participant has its own organizational structure, consisting of different legal entities and/or subsidiaries. Depending on the organizational structures, data space participants must consider how to organize the representation of their organization in the Catena-X data space. This includes considerations for setting up connector instances regarding organizational, technical, and legal conditions. The following premises apply:"}),"\n",(0,a.jsxs)(n.ul,{children:["\n",(0,a.jsx)(n.li,{children:"The data exchange always takes place between two legal entities, as only their representatives can sign legally binding contracts."}),"\n",(0,a.jsx)(n.li,{children:"Legal entities must be registered and known in the data space."}),"\n",(0,a.jsx)(n.li,{children:"To represent a legal entity in the data space, an associated business partner number (BPNL) is required."}),"\n",(0,a.jsx)(n.li,{children:"The deployment and use of at least one connector (e.g., EDC) per legal entity for data exchange is mandatory."}),"\n",(0,a.jsx)(n.li,{children:"The connector negotiates data usage between endpoints (data plane) by synchronizing access and usage policies between data providers and data consumers."}),"\n",(0,a.jsx)(n.li,{children:"There is no data processing or reviewing of data within the connector itself."}),"\n",(0,a.jsx)(n.li,{children:"Data usage takes place instead at the endpoints of the data providers or data consumers, respectively."}),"\n",(0,a.jsx)(n.li,{children:"Data usage with respect to location and assignment to computer instances/platforms is independent of the runtime environment of the connector itself."}),"\n"]}),"\n",(0,a.jsxs)(n.p,{children:["There are various options for organizational structures and data exchange scenarios such as \u201cone legal entity and one site in one country\u201d, \u201cone legal entity and multiple sites in one country\u201d or \u201cone legal entity and multiple sites in different countries\u201d. For more details on possible connector usage scenarios, please refer to our ",(0,a.jsx)(n.a,{href:"https://catena-x.net/fileadmin/user_upload/Standard-Bibliothek/Update_PDF_Maerz/6_Onboarding/CX_-_0006_Registration_and_Initial_Onboarding_v_1.1.1.pdf",children:"Initial Onboarding Guide"}),". This includes also the different options to obtain a connector, e.g., it can be acquired via an ESP, it can be self-developed or adapted from open-source, or it can be part of a business application from a BAP. If the data exchange does not take place between several legal entities within Catena-X as defined above, no EDC is required. An example would be the connection of the OSP to the GXDCH. For this connection no connector is needed, because this is not an exchange of data between two legal entities within Catena-X."]})]})}function h(e={}){const{wrapper:n}={...(0,i.R)(),...e.components};return n?(0,a.jsx)(n,{...e,children:(0,a.jsx)(l,{...e})}):l(e)}},2224:(e,n,t)=>{t.d(n,{A:()=>a});const a=t.p+"assets/images/data-exchange-process-2de9e4cb18ad9602cb2ba975287579f6.png"},4478:(e,n,t)=>{t.d(n,{A:()=>a});const a=t.p+"assets/images/general-onboarding-process-756b55f51977bf98f2df2d9957704e90.png"},8453:(e,n,t)=>{t.d(n,{R:()=>o,x:()=>r});var a=t(6540);const i={},s=a.createContext(i);function o(e){const n=a.useContext(s);return a.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function r(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:o(e.components),a.createElement(s.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/8389dc22.eccc2b17.js b/assets/js/8389dc22.eccc2b17.js deleted file mode 100644 index 5b547872..00000000 --- a/assets/js/8389dc22.eccc2b17.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[94],{5206:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>c,contentTitle:()=>o,default:()=>h,frontMatter:()=>s,metadata:()=>r,toc:()=>d});var a=t(4848),i=t(8453);const s={sidebar_position:1},o="How: Data Space Operations",r={id:"operating-model/how-data-space-operations/how-data-space-operations",title:"How: Data Space Operations",description:"This chapter outlines the overarching processes and premises to onboard and exchange",source:"@site/docs/operating-model/how-data-space-operations/how-data-space-operations.md",sourceDirName:"operating-model/how-data-space-operations",slug:"/operating-model/how-data-space-operations/",permalink:"/docs/next/operating-model/how-data-space-operations/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"What: Service Map",permalink:"/docs/next/operating-model/what-service-map/"},next:{title:"How: Data Space Governance",permalink:"/docs/next/operating-model/how-data-space-governance/"}},c={},d=[{value:"General Onboarding",id:"general-onboarding",level:2},{value:"Gaia-X Compliance",id:"gaia-x-compliance",level:2},{value:"SSI Issuer Concept",id:"ssi-issuer-concept",level:2},{value:"Data Exchange based on SSI",id:"data-exchange-based-on-ssi",level:2},{value:"EDC Deployment and Usage Premises",id:"edc-deployment-and-usage-premises",level:2}];function l(e){const n={a:"a",em:"em",h1:"h1",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",ul:"ul",...(0,i.R)(),...e.components};return(0,a.jsxs)(a.Fragment,{children:[(0,a.jsx)(n.h1,{id:"how-data-space-operations",children:"How: Data Space Operations"}),"\n",(0,a.jsx)(n.p,{children:"This chapter outlines the overarching processes and premises to onboard and exchange\ndata in the Catena-X data space. This includes the general onboarding process that all\nparticipants must complete to join the Catena-X data space. It involves registration and\ntechnical integration, as well as compliance with the regulatory framework and verification\nthrough the Gaia-X Digital Clearing House. The introduction of Self Sovereign Identities (SSI)\nin Tractus-X Release 23.09 updates the process for offering, exchanging, and using data,\nwhile the chapter also covers EDC deployment and usage premises and available support\noptions for participants."}),"\n",(0,a.jsx)(n.h2,{id:"general-onboarding",children:"General Onboarding"}),"\n",(0,a.jsxs)(n.p,{children:["To participate in the data space, all participants must complete the general registration process, which involves registration and can be extended by the technical integration (see Figure ",(0,a.jsx)(n.a,{href:"/docs/next/operating-model/how-data-space-operations/#general-onboarding",children:"General Onboarding Process"}),")."]}),"\n",(0,a.jsxs)(n.p,{children:[(0,a.jsx)(n.img,{alt:"General Onboarding Process",src:t(4478).A+"",width:"1465",height:"692"}),"\n",(0,a.jsx)(n.em,{children:"General Onboarding Process"})]}),"\n",(0,a.jsxs)(n.p,{children:["During ",(0,a.jsx)(n.strong,{children:"registration"}),", all participants must fill out their company data, select their data space role, and agree to the regulatory framework via one of the OSPs (see Chapter ",(0,a.jsx)(n.a,{href:"/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/#onboarding-service-provider",children:"Onboarding Service Provider"}),"). A BPNL (if not yet existing) as well as a Managed Wallet Tenant with BPNL Credential and CX membership Credential are created as part of the registration approval process, which is owned/managed by the operation company. Each participant can collect their identity proofs, certificates and other verifiable information, rights, or services in its identity wallet."]}),"\n",(0,a.jsxs)(n.p,{children:["During ",(0,a.jsx)(n.strong,{children:"technical integration"}),", the technical user creation and registration of the connectors are essential to enable the company communication with the data space. The technical user enables the customer company to connect the connector with the wallet and the connector registration is needed to ensure that the connector can get found by other data space members."]}),"\n",(0,a.jsxs)(n.p,{children:["The self-descriptions of newly registered legal entities and connectors are validated by the GXDCH (see Chapter ",(0,a.jsx)(n.a,{href:"/docs/next/operating-model/how-data-space-operations/#gaia-x-compliance",children:"Gaia-X Compliance"}),"). This involves signing and issuing credentials to the identity wallet of a DPC, providing proof of Gaia-X compliance and legal entity notarization. Detailed information about the Standard CX-0006 in the ",(0,a.jsx)(n.a,{href:"https://catena-x.net/de/standard-library",children:"Standard Library"})," of the Catena-X Association."]}),"\n",(0,a.jsx)(n.h2,{id:"gaia-x-compliance",children:"Gaia-X Compliance"}),"\n",(0,a.jsx)(n.p,{children:"The Gaia-X Digital Clearing House (GXDCH) is an external service that maximizes trust within the Catena-X data space and interoperability with other data space initiatives based on the Gaia-X Trust Framework. The GXDCH enables the validation of legal entities, ensures Gaia-X compliance, and creates an eIDAS conform digital signature (SelfDescription) 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, every OSP must connect to the GXDCH. OSP candidates can request more information during conformity assessment."}),"\n",(0,a.jsx)(n.h2,{id:"ssi-issuer-concept",children:"SSI Issuer Concept"}),"\n",(0,a.jsxs)(n.p,{children:["The Tractus-X Release 23.09 initiates the introduction of Self Sovereign Identities (SSI), replacing the Dynamic Attribute Provisioning Service (DAPS). The current release and version of SSI allows only one issuer and one centrally managed identity wallet operated by the CSP-B (see Chapter ",(0,a.jsx)(n.a,{href:"/docs/next/operating-model/what-service-map/",children:"What: Service Map"}),"). This also includes the revocation of issued certificates. This is done in cooperation with the Catena-X Association e.g., in case of conscious violation of legal and technical framework. With the 23.09. Release the CSP-B is the single issuer authority of Catena-X credentials. Multi-issuer concept is planned in the following releases. The BPNL can be found on the Catena-X Association website and the portal of the CSP-B. This concept will evolve in future releases, the details of which can be found in Chapter ",(0,a.jsx)(n.a,{href:"/docs/next/operating-model/outlook/#further-integration-of-ssi-technologies",children:"Further Integration of SSI Technologies"}),"."]}),"\n",(0,a.jsx)(n.h2,{id:"data-exchange-based-on-ssi",children:"Data Exchange based on SSI"}),"\n",(0,a.jsxs)(n.p,{children:["With the introduction of Self Sovereign Identities (SSI) in the Tractus-X Release 23.09, the processes to participate in a use case as well as offer, exchange, and use data are updated as follows (see Figure ",(0,a.jsx)(n.a,{href:"/docs/next/operating-model/how-data-space-operations/#data-exchange-based-on-ssi",children:"Data Exchange Process"}),"):"]}),"\n",(0,a.jsxs)(n.p,{children:[(0,a.jsx)(n.img,{alt:"Data Exchange Process",src:t(2224).A+"",width:"1037",height:"781"}),"\n",(0,a.jsx)(n.em,{children:"Data Exchange Process"})]}),"\n",(0,a.jsxs)(n.ol,{children:["\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Participant signs pre-defined use case framework conditions and requests credential via CSP-B"})}),"\n",(0,a.jsx)(n.p,{children:"The data consumer must sign and upload the respective use case framework conditions to request the use case participation credential."}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Issuer validates request and issues credential"})}),"\n",(0,a.jsx)(n.p,{children:"The request from the participant (e.g., data consumer) is sent to the issuer (operator) for validation (frame version and existing signature) and confirmation, which triggers the creation of the VC."}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Requests credential"})}),"\n",(0,a.jsx)(n.p,{children:"The customer EDC calls the MIW to retrieve the verified summary credentials, requests the signature and retrieves the verified presentation with the summary credential."}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Query catalogue/offers"})}),"\n",(0,a.jsx)(n.p,{children:"With the query of the data provider catalog, the consumer EDC submits the request with the VP in the request header. Upon successful validation, the issuer generates the verified credential using the MIW component and stores it in the wallet tenant of the customer company wallet. is recreated containing both the previous credentials and the newly added credential."}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Submit catalog"})}),"\n",(0,a.jsx)(n.p,{children:"The received offer catalog request and the submitted customer VP are validated by the provider EDC. All data offers where the data access policies set by the provider match the verified credentials owned by the data consumer are sent to the customer. Any data offers that require verified credentials that the data consumer does not have will not be sent/published to the data consumer."}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Manual checking of data offering policies"})}),"\n",(0,a.jsx)(n.p,{children:"Configured data offer policies must be manually checked by the data consumer."}),"\n",(0,a.jsxs)(n.ul,{children:["\n",(0,a.jsx)(n.li,{children:"If a purpose is specified, the purpose must be validated internally by the data consumer. The purpose may refer to an individual contract concluded between the data consumer and the data provider. The data consumer must review the contract and decide whether the policies are acceptable for the specific data offering based on the established policies (see next step 7)."}),"\n",(0,a.jsx)(n.li,{children:"If no purpose is specified, the negotiation can start immediately, as the access and usage policies are automatically technically enforced and validated by the EDCs."}),"\n"]}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Decision on the purpose of the data offer"})}),"\n",(0,a.jsx)(n.p,{children:"Based on step 6 individual data contract validation, the data consumer must decide whether to proceed with the negotiation or whether to disagree with the individual purpose. If there is disagreement, the negotiation should not be started. If there is consent, the data consumer can start the negotiation."}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Contract negotiation"})}),"\n",(0,a.jsx)(n.p,{children:"The data consumer starts the contract negotiation by sending a request for an agreement/contract"}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Contract conclusion/success"})}),"\n",(0,a.jsx)(n.p,{children:"The EDC of the data provider receives the negotiation requests, validates the access and usage policies of the specific data offer requested by the data provider, and matches it with the VP of the data consumer. If the data consumer has all relevant credentials, the agreement is successfully concluded, and an agreement log is stored in both EDCs."}),"\n"]}),"\n",(0,a.jsxs)(n.li,{children:["\n",(0,a.jsx)(n.p,{children:(0,a.jsx)(n.strong,{children:"Data transfer"})}),"\n",(0,a.jsx)(n.p,{children:"Data transmission/access by the data consumer can take place as long as the contract is active."}),"\n"]}),"\n"]}),"\n",(0,a.jsx)(n.h2,{id:"edc-deployment-and-usage-premises",children:"EDC Deployment and Usage Premises"}),"\n",(0,a.jsx)(n.p,{children:"Each data space participant has its own organizational structure, consisting of different legal entities and/or subsidiaries. Depending on the organizational structures, data space participants must consider how to organize the representation of their organization in the Catena-X data space. This includes considerations for setting up connector instances regarding organizational, technical, and legal conditions. The following premises apply:"}),"\n",(0,a.jsxs)(n.ul,{children:["\n",(0,a.jsx)(n.li,{children:"The data exchange always takes place between two legal entities, as only their representatives can sign legally binding contracts."}),"\n",(0,a.jsx)(n.li,{children:"Legal entities must be registered and known in the data space."}),"\n",(0,a.jsx)(n.li,{children:"To represent a legal entity in the data space, an associated business partner number (BPNL) is required."}),"\n",(0,a.jsx)(n.li,{children:"The deployment and use of at least one connector (e.g., EDC) per legal entity for data exchange is mandatory."}),"\n",(0,a.jsx)(n.li,{children:"The connector negotiates data usage between endpoints (data plane) by synchronizing access and usage policies between data providers and data consumers."}),"\n",(0,a.jsx)(n.li,{children:"There is no data processing or reviewing of data within the connector itself."}),"\n",(0,a.jsx)(n.li,{children:"Data usage takes place instead at the endpoints of the data providers or data consumers, respectively."}),"\n",(0,a.jsx)(n.li,{children:"Data usage with respect to location and assignment to computer instances/platforms is independent of the runtime environment of the connector itself."}),"\n"]}),"\n",(0,a.jsxs)(n.p,{children:["There are various options for organizational structures and data exchange scenarios such as \u201cone legal entity and one site in one country\u201d, \u201cone legal entity and multiple sites in one country\u201d or \u201cone legal entity and multiple sites in different countries\u201d. For more details on possible connector usage scenarios, please refer to our ",(0,a.jsx)(n.a,{href:"https://catena-x.net/fileadmin/user_upload/Standard-Bibliothek/Update_PDF_Maerz/6_Onboarding/CX_-_0006_Registration_and_Initial_Onboarding_v_1.1.1.pdf",children:"Initial Onboarding Guide"}),". This includes also the different options to obtain a connector, e.g., it can be acquired via an ESP, it can be self-developed or adapted from open-source, or it can be part of a business application from a BAP. If the data exchange does not take place between several legal entities within Catena-X as defined above, no EDC is required. An example would be the connection of the OSP to the GXDCH. For this connection no connector is needed, because this is not an exchange of data between two legal entities within Catena-X."]})]})}function h(e={}){const{wrapper:n}={...(0,i.R)(),...e.components};return n?(0,a.jsx)(n,{...e,children:(0,a.jsx)(l,{...e})}):l(e)}},2224:(e,n,t)=>{t.d(n,{A:()=>a});const a=t.p+"assets/images/data-exchange-process-2de9e4cb18ad9602cb2ba975287579f6.png"},4478:(e,n,t)=>{t.d(n,{A:()=>a});const a=t.p+"assets/images/general-onboarding-process-756b55f51977bf98f2df2d9957704e90.png"},8453:(e,n,t)=>{t.d(n,{R:()=>o,x:()=>r});var a=t(6540);const i={},s=a.createContext(i);function o(e){const n=a.useContext(s);return a.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function r(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:o(e.components),a.createElement(s.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/851dcdeb.27d33105.js b/assets/js/851dcdeb.27d33105.js new file mode 100644 index 00000000..5252c4d6 --- /dev/null +++ b/assets/js/851dcdeb.27d33105.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8545],{470:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>a,contentTitle:()=>s,default:()=>l,frontMatter:()=>r,metadata:()=>c,toc:()=>u});var o=n(4848),i=n(8453);const r={sidebar_position:2,title:"Tractus-X Open Source Project Contribution Guide"},s=void 0,c={id:"working-model/process-from-idea-to-production/03-02-Contribution-Guideline",title:"Tractus-X Open Source Project Contribution Guide",description:"Welcome to the Tractus-X open source project! This guide is designed to help you understand how you can contribute to the Tractus-X project. There are different levels of contributions you can make, such as standard contributions, feature contributions and improvements.",source:"@site/docs/working-model/03-process-from-idea-to-production/03-02-Contribution-Guideline.md",sourceDirName:"working-model/03-process-from-idea-to-production",slug:"/working-model/process-from-idea-to-production/03-02-Contribution-Guideline",permalink:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-02-Contribution-Guideline",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:2,frontMatter:{sidebar_position:2,title:"Tractus-X Open Source Project Contribution Guide"},sidebar:"sidebar_working_model",previous:{title:"Process Organization - From Idea to Release",permalink:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production"},next:{title:"Contribution Levels",permalink:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-04-Issue-Process"}},a={},u=[{value:"Understanding Tractus-X",id:"understanding-tractus-x",level:2},{value:"General Contribution Guidelines",id:"general-contribution-guidelines",level:2},{value:"Further links",id:"further-links",level:3}];function d(e){const t={a:"a",blockquote:"blockquote",h2:"h2",h3:"h3",li:"li",p:"p",strong:"strong",ul:"ul",...(0,i.R)(),...e.components};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsx)(t.p,{children:"Welcome to the Tractus-X open source project! This guide is designed to help you understand how you can contribute to the Tractus-X project. There are different levels of contributions you can make, such as standard contributions, feature contributions and improvements.\nBelow you'll find the steps and guidelines for each."}),"\n",(0,o.jsx)(t.h2,{id:"understanding-tractus-x",children:"Understanding Tractus-X"}),"\n",(0,o.jsx)(t.p,{children:"Before contributing, it's important to have a good understanding of what Tractus-X is and what it aims to achieve. Tractus-X is a collaborative effort to create FOSS applications enabling the Catena-X dataspace core services for trusted and effective exchange. Familiarize yourself with the project's goals, architecture, and existing features by reviewing the documentation and codebase."}),"\n",(0,o.jsx)(t.h2,{id:"general-contribution-guidelines",children:"General Contribution Guidelines"}),"\n",(0,o.jsx)(t.p,{children:"Regardless of the type of contribution, here are some general guidelines to follow:"}),"\n",(0,o.jsxs)(t.ul,{children:["\n",(0,o.jsxs)(t.li,{children:[(0,o.jsx)(t.strong,{children:"Read the Contribution Guidelines:"})," Before contributing, make sure to read the project's contribution guidelines thoroughly."]}),"\n",(0,o.jsxs)(t.li,{children:[(0,o.jsx)(t.strong,{children:"Code of Conduct:"})," Adhere to the project's code of conduct to maintain a respectful and collaborative environment."]}),"\n",(0,o.jsxs)(t.li,{children:[(0,o.jsx)(t.strong,{children:"Stay Updated:"})," Regularly pull the latest changes from the main branch to keep your local repository up-to-date."]}),"\n",(0,o.jsxs)(t.li,{children:[(0,o.jsx)(t.strong,{children:"Communicate:"})," Engage with the community through issues, pull requests, and discussions to collaborate effectively."]}),"\n",(0,o.jsxs)(t.li,{children:[(0,o.jsx)(t.strong,{children:"Write Tests:"})," If you're contributing code, make sure to write tests that cover your changes."]}),"\n",(0,o.jsxs)(t.li,{children:[(0,o.jsx)(t.strong,{children:"Documentation:"})," Update or add documentation as necessary to reflect your changes or new features."]}),"\n"]}),"\n",(0,o.jsx)(t.p,{children:"By following these guidelines, you can make valuable contributions to the Tractus-X project and help drive its success. Thank you for your interest in contributing to Tractus-X!"}),"\n",(0,o.jsx)(t.h3,{id:"further-links",children:"Further links"}),"\n",(0,o.jsxs)(t.blockquote,{children:["\n",(0,o.jsx)(t.p,{children:(0,o.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-04-Issue-Process",children:"Contribution Levels"})}),"\n"]})]})}function l(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,o.jsx)(t,{...e,children:(0,o.jsx)(d,{...e})}):d(e)}},8453:(e,t,n)=>{n.d(t,{R:()=>s,x:()=>c});var o=n(6540);const i={},r=o.createContext(i);function s(e){const t=o.useContext(r);return o.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function c(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:s(e.components),o.createElement(r.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/851dcdeb.ebc951b4.js b/assets/js/851dcdeb.ebc951b4.js deleted file mode 100644 index b949af63..00000000 --- a/assets/js/851dcdeb.ebc951b4.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8545],{470:(e,t,o)=>{o.r(t),o.d(t,{assets:()=>a,contentTitle:()=>s,default:()=>l,frontMatter:()=>r,metadata:()=>c,toc:()=>u});var n=o(4848),i=o(8453);const r={sidebar_position:2,title:"Tractus-X Open Source Project Contribution Guide"},s=void 0,c={id:"working-model/process-from-idea-to-production/03-02-Contribution-Guideline",title:"Tractus-X Open Source Project Contribution Guide",description:"Welcome to the Tractus-X open source project! This guide is designed to help you understand how you can contribute to the Tractus-X project. There are different levels of contributions you can make, such as standard contributions, feature contributions and improvements.",source:"@site/docs/working-model/03-process-from-idea-to-production/03-02-Contribution-Guideline.md",sourceDirName:"working-model/03-process-from-idea-to-production",slug:"/working-model/process-from-idea-to-production/03-02-Contribution-Guideline",permalink:"/docs/next/working-model/process-from-idea-to-production/03-02-Contribution-Guideline",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:2,frontMatter:{sidebar_position:2,title:"Tractus-X Open Source Project Contribution Guide"},sidebar:"sidebar_working_model",previous:{title:"Process Organization - From Idea to Release",permalink:"/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production"},next:{title:"Contribution Levels",permalink:"/docs/next/working-model/process-from-idea-to-production/03-04-Issue-Process"}},a={},u=[{value:"Understanding Tractus-X",id:"understanding-tractus-x",level:2},{value:"General Contribution Guidelines",id:"general-contribution-guidelines",level:2},{value:"Further links",id:"further-links",level:3}];function d(e){const t={a:"a",blockquote:"blockquote",h2:"h2",h3:"h3",li:"li",p:"p",strong:"strong",ul:"ul",...(0,i.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(t.p,{children:"Welcome to the Tractus-X open source project! This guide is designed to help you understand how you can contribute to the Tractus-X project. There are different levels of contributions you can make, such as standard contributions, feature contributions and improvements.\nBelow you'll find the steps and guidelines for each."}),"\n",(0,n.jsx)(t.h2,{id:"understanding-tractus-x",children:"Understanding Tractus-X"}),"\n",(0,n.jsx)(t.p,{children:"Before contributing, it's important to have a good understanding of what Tractus-X is and what it aims to achieve. Tractus-X is a collaborative effort to create FOSS applications enabling the Catena-X dataspace core services for trusted and effective exchange. Familiarize yourself with the project's goals, architecture, and existing features by reviewing the documentation and codebase."}),"\n",(0,n.jsx)(t.h2,{id:"general-contribution-guidelines",children:"General Contribution Guidelines"}),"\n",(0,n.jsx)(t.p,{children:"Regardless of the type of contribution, here are some general guidelines to follow:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Read the Contribution Guidelines:"})," Before contributing, make sure to read the project's contribution guidelines thoroughly."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Code of Conduct:"})," Adhere to the project's code of conduct to maintain a respectful and collaborative environment."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Stay Updated:"})," Regularly pull the latest changes from the main branch to keep your local repository up-to-date."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Communicate:"})," Engage with the community through issues, pull requests, and discussions to collaborate effectively."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Write Tests:"})," If you're contributing code, make sure to write tests that cover your changes."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Documentation:"})," Update or add documentation as necessary to reflect your changes or new features."]}),"\n"]}),"\n",(0,n.jsx)(t.p,{children:"By following these guidelines, you can make valuable contributions to the Tractus-X project and help drive its success. Thank you for your interest in contributing to Tractus-X!"}),"\n",(0,n.jsx)(t.h3,{id:"further-links",children:"Further links"}),"\n",(0,n.jsxs)(t.blockquote,{children:["\n",(0,n.jsx)(t.p,{children:(0,n.jsx)(t.a,{href:"/docs/next/working-model/process-from-idea-to-production/03-04-Issue-Process",children:"Contribution Levels"})}),"\n"]})]})}function l(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,n.jsx)(t,{...e,children:(0,n.jsx)(d,{...e})}):d(e)}},8453:(e,t,o)=>{o.d(t,{R:()=>s,x:()=>c});var n=o(6540);const i={},r=n.createContext(i);function s(e){const t=n.useContext(r);return n.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function c(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:s(e.components),n.createElement(r.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/86cc9362.8dd8d276.js b/assets/js/86cc9362.8dd8d276.js deleted file mode 100644 index 9b4ceea1..00000000 --- a/assets/js/86cc9362.8dd8d276.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[423],{2474:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>d,contentTitle:()=>r,default:()=>l,frontMatter:()=>i,metadata:()=>a,toc:()=>c});var s=t(4848),o=t(8453);const i={sidebar_position:1,title:"Overview Standards"},r=void 0,a={id:"standards/overview",title:"Overview Standards",description:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.",source:"@site/versioned_docs/version-24.03/standards/overview.md",sourceDirName:"standards",slug:"/standards/overview",permalink:"/docs/standards/overview",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Overview Standards"},sidebar:"sidebar_standards"},d={},c=[];function u(e){const n={admonition:"admonition",p:"p",...(0,o.R)(),...e.components};return(0,s.jsx)(n.admonition,{type:"danger",children:(0,s.jsx)(n.p,{children:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation."})})}function l(e={}){const{wrapper:n}={...(0,o.R)(),...e.components};return n?(0,s.jsx)(n,{...e,children:(0,s.jsx)(u,{...e})}):u(e)}},8453:(e,n,t)=>{t.d(n,{R:()=>r,x:()=>a});var s=t(6540);const o={},i=s.createContext(o);function r(e){const n=s.useContext(i);return s.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function a(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(o):e.components||o:r(e.components),s.createElement(i.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/86cc9362.bf26d0aa.js b/assets/js/86cc9362.bf26d0aa.js new file mode 100644 index 00000000..412697db --- /dev/null +++ b/assets/js/86cc9362.bf26d0aa.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[423],{2474:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>d,contentTitle:()=>a,default:()=>l,frontMatter:()=>i,metadata:()=>r,toc:()=>c});var s=t(4848),o=t(8453);const i={sidebar_position:1,title:"Overview Standards"},a=void 0,r={id:"standards/overview",title:"Overview Standards",description:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.",source:"@site/versioned_docs/version-24.03/standards/overview.md",sourceDirName:"standards",slug:"/standards/overview",permalink:"/catenax-ev.github.io.new/docs/standards/overview",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Overview Standards"},sidebar:"sidebar_standards"},d={},c=[];function u(e){const n={admonition:"admonition",p:"p",...(0,o.R)(),...e.components};return(0,s.jsx)(n.admonition,{type:"danger",children:(0,s.jsx)(n.p,{children:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation."})})}function l(e={}){const{wrapper:n}={...(0,o.R)(),...e.components};return n?(0,s.jsx)(n,{...e,children:(0,s.jsx)(u,{...e})}):u(e)}},8453:(e,n,t)=>{t.d(n,{R:()=>a,x:()=>r});var s=t(6540);const o={},i=s.createContext(o);function a(e){const n=s.useContext(i);return s.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function r(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(o):e.components||o:a(e.components),s.createElement(i.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/8717b14a.61162e66.js b/assets/js/8717b14a.61162e66.js new file mode 100644 index 00000000..6732fc5b --- /dev/null +++ b/assets/js/8717b14a.61162e66.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3694],{1615:(e,t,o)=>{o.r(t),o.d(t,{assets:()=>r,contentTitle:()=>l,default:()=>g,frontMatter:()=>i,metadata:()=>a,toc:()=>c});var n=o(4848),s=o(8453);const i={slug:"long-blog-post",title:"Long Blog Post",authors:"endi",tags:["hello","docusaurus"]},l=void 0,a={permalink:"/catenax-ev.github.io.new/blog/long-blog-post",source:"@site/blog/2019-05-29-long-blog-post.md",title:"Long Blog Post",description:"This is the summary of a very long blog post,",date:"2019-05-29T00:00:00.000Z",tags:[{inline:!1,label:"Hello",permalink:"/catenax-ev.github.io.new/blog/tags/hello",description:"Hello tag description"},{inline:!1,label:"Docusaurus",permalink:"/catenax-ev.github.io.new/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:2.05,hasTruncateMarker:!0,authors:[{name:"Endilie Yacop Sucipto",title:"Maintainer of Docusaurus",url:"https://github.com/endiliey",imageURL:"https://github.com/endiliey.png",key:"endi"}],frontMatter:{slug:"long-blog-post",title:"Long Blog Post",authors:"endi",tags:["hello","docusaurus"]},unlisted:!1,prevItem:{title:"MDX Blog Post",permalink:"/catenax-ev.github.io.new/blog/mdx-blog-post"},nextItem:{title:"First Blog Post",permalink:"/catenax-ev.github.io.new/blog/first-blog-post"}},r={authorsImageUrls:[void 0]},c=[];function u(e){const t={code:"code",p:"p",...(0,s.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(t.p,{children:"This is the summary of a very long blog post,"}),"\n",(0,n.jsxs)(t.p,{children:["Use a ",(0,n.jsx)(t.code,{children:"\x3c!--"})," ",(0,n.jsx)(t.code,{children:"truncate"})," ",(0,n.jsx)(t.code,{children:"--\x3e"})," comment to limit blog post size in the list view."]})]})}function g(e={}){const{wrapper:t}={...(0,s.R)(),...e.components};return t?(0,n.jsx)(t,{...e,children:(0,n.jsx)(u,{...e})}):u(e)}},8453:(e,t,o)=>{o.d(t,{R:()=>l,x:()=>a});var n=o(6540);const s={},i=n.createContext(s);function l(e){const t=n.useContext(i);return n.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function a(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:l(e.components),n.createElement(i.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/8717b14a.f509a579.js b/assets/js/8717b14a.f509a579.js deleted file mode 100644 index 645b69ab..00000000 --- a/assets/js/8717b14a.f509a579.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3694],{1615:(t,e,o)=>{o.r(e),o.d(e,{assets:()=>a,contentTitle:()=>l,default:()=>g,frontMatter:()=>i,metadata:()=>r,toc:()=>c});var n=o(4848),s=o(8453);const i={slug:"long-blog-post",title:"Long Blog Post",authors:"endi",tags:["hello","docusaurus"]},l=void 0,r={permalink:"/blog/long-blog-post",source:"@site/blog/2019-05-29-long-blog-post.md",title:"Long Blog Post",description:"This is the summary of a very long blog post,",date:"2019-05-29T00:00:00.000Z",tags:[{inline:!1,label:"Hello",permalink:"/blog/tags/hello",description:"Hello tag description"},{inline:!1,label:"Docusaurus",permalink:"/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:2.05,hasTruncateMarker:!0,authors:[{name:"Endilie Yacop Sucipto",title:"Maintainer of Docusaurus",url:"https://github.com/endiliey",imageURL:"https://github.com/endiliey.png",key:"endi"}],frontMatter:{slug:"long-blog-post",title:"Long Blog Post",authors:"endi",tags:["hello","docusaurus"]},unlisted:!1,prevItem:{title:"MDX Blog Post",permalink:"/blog/mdx-blog-post"},nextItem:{title:"First Blog Post",permalink:"/blog/first-blog-post"}},a={authorsImageUrls:[void 0]},c=[];function u(t){const e={code:"code",p:"p",...(0,s.R)(),...t.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(e.p,{children:"This is the summary of a very long blog post,"}),"\n",(0,n.jsxs)(e.p,{children:["Use a ",(0,n.jsx)(e.code,{children:"\x3c!--"})," ",(0,n.jsx)(e.code,{children:"truncate"})," ",(0,n.jsx)(e.code,{children:"--\x3e"})," comment to limit blog post size in the list view."]})]})}function g(t={}){const{wrapper:e}={...(0,s.R)(),...t.components};return e?(0,n.jsx)(e,{...t,children:(0,n.jsx)(u,{...t})}):u(t)}},8453:(t,e,o)=>{o.d(e,{R:()=>l,x:()=>r});var n=o(6540);const s={},i=n.createContext(s);function l(t){const e=n.useContext(i);return n.useMemo((function(){return"function"==typeof t?t(e):{...e,...t}}),[e,t])}function r(t){let e;return e=t.disableParentContext?"function"==typeof t.components?t.components(s):t.components||s:l(t.components),n.createElement(i.Provider,{value:e},t.children)}}}]); \ No newline at end of file diff --git a/assets/js/8843b0b9.17ea4325.js b/assets/js/8843b0b9.17ea4325.js new file mode 100644 index 00000000..5dda3450 --- /dev/null +++ b/assets/js/8843b0b9.17ea4325.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[1721],{6474:(e,a,t)=>{t.r(a),t.d(a,{assets:()=>d,contentTitle:()=>o,default:()=>h,frontMatter:()=>s,metadata:()=>r,toc:()=>c});var i=t(4848),n=t(8453);const s={sidebar_position:1},o="How: Data Space Governance",r={id:"operating-model/how-data-space-governance/how-data-space-governance",title:"How: Data Space Governance",description:"Standardization",source:"@site/docs/operating-model/how-data-space-governance/how-data-space-governance.md",sourceDirName:"operating-model/how-data-space-governance",slug:"/operating-model/how-data-space-governance/",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"How: Data Space Operations",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-operations/"},next:{title:"How: Life Cycle Management",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/how-life-cycle-management/"}},d={},c=[{value:"Standardization",id:"standardization",level:2},{value:"Why do we standardize?",id:"why-do-we-standardize",level:3},{value:"What do we standardize?",id:"what-do-we-standardize",level:3},{value:"How do we standardize?",id:"how-do-we-standardize",level:3},{value:"Conformity Assessment",id:"conformity-assessment",level:2},{value:"Why do we certify?",id:"why-do-we-certify",level:3},{value:"What do we certify?",id:"what-do-we-certify",level:3},{value:"How do we certify?",id:"how-do-we-certify",level:3},{value:"Catena-X Labels",id:"catena-x-labels",level:3},{value:"Exceptions & Timeline for Release 23.09",id:"exceptions--timeline-for-release-2309",level:3},{value:"1. 45-day grace period to obtain valid certification after Release 3.2 (23.09)",id:"1-45-day-grace-period-to-obtain-valid-certification-after-release-32-2309",level:4},{value:"2. Certification of business applications vs. internal systems that fall under the definition of a Catena-X business application*",id:"2-certification-of-business-applications-vs-internal-systems-that-fall-under-the-definition-of-a-catena-x-business-application",level:4},{value:"3. No Catena-X Business Applications without listing on a certified CX Marketplace",id:"3-no-catena-x-business-applications-without-listing-on-a-certified-cx-marketplace",level:4},{value:"Nomination Process for unique Roles (e.g., CSP-B)",id:"nomination-process-for-unique-roles-eg-csp-b",level:2},{value:"Qualification Process",id:"qualification-process",level:2},{value:"Why do we qualify?",id:"why-do-we-qualify",level:3},{value:"Who do we qualify?",id:"who-do-we-qualify",level:3},{value:"How do we qualify?",id:"how-do-we-qualify",level:3},{value:"Regulatory Framework",id:"regulatory-framework",level:2}];function l(e){const a={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",h4:"h4",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",ul:"ul",...(0,n.R)(),...e.components};return(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(a.h1,{id:"how-data-space-governance",children:"How: Data Space Governance"}),"\n",(0,i.jsx)(a.h2,{id:"standardization",children:"Standardization"}),"\n",(0,i.jsx)(a.h3,{id:"why-do-we-standardize",children:"Why do we standardize?"}),"\n",(0,i.jsx)(a.p,{children:"The success of the digital transformation of the automotive industry critically depends on multilateral collaboration between all stakeholders along the automotive value chain. Our growing Catena-X ecosystem will enable enormous amounts of data to be integrated and collaboratively harnessed."}),"\n",(0,i.jsxs)(a.p,{children:["However, this vision is complex: companies at various stages of the automotive value chain, such as production, delivery, or logistics, often have their own IT systems to manage their data. To ensure that these complex data volumes can be sent, received, and processed smoothly across all stages of the value chain, we need one language for all players: ",(0,i.jsx)(a.strong,{children:"common standards and frameworks"}),"."]}),"\n",(0,i.jsx)(a.h3,{id:"what-do-we-standardize",children:"What do we standardize?"}),"\n",(0,i.jsx)(a.p,{children:"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."}),"\n",(0,i.jsxs)(a.p,{children:["The Catena-X Association publishes standards for generic core and enabling services as well as for domain-specific business applications (see KITs Chapter ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/what-service-map/#kits--keep-it-together",children:"KITs \u2013 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 ",(0,i.jsx)(a.a,{href:"https://catena-x.net/de/standard-library",children:"Catena-X standard library"}),"."]}),"\n",(0,i.jsx)(a.h3,{id:"how-do-we-standardize",children:"How do we standardize?"}),"\n",(0,i.jsxs)(a.p,{children:["Based on ",(0,i.jsx)(a.a,{href:"https://catena-x.net/fileadmin/user_upload/Vereinsdokumente/Catena-X_IP_Regelwerk_IP_Regulations.pdf",children:"Catena-X\u2019s Intellectual Property(IP)-Regulations"})," 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 ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance/#how-do-we-standardize",children:"Catena-X Standardization Process"}),":"]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Standardization Process",src:t(3485).A+"",width:"1492",height:"587"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Standardization Process"})]}),"\n",(0,i.jsxs)(a.p,{children:["The ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/standardisierung",children:"Catena-X standardization policy"})," provides a detailed description of how Catena-X standards are being developed including everyone involved and their respective responsibilities."]}),"\n",(0,i.jsx)(a.h2,{id:"conformity-assessment",children:"Conformity Assessment"}),"\n",(0,i.jsx)(a.h3,{id:"why-do-we-certify",children:"Why do we certify?"}),"\n",(0,i.jsx)(a.p,{children:"Cross company interactions highly rely on mutual trust. Our certifications provide trust via transparency and reliability based on our Catena-X standards. By setting up a certification process, we guarantee that our major principles are considered in every component of the network. From the core service providers to the data connectors and every single application in the network, a consistent framework was created to ensure beneficial participation for all participants in the network. A chain is only as strong as its weakest link, and to gain trust we need to ensure that all links are as strong as possible."}),"\n",(0,i.jsx)(a.h3,{id:"what-do-we-certify",children:"What do we certify?"}),"\n",(0,i.jsxs)(a.p,{children:["Catena-X certification is done in a modular, role-based way, to fulfill different requirements of participants in our ecosystem, whether IT application providers, service providers or onboarding partners. The modularity allows high flexibility and lowers the efforts and redundancies for all parties involved. Catena-X standards become mandatory for certification as soon as they have been integrated into the certification framework. The Catena-X Association aims to release an update of its certification framework simultaneously with newly released standards. The most current version can always be found on the ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/certification",children:"Catena-X website"}),"."]}),"\n",(0,i.jsx)(a.h3,{id:"how-do-we-certify",children:"How do we certify?"}),"\n",(0,i.jsxs)(a.p,{children:["An overview of the certification process is depicted in Figure ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance/#how-do-we-certify",children:"Catena-X Certification Process"}),".\n",(0,i.jsx)(a.img,{alt:"Catena-X Certification Process",src:t(5130).A+"",width:"1202",height:"692"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Certification Process"})]}),"\n",(0,i.jsxs)(a.p,{children:["The ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/certification",children:"Catena-X Conformity Assessment Framework Handbook"})," provides a detailed description of how Catena-X conducts conformity assessment through Conformity Assessment Bodies."]}),"\n",(0,i.jsx)(a.h3,{id:"catena-x-labels",children:"Catena-X Labels"}),"\n",(0,i.jsx)(a.p,{children:"Catena-X issues four different labels to help customers find suitable and legitimate providers for their needs. Each label is issued to the relevant role after achieving successful certification and/or qualification. Labels are associated with the offered services of the provider."}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Certified Operating Company"})," (CSP-A/CSP-B)\n",(0,i.jsx)(a.img,{alt:"Certified Operating Company",src:t(3947).A+"",width:"1103",height:"568"})]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Certified Provider"})," (e.g., BAP, ESP, OSP)\n",(0,i.jsx)(a.img,{alt:"Certified Provider",src:t(2609).A+"",width:"1103",height:"567"})]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Certified Solution"})," (e.g., Business App, Service\u2026.)\n",(0,i.jsx)(a.img,{alt:"Certified Solution",src:t(4675).A+"",width:"1110",height:"563"})]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Qualified Advisor"})," (Advisory Provider)\n",(0,i.jsx)(a.img,{alt:"Qualified Advisor",src:t(2909).A+"",width:"1101",height:"563"})]}),"\n",(0,i.jsx)(a.p,{children:"Each label is obtained after successful completion of the Catena-X certification or qualification process. Details on pathways to be added."}),"\n",(0,i.jsx)(a.h3,{id:"exceptions--timeline-for-release-2309",children:"Exceptions & Timeline for Release 23.09"}),"\n",(0,i.jsx)(a.p,{children:"Release 23.09 is the official GoLive Release of the Catena-X data ecosystem. For the first time, all major components of the Catena-X data ecosystem will be available to the vast majority of the automotive value chain. To fulfil this promise to all our stakeholders while some areas of Catena-X are still under development, certain exceptions are made during this transitional period:"}),"\n",(0,i.jsx)(a.h4,{id:"1-45-day-grace-period-to-obtain-valid-certification-after-release-32-2309",children:"1. 45-day grace period to obtain valid certification after Release 3.2 (23.09)"}),"\n",(0,i.jsxs)(a.p,{children:["Catena-X will release a standard update (Release 3.2) on Sept. 28, 2023, on the Catena-X Association website. ",(0,i.jsx)(a.strong,{children:"This release will include \u201cbreaking changes\u201d as defined in the"})," ",(0,i.jsx)(a.a,{href:"https://semver.org/",children:"Semantic Versioning"}),"."]}),"\n",(0,i.jsxs)(a.p,{children:["The GoLive of the Catena-X data ecosystem (productive environment) will be ",(0,i.jsx)(a.strong,{children:"exclusively on Release 3.2"}),". This will be accompanied by an ",(0,i.jsx)(a.strong,{children:"update of the certification framework"})," (\u201cwhich role needs to have which components certified\u201d) for release 3.2."]}),"\n",(0,i.jsxs)(a.p,{children:["Each partner needs to ensure conformity to the new standards to be active in the data space. To this end, the following procedure applies: Every participant in the data space has ",(0,i.jsx)(a.strong,{children:"45 days after Sept. 28"})," (grace period) to complete their certification via a CAB or, in case of an existing certification, via free self-assessment. ",(0,i.jsx)(a.strong,{children:"Deadline is Nov. 12, 2023"})," (Sept. 28 + 45 days)."]}),"\n",(0,i.jsxs)(a.p,{children:["Cofinity-X will ",(0,i.jsx)(a.strong,{children:"allow data space registration"})," of a partner from GoLive Oct. 16 after consultation with the Association, ",(0,i.jsx)(a.strong,{children:"subject to the proviso that certification must be completed by the Nov. 12 deadline"}),". If the certificate is not proven within the 45 days, Partners must be removed from the data space at the direction of the Catena-X Association."]}),"\n",(0,i.jsxs)(a.p,{children:["Data space participants and their solutions that were already certified for Release 3.0/3.1 can use the 45-day grace period to prove their compliance to the Association via a ",(0,i.jsx)(a.strong,{children:"free self-assessment"})," and thus confirm the validity of their certificate even after release updates (up to a maximum of 12 months after initial issue). A corresponding form including confirmation of conformity with each standard required for the certificate can be requested from ",(0,i.jsx)(a.a,{href:"mailto:info@catena-x.net",children:"info@catena-x.net"}),". This does not apply to a CSP-B."]}),"\n",(0,i.jsx)(a.h4,{id:"2-certification-of-business-applications-vs-internal-systems-that-fall-under-the-definition-of-a-catena-x-business-application",children:"2. Certification of business applications vs. internal systems that fall under the definition of a Catena-X business application*"}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"A business application"})," provides specific logic and schemas defined in a Catena-X use case (e. g., data processing, transformation functions) that is applied to input data to produce an expected output. This includes the transformation of data from an input format into an output format using Catena-X semantic models (semantic interoperability) as well as the technical data exchange using standardized protocols and API-specifications (technical interoperability). This does not apply to internal systems of an organization, such as internal databases, data lakes, data pipelines (ETL) or source systems. To become operational on the Catena-X data space, a business application must comply with the corresponding standards (see Chapter ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),")."]}),"\n",(0,i.jsxs)(a.p,{children:["Companies connected to Catena-X might want to ",(0,i.jsx)(a.strong,{children:"connect certain internal systems"})," including company-internal business applications to the Catena-X network. It remains, however, crucial that all participants can rely on a standardized data exchange that guarantees stable data chains built on data sovereignty and interoperability."]}),"\n",(0,i.jsx)(a.p,{children:"Consequently, the following two principles apply:"}),"\n",(0,i.jsxs)(a.ul,{children:["\n",(0,i.jsx)(a.li,{children:"Everything that is necessary to uphold a stable data chain is required to follow Catena-X standards and has to be certified by a CAB."}),"\n",(0,i.jsx)(a.li,{children:"All business applications that are either associated with the Catena-X brand and/or are offered on a Catena-X marketplace are required to follow Catena-X standards and have to be certified by a CAB."}),"\n"]}),"\n",(0,i.jsx)(a.p,{children:"If an internal system fulfills one of these two criteria, a Catena-X certification is mandatory."}),"\n",(0,i.jsx)(a.p,{children:"*For future reference, to provide a scalable way of certification, additional technical and partially automated solutions\nof assessing conformity are currently under assessment. (10 votes for, 0 against \xe0 also Steve vote for publication)"}),"\n",(0,i.jsx)(a.h4,{id:"3-no-catena-x-business-applications-without-listing-on-a-certified-cx-marketplace",children:"3. No Catena-X Business Applications without listing on a certified CX Marketplace"}),"\n",(0,i.jsx)(a.p,{children:"Catena-X is built on trust. Consequently, certified Catena-X marketplaces (CSP-A) are checking, whether services provided are coming with verified credentials to ensure that the listed offer is trustworthy and conform to Catena-X standards."}),"\n",(0,i.jsx)(a.p,{children:"To further anchor this trust, all Catena-X related business applications and services require a listing on a Catena-X certified marketplace. Catena-X does not permit operating a Catena-X solution outside of a certified Catena-X market place."}),"\n",(0,i.jsxs)(a.p,{children:["As noted in Chapter ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),", as of release 23.12, Catena-X will provide the technical possibility for multiple CSP-A providers. This will foster multiple verifiers of credentials."]}),"\n",(0,i.jsx)(a.h2,{id:"nomination-process-for-unique-roles-eg-csp-b",children:"Nomination Process for unique Roles (e.g., CSP-B)"}),"\n",(0,i.jsx)(a.p,{children:"The nomination process is intended to ensure neutrality and trustworthy execution of selected roles and tasks within the Catena-X ecosystem. The Catena-X Association is responsible for the execution of the nomination process including partner selection."}),"\n",(0,i.jsxs)(a.p,{children:["The various rights and obligations of the provider are described in the Request for Tender (RFT). This is, for example, the license for operation, which can also be withdrawn in case of unfair behavior. This ensures fair awarding and safe operation of the various components. Tasks include, for example, the operation of Core Services - Section B by Core Service Providers or the certification of providers and solutions by CABs. An overview of the nomination process is depicted in Figure ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance/#nomination-process-for-unique-roles-eg-csp-b",children:"Catena-X Nomination Process"}),"."]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Nomination Process",src:t(3032).A+"",width:"1451",height:"652"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Nomination Process"})]}),"\n",(0,i.jsx)(a.p,{children:"The process steps of the nomination process are described in detail below."}),"\n",(0,i.jsxs)(a.table,{children:[(0,i.jsx)(a.thead,{children:(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.th,{children:"Process Step"}),(0,i.jsx)(a.th,{children:"Description"}),(0,i.jsx)(a.th,{children:"Input"}),(0,i.jsx)(a.th,{children:"Output"})]})}),(0,i.jsxs)(a.tbody,{children:[(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Create Request for Tender (RfT)"}),(0,i.jsx)(a.td,{children:"The Catena-X Association is responsible for the creation of the Request for Tender (RfT) document (e.g., for Core Services - section B)"}),(0,i.jsx)(a.td,{}),(0,i.jsx)(a.td,{children:"RfT Document(s)"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Publish RfT on Website"}),(0,i.jsxs)(a.td,{children:["The Catena-X Association is responsible for the publication and distribution of the ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/",children:"RfT Document on the website"}),"."]}),(0,i.jsx)(a.td,{children:"RfT Document(s)"}),(0,i.jsx)(a.td,{children:"RfT Document(s) RfT Event incl. Timeline RfT Template"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Create and Submit Tender for selected Core Service(s)"}),(0,i.jsx)(a.td,{children:"A provider can create and submit a tender for the published RfT."}),(0,i.jsx)(a.td,{children:"RfT Document RfT Event RfT Template"}),(0,i.jsx)(a.td,{children:"Tender"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Receive and Review Submissions"}),(0,i.jsx)(a.td,{children:"The CX Association compares the tender(s), regarding the fulfillment of the nomination criteria and creates a short list of candidates for the board."}),(0,i.jsx)(a.td,{children:"Tender(s)"}),(0,i.jsx)(a.td,{children:"Short List of Provider Candidates"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Select Provider"}),(0,i.jsx)(a.td,{children:"The board of the Association elects a provider with an absolute majority vote."}),(0,i.jsx)(a.td,{children:"Short List of Provider Candidates"}),(0,i.jsx)(a.td,{children:"Nomination of Provider"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Inform Providers"}),(0,i.jsx)(a.td,{children:"The CX Association informs all provider(s) about the result of the nomination process."}),(0,i.jsx)(a.td,{}),(0,i.jsx)(a.td,{})]})]})]}),"\n",(0,i.jsx)(a.h2,{id:"qualification-process",children:"Qualification Process"}),"\n",(0,i.jsx)(a.h3,{id:"why-do-we-qualify",children:"Why do we qualify?"}),"\n",(0,i.jsx)(a.p,{children:"On the way to creating value with Catena-X, companies may be dependent on advisory services. The quality of these advisory services is decisive for the success of the participation and thus for the success of Catena-X. Catena-X can only be successful if it succeeds in integrating large parts of the automotive value chain. We assume that this will lead to a high demand for advisory services, which must be met. These advisory services must cover the needs of small and medium-sized companies as well as the needs of large companies, which have extended integration requirements."}),"\n",(0,i.jsx)(a.p,{children:"Advisory services are hard, if not impossible, to standardize. Consequently, conformity assessment of qualified advisory services cannot take place through certification. To maintain a consistent level of quality among advisory service providers in the Catena-X data space, the Catena-X Association thus offers a qualification process that is mandatory for all advisory service providers that want to get listed in a marketplace. Advisory service providers, like all other participants active on the Catena-X data space, must adhere to the Catena-X regulatory framework and thereby confirm their full and unconditional support of our data ecosystem including its mission and standards."}),"\n",(0,i.jsx)(a.h3,{id:"who-do-we-qualify",children:"Who do we qualify?"}),"\n",(0,i.jsx)(a.p,{children:"Catena-X invites advisory service providers of all kinds to support the successful onboarding of data space participants, SMEs in particular. One of the few prerequisites is the binding commitment to provide high-quality consulting at fair and reasonable costs. Catena-X supports this endeavor with information and predefined content as well as a qualification system to prove appropriate support and consulting competencies."}),"\n",(0,i.jsx)(a.h3,{id:"how-do-we-qualify",children:"How do we qualify?"}),"\n",(0,i.jsx)(a.p,{children:"There are two ways to become a Catena-X qualified advisory service provider."}),"\n",(0,i.jsxs)(a.ol,{children:["\n",(0,i.jsx)(a.li,{children:"Qualification through training"}),"\n",(0,i.jsx)(a.li,{children:"Qualification through existing experience"}),"\n"]}),"\n",(0,i.jsxs)(a.p,{children:["For most advisory service providers, the first option applies. Qualification through existing experience is a path offered to advisory service providers that have gained experience by actively contributing to the Catena-X ecosystem either by directly accompanying companies within the Catena-X beta phase or contributing directly to the Catena-X kickstarter consortium as a listed member. An overview of the qualification process is depicted in Figure ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance/#how-do-we-qualify",children:"Catena-X Qualification Process"}),"."]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Qualification Process",src:t(4995).A+"",width:"1591",height:"505"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Qualification Process"})]}),"\n",(0,i.jsxs)(a.p,{children:["As of the Operating Model White Paper v.2.1, the process for qualification through training has yet to be established. It will be released on the Catena-X website as soon as it is available. Qualification through experience applies to all advisory service providers that registered for and participated in the Catena-X beta phase. If a company is interested in qualification and/or the proof of qualification, the first step is to contact the Catena-X Association via ",(0,i.jsx)(a.a,{href:"mailto:info@catena-x.net",children:"info@catena-x.net"}),". Further information and a first questionnaire to collect basic information about the company will then be made accessible."]}),"\n",(0,i.jsx)(a.h2,{id:"regulatory-framework",children:"Regulatory Framework"}),"\n",(0,i.jsxs)(a.p,{children:["The ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/governance-framework-for-data-space-operations",children:"Catena-X Regulatory Framework for data space operations"})," outlines the 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. To understand the layers of our Regulatory Framework, Catena-X uses flight levels as a metaphor (see Figure ",(0,i.jsx)(a.a,{href:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance/#regulatory-framework",children:"Catena-X Governance Framework flight levels"}),"):"]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Governance Framework flight levels",src:t(8636).A+"",width:"1701",height:"662"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Governance Framework flight levels"})]}),"\n",(0,i.jsxs)(a.p,{children:["Each higher-level cascades into the lower ones, and the lower levels align with those above. Each level comes with specific guidelines and resources but also responsibilities for participants in our data space. This Operating Model falls under the 30,000 ft level and is thus mandatory for all data space participants. Maintaining and updating our Regulatory Framework for data space operations lies within the responsibility of the Catena-X Association. All resources and normative documents included in the regulatory framework are listed on the ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/governance-framework-for-data-space-operations",children:"Catena-X website"}),"."]})]})}function h(e={}){const{wrapper:a}={...(0,n.R)(),...e.components};return a?(0,i.jsx)(a,{...e,children:(0,i.jsx)(l,{...e})}):l(e)}},5130:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-certification-process-5188b323c489dc3b8783cb25e078a8cf.png"},8636:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-governance-framework-flight-levels-eb3e47026bd2885a5180e41e529b5dd3.png"},3032:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-nomination-process-4ab5adfcbe19d906086d2c9784aad62c.png"},4995:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-qualification-process-cecb836c907111ca0c82681abea72b3c.png"},3485:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-standardization-process-df4553a1e20cbbd0726dc32b55eacb34.png"},3947:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/certified-operating-company-531b11afad6c5e656d308840540013ff.png"},2609:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/certified-provider-a9f19580a33e21651b270df4075d7682.png"},4675:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/certified-solution-4cbc5006ae66d72ec0c239e75b83e29e.png"},2909:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/qualified-advisor-59653148b29b5466ff8be87dedf565a4.png"},8453:(e,a,t)=>{t.d(a,{R:()=>o,x:()=>r});var i=t(6540);const n={},s=i.createContext(n);function o(e){const a=i.useContext(s);return i.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function r(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:o(e.components),i.createElement(s.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/8843b0b9.bee4b4e3.js b/assets/js/8843b0b9.bee4b4e3.js deleted file mode 100644 index 3367ddc3..00000000 --- a/assets/js/8843b0b9.bee4b4e3.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[1721],{6474:(e,a,t)=>{t.r(a),t.d(a,{assets:()=>d,contentTitle:()=>o,default:()=>h,frontMatter:()=>s,metadata:()=>r,toc:()=>c});var i=t(4848),n=t(8453);const s={sidebar_position:1},o="How: Data Space Governance",r={id:"operating-model/how-data-space-governance/how-data-space-governance",title:"How: Data Space Governance",description:"Standardization",source:"@site/docs/operating-model/how-data-space-governance/how-data-space-governance.md",sourceDirName:"operating-model/how-data-space-governance",slug:"/operating-model/how-data-space-governance/",permalink:"/docs/next/operating-model/how-data-space-governance/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"How: Data Space Operations",permalink:"/docs/next/operating-model/how-data-space-operations/"},next:{title:"How: Life Cycle Management",permalink:"/docs/next/operating-model/how-life-cycle-management/"}},d={},c=[{value:"Standardization",id:"standardization",level:2},{value:"Why do we standardize?",id:"why-do-we-standardize",level:3},{value:"What do we standardize?",id:"what-do-we-standardize",level:3},{value:"How do we standardize?",id:"how-do-we-standardize",level:3},{value:"Conformity Assessment",id:"conformity-assessment",level:2},{value:"Why do we certify?",id:"why-do-we-certify",level:3},{value:"What do we certify?",id:"what-do-we-certify",level:3},{value:"How do we certify?",id:"how-do-we-certify",level:3},{value:"Catena-X Labels",id:"catena-x-labels",level:3},{value:"Exceptions & Timeline for Release 23.09",id:"exceptions--timeline-for-release-2309",level:3},{value:"1. 45-day grace period to obtain valid certification after Release 3.2 (23.09)",id:"1-45-day-grace-period-to-obtain-valid-certification-after-release-32-2309",level:4},{value:"2. Certification of business applications vs. internal systems that fall under the definition of a Catena-X business application*",id:"2-certification-of-business-applications-vs-internal-systems-that-fall-under-the-definition-of-a-catena-x-business-application",level:4},{value:"3. No Catena-X Business Applications without listing on a certified CX Marketplace",id:"3-no-catena-x-business-applications-without-listing-on-a-certified-cx-marketplace",level:4},{value:"Nomination Process for unique Roles (e.g., CSP-B)",id:"nomination-process-for-unique-roles-eg-csp-b",level:2},{value:"Qualification Process",id:"qualification-process",level:2},{value:"Why do we qualify?",id:"why-do-we-qualify",level:3},{value:"Who do we qualify?",id:"who-do-we-qualify",level:3},{value:"How do we qualify?",id:"how-do-we-qualify",level:3},{value:"Regulatory Framework",id:"regulatory-framework",level:2}];function l(e){const a={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",h4:"h4",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",ul:"ul",...(0,n.R)(),...e.components};return(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(a.h1,{id:"how-data-space-governance",children:"How: Data Space Governance"}),"\n",(0,i.jsx)(a.h2,{id:"standardization",children:"Standardization"}),"\n",(0,i.jsx)(a.h3,{id:"why-do-we-standardize",children:"Why do we standardize?"}),"\n",(0,i.jsx)(a.p,{children:"The success of the digital transformation of the automotive industry critically depends on multilateral collaboration between all stakeholders along the automotive value chain. Our growing Catena-X ecosystem will enable enormous amounts of data to be integrated and collaboratively harnessed."}),"\n",(0,i.jsxs)(a.p,{children:["However, this vision is complex: companies at various stages of the automotive value chain, such as production, delivery, or logistics, often have their own IT systems to manage their data. To ensure that these complex data volumes can be sent, received, and processed smoothly across all stages of the value chain, we need one language for all players: ",(0,i.jsx)(a.strong,{children:"common standards and frameworks"}),"."]}),"\n",(0,i.jsx)(a.h3,{id:"what-do-we-standardize",children:"What do we standardize?"}),"\n",(0,i.jsx)(a.p,{children:"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."}),"\n",(0,i.jsxs)(a.p,{children:["The Catena-X Association publishes standards for generic core and enabling services as well as for domain-specific business applications (see KITs Chapter ",(0,i.jsx)(a.a,{href:"/docs/next/operating-model/what-service-map/#kits--keep-it-together",children:"KITs \u2013 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 ",(0,i.jsx)(a.a,{href:"https://catena-x.net/de/standard-library",children:"Catena-X standard library"}),"."]}),"\n",(0,i.jsx)(a.h3,{id:"how-do-we-standardize",children:"How do we standardize?"}),"\n",(0,i.jsxs)(a.p,{children:["Based on ",(0,i.jsx)(a.a,{href:"https://catena-x.net/fileadmin/user_upload/Vereinsdokumente/Catena-X_IP_Regelwerk_IP_Regulations.pdf",children:"Catena-X\u2019s Intellectual Property(IP)-Regulations"})," 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 ",(0,i.jsx)(a.a,{href:"/docs/next/operating-model/how-data-space-governance/#how-do-we-standardize",children:"Catena-X Standardization Process"}),":"]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Standardization Process",src:t(3485).A+"",width:"1492",height:"587"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Standardization Process"})]}),"\n",(0,i.jsxs)(a.p,{children:["The ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/standardisierung",children:"Catena-X standardization policy"})," provides a detailed description of how Catena-X standards are being developed including everyone involved and their respective responsibilities."]}),"\n",(0,i.jsx)(a.h2,{id:"conformity-assessment",children:"Conformity Assessment"}),"\n",(0,i.jsx)(a.h3,{id:"why-do-we-certify",children:"Why do we certify?"}),"\n",(0,i.jsx)(a.p,{children:"Cross company interactions highly rely on mutual trust. Our certifications provide trust via transparency and reliability based on our Catena-X standards. By setting up a certification process, we guarantee that our major principles are considered in every component of the network. From the core service providers to the data connectors and every single application in the network, a consistent framework was created to ensure beneficial participation for all participants in the network. A chain is only as strong as its weakest link, and to gain trust we need to ensure that all links are as strong as possible."}),"\n",(0,i.jsx)(a.h3,{id:"what-do-we-certify",children:"What do we certify?"}),"\n",(0,i.jsxs)(a.p,{children:["Catena-X certification is done in a modular, role-based way, to fulfill different requirements of participants in our ecosystem, whether IT application providers, service providers or onboarding partners. The modularity allows high flexibility and lowers the efforts and redundancies for all parties involved. Catena-X standards become mandatory for certification as soon as they have been integrated into the certification framework. The Catena-X Association aims to release an update of its certification framework simultaneously with newly released standards. The most current version can always be found on the ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/certification",children:"Catena-X website"}),"."]}),"\n",(0,i.jsx)(a.h3,{id:"how-do-we-certify",children:"How do we certify?"}),"\n",(0,i.jsxs)(a.p,{children:["An overview of the certification process is depicted in Figure ",(0,i.jsx)(a.a,{href:"/docs/next/operating-model/how-data-space-governance/#how-do-we-certify",children:"Catena-X Certification Process"}),".\n",(0,i.jsx)(a.img,{alt:"Catena-X Certification Process",src:t(5130).A+"",width:"1202",height:"692"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Certification Process"})]}),"\n",(0,i.jsxs)(a.p,{children:["The ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/certification",children:"Catena-X Conformity Assessment Framework Handbook"})," provides a detailed description of how Catena-X conducts conformity assessment through Conformity Assessment Bodies."]}),"\n",(0,i.jsx)(a.h3,{id:"catena-x-labels",children:"Catena-X Labels"}),"\n",(0,i.jsx)(a.p,{children:"Catena-X issues four different labels to help customers find suitable and legitimate providers for their needs. Each label is issued to the relevant role after achieving successful certification and/or qualification. Labels are associated with the offered services of the provider."}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Certified Operating Company"})," (CSP-A/CSP-B)\n",(0,i.jsx)(a.img,{alt:"Certified Operating Company",src:t(3947).A+"",width:"1103",height:"568"})]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Certified Provider"})," (e.g., BAP, ESP, OSP)\n",(0,i.jsx)(a.img,{alt:"Certified Provider",src:t(2609).A+"",width:"1103",height:"567"})]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Certified Solution"})," (e.g., Business App, Service\u2026.)\n",(0,i.jsx)(a.img,{alt:"Certified Solution",src:t(4675).A+"",width:"1110",height:"563"})]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"Qualified Advisor"})," (Advisory Provider)\n",(0,i.jsx)(a.img,{alt:"Qualified Advisor",src:t(2909).A+"",width:"1101",height:"563"})]}),"\n",(0,i.jsx)(a.p,{children:"Each label is obtained after successful completion of the Catena-X certification or qualification process. Details on pathways to be added."}),"\n",(0,i.jsx)(a.h3,{id:"exceptions--timeline-for-release-2309",children:"Exceptions & Timeline for Release 23.09"}),"\n",(0,i.jsx)(a.p,{children:"Release 23.09 is the official GoLive Release of the Catena-X data ecosystem. For the first time, all major components of the Catena-X data ecosystem will be available to the vast majority of the automotive value chain. To fulfil this promise to all our stakeholders while some areas of Catena-X are still under development, certain exceptions are made during this transitional period:"}),"\n",(0,i.jsx)(a.h4,{id:"1-45-day-grace-period-to-obtain-valid-certification-after-release-32-2309",children:"1. 45-day grace period to obtain valid certification after Release 3.2 (23.09)"}),"\n",(0,i.jsxs)(a.p,{children:["Catena-X will release a standard update (Release 3.2) on Sept. 28, 2023, on the Catena-X Association website. ",(0,i.jsx)(a.strong,{children:"This release will include \u201cbreaking changes\u201d as defined in the"})," ",(0,i.jsx)(a.a,{href:"https://semver.org/",children:"Semantic Versioning"}),"."]}),"\n",(0,i.jsxs)(a.p,{children:["The GoLive of the Catena-X data ecosystem (productive environment) will be ",(0,i.jsx)(a.strong,{children:"exclusively on Release 3.2"}),". This will be accompanied by an ",(0,i.jsx)(a.strong,{children:"update of the certification framework"})," (\u201cwhich role needs to have which components certified\u201d) for release 3.2."]}),"\n",(0,i.jsxs)(a.p,{children:["Each partner needs to ensure conformity to the new standards to be active in the data space. To this end, the following procedure applies: Every participant in the data space has ",(0,i.jsx)(a.strong,{children:"45 days after Sept. 28"})," (grace period) to complete their certification via a CAB or, in case of an existing certification, via free self-assessment. ",(0,i.jsx)(a.strong,{children:"Deadline is Nov. 12, 2023"})," (Sept. 28 + 45 days)."]}),"\n",(0,i.jsxs)(a.p,{children:["Cofinity-X will ",(0,i.jsx)(a.strong,{children:"allow data space registration"})," of a partner from GoLive Oct. 16 after consultation with the Association, ",(0,i.jsx)(a.strong,{children:"subject to the proviso that certification must be completed by the Nov. 12 deadline"}),". If the certificate is not proven within the 45 days, Partners must be removed from the data space at the direction of the Catena-X Association."]}),"\n",(0,i.jsxs)(a.p,{children:["Data space participants and their solutions that were already certified for Release 3.0/3.1 can use the 45-day grace period to prove their compliance to the Association via a ",(0,i.jsx)(a.strong,{children:"free self-assessment"})," and thus confirm the validity of their certificate even after release updates (up to a maximum of 12 months after initial issue). A corresponding form including confirmation of conformity with each standard required for the certificate can be requested from ",(0,i.jsx)(a.a,{href:"mailto:info@catena-x.net",children:"info@catena-x.net"}),". This does not apply to a CSP-B."]}),"\n",(0,i.jsx)(a.h4,{id:"2-certification-of-business-applications-vs-internal-systems-that-fall-under-the-definition-of-a-catena-x-business-application",children:"2. Certification of business applications vs. internal systems that fall under the definition of a Catena-X business application*"}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.strong,{children:"A business application"})," provides specific logic and schemas defined in a Catena-X use case (e. g., data processing, transformation functions) that is applied to input data to produce an expected output. This includes the transformation of data from an input format into an output format using Catena-X semantic models (semantic interoperability) as well as the technical data exchange using standardized protocols and API-specifications (technical interoperability). This does not apply to internal systems of an organization, such as internal databases, data lakes, data pipelines (ETL) or source systems. To become operational on the Catena-X data space, a business application must comply with the corresponding standards (see Chapter ",(0,i.jsx)(a.a,{href:"/docs/next/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),")."]}),"\n",(0,i.jsxs)(a.p,{children:["Companies connected to Catena-X might want to ",(0,i.jsx)(a.strong,{children:"connect certain internal systems"})," including company-internal business applications to the Catena-X network. It remains, however, crucial that all participants can rely on a standardized data exchange that guarantees stable data chains built on data sovereignty and interoperability."]}),"\n",(0,i.jsx)(a.p,{children:"Consequently, the following two principles apply:"}),"\n",(0,i.jsxs)(a.ul,{children:["\n",(0,i.jsx)(a.li,{children:"Everything that is necessary to uphold a stable data chain is required to follow Catena-X standards and has to be certified by a CAB."}),"\n",(0,i.jsx)(a.li,{children:"All business applications that are either associated with the Catena-X brand and/or are offered on a Catena-X marketplace are required to follow Catena-X standards and have to be certified by a CAB."}),"\n"]}),"\n",(0,i.jsx)(a.p,{children:"If an internal system fulfills one of these two criteria, a Catena-X certification is mandatory."}),"\n",(0,i.jsx)(a.p,{children:"*For future reference, to provide a scalable way of certification, additional technical and partially automated solutions\nof assessing conformity are currently under assessment. (10 votes for, 0 against \xe0 also Steve vote for publication)"}),"\n",(0,i.jsx)(a.h4,{id:"3-no-catena-x-business-applications-without-listing-on-a-certified-cx-marketplace",children:"3. No Catena-X Business Applications without listing on a certified CX Marketplace"}),"\n",(0,i.jsx)(a.p,{children:"Catena-X is built on trust. Consequently, certified Catena-X marketplaces (CSP-A) are checking, whether services provided are coming with verified credentials to ensure that the listed offer is trustworthy and conform to Catena-X standards."}),"\n",(0,i.jsx)(a.p,{children:"To further anchor this trust, all Catena-X related business applications and services require a listing on a Catena-X certified marketplace. Catena-X does not permit operating a Catena-X solution outside of a certified Catena-X market place."}),"\n",(0,i.jsxs)(a.p,{children:["As noted in Chapter ",(0,i.jsx)(a.a,{href:"/docs/next/operating-model/outlook/#increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),", as of release 23.12, Catena-X will provide the technical possibility for multiple CSP-A providers. This will foster multiple verifiers of credentials."]}),"\n",(0,i.jsx)(a.h2,{id:"nomination-process-for-unique-roles-eg-csp-b",children:"Nomination Process for unique Roles (e.g., CSP-B)"}),"\n",(0,i.jsx)(a.p,{children:"The nomination process is intended to ensure neutrality and trustworthy execution of selected roles and tasks within the Catena-X ecosystem. The Catena-X Association is responsible for the execution of the nomination process including partner selection."}),"\n",(0,i.jsxs)(a.p,{children:["The various rights and obligations of the provider are described in the Request for Tender (RFT). This is, for example, the license for operation, which can also be withdrawn in case of unfair behavior. This ensures fair awarding and safe operation of the various components. Tasks include, for example, the operation of Core Services - Section B by Core Service Providers or the certification of providers and solutions by CABs. An overview of the nomination process is depicted in Figure ",(0,i.jsx)(a.a,{href:"/docs/next/operating-model/how-data-space-governance/#nomination-process-for-unique-roles-eg-csp-b",children:"Catena-X Nomination Process"}),"."]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Nomination Process",src:t(3032).A+"",width:"1451",height:"652"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Nomination Process"})]}),"\n",(0,i.jsx)(a.p,{children:"The process steps of the nomination process are described in detail below."}),"\n",(0,i.jsxs)(a.table,{children:[(0,i.jsx)(a.thead,{children:(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.th,{children:"Process Step"}),(0,i.jsx)(a.th,{children:"Description"}),(0,i.jsx)(a.th,{children:"Input"}),(0,i.jsx)(a.th,{children:"Output"})]})}),(0,i.jsxs)(a.tbody,{children:[(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Create Request for Tender (RfT)"}),(0,i.jsx)(a.td,{children:"The Catena-X Association is responsible for the creation of the Request for Tender (RfT) document (e.g., for Core Services - section B)"}),(0,i.jsx)(a.td,{}),(0,i.jsx)(a.td,{children:"RfT Document(s)"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Publish RfT on Website"}),(0,i.jsxs)(a.td,{children:["The Catena-X Association is responsible for the publication and distribution of the ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/",children:"RfT Document on the website"}),"."]}),(0,i.jsx)(a.td,{children:"RfT Document(s)"}),(0,i.jsx)(a.td,{children:"RfT Document(s) RfT Event incl. Timeline RfT Template"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Create and Submit Tender for selected Core Service(s)"}),(0,i.jsx)(a.td,{children:"A provider can create and submit a tender for the published RfT."}),(0,i.jsx)(a.td,{children:"RfT Document RfT Event RfT Template"}),(0,i.jsx)(a.td,{children:"Tender"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Receive and Review Submissions"}),(0,i.jsx)(a.td,{children:"The CX Association compares the tender(s), regarding the fulfillment of the nomination criteria and creates a short list of candidates for the board."}),(0,i.jsx)(a.td,{children:"Tender(s)"}),(0,i.jsx)(a.td,{children:"Short List of Provider Candidates"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Select Provider"}),(0,i.jsx)(a.td,{children:"The board of the Association elects a provider with an absolute majority vote."}),(0,i.jsx)(a.td,{children:"Short List of Provider Candidates"}),(0,i.jsx)(a.td,{children:"Nomination of Provider"})]}),(0,i.jsxs)(a.tr,{children:[(0,i.jsx)(a.td,{children:"Inform Providers"}),(0,i.jsx)(a.td,{children:"The CX Association informs all provider(s) about the result of the nomination process."}),(0,i.jsx)(a.td,{}),(0,i.jsx)(a.td,{})]})]})]}),"\n",(0,i.jsx)(a.h2,{id:"qualification-process",children:"Qualification Process"}),"\n",(0,i.jsx)(a.h3,{id:"why-do-we-qualify",children:"Why do we qualify?"}),"\n",(0,i.jsx)(a.p,{children:"On the way to creating value with Catena-X, companies may be dependent on advisory services. The quality of these advisory services is decisive for the success of the participation and thus for the success of Catena-X. Catena-X can only be successful if it succeeds in integrating large parts of the automotive value chain. We assume that this will lead to a high demand for advisory services, which must be met. These advisory services must cover the needs of small and medium-sized companies as well as the needs of large companies, which have extended integration requirements."}),"\n",(0,i.jsx)(a.p,{children:"Advisory services are hard, if not impossible, to standardize. Consequently, conformity assessment of qualified advisory services cannot take place through certification. To maintain a consistent level of quality among advisory service providers in the Catena-X data space, the Catena-X Association thus offers a qualification process that is mandatory for all advisory service providers that want to get listed in a marketplace. Advisory service providers, like all other participants active on the Catena-X data space, must adhere to the Catena-X regulatory framework and thereby confirm their full and unconditional support of our data ecosystem including its mission and standards."}),"\n",(0,i.jsx)(a.h3,{id:"who-do-we-qualify",children:"Who do we qualify?"}),"\n",(0,i.jsx)(a.p,{children:"Catena-X invites advisory service providers of all kinds to support the successful onboarding of data space participants, SMEs in particular. One of the few prerequisites is the binding commitment to provide high-quality consulting at fair and reasonable costs. Catena-X supports this endeavor with information and predefined content as well as a qualification system to prove appropriate support and consulting competencies."}),"\n",(0,i.jsx)(a.h3,{id:"how-do-we-qualify",children:"How do we qualify?"}),"\n",(0,i.jsx)(a.p,{children:"There are two ways to become a Catena-X qualified advisory service provider."}),"\n",(0,i.jsxs)(a.ol,{children:["\n",(0,i.jsx)(a.li,{children:"Qualification through training"}),"\n",(0,i.jsx)(a.li,{children:"Qualification through existing experience"}),"\n"]}),"\n",(0,i.jsxs)(a.p,{children:["For most advisory service providers, the first option applies. Qualification through existing experience is a path offered to advisory service providers that have gained experience by actively contributing to the Catena-X ecosystem either by directly accompanying companies within the Catena-X beta phase or contributing directly to the Catena-X kickstarter consortium as a listed member. An overview of the qualification process is depicted in Figure ",(0,i.jsx)(a.a,{href:"/docs/next/operating-model/how-data-space-governance/#how-do-we-qualify",children:"Catena-X Qualification Process"}),"."]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Qualification Process",src:t(4995).A+"",width:"1591",height:"505"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Qualification Process"})]}),"\n",(0,i.jsxs)(a.p,{children:["As of the Operating Model White Paper v.2.1, the process for qualification through training has yet to be established. It will be released on the Catena-X website as soon as it is available. Qualification through experience applies to all advisory service providers that registered for and participated in the Catena-X beta phase. If a company is interested in qualification and/or the proof of qualification, the first step is to contact the Catena-X Association via ",(0,i.jsx)(a.a,{href:"mailto:info@catena-x.net",children:"info@catena-x.net"}),". Further information and a first questionnaire to collect basic information about the company will then be made accessible."]}),"\n",(0,i.jsx)(a.h2,{id:"regulatory-framework",children:"Regulatory Framework"}),"\n",(0,i.jsxs)(a.p,{children:["The ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/governance-framework-for-data-space-operations",children:"Catena-X Regulatory Framework for data space operations"})," outlines the 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. To understand the layers of our Regulatory Framework, Catena-X uses flight levels as a metaphor (see Figure ",(0,i.jsx)(a.a,{href:"/docs/next/operating-model/how-data-space-governance/#regulatory-framework",children:"Catena-X Governance Framework flight levels"}),"):"]}),"\n",(0,i.jsxs)(a.p,{children:[(0,i.jsx)(a.img,{alt:"Catena-X Governance Framework flight levels",src:t(8636).A+"",width:"1701",height:"662"}),"\n",(0,i.jsx)(a.em,{children:"Catena-X Governance Framework flight levels"})]}),"\n",(0,i.jsxs)(a.p,{children:["Each higher-level cascades into the lower ones, and the lower levels align with those above. Each level comes with specific guidelines and resources but also responsibilities for participants in our data space. This Operating Model falls under the 30,000 ft level and is thus mandatory for all data space participants. Maintaining and updating our Regulatory Framework for data space operations lies within the responsibility of the Catena-X Association. All resources and normative documents included in the regulatory framework are listed on the ",(0,i.jsx)(a.a,{href:"https://catena-x.net/en/catena-x-introduce-implement/governance-framework-for-data-space-operations",children:"Catena-X website"}),"."]})]})}function h(e={}){const{wrapper:a}={...(0,n.R)(),...e.components};return a?(0,i.jsx)(a,{...e,children:(0,i.jsx)(l,{...e})}):l(e)}},5130:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-certification-process-5188b323c489dc3b8783cb25e078a8cf.png"},8636:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-governance-framework-flight-levels-eb3e47026bd2885a5180e41e529b5dd3.png"},3032:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-nomination-process-4ab5adfcbe19d906086d2c9784aad62c.png"},4995:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-qualification-process-cecb836c907111ca0c82681abea72b3c.png"},3485:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/catena-x-standardization-process-df4553a1e20cbbd0726dc32b55eacb34.png"},3947:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/certified-operating-company-531b11afad6c5e656d308840540013ff.png"},2609:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/certified-provider-a9f19580a33e21651b270df4075d7682.png"},4675:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/certified-solution-4cbc5006ae66d72ec0c239e75b83e29e.png"},2909:(e,a,t)=>{t.d(a,{A:()=>i});const i=t.p+"assets/images/qualified-advisor-59653148b29b5466ff8be87dedf565a4.png"},8453:(e,a,t)=>{t.d(a,{R:()=>o,x:()=>r});var i=t(6540);const n={},s=i.createContext(n);function o(e){const a=i.useContext(s);return i.useMemo((function(){return"function"==typeof e?e(a):{...a,...e}}),[a,e])}function r(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:o(e.components),i.createElement(s.Provider,{value:a},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/8acd709f.f254a944.js b/assets/js/8acd709f.f254a944.js deleted file mode 100644 index 54244ebb..00000000 --- a/assets/js/8acd709f.f254a944.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[4047],{6989:(e,n,o)=>{o.r(n),o.d(n,{assets:()=>d,contentTitle:()=>s,default:()=>u,frontMatter:()=>r,metadata:()=>a,toc:()=>c});var t=o(4848),i=o(8453);const r={sidebar_position:1,title:"Overview Working Model"},s=void 0,a={id:"working-model/overview",title:"Overview Working Model",description:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.",source:"@site/versioned_docs/version-24.03/working-model/overview.md",sourceDirName:"working-model",slug:"/working-model/overview",permalink:"/docs/working-model/overview",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Overview Working Model"},sidebar:"sidebar_working_model"},d={},c=[];function l(e){const n={admonition:"admonition",p:"p",...(0,i.R)(),...e.components};return(0,t.jsx)(n.admonition,{type:"danger",children:(0,t.jsx)(n.p,{children:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation."})})}function u(e={}){const{wrapper:n}={...(0,i.R)(),...e.components};return n?(0,t.jsx)(n,{...e,children:(0,t.jsx)(l,{...e})}):l(e)}},8453:(e,n,o)=>{o.d(n,{R:()=>s,x:()=>a});var t=o(6540);const i={},r=t.createContext(i);function s(e){const n=t.useContext(r);return t.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function a(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:s(e.components),t.createElement(r.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/8acd709f.f97fb67c.js b/assets/js/8acd709f.f97fb67c.js new file mode 100644 index 00000000..a2176091 --- /dev/null +++ b/assets/js/8acd709f.f97fb67c.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[4047],{6989:(e,n,o)=>{o.r(n),o.d(n,{assets:()=>d,contentTitle:()=>s,default:()=>u,frontMatter:()=>r,metadata:()=>a,toc:()=>c});var t=o(4848),i=o(8453);const r={sidebar_position:1,title:"Overview Working Model"},s=void 0,a={id:"working-model/overview",title:"Overview Working Model",description:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.",source:"@site/versioned_docs/version-24.03/working-model/overview.md",sourceDirName:"working-model",slug:"/working-model/overview",permalink:"/catenax-ev.github.io.new/docs/working-model/overview",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Overview Working Model"},sidebar:"sidebar_working_model"},d={},c=[];function l(e){const n={admonition:"admonition",p:"p",...(0,i.R)(),...e.components};return(0,t.jsx)(n.admonition,{type:"danger",children:(0,t.jsx)(n.p,{children:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation."})})}function u(e={}){const{wrapper:n}={...(0,i.R)(),...e.components};return n?(0,t.jsx)(n,{...e,children:(0,t.jsx)(l,{...e})}):l(e)}},8453:(e,n,o)=>{o.d(n,{R:()=>s,x:()=>a});var t=o(6540);const i={},r=t.createContext(i);function s(e){const n=t.useContext(r);return t.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function a(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:s(e.components),t.createElement(r.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/925b3f96.0c146a7d.js b/assets/js/925b3f96.0c146a7d.js new file mode 100644 index 00000000..6c4f87b4 --- /dev/null +++ b/assets/js/925b3f96.0c146a7d.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8609],{5026:(t,e,o)=>{o.r(e),o.d(e,{assets:()=>r,contentTitle:()=>a,default:()=>g,frontMatter:()=>n,metadata:()=>u,toc:()=>l});var s=o(4848),i=o(8453);const n={slug:"first-blog-post",title:"First Blog Post",authors:{name:"Gao Wei",title:"Docusaurus Core Team",url:"https://github.com/wgao19",image_url:"https://github.com/wgao19.png"},tags:["hola","docusaurus"]},a=void 0,u={permalink:"/catenax-ev.github.io.new/blog/first-blog-post",source:"@site/blog/2019-05-28-first-blog-post.md",title:"First Blog Post",description:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet",date:"2019-05-28T00:00:00.000Z",tags:[{inline:!1,label:"Hola",permalink:"/catenax-ev.github.io.new/blog/tags/hola",description:"Hola tag description"},{inline:!1,label:"Docusaurus",permalink:"/catenax-ev.github.io.new/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:.12,hasTruncateMarker:!1,authors:[{name:"Gao Wei",title:"Docusaurus Core Team",url:"https://github.com/wgao19",image_url:"https://github.com/wgao19.png",imageURL:"https://github.com/wgao19.png"}],frontMatter:{slug:"first-blog-post",title:"First Blog Post",authors:{name:"Gao Wei",title:"Docusaurus Core Team",url:"https://github.com/wgao19",image_url:"https://github.com/wgao19.png",imageURL:"https://github.com/wgao19.png"},tags:["hola","docusaurus"]},unlisted:!1,prevItem:{title:"Long Blog Post",permalink:"/catenax-ev.github.io.new/blog/long-blog-post"}},r={authorsImageUrls:[void 0]},l=[];function c(t){const e={p:"p",...(0,i.R)(),...t.components};return(0,s.jsx)(e.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"})}function g(t={}){const{wrapper:e}={...(0,i.R)(),...t.components};return e?(0,s.jsx)(e,{...t,children:(0,s.jsx)(c,{...t})}):c(t)}},8453:(t,e,o)=>{o.d(e,{R:()=>a,x:()=>u});var s=o(6540);const i={},n=s.createContext(i);function a(t){const e=s.useContext(n);return s.useMemo((function(){return"function"==typeof t?t(e):{...e,...t}}),[e,t])}function u(t){let e;return e=t.disableParentContext?"function"==typeof t.components?t.components(i):t.components||i:a(t.components),s.createElement(n.Provider,{value:e},t.children)}}}]); \ No newline at end of file diff --git a/assets/js/925b3f96.32f6b67d.js b/assets/js/925b3f96.32f6b67d.js deleted file mode 100644 index ede69375..00000000 --- a/assets/js/925b3f96.32f6b67d.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8609],{5026:(t,e,o)=>{o.r(e),o.d(e,{assets:()=>r,contentTitle:()=>a,default:()=>m,frontMatter:()=>n,metadata:()=>u,toc:()=>l});var s=o(4848),i=o(8453);const n={slug:"first-blog-post",title:"First Blog Post",authors:{name:"Gao Wei",title:"Docusaurus Core Team",url:"https://github.com/wgao19",image_url:"https://github.com/wgao19.png"},tags:["hola","docusaurus"]},a=void 0,u={permalink:"/blog/first-blog-post",source:"@site/blog/2019-05-28-first-blog-post.md",title:"First Blog Post",description:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet",date:"2019-05-28T00:00:00.000Z",tags:[{inline:!1,label:"Hola",permalink:"/blog/tags/hola",description:"Hola tag description"},{inline:!1,label:"Docusaurus",permalink:"/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:.12,hasTruncateMarker:!1,authors:[{name:"Gao Wei",title:"Docusaurus Core Team",url:"https://github.com/wgao19",image_url:"https://github.com/wgao19.png",imageURL:"https://github.com/wgao19.png"}],frontMatter:{slug:"first-blog-post",title:"First Blog Post",authors:{name:"Gao Wei",title:"Docusaurus Core Team",url:"https://github.com/wgao19",image_url:"https://github.com/wgao19.png",imageURL:"https://github.com/wgao19.png"},tags:["hola","docusaurus"]},unlisted:!1,prevItem:{title:"Long Blog Post",permalink:"/blog/long-blog-post"}},r={authorsImageUrls:[void 0]},l=[];function c(t){const e={p:"p",...(0,i.R)(),...t.components};return(0,s.jsx)(e.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"})}function m(t={}){const{wrapper:e}={...(0,i.R)(),...t.components};return e?(0,s.jsx)(e,{...t,children:(0,s.jsx)(c,{...t})}):c(t)}},8453:(t,e,o)=>{o.d(e,{R:()=>a,x:()=>u});var s=o(6540);const i={},n=s.createContext(i);function a(t){const e=s.useContext(n);return s.useMemo((function(){return"function"==typeof t?t(e):{...e,...t}}),[e,t])}function u(t){let e;return e=t.disableParentContext?"function"==typeof t.components?t.components(i):t.components||i:a(t.components),s.createElement(n.Provider,{value:e},t.children)}}}]); \ No newline at end of file diff --git a/assets/js/9bc6bf15.38bcf64b.js b/assets/js/9bc6bf15.38bcf64b.js new file mode 100644 index 00000000..4f9fd0ad --- /dev/null +++ b/assets/js/9bc6bf15.38bcf64b.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[7803],{1066:(e,t,i)=>{i.r(t),i.d(t,{assets:()=>d,contentTitle:()=>r,default:()=>c,frontMatter:()=>o,metadata:()=>a,toc:()=>l});var n=i(4848),s=i(8453);const o={sidebar_position:1,title:"Catena-X association"},r=void 0,a={id:"working-model/organizational-structure/overview-roles/catena-x-roles",title:"Catena-X association",description:"General",source:"@site/docs/working-model/02-organizational-structure/overview-roles/catena-x-roles.md",sourceDirName:"working-model/02-organizational-structure/overview-roles",slug:"/working-model/organizational-structure/overview-roles/catena-x-roles",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Catena-X association"},sidebar:"sidebar_working_model",previous:{title:"Overview of roles and groups",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/"},next:{title:"Tractus-X",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles"}},d={},l=[{value:"General",id:"general",level:2},{value:"RASIC matrix for association bodies",id:"rasic-matrix-for-association-bodies",level:2},{value:"Management board",id:"management-board",level:2},{value:"Association Strategy",id:"association-strategy",level:3},{value:"Tasks and Responsibilities",id:"tasks-and-responsibilities",level:3},{value:"Management board roles",id:"management-board-roles",level:3},{value:"Board sponsor",id:"board-sponsor",level:4},{value:"Mediation board member",id:"mediation-board-member",level:4},{value:"Committee",id:"committee",level:2},{value:"Committee roles",id:"committee-roles",level:3},{value:"Lead and Co-Lead",id:"lead-and-co-lead",level:4},{value:"Mentor for Expert Groups (optional)",id:"mentor-for-expert-groups-optional",level:4},{value:"Business domain strategy",id:"business-domain-strategy",level:3},{value:"Communication",id:"communication",level:3},{value:"Alignment with Other Committees",id:"alignment-with-other-committees",level:4},{value:"Assigning and Mentoring Expert Groups",id:"assigning-and-mentoring-expert-groups",level:4},{value:"Feature Review",id:"feature-review",level:4},{value:"Feature Prioritization",id:"feature-prioritization",level:4},{value:"Tasks",id:"tasks",level:3},{value:"Powers",id:"powers",level:3},{value:"Responsibilities",id:"responsibilities",level:3},{value:"Election",id:"election",level:3},{value:"Decision Making & Communication",id:"decision-making--communication",level:3},{value:"Escalation Paths",id:"escalation-paths",level:3},{value:"Expert Group",id:"expert-group",level:2},{value:"Functional level strategy",id:"functional-level-strategy",level:3},{value:"Tasks and responsibilities for Expert Groups",id:"tasks-and-responsibilities-for-expert-groups",level:3},{value:"Existing Expert Groups",id:"existing-expert-groups",level:3},{value:"Expert Group Election",id:"expert-group-election",level:3},{value:"Request Submission",id:"request-submission",level:4},{value:"Initial validation",id:"initial-validation",level:4},{value:"Onepager creation",id:"onepager-creation",level:4},{value:"Final validation",id:"final-validation",level:4},{value:"Application Phase",id:"application-phase",level:4},{value:"Expert Group composition",id:"expert-group-composition",level:4},{value:"Expert Group approval",id:"expert-group-approval",level:4},{value:"Notification and Kick-off",id:"notification-and-kick-off",level:4},{value:"Review Group Formation",id:"review-group-formation",level:4},{value:"Kickoff",id:"kickoff",level:4},{value:"Expert Group maintenance over the life time",id:"expert-group-maintenance-over-the-life-time",level:3},{value:"Replacement of Expert Group members",id:"replacement-of-expert-group-members",level:4},{value:"Adding additional members",id:"adding-additional-members",level:4},{value:"Closing of Expert Groups",id:"closing-of-expert-groups",level:3},{value:"Expert Group Decision Making & Communication",id:"expert-group-decision-making--communication",level:3},{value:"Expert Group Escalation Paths",id:"expert-group-escalation-paths",level:3},{value:"Catena-X office",id:"catena-x-office",level:2}];function h(e){const t={a:"a",h2:"h2",h3:"h3",h4:"h4",img:"img",li:"li",p:"p",strong:"strong",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",ul:"ul",...(0,s.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(t.h2,{id:"general",children:"General"}),"\n",(0,n.jsxs)(t.p,{children:["The ",(0,n.jsx)(t.strong,{children:"Catena-X Automotive Network e.V."})," is often referred to as 'the association'. It is important to understand that the association consists of four bodies with different tasks and responsibilities. The association bodies are:"]}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"The Management board"}),"\n",(0,n.jsx)(t.li,{children:"Committees"}),"\n",(0,n.jsx)(t.li,{children:"Expert Groups"}),"\n",(0,n.jsx)(t.li,{children:"Catena-X office"}),"\n"]}),"\n",(0,n.jsx)(t.p,{children:(0,n.jsx)(t.img,{alt:"The association",src:i(3068).A+""})}),"\n",(0,n.jsx)(t.p,{children:"As the association, all four bodies aim to advance Catena-X as the leading global data ecosystem for the automotive value chain. In order to do so they follow the SOAR model."}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"S"})," = Standardizes to lay the foundation/basis for the ecosystem"]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"O"})," = Orchestrates to structure and organize the ecosystem"]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"A"})," = Activates by making standards applicable and relevant"]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"R"})," = Represent as the only ones speaking for Catena-X"]}),"\n"]}),"\n",(0,n.jsx)(t.p,{children:(0,n.jsx)(t.img,{alt:"C-X Office SOAR",src:i(3).A+""})}),"\n",(0,n.jsx)(t.p,{children:"Please note that while this page captures the essence of the Committee and the Expert Group roles, it is not exhaustive. The dynamic nature of the association means that roles can evolve, and members of the Committee and Expert Groups may engage in additional activities beyond what is described here. The descriptions below are intended to serve as a guide, providing a clear indication of the expected contributions of the Committee and the Expert Groups, yet it allows for flexibility and adaptation as the project and its needs grow and change."}),"\n",(0,n.jsx)(t.h2,{id:"rasic-matrix-for-association-bodies",children:"RASIC matrix for association bodies"}),"\n",(0,n.jsxs)(t.table,{children:[(0,n.jsx)(t.thead,{children:(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.th,{}),(0,n.jsx)(t.th,{children:"R = Responsible; A = Accountable; S = Supportive; I = Informed; C = Consulted"}),(0,n.jsx)(t.th,{children:"Management board"}),(0,n.jsx)(t.th,{}),(0,n.jsx)(t.th,{children:"Committee"}),(0,n.jsx)(t.th,{}),(0,n.jsx)(t.th,{}),(0,n.jsx)(t.th,{children:"Expert Group"}),(0,n.jsx)(t.th,{}),(0,n.jsx)(t.th,{children:"Catena-X office"})]})}),(0,n.jsxs)(t.tbody,{children:[(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"Member"}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#board-sponsor",children:"Sponsor"})}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#lead-and-co-lead",children:"Lead"})}),(0,n.jsx)(t.td,{children:"Member"}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#mentor-for-expert-groups-optional",children:"Mentor"})}),(0,n.jsx)(t.td,{children:"Lead"}),(0,n.jsx)(t.td,{children:"Member"}),(0,n.jsx)(t.td,{})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Strategy"}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#association-strategy",children:"Develop and maintain the Association Stratgey"})}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"S"})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#business-domain-strategy",children:"Develop and maintain the business domain strategy"})}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{children:"A,C"}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{children:"S"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{children:"S"})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#functional-level-strategy",children:"Develop and maintain a strategy on functional level"})}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"C"}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{children:"S"}),(0,n.jsx)(t.td,{children:"S"})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Mgmt. of association bodies"}),(0,n.jsx)(t.td,{children:"Setup Committees"}),(0,n.jsx)(t.td,{children:"R,A"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"S"})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"Close Committees"}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{children:"C"}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#expert-group-election",children:"Setup Expert Groups"})}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"C"}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"S"})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#closing-of-expert-groups",children:"Close Expert Groups"})}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"C"}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{children:"C,I"}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{children:"S"})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Development"}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production#create-new-feature-proposal",children:"Develop new feature requests"})}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"C"}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production#check-strategic-fit",children:"Approve features requests"})}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{children:"S"}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"Foster the development of features by providing development resources"}),(0,n.jsx)(t.td,{children:"S"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"S"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"A,R"}),(0,n.jsx)(t.td,{})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"Remove impediments for the features development / for Expert Group(s)"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"C"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"S"}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Promote"}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#communication",children:"Promote the use cases of the business domain inside and outside the association"})}),(0,n.jsx)(t.td,{children:"S"}),(0,n.jsx)(t.td,{children:"C"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"S"})]})]})]}),"\n",(0,n.jsx)(t.p,{children:'The RASIC should provide an overview of the tasks the Association bodies are engaging in. Each individual in the mgmt. board, a Committee or an Expert Group is at least a "member". If one takes over additional roles, e.g. as "Lead", the responsibilities of that role are added to those as member.'}),"\n",(0,n.jsx)(t.h2,{id:"management-board",children:"Management board"}),"\n",(0,n.jsx)(t.h3,{id:"association-strategy",children:"Association Strategy"}),"\n",(0,n.jsx)(t.p,{children:"The Management Board is responsible to develop, maintain and communicate the Association strategy. The strategy focuses on the overall mission, vision, and long-term objectives of the Association. It defines the broad purpose of the Association and its key goals."}),"\n",(0,n.jsx)(t.p,{children:"Decisions include determining the areas of focus for the Association, establishing partnerships, and setting the overall direction. This level may also involve decisions about expanding the Association's reach or services."}),"\n",(0,n.jsx)(t.p,{children:"The primary goal is to enhance the value provided to members and other stakeholders, ensuring the Association\u2019s sustainability and growth. This might involve increasing membership, enhancing influence, or expanding the range of services offered."}),"\n",(0,n.jsx)(t.h3,{id:"tasks-and-responsibilities",children:"Tasks and Responsibilities"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Approving of requests for new Committees"}),"\n",(0,n.jsx)(t.li,{children:"Appointment of Committee leaders"}),"\n",(0,n.jsx)(t.li,{children:"Preliminary selection of applicants for Committees"}),"\n",(0,n.jsx)(t.li,{children:"Approving of final composition of Committees"}),"\n",(0,n.jsx)(t.li,{children:"Mentoring of Committees"}),"\n",(0,n.jsx)(t.li,{children:"Last point of escalation"}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"management-board-roles",children:"Management board roles"}),"\n",(0,n.jsx)(t.h4,{id:"board-sponsor",children:"Board sponsor"}),"\n",(0,n.jsx)(t.h4,{id:"mediation-board-member",children:"Mediation board member"}),"\n",(0,n.jsx)(t.h2,{id:"committee",children:"Committee"}),"\n",(0,n.jsx)(t.p,{children:"The Committee plays a pivotal role in steering the direction of the open source project. This role description serves as a framework outlining the key responsibilities and tasks associated with the Committee. It provides a structured overview of the governance, communication strategies, and operational tasks that are central to the Committee's function within the organization."}),"\n",(0,n.jsx)(t.p,{children:"The Committee is encouraged to embrace this adaptability, taking initiative to address emerging challenges and opportunities, and to collaborate with other Committees and Expert Groups to achieve the organization's objectives. The success of the project hinges on the proactive and collaborative efforts of the Committee to lead with vision, communicate effectively, and prioritize features that align with our mission and strategic goals."}),"\n",(0,n.jsxs)(t.p,{children:["Committees are specialized bodies appointed by the board to address specific topics or tasks relevant to the association and the related eco system. Within the Catena-X Automotive Network e.V., the purpose and mandate of these Committees are to formulate recommendations for the board's decisions regarding matters to the association, in alignment with Catena-X's roadmap and the organization's strategic direction. Which means, they are responsible for the ",(0,n.jsx)(t.strong,{children:"mission"}),", ",(0,n.jsx)(t.strong,{children:"vision"})," and the ",(0,n.jsx)(t.strong,{children:"roadmap"})," related to their specific topic."]}),"\n",(0,n.jsx)(t.p,{children:"The Committee is also responsible for electing and managing the needed Expert Groups to work on specific tasks."}),"\n",(0,n.jsxs)(t.p,{children:["For more information please refer to the ",(0,n.jsx)(t.a,{href:"https://catena-x.net",children:"Framework for Committees"}),"."]}),"\n",(0,n.jsx)(t.p,{children:"There is already a list of Committees that have been established and are currently active. The list includes the following Committees:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Network Service Committee"}),"\n",(0,n.jsx)(t.li,{children:"Architecture Management Committee"}),"\n",(0,n.jsx)(t.li,{children:"..."}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"committee-roles",children:"Committee roles"}),"\n",(0,n.jsx)(t.h4,{id:"lead-and-co-lead",children:"Lead and Co-Lead"}),"\n",(0,n.jsx)(t.p,{children:"Every Committee must elect a Lead and a Co-Lead. Both act as first point of contact for any inquiries and requests towards the Committee. Further the leads are required to take care of the following taks:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"The leaders of the Committee appoint the Committee members based on the preliminary selection of applications by the board and their existing professional expertise."}),"\n",(0,n.jsx)(t.li,{children:"Creation of work packages in alignment with the other Committee members"}),"\n"]}),"\n",(0,n.jsx)(t.p,{children:"If the leads see fit they can they can handover the exectution of the task to other Committee members or create additional roles if they see fit. The general intention for the lead role is to be first among equals by keeping the strings together."}),"\n",(0,n.jsx)(t.h4,{id:"mentor-for-expert-groups-optional",children:"Mentor for Expert Groups (optional)"}),"\n",(0,n.jsx)(t.p,{children:"For each Expert Group associated to a Committee, a member of the Committee must be nominated as mentor. The mentor should a senior matter expert in the respective field of the Expert Group. The mentor works as interface to the Expert Groups and provide mentoring to ensure the success of the Expert Group."}),"\n",(0,n.jsx)(t.h3,{id:"business-domain-strategy",children:"Business domain strategy"}),"\n",(0,n.jsx)(t.p,{children:"The Committee is responsible for developing a clear and forward-looking strategy for the business domain. The strategy should contain a vision guides the direction for the coming years and serve as a beacon for all strategic decisions."}),"\n",(0,n.jsx)(t.p,{children:"Decisions at this level focus on how each Expert Group can effectively contribute to the overall mission and goals of the association."}),"\n",(0,n.jsx)(t.p,{children:"The main goal is to ensure that each Expert Group is effective in serving the members and supporting the association\u2019s objectives."}),"\n",(0,n.jsx)(t.p,{children:"The Committee creates a roadmap outlining key initiatives and milestones for the upcoming year. This roadmap is continuously reviewed and updated to respond to changes in the market and within the organization."}),"\n",(0,n.jsx)(t.h3,{id:"communication",children:"Communication"}),"\n",(0,n.jsx)(t.p,{children:"The Committee promotes the organization and its projects within the broader community. It builds relationships with other organizations and organizes events to foster engagement and collaboration. The group works closely with committers and members of Expert Groups to ensure a deep understanding of ongoing activities and the needs of the organization."}),"\n",(0,n.jsx)(t.h4,{id:"alignment-with-other-committees",children:"Alignment with Other Committees"}),"\n",(0,n.jsx)(t.p,{children:"The Committee coordinates its activities with other Committees to ensure a unified strategy and direction."}),"\n",(0,n.jsx)(t.h4,{id:"assigning-and-mentoring-expert-groups",children:"Assigning and Mentoring Expert Groups"}),"\n",(0,n.jsx)(t.p,{children:"The Committee is responsible for assigning tasks to Expert Groups and providing support and mentoring to ensure their success."}),"\n",(0,n.jsx)(t.h4,{id:"feature-review",children:"Feature Review"}),"\n",(0,n.jsx)(t.p,{children:"The Committee reviews contributions to the projects for quality, security, and functionality to ensure they meet the organization's standards."}),"\n",(0,n.jsx)(t.h4,{id:"feature-prioritization",children:"Feature Prioritization"}),"\n",(0,n.jsx)(t.p,{children:"The Committee prioritizes features on a cross-Expert Group level, focusing on the needs of the organization and the market."}),"\n",(0,n.jsx)(t.h3,{id:"tasks",children:"Tasks"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:["Vision and big picture","\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Develop and maintain a forward-looking vision for the domain"}),"\n",(0,n.jsx)(t.li,{children:"Create a roadmap outlining key initiatives and milestones"}),"\n"]}),"\n"]}),"\n",(0,n.jsxs)(t.li,{children:["Gate keeping","\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Evaluate the strategic fit for standard (change) requests"}),"\n",(0,n.jsx)(t.li,{children:"Evaluate the strategic fit for feature requests (in Tractus-X)"}),"\n",(0,n.jsx)(t.li,{children:"Analyze / Request details on dependencies between features"}),"\n",(0,n.jsx)(t.li,{children:"Provide feedback upfront to refinement and planning regarding missing details or proposal against mission/vision"}),"\n",(0,n.jsx)(t.li,{children:"Prioritize roadmap at feature level in alignment with Expert Groups"}),"\n",(0,n.jsx)(t.li,{children:"Define status/readiness for planning"}),"\n"]}),"\n"]}),"\n",(0,n.jsxs)(t.li,{children:["Expert Group supervision","\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Initiate new Expert Group in their domain"}),"\n",(0,n.jsx)(t.li,{children:"Close Expert Groups if needed"}),"\n",(0,n.jsx)(t.li,{children:"Review applications for new Expert Groups"}),"\n",(0,n.jsxs)(t.li,{children:["provide mentoring to Expert Groups (see ",(0,n.jsx)(t.a,{href:"#mentor-for-expert-groups-optional",children:"Mentor"}),")"]}),"\n"]}),"\n"]}),"\n",(0,n.jsxs)(t.li,{children:["Knowledge transfer","\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Promote the knowledge transfer for the domain to other association bodies"}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"powers",children:"Powers"}),"\n",(0,n.jsx)(t.h3,{id:"responsibilities",children:"Responsibilities"}),"\n",(0,n.jsx)(t.h3,{id:"election",children:"Election"}),"\n",(0,n.jsx)(t.h3,{id:"decision-making--communication",children:"Decision Making & Communication"}),"\n",(0,n.jsx)(t.h3,{id:"escalation-paths",children:"Escalation Paths"}),"\n",(0,n.jsx)(t.h2,{id:"expert-group",children:"Expert Group"}),"\n",(0,n.jsx)(t.p,{children:"The aim of the Expert Groups within the Catena-X Automotive Network e.V. is to develop results together with the members in line with the association's strategic direction. The Expert Groups are managed by the related Committee. The Expert Groups don't exist forever. They work on dedicated topics, present the results to the Committee and are then retired."}),"\n",(0,n.jsx)(t.p,{children:(0,n.jsx)(t.img,{alt:"Expert Group Lifeline",src:i(7853).A+""})}),"\n",(0,n.jsx)(t.h3,{id:"functional-level-strategy",children:"Functional level strategy"}),"\n",(0,n.jsx)(t.p,{children:"The functional level strategy involves the specific operational activities within a Expert Groups. It deals with the day-to-day tasks and processes that need to be executed to support the business domain strategy."}),"\n",(0,n.jsx)(t.p,{children:"The focus lies on implementation, realisation and the delivery of tangible results."}),"\n",(0,n.jsx)(t.h3,{id:"tasks-and-responsibilities-for-expert-groups",children:"Tasks and responsibilities for Expert Groups"}),"\n",(0,n.jsx)(t.p,{children:"In addition to the results to be elaborated in terms of content, the working groups have to fulfil the following, overarching tasks:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Elaboration of the strategic orientation"}),"\n",(0,n.jsx)(t.li,{children:"Advancing standardisation"}),"\n",(0,n.jsx)(t.li,{children:"Realisation of the strategic roadmap of the association"}),"\n",(0,n.jsx)(t.li,{children:"Harmonisation of interests"}),"\n",(0,n.jsx)(t.li,{children:"Achieving majority feedback on the orientation of the association"}),"\n",(0,n.jsx)(t.li,{children:"Identifying areas for action"}),"\n",(0,n.jsx)(t.li,{children:"Focus on tangible results"}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"existing-expert-groups",children:"Existing Expert Groups"}),"\n",(0,n.jsx)(t.p,{children:"There is already a list of groups that have been established and are currently active. The list includes the following groups:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"..."}),"\n",(0,n.jsx)(t.li,{children:"..."}),"\n",(0,n.jsx)(t.li,{children:"..."}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"expert-group-election",children:"Expert Group Election"}),"\n",(0,n.jsx)(t.p,{children:"Association members can join any Expert Groups by applying for open seats. The recommended size for Expert Groups is 5 to 15 core team members. Less core team members might indicated that the topic is not relevant enough to the assosciation and cause the Expert Group not being established. More core team members would make the Expert Group to inflexible and a split of the Expert Group might be considered."}),"\n",(0,n.jsx)(t.p,{children:"The composition of the core team is considering a balance between OEM, tier-1, tier-2, tier-n and small, medium and large sized companies with up to one participant per company with one voting right per company."}),"\n",(0,n.jsx)(t.p,{children:"The members of the core team are selected according to the following criteria:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Proper expertise in the relevant field of the Expert Group"}),"\n",(0,n.jsx)(t.li,{children:"Minimum availability of 20 hours per month, more is a plus"}),"\n",(0,n.jsx)(t.li,{children:"Commitment to regular, active participation and active contribution"}),"\n"]}),"\n",(0,n.jsx)(t.p,{children:"Based on their availability, applicants are assigned either to the core or the review team:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:["The ",(0,n.jsx)(t.strong,{children:"core team"})," is responsible for creating and working on dedicated features. The group acts here as a requester for the features and drives the development."]}),"\n",(0,n.jsxs)(t.li,{children:["The ",(0,n.jsx)(t.strong,{children:"review team"})," acts as a sparring partner to the core team and provides feedback on a regular basis. The review team has no recommended team size."]}),"\n"]}),"\n",(0,n.jsx)(t.p,{children:(0,n.jsx)(t.img,{alt:"ExpertGroup establishment",src:i(4913).A+""})}),"\n",(0,n.jsx)(t.h4,{id:"request-submission",children:"Request Submission"}),"\n",(0,n.jsx)(t.p,{children:"Individuals or organizations interested in forming an Expert Group can reach out to the Catena-X Association. The request is then going to be assigned to an committe. The request is then added to the Committee's agenda for validation."}),"\n",(0,n.jsx)(t.h4,{id:"initial-validation",children:"Initial validation"}),"\n",(0,n.jsx)(t.p,{children:"The Committee is going to do a initial validation of the request. If the request is deemed valid, one of the Committee members is going to be assigned to the request to serve as the Single Point of Contact (SPOC) for requestors and guides them through the initiation process. The mentor explains the process and provides necessary documents to the requestors."}),"\n",(0,n.jsx)(t.h4,{id:"onepager-creation",children:"Onepager creation"}),"\n",(0,n.jsx)(t.p,{children:"Once the request is validated, the requester has to write a onepager describing the challenge the Expert Group should tackle, what the status quo is and state the objectives the Expert Group should achieve. The requester is going to be supported by the mentor. The onepager ensures a comprehensive understanding of the group's objectives and scope."}),"\n",(0,n.jsx)(t.h4,{id:"final-validation",children:"Final validation"}),"\n",(0,n.jsx)(t.p,{children:"The onepager then has to be presented to the Committee. The committe then approves or disapproves the request."}),"\n",(0,n.jsx)(t.h4,{id:"application-phase",children:"Application Phase"}),"\n",(0,n.jsx)(t.p,{children:"Validated request are then taken over by the association which is then starting the application phase for the Expert Group. The application phase typically lasts around two to four weeks."}),"\n",(0,n.jsx)(t.h4,{id:"expert-group-composition",children:"Expert Group composition"}),"\n",(0,n.jsxs)(t.p,{children:["All applicants are going to be reviewed by the mentor. Based on predefined criteria the members for the Expert Group are going to be selected. If there are sufficient applicants, an optional review group may be created (see ",(0,n.jsx)(t.a,{href:"#expert-group-election",children:"Expert Group election"}),")."]}),"\n",(0,n.jsx)(t.h4,{id:"expert-group-approval",children:"Expert Group approval"}),"\n",(0,n.jsx)(t.p,{children:"Once the application phase is complete, the mentor seeks final approval from managing director value and technology creation, Catena-X e.V., for the formation of the Expert Group."}),"\n",(0,n.jsx)(t.h4,{id:"notification-and-kick-off",children:"Notification and Kick-off"}),"\n",(0,n.jsx)(t.p,{children:"Upon approval, the mentor informs all applicatns the outcome of their application (core team, review team or rejected). Core team members are invited to a kick-off for the group's inaugural meeting (usually two weeks after the application phase ended)."}),"\n",(0,n.jsx)(t.h4,{id:"review-group-formation",children:"Review Group Formation"}),"\n",(0,n.jsx)(t.p,{children:"If applicable, the mentor informs all review group members about the process and schedules the first review session."}),"\n",(0,n.jsx)(t.h4,{id:"kickoff",children:"Kickoff"}),"\n",(0,n.jsx)(t.p,{children:"During the kickoff the mentor presents the overall process, including reporting to the Committee and the next review session with the review group. Additionally, the mentor supports with lead selection and then hands over the leadership responsibilities to the appointed leads."}),"\n",(0,n.jsx)(t.h3,{id:"expert-group-maintenance-over-the-life-time",children:"Expert Group maintenance over the life time"}),"\n",(0,n.jsx)(t.p,{children:"The composition of the Expert Groups is not static and is expected to change over the life time of the Expert Group. In any case people that want to join an existing Expert Group need to be approved the same way, as applicants for new Expert Groups. This means they need to be approved by the mentor of the Expert Group and the managing director value and technology creation."}),"\n",(0,n.jsx)(t.h4,{id:"replacement-of-expert-group-members",children:"Replacement of Expert Group members"}),"\n",(0,n.jsx)(t.p,{children:"If a Expert Group member is stepping down from its position, it can not be handed over to another employee of the same company. The replacement needs to be approved."}),"\n",(0,n.jsx)(t.h4,{id:"adding-additional-members",children:"Adding additional members"}),"\n",(0,n.jsx)(t.p,{children:"The recommended maximal number of Expert Group members is 15. If the Expert Group has less members, new members might be added. If the number of members is greater than 15, new members might be added after consideration by the Committee."}),"\n",(0,n.jsx)(t.h3,{id:"closing-of-expert-groups",children:"Closing of Expert Groups"}),"\n",(0,n.jsx)(t.h3,{id:"expert-group-decision-making--communication",children:"Expert Group Decision Making & Communication"}),"\n",(0,n.jsx)(t.p,{children:(0,n.jsx)(t.img,{alt:"Expert Group meeting intervals",src:i(6259).A+""})}),"\n",(0,n.jsx)(t.p,{children:"Expert Groups are required to be transparent about their work and communicate regualarely with other association members to gather their feedback."}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"The Expert Group should meet on a weekly or bi-weekly schedule to align internally"}),"\n",(0,n.jsx)(t.li,{children:"If the Expert Group has a review group a monthly exchange should be scheduled to present the work of the Expert Group and get feedback"}),"\n",(0,n.jsx)(t.li,{children:"A quartely sounding event should be organised to inform all associations members about the work of the Expert Group and forthcoming initiatives. This event should be aligned with next release planning, to allow ample time for the integration of any valuable feedback that may arise."}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"expert-group-escalation-paths",children:"Expert Group Escalation Paths"}),"\n",(0,n.jsx)(t.h2,{id:"catena-x-office",children:"Catena-X office"})]})}function c(e={}){const{wrapper:t}={...(0,s.R)(),...e.components};return t?(0,n.jsx)(t,{...e,children:(0,n.jsx)(h,{...e})}):h(e)}},3068:(e,t,i)=>{i.d(t,{A:()=>n});const n=i.p+"assets/images/cx-association-overview.drawio-368e963120cbc2da3ed9b1246e335504.svg"},3:(e,t,i)=>{i.d(t,{A:()=>n});const n=i.p+"assets/images/cx-mgmt-office-soar.drawio-ee095a2094496912d8ef8725b2d7054a.svg"},4913:(e,t,i)=>{i.d(t,{A:()=>n});const n=i.p+"assets/images/expert-group-establishment-process.drawio-a1f4b7e38f19c18c37df6b8edb8c67bc.svg"},7853:(e,t,i)=>{i.d(t,{A:()=>n});const n=i.p+"assets/images/expert-group-life-line.drawio-23d8a7ecc214a637ae9514a528a194fb.svg"},6259:(e,t,i)=>{i.d(t,{A:()=>n});const n=i.p+"assets/images/expert-group-meeting-interval.drawio-ea54d8f5a15351a9ce837cc3bf7221b5.svg"},8453:(e,t,i)=>{i.d(t,{R:()=>r,x:()=>a});var n=i(6540);const s={},o=n.createContext(s);function r(e){const t=n.useContext(o);return n.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function a(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:r(e.components),n.createElement(o.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/9bc6bf15.f3c661c2.js b/assets/js/9bc6bf15.f3c661c2.js deleted file mode 100644 index 8e39f727..00000000 --- a/assets/js/9bc6bf15.f3c661c2.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[7803],{1066:(e,t,i)=>{i.r(t),i.d(t,{assets:()=>d,contentTitle:()=>o,default:()=>c,frontMatter:()=>r,metadata:()=>a,toc:()=>l});var n=i(4848),s=i(8453);const r={sidebar_position:1,title:"Catena-X association"},o=void 0,a={id:"working-model/organizational-structure/overview-roles/catena-x-roles",title:"Catena-X association",description:"General",source:"@site/docs/working-model/02-organizational-structure/overview-roles/catena-x-roles.md",sourceDirName:"working-model/02-organizational-structure/overview-roles",slug:"/working-model/organizational-structure/overview-roles/catena-x-roles",permalink:"/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Catena-X association"},sidebar:"sidebar_working_model",previous:{title:"Overview of roles and groups",permalink:"/docs/next/working-model/organizational-structure/overview-roles/"},next:{title:"Tractus-X",permalink:"/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles"}},d={},l=[{value:"General",id:"general",level:2},{value:"RASIC matrix for association bodies",id:"rasic-matrix-for-association-bodies",level:2},{value:"Management board",id:"management-board",level:2},{value:"Association Strategy",id:"association-strategy",level:3},{value:"Tasks and Responsibilities",id:"tasks-and-responsibilities",level:3},{value:"Management board roles",id:"management-board-roles",level:3},{value:"Board sponsor",id:"board-sponsor",level:4},{value:"Mediation board member",id:"mediation-board-member",level:4},{value:"Committee",id:"committee",level:2},{value:"Committee roles",id:"committee-roles",level:3},{value:"Lead and Co-Lead",id:"lead-and-co-lead",level:4},{value:"Mentor for Expert Groups (optional)",id:"mentor-for-expert-groups-optional",level:4},{value:"Business domain strategy",id:"business-domain-strategy",level:3},{value:"Communication",id:"communication",level:3},{value:"Alignment with Other Committees",id:"alignment-with-other-committees",level:4},{value:"Assigning and Mentoring Expert Groups",id:"assigning-and-mentoring-expert-groups",level:4},{value:"Feature Review",id:"feature-review",level:4},{value:"Feature Prioritization",id:"feature-prioritization",level:4},{value:"Tasks",id:"tasks",level:3},{value:"Powers",id:"powers",level:3},{value:"Responsibilities",id:"responsibilities",level:3},{value:"Election",id:"election",level:3},{value:"Decision Making & Communication",id:"decision-making--communication",level:3},{value:"Escalation Paths",id:"escalation-paths",level:3},{value:"Expert Group",id:"expert-group",level:2},{value:"Functional level strategy",id:"functional-level-strategy",level:3},{value:"Tasks and responsibilities for Expert Groups",id:"tasks-and-responsibilities-for-expert-groups",level:3},{value:"Existing Expert Groups",id:"existing-expert-groups",level:3},{value:"Expert Group Election",id:"expert-group-election",level:3},{value:"Request Submission",id:"request-submission",level:4},{value:"Initial validation",id:"initial-validation",level:4},{value:"Onepager creation",id:"onepager-creation",level:4},{value:"Final validation",id:"final-validation",level:4},{value:"Application Phase",id:"application-phase",level:4},{value:"Expert Group composition",id:"expert-group-composition",level:4},{value:"Expert Group approval",id:"expert-group-approval",level:4},{value:"Notification and Kick-off",id:"notification-and-kick-off",level:4},{value:"Review Group Formation",id:"review-group-formation",level:4},{value:"Kickoff",id:"kickoff",level:4},{value:"Expert Group maintenance over the life time",id:"expert-group-maintenance-over-the-life-time",level:3},{value:"Replacement of Expert Group members",id:"replacement-of-expert-group-members",level:4},{value:"Adding additional members",id:"adding-additional-members",level:4},{value:"Closing of Expert Groups",id:"closing-of-expert-groups",level:3},{value:"Expert Group Decision Making & Communication",id:"expert-group-decision-making--communication",level:3},{value:"Expert Group Escalation Paths",id:"expert-group-escalation-paths",level:3},{value:"Catena-X office",id:"catena-x-office",level:2}];function h(e){const t={a:"a",h2:"h2",h3:"h3",h4:"h4",img:"img",li:"li",p:"p",strong:"strong",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",ul:"ul",...(0,s.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(t.h2,{id:"general",children:"General"}),"\n",(0,n.jsxs)(t.p,{children:["The ",(0,n.jsx)(t.strong,{children:"Catena-X Automotive Network e.V."})," is often referred to as 'the association'. It is important to understand that the association consists of four bodies with different tasks and responsibilities. The association bodies are:"]}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"The Management board"}),"\n",(0,n.jsx)(t.li,{children:"Committees"}),"\n",(0,n.jsx)(t.li,{children:"Expert Groups"}),"\n",(0,n.jsx)(t.li,{children:"Catena-X office"}),"\n"]}),"\n",(0,n.jsx)(t.p,{children:(0,n.jsx)(t.img,{alt:"The association",src:i(3068).A+""})}),"\n",(0,n.jsx)(t.p,{children:"As the association, all four bodies aim to advance Catena-X as the leading global data ecosystem for the automotive value chain. In order to do so they follow the SOAR model."}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"S"})," = Standardizes to lay the foundation/basis for the ecosystem"]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"O"})," = Orchestrates to structure and organize the ecosystem"]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"A"})," = Activates by making standards applicable and relevant"]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"R"})," = Represent as the only ones speaking for Catena-X"]}),"\n"]}),"\n",(0,n.jsx)(t.p,{children:(0,n.jsx)(t.img,{alt:"C-X Office SOAR",src:i(3).A+""})}),"\n",(0,n.jsx)(t.p,{children:"Please note that while this page captures the essence of the Committee and the Expert Group roles, it is not exhaustive. The dynamic nature of the association means that roles can evolve, and members of the Committee and Expert Groups may engage in additional activities beyond what is described here. The descriptions below are intended to serve as a guide, providing a clear indication of the expected contributions of the Committee and the Expert Groups, yet it allows for flexibility and adaptation as the project and its needs grow and change."}),"\n",(0,n.jsx)(t.h2,{id:"rasic-matrix-for-association-bodies",children:"RASIC matrix for association bodies"}),"\n",(0,n.jsxs)(t.table,{children:[(0,n.jsx)(t.thead,{children:(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.th,{}),(0,n.jsx)(t.th,{children:"R = Responsible; A = Accountable; S = Supportive; I = Informed; C = Consulted"}),(0,n.jsx)(t.th,{children:"Management board"}),(0,n.jsx)(t.th,{}),(0,n.jsx)(t.th,{children:"Committee"}),(0,n.jsx)(t.th,{}),(0,n.jsx)(t.th,{}),(0,n.jsx)(t.th,{children:"Expert Group"}),(0,n.jsx)(t.th,{}),(0,n.jsx)(t.th,{children:"Catena-X office"})]})}),(0,n.jsxs)(t.tbody,{children:[(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"Member"}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#board-sponsor",children:"Sponsor"})}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#lead-and-co-lead",children:"Lead"})}),(0,n.jsx)(t.td,{children:"Member"}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#mentor-for-expert-groups-optional",children:"Mentor"})}),(0,n.jsx)(t.td,{children:"Lead"}),(0,n.jsx)(t.td,{children:"Member"}),(0,n.jsx)(t.td,{})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Strategy"}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#association-strategy",children:"Develop and maintain the Association Stratgey"})}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"S"})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#business-domain-strategy",children:"Develop and maintain the business domain strategy"})}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{children:"A,C"}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{children:"S"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{children:"S"})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#functional-level-strategy",children:"Develop and maintain a strategy on functional level"})}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"C"}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{children:"S"}),(0,n.jsx)(t.td,{children:"S"})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Mgmt. of association bodies"}),(0,n.jsx)(t.td,{children:"Setup Committees"}),(0,n.jsx)(t.td,{children:"R,A"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"S"})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"Close Committees"}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{children:"C"}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#expert-group-election",children:"Setup Expert Groups"})}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"C"}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"S"})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#closing-of-expert-groups",children:"Close Expert Groups"})}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"C"}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{children:"C,I"}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{children:"S"})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Development"}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production#create-new-feature-proposal",children:"Develop new feature requests"})}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"C"}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production#check-strategic-fit",children:"Approve features requests"})}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{children:"S"}),(0,n.jsx)(t.td,{children:"I"}),(0,n.jsx)(t.td,{})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"Foster the development of features by providing development resources"}),(0,n.jsx)(t.td,{children:"S"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"S"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"A,R"}),(0,n.jsx)(t.td,{})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"Remove impediments for the features development / for Expert Group(s)"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"C"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"S"}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{})]}),(0,n.jsxs)(t.tr,{children:[(0,n.jsx)(t.td,{children:"Promote"}),(0,n.jsx)(t.td,{children:(0,n.jsx)(t.a,{href:"#communication",children:"Promote the use cases of the business domain inside and outside the association"})}),(0,n.jsx)(t.td,{children:"S"}),(0,n.jsx)(t.td,{children:"C"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"R"}),(0,n.jsx)(t.td,{children:"A"}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{}),(0,n.jsx)(t.td,{children:"S"})]})]})]}),"\n",(0,n.jsx)(t.p,{children:'The RASIC should provide an overview of the tasks the Association bodies are engaging in. Each individual in the mgmt. board, a Committee or an Expert Group is at least a "member". If one takes over additional roles, e.g. as "Lead", the responsibilities of that role are added to those as member.'}),"\n",(0,n.jsx)(t.h2,{id:"management-board",children:"Management board"}),"\n",(0,n.jsx)(t.h3,{id:"association-strategy",children:"Association Strategy"}),"\n",(0,n.jsx)(t.p,{children:"The Management Board is responsible to develop, maintain and communicate the Association strategy. The strategy focuses on the overall mission, vision, and long-term objectives of the Association. It defines the broad purpose of the Association and its key goals."}),"\n",(0,n.jsx)(t.p,{children:"Decisions include determining the areas of focus for the Association, establishing partnerships, and setting the overall direction. This level may also involve decisions about expanding the Association's reach or services."}),"\n",(0,n.jsx)(t.p,{children:"The primary goal is to enhance the value provided to members and other stakeholders, ensuring the Association\u2019s sustainability and growth. This might involve increasing membership, enhancing influence, or expanding the range of services offered."}),"\n",(0,n.jsx)(t.h3,{id:"tasks-and-responsibilities",children:"Tasks and Responsibilities"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Approving of requests for new Committees"}),"\n",(0,n.jsx)(t.li,{children:"Appointment of Committee leaders"}),"\n",(0,n.jsx)(t.li,{children:"Preliminary selection of applicants for Committees"}),"\n",(0,n.jsx)(t.li,{children:"Approving of final composition of Committees"}),"\n",(0,n.jsx)(t.li,{children:"Mentoring of Committees"}),"\n",(0,n.jsx)(t.li,{children:"Last point of escalation"}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"management-board-roles",children:"Management board roles"}),"\n",(0,n.jsx)(t.h4,{id:"board-sponsor",children:"Board sponsor"}),"\n",(0,n.jsx)(t.h4,{id:"mediation-board-member",children:"Mediation board member"}),"\n",(0,n.jsx)(t.h2,{id:"committee",children:"Committee"}),"\n",(0,n.jsx)(t.p,{children:"The Committee plays a pivotal role in steering the direction of the open source project. This role description serves as a framework outlining the key responsibilities and tasks associated with the Committee. It provides a structured overview of the governance, communication strategies, and operational tasks that are central to the Committee's function within the organization."}),"\n",(0,n.jsx)(t.p,{children:"The Committee is encouraged to embrace this adaptability, taking initiative to address emerging challenges and opportunities, and to collaborate with other Committees and Expert Groups to achieve the organization's objectives. The success of the project hinges on the proactive and collaborative efforts of the Committee to lead with vision, communicate effectively, and prioritize features that align with our mission and strategic goals."}),"\n",(0,n.jsxs)(t.p,{children:["Committees are specialized bodies appointed by the board to address specific topics or tasks relevant to the association and the related eco system. Within the Catena-X Automotive Network e.V., the purpose and mandate of these Committees are to formulate recommendations for the board's decisions regarding matters to the association, in alignment with Catena-X's roadmap and the organization's strategic direction. Which means, they are responsible for the ",(0,n.jsx)(t.strong,{children:"mission"}),", ",(0,n.jsx)(t.strong,{children:"vision"})," and the ",(0,n.jsx)(t.strong,{children:"roadmap"})," related to their specific topic."]}),"\n",(0,n.jsx)(t.p,{children:"The Committee is also responsible for electing and managing the needed Expert Groups to work on specific tasks."}),"\n",(0,n.jsxs)(t.p,{children:["For more information please refer to the ",(0,n.jsx)(t.a,{href:"https://catena-x.net",children:"Framework for Committees"}),"."]}),"\n",(0,n.jsx)(t.p,{children:"There is already a list of Committees that have been established and are currently active. The list includes the following Committees:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Network Service Committee"}),"\n",(0,n.jsx)(t.li,{children:"Architecture Management Committee"}),"\n",(0,n.jsx)(t.li,{children:"..."}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"committee-roles",children:"Committee roles"}),"\n",(0,n.jsx)(t.h4,{id:"lead-and-co-lead",children:"Lead and Co-Lead"}),"\n",(0,n.jsx)(t.p,{children:"Every Committee must elect a Lead and a Co-Lead. Both act as first point of contact for any inquiries and requests towards the Committee. Further the leads are required to take care of the following taks:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"The leaders of the Committee appoint the Committee members based on the preliminary selection of applications by the board and their existing professional expertise."}),"\n",(0,n.jsx)(t.li,{children:"Creation of work packages in alignment with the other Committee members"}),"\n"]}),"\n",(0,n.jsx)(t.p,{children:"If the leads see fit they can they can handover the exectution of the task to other Committee members or create additional roles if they see fit. The general intention for the lead role is to be first among equals by keeping the strings together."}),"\n",(0,n.jsx)(t.h4,{id:"mentor-for-expert-groups-optional",children:"Mentor for Expert Groups (optional)"}),"\n",(0,n.jsx)(t.p,{children:"For each Expert Group associated to a Committee, a member of the Committee must be nominated as mentor. The mentor should a senior matter expert in the respective field of the Expert Group. The mentor works as interface to the Expert Groups and provide mentoring to ensure the success of the Expert Group."}),"\n",(0,n.jsx)(t.h3,{id:"business-domain-strategy",children:"Business domain strategy"}),"\n",(0,n.jsx)(t.p,{children:"The Committee is responsible for developing a clear and forward-looking strategy for the business domain. The strategy should contain a vision guides the direction for the coming years and serve as a beacon for all strategic decisions."}),"\n",(0,n.jsx)(t.p,{children:"Decisions at this level focus on how each Expert Group can effectively contribute to the overall mission and goals of the association."}),"\n",(0,n.jsx)(t.p,{children:"The main goal is to ensure that each Expert Group is effective in serving the members and supporting the association\u2019s objectives."}),"\n",(0,n.jsx)(t.p,{children:"The Committee creates a roadmap outlining key initiatives and milestones for the upcoming year. This roadmap is continuously reviewed and updated to respond to changes in the market and within the organization."}),"\n",(0,n.jsx)(t.h3,{id:"communication",children:"Communication"}),"\n",(0,n.jsx)(t.p,{children:"The Committee promotes the organization and its projects within the broader community. It builds relationships with other organizations and organizes events to foster engagement and collaboration. The group works closely with committers and members of Expert Groups to ensure a deep understanding of ongoing activities and the needs of the organization."}),"\n",(0,n.jsx)(t.h4,{id:"alignment-with-other-committees",children:"Alignment with Other Committees"}),"\n",(0,n.jsx)(t.p,{children:"The Committee coordinates its activities with other Committees to ensure a unified strategy and direction."}),"\n",(0,n.jsx)(t.h4,{id:"assigning-and-mentoring-expert-groups",children:"Assigning and Mentoring Expert Groups"}),"\n",(0,n.jsx)(t.p,{children:"The Committee is responsible for assigning tasks to Expert Groups and providing support and mentoring to ensure their success."}),"\n",(0,n.jsx)(t.h4,{id:"feature-review",children:"Feature Review"}),"\n",(0,n.jsx)(t.p,{children:"The Committee reviews contributions to the projects for quality, security, and functionality to ensure they meet the organization's standards."}),"\n",(0,n.jsx)(t.h4,{id:"feature-prioritization",children:"Feature Prioritization"}),"\n",(0,n.jsx)(t.p,{children:"The Committee prioritizes features on a cross-Expert Group level, focusing on the needs of the organization and the market."}),"\n",(0,n.jsx)(t.h3,{id:"tasks",children:"Tasks"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:["Vision and big picture","\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Develop and maintain a forward-looking vision for the domain"}),"\n",(0,n.jsx)(t.li,{children:"Create a roadmap outlining key initiatives and milestones"}),"\n"]}),"\n"]}),"\n",(0,n.jsxs)(t.li,{children:["Gate keeping","\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Evaluate the strategic fit for standard (change) requests"}),"\n",(0,n.jsx)(t.li,{children:"Evaluate the strategic fit for feature requests (in Tractus-X)"}),"\n",(0,n.jsx)(t.li,{children:"Analyze / Request details on dependencies between features"}),"\n",(0,n.jsx)(t.li,{children:"Provide feedback upfront to refinement and planning regarding missing details or proposal against mission/vision"}),"\n",(0,n.jsx)(t.li,{children:"Prioritize roadmap at feature level in alignment with Expert Groups"}),"\n",(0,n.jsx)(t.li,{children:"Define status/readiness for planning"}),"\n"]}),"\n"]}),"\n",(0,n.jsxs)(t.li,{children:["Expert Group supervision","\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Initiate new Expert Group in their domain"}),"\n",(0,n.jsx)(t.li,{children:"Close Expert Groups if needed"}),"\n",(0,n.jsx)(t.li,{children:"Review applications for new Expert Groups"}),"\n",(0,n.jsxs)(t.li,{children:["provide mentoring to Expert Groups (see ",(0,n.jsx)(t.a,{href:"#mentor-for-expert-groups-optional",children:"Mentor"}),")"]}),"\n"]}),"\n"]}),"\n",(0,n.jsxs)(t.li,{children:["Knowledge transfer","\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Promote the knowledge transfer for the domain to other association bodies"}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"powers",children:"Powers"}),"\n",(0,n.jsx)(t.h3,{id:"responsibilities",children:"Responsibilities"}),"\n",(0,n.jsx)(t.h3,{id:"election",children:"Election"}),"\n",(0,n.jsx)(t.h3,{id:"decision-making--communication",children:"Decision Making & Communication"}),"\n",(0,n.jsx)(t.h3,{id:"escalation-paths",children:"Escalation Paths"}),"\n",(0,n.jsx)(t.h2,{id:"expert-group",children:"Expert Group"}),"\n",(0,n.jsx)(t.p,{children:"The aim of the Expert Groups within the Catena-X Automotive Network e.V. is to develop results together with the members in line with the association's strategic direction. The Expert Groups are managed by the related Committee. The Expert Groups don't exist forever. They work on dedicated topics, present the results to the Committee and are then retired."}),"\n",(0,n.jsx)(t.p,{children:(0,n.jsx)(t.img,{alt:"Expert Group Lifeline",src:i(7853).A+""})}),"\n",(0,n.jsx)(t.h3,{id:"functional-level-strategy",children:"Functional level strategy"}),"\n",(0,n.jsx)(t.p,{children:"The functional level strategy involves the specific operational activities within a Expert Groups. It deals with the day-to-day tasks and processes that need to be executed to support the business domain strategy."}),"\n",(0,n.jsx)(t.p,{children:"The focus lies on implementation, realisation and the delivery of tangible results."}),"\n",(0,n.jsx)(t.h3,{id:"tasks-and-responsibilities-for-expert-groups",children:"Tasks and responsibilities for Expert Groups"}),"\n",(0,n.jsx)(t.p,{children:"In addition to the results to be elaborated in terms of content, the working groups have to fulfil the following, overarching tasks:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Elaboration of the strategic orientation"}),"\n",(0,n.jsx)(t.li,{children:"Advancing standardisation"}),"\n",(0,n.jsx)(t.li,{children:"Realisation of the strategic roadmap of the association"}),"\n",(0,n.jsx)(t.li,{children:"Harmonisation of interests"}),"\n",(0,n.jsx)(t.li,{children:"Achieving majority feedback on the orientation of the association"}),"\n",(0,n.jsx)(t.li,{children:"Identifying areas for action"}),"\n",(0,n.jsx)(t.li,{children:"Focus on tangible results"}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"existing-expert-groups",children:"Existing Expert Groups"}),"\n",(0,n.jsx)(t.p,{children:"There is already a list of groups that have been established and are currently active. The list includes the following groups:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"..."}),"\n",(0,n.jsx)(t.li,{children:"..."}),"\n",(0,n.jsx)(t.li,{children:"..."}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"expert-group-election",children:"Expert Group Election"}),"\n",(0,n.jsx)(t.p,{children:"Association members can join any Expert Groups by applying for open seats. The recommended size for Expert Groups is 5 to 15 core team members. Less core team members might indicated that the topic is not relevant enough to the assosciation and cause the Expert Group not being established. More core team members would make the Expert Group to inflexible and a split of the Expert Group might be considered."}),"\n",(0,n.jsx)(t.p,{children:"The composition of the core team is considering a balance between OEM, tier-1, tier-2, tier-n and small, medium and large sized companies with up to one participant per company with one voting right per company."}),"\n",(0,n.jsx)(t.p,{children:"The members of the core team are selected according to the following criteria:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Proper expertise in the relevant field of the Expert Group"}),"\n",(0,n.jsx)(t.li,{children:"Minimum availability of 20 hours per month, more is a plus"}),"\n",(0,n.jsx)(t.li,{children:"Commitment to regular, active participation and active contribution"}),"\n"]}),"\n",(0,n.jsx)(t.p,{children:"Based on their availability, applicants are assigned either to the core or the review team:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:["The ",(0,n.jsx)(t.strong,{children:"core team"})," is responsible for creating and working on dedicated features. The group acts here as a requester for the features and drives the development."]}),"\n",(0,n.jsxs)(t.li,{children:["The ",(0,n.jsx)(t.strong,{children:"review team"})," acts as a sparring partner to the core team and provides feedback on a regular basis. The review team has no recommended team size."]}),"\n"]}),"\n",(0,n.jsx)(t.p,{children:(0,n.jsx)(t.img,{alt:"ExpertGroup establishment",src:i(4913).A+""})}),"\n",(0,n.jsx)(t.h4,{id:"request-submission",children:"Request Submission"}),"\n",(0,n.jsx)(t.p,{children:"Individuals or organizations interested in forming an Expert Group can reach out to the Catena-X Association. The request is then going to be assigned to an committe. The request is then added to the Committee's agenda for validation."}),"\n",(0,n.jsx)(t.h4,{id:"initial-validation",children:"Initial validation"}),"\n",(0,n.jsx)(t.p,{children:"The Committee is going to do a initial validation of the request. If the request is deemed valid, one of the Committee members is going to be assigned to the request to serve as the Single Point of Contact (SPOC) for requestors and guides them through the initiation process. The mentor explains the process and provides necessary documents to the requestors."}),"\n",(0,n.jsx)(t.h4,{id:"onepager-creation",children:"Onepager creation"}),"\n",(0,n.jsx)(t.p,{children:"Once the request is validated, the requester has to write a onepager describing the challenge the Expert Group should tackle, what the status quo is and state the objectives the Expert Group should achieve. The requester is going to be supported by the mentor. The onepager ensures a comprehensive understanding of the group's objectives and scope."}),"\n",(0,n.jsx)(t.h4,{id:"final-validation",children:"Final validation"}),"\n",(0,n.jsx)(t.p,{children:"The onepager then has to be presented to the Committee. The committe then approves or disapproves the request."}),"\n",(0,n.jsx)(t.h4,{id:"application-phase",children:"Application Phase"}),"\n",(0,n.jsx)(t.p,{children:"Validated request are then taken over by the association which is then starting the application phase for the Expert Group. The application phase typically lasts around two to four weeks."}),"\n",(0,n.jsx)(t.h4,{id:"expert-group-composition",children:"Expert Group composition"}),"\n",(0,n.jsxs)(t.p,{children:["All applicants are going to be reviewed by the mentor. Based on predefined criteria the members for the Expert Group are going to be selected. If there are sufficient applicants, an optional review group may be created (see ",(0,n.jsx)(t.a,{href:"#expert-group-election",children:"Expert Group election"}),")."]}),"\n",(0,n.jsx)(t.h4,{id:"expert-group-approval",children:"Expert Group approval"}),"\n",(0,n.jsx)(t.p,{children:"Once the application phase is complete, the mentor seeks final approval from managing director value and technology creation, Catena-X e.V., for the formation of the Expert Group."}),"\n",(0,n.jsx)(t.h4,{id:"notification-and-kick-off",children:"Notification and Kick-off"}),"\n",(0,n.jsx)(t.p,{children:"Upon approval, the mentor informs all applicatns the outcome of their application (core team, review team or rejected). Core team members are invited to a kick-off for the group's inaugural meeting (usually two weeks after the application phase ended)."}),"\n",(0,n.jsx)(t.h4,{id:"review-group-formation",children:"Review Group Formation"}),"\n",(0,n.jsx)(t.p,{children:"If applicable, the mentor informs all review group members about the process and schedules the first review session."}),"\n",(0,n.jsx)(t.h4,{id:"kickoff",children:"Kickoff"}),"\n",(0,n.jsx)(t.p,{children:"During the kickoff the mentor presents the overall process, including reporting to the Committee and the next review session with the review group. Additionally, the mentor supports with lead selection and then hands over the leadership responsibilities to the appointed leads."}),"\n",(0,n.jsx)(t.h3,{id:"expert-group-maintenance-over-the-life-time",children:"Expert Group maintenance over the life time"}),"\n",(0,n.jsx)(t.p,{children:"The composition of the Expert Groups is not static and is expected to change over the life time of the Expert Group. In any case people that want to join an existing Expert Group need to be approved the same way, as applicants for new Expert Groups. This means they need to be approved by the mentor of the Expert Group and the managing director value and technology creation."}),"\n",(0,n.jsx)(t.h4,{id:"replacement-of-expert-group-members",children:"Replacement of Expert Group members"}),"\n",(0,n.jsx)(t.p,{children:"If a Expert Group member is stepping down from its position, it can not be handed over to another employee of the same company. The replacement needs to be approved."}),"\n",(0,n.jsx)(t.h4,{id:"adding-additional-members",children:"Adding additional members"}),"\n",(0,n.jsx)(t.p,{children:"The recommended maximal number of Expert Group members is 15. If the Expert Group has less members, new members might be added. If the number of members is greater than 15, new members might be added after consideration by the Committee."}),"\n",(0,n.jsx)(t.h3,{id:"closing-of-expert-groups",children:"Closing of Expert Groups"}),"\n",(0,n.jsx)(t.h3,{id:"expert-group-decision-making--communication",children:"Expert Group Decision Making & Communication"}),"\n",(0,n.jsx)(t.p,{children:(0,n.jsx)(t.img,{alt:"Expert Group meeting intervals",src:i(6259).A+""})}),"\n",(0,n.jsx)(t.p,{children:"Expert Groups are required to be transparent about their work and communicate regualarely with other association members to gather their feedback."}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"The Expert Group should meet on a weekly or bi-weekly schedule to align internally"}),"\n",(0,n.jsx)(t.li,{children:"If the Expert Group has a review group a monthly exchange should be scheduled to present the work of the Expert Group and get feedback"}),"\n",(0,n.jsx)(t.li,{children:"A quartely sounding event should be organised to inform all associations members about the work of the Expert Group and forthcoming initiatives. This event should be aligned with next release planning, to allow ample time for the integration of any valuable feedback that may arise."}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"expert-group-escalation-paths",children:"Expert Group Escalation Paths"}),"\n",(0,n.jsx)(t.h2,{id:"catena-x-office",children:"Catena-X office"})]})}function c(e={}){const{wrapper:t}={...(0,s.R)(),...e.components};return t?(0,n.jsx)(t,{...e,children:(0,n.jsx)(h,{...e})}):h(e)}},3068:(e,t,i)=>{i.d(t,{A:()=>n});const n=i.p+"assets/images/cx-association-overview.drawio-368e963120cbc2da3ed9b1246e335504.svg"},3:(e,t,i)=>{i.d(t,{A:()=>n});const n=i.p+"assets/images/cx-mgmt-office-soar.drawio-ee095a2094496912d8ef8725b2d7054a.svg"},4913:(e,t,i)=>{i.d(t,{A:()=>n});const n=i.p+"assets/images/expert-group-establishment-process.drawio-a1f4b7e38f19c18c37df6b8edb8c67bc.svg"},7853:(e,t,i)=>{i.d(t,{A:()=>n});const n=i.p+"assets/images/expert-group-life-line.drawio-23d8a7ecc214a637ae9514a528a194fb.svg"},6259:(e,t,i)=>{i.d(t,{A:()=>n});const n=i.p+"assets/images/expert-group-meeting-interval.drawio-ea54d8f5a15351a9ce837cc3bf7221b5.svg"},8453:(e,t,i)=>{i.d(t,{R:()=>o,x:()=>a});var n=i(6540);const s={},r=n.createContext(s);function o(e){const t=n.useContext(r);return n.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function a(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:o(e.components),n.createElement(r.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/9c06b359.3fbf8174.js b/assets/js/9c06b359.3fbf8174.js deleted file mode 100644 index 30640a37..00000000 --- a/assets/js/9c06b359.3fbf8174.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[7790],{7862:(e,t,o)=>{o.r(t),o.d(t,{assets:()=>c,contentTitle:()=>s,default:()=>h,frontMatter:()=>n,metadata:()=>a,toc:()=>l});var r=o(4848),i=o(8453);const n={sidebar_position:1,title:"Overview of roles and groups"},s=void 0,a={id:"working-model/organizational-structure/overview-roles/overview-roles",title:"Overview of roles and groups",description:'Welcome to the "Open Source Roles" section of our documentation. This chapter is dedicated to providing a comprehensive overview of the various roles that are integral to the success and sustainability of our open source project. Open source projects thrive on the collaboration and contributions of a diverse and active community. Understanding the different roles within this ecosystem is crucial for both current and prospective members who wish to engage with and contribute to the project.',source:"@site/docs/working-model/02-organizational-structure/overview-roles/overview-roles.md",sourceDirName:"working-model/02-organizational-structure/overview-roles",slug:"/working-model/organizational-structure/overview-roles/",permalink:"/docs/next/working-model/organizational-structure/overview-roles/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Overview of roles and groups"},sidebar:"sidebar_working_model",previous:{title:"Tooling",permalink:"/docs/next/working-model/organizational-structure/02-03-tooling"},next:{title:"Catena-X association",permalink:"/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles"}},c={},l=[{value:"Collaboration between Expert Group, Experts and Committer",id:"collaboration-between-expert-group-experts-and-committer",level:2}];function d(e){const t={a:"a",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",...(0,i.R)(),...e.components};return(0,r.jsxs)(r.Fragment,{children:[(0,r.jsx)(t.p,{children:'Welcome to the "Open Source Roles" section of our documentation. This chapter is dedicated to providing a comprehensive overview of the various roles that are integral to the success and sustainability of our open source project. Open source projects thrive on the collaboration and contributions of a diverse and active community. Understanding the different roles within this ecosystem is crucial for both current and prospective members who wish to engage with and contribute to the project.'}),"\n",(0,r.jsx)(t.p,{children:(0,r.jsx)(t.img,{alt:"Overview",src:o(4781).A+""})}),"\n",(0,r.jsx)(t.p,{children:"Within this chapter, we will explore the responsibilities, expectations, and contributions of four key roles:"}),"\n",(0,r.jsxs)(t.ol,{children:["\n",(0,r.jsxs)(t.li,{children:["\n",(0,r.jsxs)(t.p,{children:[(0,r.jsx)(t.a,{href:"/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles#committee",children:(0,r.jsx)(t.strong,{children:"Committee"})}),": The Committee is a governing body that provides overarching guidance and direction for the project. It is responsible for the project's governance, strategic planning, and ensuring that the project's goals and activities align with its vision and mission."]}),"\n"]}),"\n",(0,r.jsxs)(t.li,{children:["\n",(0,r.jsxs)(t.p,{children:[(0,r.jsx)(t.a,{href:"/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles#expert-group",children:(0,r.jsx)(t.strong,{children:"Expert Group"})}),": Expert Groups consist of individuals with specialized knowledge or skills in a particular area of the project. They work collaboratively to drive the project's development, make strategic decisions, and ensure the quality and integrity of the project."]}),"\n"]}),"\n",(0,r.jsxs)(t.li,{children:["\n",(0,r.jsxs)(t.p,{children:[(0,r.jsx)(t.a,{href:"/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles#contributor",children:(0,r.jsx)(t.strong,{children:"Contributor"})}),": Contributors are the backbone of any open source project. They are individuals who offer their skills and time to contribute to the project in various forms, such as code, documentation, design, or community support."]}),"\n"]}),"\n",(0,r.jsxs)(t.li,{children:["\n",(0,r.jsxs)(t.p,{children:[(0,r.jsx)(t.a,{href:"/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles#committer",children:(0,r.jsx)(t.strong,{children:"Committer"})}),": Committers are contributors who have been granted the ability to directly access the project's code repository to make changes. They have a deeper level of commitment to the project and are responsible for reviewing and accepting contributions from others."]}),"\n"]}),"\n"]}),"\n",(0,r.jsxs)(t.p,{children:["Each role is vital to the project's ecosystem and contributes uniquely to its growth and direction. ",(0,r.jsx)(t.strong,{children:"As we delve into the specifics of each role, we invite you to consider where your skills and interests may best align with the needs of the project."})," Whether you are just starting out or looking to increase your involvement, there is a place for everyone to contribute and make an impact in our open source community."]}),"\n",(0,r.jsx)(t.h2,{id:"collaboration-between-expert-group-experts-and-committer",children:"Collaboration between Expert Group, Experts and Committer"}),"\n",(0,r.jsx)(t.p,{children:(0,r.jsx)(t.img,{alt:"Collaboration",src:o(6863).A+""})}),"\n",(0,r.jsx)(t.p,{children:"Even if it appears to be an organisational separation, it is important to understand that Catena-X and Tractus-X must work closely together. The Expert Groups and Committees are the ones who define the features and the roadmap. The committers are the ones who implement the features and the roadmap. The experts are the ones who provide the knowledge and the expertise to the committers."}),"\n",(0,r.jsx)(t.p,{children:"The committers are responsible for the prioritization of the features within the open-source boards. committers are also responsible for overarching topics like quality, security, and functionality. Committers are representatives of their own company and should also work/support within the Expert Groups."})]})}function h(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,r.jsx)(t,{...e,children:(0,r.jsx)(d,{...e})}):d(e)}},6863:(e,t,o)=>{o.d(t,{A:()=>r});const r=o.p+"assets/images/expert-group-experts-committers.drawio-5dc06a29394a3c83949c765395ecd492.svg"},4781:(e,t,o)=>{o.d(t,{A:()=>r});const r=o.p+"assets/images/groups-roles.drawio-172ee141f7527e901adedb20a9419557.svg"},8453:(e,t,o)=>{o.d(t,{R:()=>s,x:()=>a});var r=o(6540);const i={},n=r.createContext(i);function s(e){const t=r.useContext(n);return r.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function a(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:s(e.components),r.createElement(n.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/9c06b359.6515b964.js b/assets/js/9c06b359.6515b964.js new file mode 100644 index 00000000..7dfb0c58 --- /dev/null +++ b/assets/js/9c06b359.6515b964.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[7790],{7862:(e,t,o)=>{o.r(t),o.d(t,{assets:()=>c,contentTitle:()=>s,default:()=>h,frontMatter:()=>n,metadata:()=>a,toc:()=>l});var r=o(4848),i=o(8453);const n={sidebar_position:1,title:"Overview of roles and groups"},s=void 0,a={id:"working-model/organizational-structure/overview-roles/overview-roles",title:"Overview of roles and groups",description:'Welcome to the "Open Source Roles" section of our documentation. This chapter is dedicated to providing a comprehensive overview of the various roles that are integral to the success and sustainability of our open source project. Open source projects thrive on the collaboration and contributions of a diverse and active community. Understanding the different roles within this ecosystem is crucial for both current and prospective members who wish to engage with and contribute to the project.',source:"@site/docs/working-model/02-organizational-structure/overview-roles/overview-roles.md",sourceDirName:"working-model/02-organizational-structure/overview-roles",slug:"/working-model/organizational-structure/overview-roles/",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Overview of roles and groups"},sidebar:"sidebar_working_model",previous:{title:"Tooling",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/02-03-tooling"},next:{title:"Catena-X association",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles"}},c={},l=[{value:"Collaboration between Expert Group, Experts and Committer",id:"collaboration-between-expert-group-experts-and-committer",level:2}];function d(e){const t={a:"a",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",...(0,i.R)(),...e.components};return(0,r.jsxs)(r.Fragment,{children:[(0,r.jsx)(t.p,{children:'Welcome to the "Open Source Roles" section of our documentation. This chapter is dedicated to providing a comprehensive overview of the various roles that are integral to the success and sustainability of our open source project. Open source projects thrive on the collaboration and contributions of a diverse and active community. Understanding the different roles within this ecosystem is crucial for both current and prospective members who wish to engage with and contribute to the project.'}),"\n",(0,r.jsx)(t.p,{children:(0,r.jsx)(t.img,{alt:"Overview",src:o(4781).A+""})}),"\n",(0,r.jsx)(t.p,{children:"Within this chapter, we will explore the responsibilities, expectations, and contributions of four key roles:"}),"\n",(0,r.jsxs)(t.ol,{children:["\n",(0,r.jsxs)(t.li,{children:["\n",(0,r.jsxs)(t.p,{children:[(0,r.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles#committee",children:(0,r.jsx)(t.strong,{children:"Committee"})}),": The Committee is a governing body that provides overarching guidance and direction for the project. It is responsible for the project's governance, strategic planning, and ensuring that the project's goals and activities align with its vision and mission."]}),"\n"]}),"\n",(0,r.jsxs)(t.li,{children:["\n",(0,r.jsxs)(t.p,{children:[(0,r.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles#expert-group",children:(0,r.jsx)(t.strong,{children:"Expert Group"})}),": Expert Groups consist of individuals with specialized knowledge or skills in a particular area of the project. They work collaboratively to drive the project's development, make strategic decisions, and ensure the quality and integrity of the project."]}),"\n"]}),"\n",(0,r.jsxs)(t.li,{children:["\n",(0,r.jsxs)(t.p,{children:[(0,r.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles#contributor",children:(0,r.jsx)(t.strong,{children:"Contributor"})}),": Contributors are the backbone of any open source project. They are individuals who offer their skills and time to contribute to the project in various forms, such as code, documentation, design, or community support."]}),"\n"]}),"\n",(0,r.jsxs)(t.li,{children:["\n",(0,r.jsxs)(t.p,{children:[(0,r.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles#committer",children:(0,r.jsx)(t.strong,{children:"Committer"})}),": Committers are contributors who have been granted the ability to directly access the project's code repository to make changes. They have a deeper level of commitment to the project and are responsible for reviewing and accepting contributions from others."]}),"\n"]}),"\n"]}),"\n",(0,r.jsxs)(t.p,{children:["Each role is vital to the project's ecosystem and contributes uniquely to its growth and direction. ",(0,r.jsx)(t.strong,{children:"As we delve into the specifics of each role, we invite you to consider where your skills and interests may best align with the needs of the project."})," Whether you are just starting out or looking to increase your involvement, there is a place for everyone to contribute and make an impact in our open source community."]}),"\n",(0,r.jsx)(t.h2,{id:"collaboration-between-expert-group-experts-and-committer",children:"Collaboration between Expert Group, Experts and Committer"}),"\n",(0,r.jsx)(t.p,{children:(0,r.jsx)(t.img,{alt:"Collaboration",src:o(6863).A+""})}),"\n",(0,r.jsx)(t.p,{children:"Even if it appears to be an organisational separation, it is important to understand that Catena-X and Tractus-X must work closely together. The Expert Groups and Committees are the ones who define the features and the roadmap. The committers are the ones who implement the features and the roadmap. The experts are the ones who provide the knowledge and the expertise to the committers."}),"\n",(0,r.jsx)(t.p,{children:"The committers are responsible for the prioritization of the features within the open-source boards. committers are also responsible for overarching topics like quality, security, and functionality. Committers are representatives of their own company and should also work/support within the Expert Groups."})]})}function h(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,r.jsx)(t,{...e,children:(0,r.jsx)(d,{...e})}):d(e)}},6863:(e,t,o)=>{o.d(t,{A:()=>r});const r=o.p+"assets/images/expert-group-experts-committers.drawio-5dc06a29394a3c83949c765395ecd492.svg"},4781:(e,t,o)=>{o.d(t,{A:()=>r});const r=o.p+"assets/images/groups-roles.drawio-172ee141f7527e901adedb20a9419557.svg"},8453:(e,t,o)=>{o.d(t,{R:()=>s,x:()=>a});var r=o(6540);const i={},n=r.createContext(i);function s(e){const t=r.useContext(n);return r.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function a(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:s(e.components),r.createElement(n.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/9e6fa7e7.84261d61.js b/assets/js/9e6fa7e7.84261d61.js new file mode 100644 index 00000000..333dde7e --- /dev/null +++ b/assets/js/9e6fa7e7.84261d61.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[421],{6463:a=>{a.exports=JSON.parse('{"tag":{"label":"Hola","permalink":"/catenax-ev.github.io.new/blog/tags/hola","description":"Hola tag description","allTagsPath":"/catenax-ev.github.io.new/blog/tags","count":1,"unlisted":false},"listMetadata":{"permalink":"/catenax-ev.github.io.new/blog/tags/hola","page":1,"postsPerPage":10,"totalPages":1,"totalCount":1,"blogDescription":"Blog","blogTitle":"Blog"}}')}}]); \ No newline at end of file diff --git a/assets/js/a618e3e0.158299c0.js b/assets/js/a618e3e0.158299c0.js new file mode 100644 index 00000000..90420426 --- /dev/null +++ b/assets/js/a618e3e0.158299c0.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[4182],{7854:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>l,contentTitle:()=>o,default:()=>h,frontMatter:()=>r,metadata:()=>a,toc:()=>d});var t=i(4848),s=i(8453);const r={sidebar_position:3,title:"Contribution Levels"},o=void 0,a={id:"working-model/process-from-idea-to-production/03-04-Issue-Process",title:"Contribution Levels",description:"Table of Contents",source:"@site/docs/working-model/03-process-from-idea-to-production/03-04-Issue-Process.md",sourceDirName:"working-model/03-process-from-idea-to-production",slug:"/working-model/process-from-idea-to-production/03-04-Issue-Process",permalink:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-04-Issue-Process",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:3,frontMatter:{sidebar_position:3,title:"Contribution Levels"},sidebar:"sidebar_working_model",previous:{title:"Tractus-X Open Source Project Contribution Guide",permalink:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-02-Contribution-Guideline"},next:{title:"Glossary",permalink:"/catenax-ev.github.io.new/docs/next/working-model/glossary"}},l={},d=[{value:"General Feature Contributions",id:"general-feature-contributions",level:2},{value:"Create New Feature Inside SIG-Release",id:"create-new-feature-inside-sig-release",level:3},{value:"Add Feature Details",id:"add-feature-details",level:3},{value:"Labeling and Tracking",id:"labeling-and-tracking",level:3},{value:"Milestones and Assignees",id:"milestones-and-assignees",level:3},{value:"1. Feature Refinement",id:"1-feature-refinement",level:2},{value:"1.1 Initial Review by Expert Group and Committee",id:"11-initial-review-by-expert-group-and-committee",level:3},{value:"1.2 Contributor's Responsibility",id:"12-contributors-responsibility",level:3},{value:"1.3 Feature Validation and Approval",id:"13-feature-validation-and-approval",level:3},{value:"1.4 Deadline for Inclusion in Release Planning",id:"14-deadline-for-inclusion-in-release-planning",level:3},{value:"2. Release Planning",id:"2-release-planning",level:2},{value:"2.1 Preparation for Release Planning (Input State)",id:"21-preparation-for-release-planning-input-state",level:3},{value:"2.2 Release Planning Meeting",id:"22-release-planning-meeting",level:3},{value:"2.3 Decision-Making by Committers",id:"23-decision-making-by-committers",level:3},{value:"2.4 Outcome of Release Planning",id:"24-outcome-of-release-planning",level:3},{value:"2.5 Communication and Documentation",id:"25-communication-and-documentation",level:4}];function c(e){const n={a:"a",admonition:"admonition",h2:"h2",h3:"h3",h4:"h4",li:"li",ol:"ol",p:"p",strong:"strong",ul:"ul",...(0,s.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(n.p,{children:"Table of Contents"}),"\n",(0,t.jsxs)(n.ol,{children:["\n",(0,t.jsx)(n.li,{children:(0,t.jsx)(n.a,{href:"#1-feature-refinement",children:"Feature Refinement"})}),"\n",(0,t.jsx)(n.li,{children:(0,t.jsx)(n.a,{href:"#2-release-planning",children:"Release Planning"})}),"\n"]}),"\n",(0,t.jsx)(n.admonition,{type:"info",children:(0,t.jsxs)(n.p,{children:[(0,t.jsx)(n.a,{href:"#general-feature-contributions",children:"General Feature Contributions"})," is this still needed?"]})}),"\n",(0,t.jsx)(n.h2,{id:"general-feature-contributions",children:"General Feature Contributions"}),"\n",(0,t.jsx)(n.p,{children:"Contributing features involves adding new functionality or enhancing existing features within the Tractus-X project. Here's the process to follow:"}),"\n",(0,t.jsx)(n.h3,{id:"create-new-feature-inside-sig-release",children:"Create New Feature Inside SIG-Release"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Access the SIG-Release repository:"})," Navigate to the SIG-Release repository within the Tractus-X project."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Use the feature template:"})," Find the feature template and fill it out with the necessary details about the new feature you're proposing."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Submit the template:"})," Once completed, submit the template to the SIG-Release for consideration."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"add-feature-details",children:"Add Feature Details"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Feature Description:"})," Clearly describe the feature, its purpose, and how it benefits the project."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Dependencies:"})," List any dependencies required for the feature."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Contribution:"})," Explain how others can contribute to the development of this feature."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Test Scope:"})," Define the scope of testing required for the feature to ensure it works as intended."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Affected Components/Repos:"})," Identify which components or repositories will be affected by this feature."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"labeling-and-tracking",children:"Labeling and Tracking"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Add Relevant Labels:"})," Apply labels related to the products and PI (Program Increment) version to your feature request for easy tracking."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Link to Release Planning Dashboard:"})," Ensure your feature is linked to the release planning dashboard for visibility and tracking."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"milestones-and-assignees",children:"Milestones and Assignees"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Keep Milestones Open:"})," Do not assign a specific milestone; leave it open for the maintainers to assign."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Assignee:"})," Leave the assignee field open unless you plan to take on the feature development yourself."]}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"1-feature-refinement",children:"1. Feature Refinement"}),"\n",(0,t.jsx)(n.p,{children:"Once a new feature proposal has been made for the Tractus-X project, it enters a validation phase where Expert Groups and committees review the proposal. Here is a step-by-step guide on what happens after a feature proposal is submitted:"}),"\n",(0,t.jsx)(n.h3,{id:"11-initial-review-by-expert-group-and-committee",children:"1.1 Initial Review by Expert Group and Committee"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Validation:"})," The Expert Group and committee assigned to the feature area will review the proposal to ensure it aligns with the project's goals and standards."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Request for Additional Details:"})," If the proposal lacks necessary details, the reviewing bodies may ask the contributor for additional information or clarification."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"12-contributors-responsibility",children:"1.2 Contributor's Responsibility"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Responding to Feedback:"})," The contributor is responsible for addressing any feedback provided by the Expert Group or committee. This may include providing additional details or making revisions to the proposal."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Sub Task Creation:"})," If required, the contributor may need to create sub-tasks that break down the feature into manageable pieces. This helps in tracking progress and facilitates easier review."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Timely Updates:"})," The contributor must update the feature details within the given timeframe. Prompt responses and updates are crucial to keep the proposal moving forward."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"13-feature-validation-and-approval",children:"1.3 Feature Validation and Approval"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Approval for Planning:"})," Once the feature has enough detail and meets the project's standards, the Expert Group and committee will approve it for inclusion in the release planning."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Continuous Communication:"})," The contributor should stay in close communication with the Expert Group and committee throughout this process to ensure any issues are promptly addressed."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"14-deadline-for-inclusion-in-release-planning",children:"1.4 Deadline for Inclusion in Release Planning"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Release Planning Cut-off:"})," Features must reach the expected level of detail before the Program Increment (PI) planning meeting. This is a critical deadline."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Consequences of Missing Deadline:"})," If the feature does not meet the required level of detail by the Release Planning, it will not be included in the planning cycle. This means it will likely be deferred to a future PI."]}),"\n"]}),"\n",(0,t.jsx)(n.p,{children:"By following this process, contributors can ensure their feature proposals are considered for inclusion in the Tractus-X project's Release Planning. It is important to be proactive, responsive, and detail-oriented to successfully navigate the post-proposal phase."}),"\n",(0,t.jsx)(n.h2,{id:"2-release-planning",children:"2. Release Planning"}),"\n",(0,t.jsx)(n.p,{children:"Program Increment (PI) Planning is a critical event in the Tractus-X project where contributors, committers, Expert Groups, and committees come together to define the scope for the next PI. This process ensures that the project's roadmap is aligned with stakeholder expectations and the project's strategic objectives. Here's how the Release Planning process typically unfolds:"}),"\n",(0,t.jsx)(n.h3,{id:"21-preparation-for-release-planning-input-state",children:"2.1 Preparation for Release Planning (Input State)"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Refined Features:"})," The features that have been refined and validated by the Expert Groups and committees serve as the primary input for the Release Planning."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Backlog Pre-Prioritization:"})," Prior to the Release Planning meeting, the committee, with input from Expert Groups and contributors, prepares a pre-prioritized list of backlog issues. This list reflects the importance and urgency of each issue based on the project's goals."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"22-release-planning-meeting",children:"2.2 Release Planning Meeting"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Attendees:"})," Contributors, committers, Expert Groups, and committees attend the Release Planning meeting."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Scope Definition:"})," The meeting's primary objective is to define the scope of the next PI. This includes discussing the refined features and the pre-prioritized backlog."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Review of Pre-Prioritized Backlog:"})," The pre-prioritized backlog is reviewed to ensure that it aligns with the project's strategic direction and available resources."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"23-decision-making-by-committers",children:"2.3 Decision-Making by Committers"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Realistic Scope Assessment:"})," Committers play a crucial role in the Release Planning process. They assess the proposed features and backlog issues to determine what is realistically achievable in the next PI, considering review, maintenance, and test efforts."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Final Prioritization:"})," Committers have the final call on the prioritization of issues, ensuring that the most critical and feasible items are included in the PI scope."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Resource Allocation:"})," Decisions regarding the allocation of resources, including developer time and testing infrastructure, are made to support the prioritized issues."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"24-outcome-of-release-planning",children:"2.4 Outcome of Release Planning"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"PI Objectives:"})," The outcome of the Release Planning meeting is a set of clear PI objectives that outline the expected deliverables for the next increment."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Commitment:"})," Teams and individuals commit to the work they will deliver, fostering accountability and setting clear expectations for the upcoming PI."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Roadmap Update:"})," The project's roadmap is updated to reflect the decisions made during the Release Planning, providing transparency to stakeholders and the community."]}),"\n"]}),"\n",(0,t.jsx)(n.h4,{id:"25-communication-and-documentation",children:"2.5 Communication and Documentation"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Documentation of Decisions:"})," All decisions and commitments made during the Release Planning are documented and made accessible to the project's stakeholders."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Communication Plan:"})," A communication plan is established to keep all parties informed about progress and any changes to the PI objectives."]}),"\n"]})]})}function h(e={}){const{wrapper:n}={...(0,s.R)(),...e.components};return n?(0,t.jsx)(n,{...e,children:(0,t.jsx)(c,{...e})}):c(e)}},8453:(e,n,i)=>{i.d(n,{R:()=>o,x:()=>a});var t=i(6540);const s={},r=t.createContext(s);function o(e){const n=t.useContext(r);return t.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function a(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:o(e.components),t.createElement(r.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/a618e3e0.b2684b5d.js b/assets/js/a618e3e0.b2684b5d.js deleted file mode 100644 index edf745c3..00000000 --- a/assets/js/a618e3e0.b2684b5d.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[4182],{7854:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>l,contentTitle:()=>o,default:()=>h,frontMatter:()=>r,metadata:()=>a,toc:()=>d});var t=i(4848),s=i(8453);const r={sidebar_position:3,title:"Contribution Levels"},o=void 0,a={id:"working-model/process-from-idea-to-production/03-04-Issue-Process",title:"Contribution Levels",description:"Table of Contents",source:"@site/docs/working-model/03-process-from-idea-to-production/03-04-Issue-Process.md",sourceDirName:"working-model/03-process-from-idea-to-production",slug:"/working-model/process-from-idea-to-production/03-04-Issue-Process",permalink:"/docs/next/working-model/process-from-idea-to-production/03-04-Issue-Process",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:3,frontMatter:{sidebar_position:3,title:"Contribution Levels"},sidebar:"sidebar_working_model",previous:{title:"Tractus-X Open Source Project Contribution Guide",permalink:"/docs/next/working-model/process-from-idea-to-production/03-02-Contribution-Guideline"},next:{title:"Glossary",permalink:"/docs/next/working-model/glossary"}},l={},d=[{value:"General Feature Contributions",id:"general-feature-contributions",level:2},{value:"Create New Feature Inside SIG-Release",id:"create-new-feature-inside-sig-release",level:3},{value:"Add Feature Details",id:"add-feature-details",level:3},{value:"Labeling and Tracking",id:"labeling-and-tracking",level:3},{value:"Milestones and Assignees",id:"milestones-and-assignees",level:3},{value:"1. Feature Refinement",id:"1-feature-refinement",level:2},{value:"1.1 Initial Review by Expert Group and Committee",id:"11-initial-review-by-expert-group-and-committee",level:3},{value:"1.2 Contributor's Responsibility",id:"12-contributors-responsibility",level:3},{value:"1.3 Feature Validation and Approval",id:"13-feature-validation-and-approval",level:3},{value:"1.4 Deadline for Inclusion in Release Planning",id:"14-deadline-for-inclusion-in-release-planning",level:3},{value:"2. Release Planning",id:"2-release-planning",level:2},{value:"2.1 Preparation for Release Planning (Input State)",id:"21-preparation-for-release-planning-input-state",level:3},{value:"2.2 Release Planning Meeting",id:"22-release-planning-meeting",level:3},{value:"2.3 Decision-Making by Committers",id:"23-decision-making-by-committers",level:3},{value:"2.4 Outcome of Release Planning",id:"24-outcome-of-release-planning",level:3},{value:"2.5 Communication and Documentation",id:"25-communication-and-documentation",level:4}];function c(e){const n={a:"a",admonition:"admonition",h2:"h2",h3:"h3",h4:"h4",li:"li",ol:"ol",p:"p",strong:"strong",ul:"ul",...(0,s.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(n.p,{children:"Table of Contents"}),"\n",(0,t.jsxs)(n.ol,{children:["\n",(0,t.jsx)(n.li,{children:(0,t.jsx)(n.a,{href:"#1-feature-refinement",children:"Feature Refinement"})}),"\n",(0,t.jsx)(n.li,{children:(0,t.jsx)(n.a,{href:"#2-release-planning",children:"Release Planning"})}),"\n"]}),"\n",(0,t.jsx)(n.admonition,{type:"info",children:(0,t.jsxs)(n.p,{children:[(0,t.jsx)(n.a,{href:"#general-feature-contributions",children:"General Feature Contributions"})," is this still needed?"]})}),"\n",(0,t.jsx)(n.h2,{id:"general-feature-contributions",children:"General Feature Contributions"}),"\n",(0,t.jsx)(n.p,{children:"Contributing features involves adding new functionality or enhancing existing features within the Tractus-X project. Here's the process to follow:"}),"\n",(0,t.jsx)(n.h3,{id:"create-new-feature-inside-sig-release",children:"Create New Feature Inside SIG-Release"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Access the SIG-Release repository:"})," Navigate to the SIG-Release repository within the Tractus-X project."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Use the feature template:"})," Find the feature template and fill it out with the necessary details about the new feature you're proposing."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Submit the template:"})," Once completed, submit the template to the SIG-Release for consideration."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"add-feature-details",children:"Add Feature Details"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Feature Description:"})," Clearly describe the feature, its purpose, and how it benefits the project."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Dependencies:"})," List any dependencies required for the feature."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Contribution:"})," Explain how others can contribute to the development of this feature."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Test Scope:"})," Define the scope of testing required for the feature to ensure it works as intended."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Affected Components/Repos:"})," Identify which components or repositories will be affected by this feature."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"labeling-and-tracking",children:"Labeling and Tracking"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Add Relevant Labels:"})," Apply labels related to the products and PI (Program Increment) version to your feature request for easy tracking."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Link to Release Planning Dashboard:"})," Ensure your feature is linked to the release planning dashboard for visibility and tracking."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"milestones-and-assignees",children:"Milestones and Assignees"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Keep Milestones Open:"})," Do not assign a specific milestone; leave it open for the maintainers to assign."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Assignee:"})," Leave the assignee field open unless you plan to take on the feature development yourself."]}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"1-feature-refinement",children:"1. Feature Refinement"}),"\n",(0,t.jsx)(n.p,{children:"Once a new feature proposal has been made for the Tractus-X project, it enters a validation phase where Expert Groups and committees review the proposal. Here is a step-by-step guide on what happens after a feature proposal is submitted:"}),"\n",(0,t.jsx)(n.h3,{id:"11-initial-review-by-expert-group-and-committee",children:"1.1 Initial Review by Expert Group and Committee"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Validation:"})," The Expert Group and committee assigned to the feature area will review the proposal to ensure it aligns with the project's goals and standards."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Request for Additional Details:"})," If the proposal lacks necessary details, the reviewing bodies may ask the contributor for additional information or clarification."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"12-contributors-responsibility",children:"1.2 Contributor's Responsibility"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Responding to Feedback:"})," The contributor is responsible for addressing any feedback provided by the Expert Group or committee. This may include providing additional details or making revisions to the proposal."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Sub Task Creation:"})," If required, the contributor may need to create sub-tasks that break down the feature into manageable pieces. This helps in tracking progress and facilitates easier review."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Timely Updates:"})," The contributor must update the feature details within the given timeframe. Prompt responses and updates are crucial to keep the proposal moving forward."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"13-feature-validation-and-approval",children:"1.3 Feature Validation and Approval"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Approval for Planning:"})," Once the feature has enough detail and meets the project's standards, the Expert Group and committee will approve it for inclusion in the release planning."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Continuous Communication:"})," The contributor should stay in close communication with the Expert Group and committee throughout this process to ensure any issues are promptly addressed."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"14-deadline-for-inclusion-in-release-planning",children:"1.4 Deadline for Inclusion in Release Planning"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Release Planning Cut-off:"})," Features must reach the expected level of detail before the Program Increment (PI) planning meeting. This is a critical deadline."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Consequences of Missing Deadline:"})," If the feature does not meet the required level of detail by the Release Planning, it will not be included in the planning cycle. This means it will likely be deferred to a future PI."]}),"\n"]}),"\n",(0,t.jsx)(n.p,{children:"By following this process, contributors can ensure their feature proposals are considered for inclusion in the Tractus-X project's Release Planning. It is important to be proactive, responsive, and detail-oriented to successfully navigate the post-proposal phase."}),"\n",(0,t.jsx)(n.h2,{id:"2-release-planning",children:"2. Release Planning"}),"\n",(0,t.jsx)(n.p,{children:"Program Increment (PI) Planning is a critical event in the Tractus-X project where contributors, committers, Expert Groups, and committees come together to define the scope for the next PI. This process ensures that the project's roadmap is aligned with stakeholder expectations and the project's strategic objectives. Here's how the Release Planning process typically unfolds:"}),"\n",(0,t.jsx)(n.h3,{id:"21-preparation-for-release-planning-input-state",children:"2.1 Preparation for Release Planning (Input State)"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Refined Features:"})," The features that have been refined and validated by the Expert Groups and committees serve as the primary input for the Release Planning."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Backlog Pre-Prioritization:"})," Prior to the Release Planning meeting, the committee, with input from Expert Groups and contributors, prepares a pre-prioritized list of backlog issues. This list reflects the importance and urgency of each issue based on the project's goals."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"22-release-planning-meeting",children:"2.2 Release Planning Meeting"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Attendees:"})," Contributors, committers, Expert Groups, and committees attend the Release Planning meeting."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Scope Definition:"})," The meeting's primary objective is to define the scope of the next PI. This includes discussing the refined features and the pre-prioritized backlog."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Review of Pre-Prioritized Backlog:"})," The pre-prioritized backlog is reviewed to ensure that it aligns with the project's strategic direction and available resources."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"23-decision-making-by-committers",children:"2.3 Decision-Making by Committers"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Realistic Scope Assessment:"})," Committers play a crucial role in the Release Planning process. They assess the proposed features and backlog issues to determine what is realistically achievable in the next PI, considering review, maintenance, and test efforts."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Final Prioritization:"})," Committers have the final call on the prioritization of issues, ensuring that the most critical and feasible items are included in the PI scope."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Resource Allocation:"})," Decisions regarding the allocation of resources, including developer time and testing infrastructure, are made to support the prioritized issues."]}),"\n"]}),"\n",(0,t.jsx)(n.h3,{id:"24-outcome-of-release-planning",children:"2.4 Outcome of Release Planning"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"PI Objectives:"})," The outcome of the Release Planning meeting is a set of clear PI objectives that outline the expected deliverables for the next increment."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Commitment:"})," Teams and individuals commit to the work they will deliver, fostering accountability and setting clear expectations for the upcoming PI."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Roadmap Update:"})," The project's roadmap is updated to reflect the decisions made during the Release Planning, providing transparency to stakeholders and the community."]}),"\n"]}),"\n",(0,t.jsx)(n.h4,{id:"25-communication-and-documentation",children:"2.5 Communication and Documentation"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Documentation of Decisions:"})," All decisions and commitments made during the Release Planning are documented and made accessible to the project's stakeholders."]}),"\n",(0,t.jsxs)(n.li,{children:[(0,t.jsx)(n.strong,{children:"Communication Plan:"})," A communication plan is established to keep all parties informed about progress and any changes to the PI objectives."]}),"\n"]})]})}function h(e={}){const{wrapper:n}={...(0,s.R)(),...e.components};return n?(0,t.jsx)(n,{...e,children:(0,t.jsx)(c,{...e})}):c(e)}},8453:(e,n,i)=>{i.d(n,{R:()=>o,x:()=>a});var t=i(6540);const s={},r=t.createContext(s);function o(e){const n=t.useContext(r);return t.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function a(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:o(e.components),t.createElement(r.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/a80828e2.28d37de2.js b/assets/js/a80828e2.28d37de2.js new file mode 100644 index 00000000..b97c4710 --- /dev/null +++ b/assets/js/a80828e2.28d37de2.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9371],{2873:(e,r,t)=>{t.r(r),t.d(r,{assets:()=>c,contentTitle:()=>d,default:()=>h,frontMatter:()=>i,metadata:()=>l,toc:()=>o});var s=t(4848),n=t(8453);const i={sidebar_position:1},d="Glossary",l={id:"operating-model/glossary/glossary",title:"Glossary",description:"| Abbreviation | Full form |",source:"@site/versioned_docs/version-24.03/operating-model/glossary/glossary.md",sourceDirName:"operating-model/glossary",slug:"/operating-model/glossary/",permalink:"/catenax-ev.github.io.new/docs/operating-model/glossary/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Outlook",permalink:"/catenax-ev.github.io.new/docs/operating-model/outlook/"},next:{title:"Appendix",permalink:"/catenax-ev.github.io.new/docs/operating-model/appendix/"}},c={},o=[];function a(e){const r={h1:"h1",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",...(0,n.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsx)(r.h1,{id:"glossary",children:"Glossary"}),"\n",(0,s.jsxs)(r.table,{children:[(0,s.jsx)(r.thead,{children:(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.th,{children:"Abbreviation"}),(0,s.jsx)(r.th,{children:"Full form"})]})}),(0,s.jsxs)(r.tbody,{children:[(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"AAS"}),(0,s.jsx)(r.td,{children:"Asset Administration Shell"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"AP"}),(0,s.jsx)(r.td,{children:"Advisory Provider"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"API"}),(0,s.jsx)(r.td,{children:"Application Programming Interfaces"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"BAP"}),(0,s.jsx)(r.td,{children:"Business Application Provider"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"BPN(BPNL, BPNA, BPNS)"}),(0,s.jsx)(r.td,{children:"Business Partner Number (Legal Entities, Addresses, Sites)"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CAB"}),(0,s.jsx)(r.td,{children:"Conformity Assessment Body"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CAC"}),(0,s.jsx)(r.td,{children:"Conformity Assessment Criteria"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"COTS"}),(0,s.jsx)(r.td,{children:"Commercial-off-the-Shelf (Software)"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CSP-A"}),(0,s.jsx)(r.td,{children:"Core Service Provider A"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CSP-B"}),(0,s.jsx)(r.td,{children:"Core Service Provider B"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"cxOS"}),(0,s.jsx)(r.td,{children:"Catena-X Operating System"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"DAPS"}),(0,s.jsx)(r.td,{children:"Dynamic Attribute Provisioning Service"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"DDTR"}),(0,s.jsx)(r.td,{children:"Decentralized Digital Twin Registry"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"DSSC"}),(0,s.jsx)(r.td,{children:"Data Space Support Center"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"EDC"}),(0,s.jsx)(r.td,{children:"Eclipse Data Space Components"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"EDWG"}),(0,s.jsx)(r.td,{children:"Eclipse Data Space Working Group"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"ETL"}),(0,s.jsx)(r.td,{children:"Extract, Transform, Load (Process)"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"GXDCH"}),(0,s.jsx)(r.td,{children:"Gaia-X Digital Clearing House"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"IAM"}),(0,s.jsx)(r.td,{children:"Identity and Access Management"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"IDSA"}),(0,s.jsx)(r.td,{children:"International Data Spaces Association"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"IRS"}),(0,s.jsx)(r.td,{children:"Item Relationship Service"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"MIW"}),(0,s.jsx)(r.td,{children:"Managed Identity Wallet"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"PCF"}),(0,s.jsx)(r.td,{children:"Product Carbon Footprint"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"RfT"}),(0,s.jsx)(r.td,{children:"Request for Tender"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"SaaS"}),(0,s.jsx)(r.td,{children:"Software-as-a-Service"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"SSI"}),(0,s.jsx)(r.td,{children:"Self-Sovereign Identity"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"TRG"}),(0,s.jsx)(r.td,{children:"Tractus-X Release Guideline"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"OSP"}),(0,s.jsx)(r.td,{children:"Onboarding Service Provider"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"VC"}),(0,s.jsx)(r.td,{children:"Verifiable Credential"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"VP"}),(0,s.jsx)(r.td,{children:"Verifiable Presentation"})]})]})]})]})}function h(e={}){const{wrapper:r}={...(0,n.R)(),...e.components};return r?(0,s.jsx)(r,{...e,children:(0,s.jsx)(a,{...e})}):a(e)}},8453:(e,r,t)=>{t.d(r,{R:()=>d,x:()=>l});var s=t(6540);const n={},i=s.createContext(n);function d(e){const r=s.useContext(i);return s.useMemo((function(){return"function"==typeof e?e(r):{...r,...e}}),[r,e])}function l(e){let r;return r=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:d(e.components),s.createElement(i.Provider,{value:r},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/a80828e2.a5eb1300.js b/assets/js/a80828e2.a5eb1300.js deleted file mode 100644 index 221509c0..00000000 --- a/assets/js/a80828e2.a5eb1300.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9371],{2873:(e,r,t)=>{t.r(r),t.d(r,{assets:()=>c,contentTitle:()=>d,default:()=>a,frontMatter:()=>i,metadata:()=>l,toc:()=>o});var s=t(4848),n=t(8453);const i={sidebar_position:1},d="Glossary",l={id:"operating-model/glossary/glossary",title:"Glossary",description:"| Abbreviation | Full form |",source:"@site/versioned_docs/version-24.03/operating-model/glossary/glossary.md",sourceDirName:"operating-model/glossary",slug:"/operating-model/glossary/",permalink:"/docs/operating-model/glossary/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Outlook",permalink:"/docs/operating-model/outlook/"},next:{title:"Appendix",permalink:"/docs/operating-model/appendix/"}},c={},o=[];function h(e){const r={h1:"h1",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",...(0,n.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsx)(r.h1,{id:"glossary",children:"Glossary"}),"\n",(0,s.jsxs)(r.table,{children:[(0,s.jsx)(r.thead,{children:(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.th,{children:"Abbreviation"}),(0,s.jsx)(r.th,{children:"Full form"})]})}),(0,s.jsxs)(r.tbody,{children:[(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"AAS"}),(0,s.jsx)(r.td,{children:"Asset Administration Shell"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"AP"}),(0,s.jsx)(r.td,{children:"Advisory Provider"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"API"}),(0,s.jsx)(r.td,{children:"Application Programming Interfaces"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"BAP"}),(0,s.jsx)(r.td,{children:"Business Application Provider"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"BPN(BPNL, BPNA, BPNS)"}),(0,s.jsx)(r.td,{children:"Business Partner Number (Legal Entities, Addresses, Sites)"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CAB"}),(0,s.jsx)(r.td,{children:"Conformity Assessment Body"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CAC"}),(0,s.jsx)(r.td,{children:"Conformity Assessment Criteria"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"COTS"}),(0,s.jsx)(r.td,{children:"Commercial-off-the-Shelf (Software)"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CSP-A"}),(0,s.jsx)(r.td,{children:"Core Service Provider A"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"CSP-B"}),(0,s.jsx)(r.td,{children:"Core Service Provider B"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"cxOS"}),(0,s.jsx)(r.td,{children:"Catena-X Operating System"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"DAPS"}),(0,s.jsx)(r.td,{children:"Dynamic Attribute Provisioning Service"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"DDTR"}),(0,s.jsx)(r.td,{children:"Decentralized Digital Twin Registry"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"DSSC"}),(0,s.jsx)(r.td,{children:"Data Space Support Center"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"EDC"}),(0,s.jsx)(r.td,{children:"Eclipse Data Space Components"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"EDWG"}),(0,s.jsx)(r.td,{children:"Eclipse Data Space Working Group"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"ETL"}),(0,s.jsx)(r.td,{children:"Extract, Transform, Load (Process)"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"GXDCH"}),(0,s.jsx)(r.td,{children:"Gaia-X Digital Clearing House"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"IAM"}),(0,s.jsx)(r.td,{children:"Identity and Access Management"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"IDSA"}),(0,s.jsx)(r.td,{children:"International Data Spaces Association"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"IRS"}),(0,s.jsx)(r.td,{children:"Item Relationship Service"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"MIW"}),(0,s.jsx)(r.td,{children:"Managed Identity Wallet"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"PCF"}),(0,s.jsx)(r.td,{children:"Product Carbon Footprint"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"RfT"}),(0,s.jsx)(r.td,{children:"Request for Tender"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"SaaS"}),(0,s.jsx)(r.td,{children:"Software-as-a-Service"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"SSI"}),(0,s.jsx)(r.td,{children:"Self-Sovereign Identity"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"TRG"}),(0,s.jsx)(r.td,{children:"Tractus-X Release Guideline"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"OSP"}),(0,s.jsx)(r.td,{children:"Onboarding Service Provider"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"VC"}),(0,s.jsx)(r.td,{children:"Verifiable Credential"})]}),(0,s.jsxs)(r.tr,{children:[(0,s.jsx)(r.td,{children:"VP"}),(0,s.jsx)(r.td,{children:"Verifiable Presentation"})]})]})]})]})}function a(e={}){const{wrapper:r}={...(0,n.R)(),...e.components};return r?(0,s.jsx)(r,{...e,children:(0,s.jsx)(h,{...e})}):h(e)}},8453:(e,r,t)=>{t.d(r,{R:()=>d,x:()=>l});var s=t(6540);const n={},i=s.createContext(n);function d(e){const r=s.useContext(i);return s.useMemo((function(){return"function"==typeof e?e(r):{...r,...e}}),[r,e])}function l(e){let r;return r=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:d(e.components),s.createElement(i.Provider,{value:r},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/aabcef9f.82d66d1c.js b/assets/js/aabcef9f.82d66d1c.js new file mode 100644 index 00000000..53d6511f --- /dev/null +++ b/assets/js/aabcef9f.82d66d1c.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3252],{337:e=>{e.exports=JSON.parse('{"tags":[{"label":"Facebook","permalink":"/catenax-ev.github.io.new/blog/tags/facebook","description":"Facebook tag description","count":1},{"label":"Hello","permalink":"/catenax-ev.github.io.new/blog/tags/hello","description":"Hello tag description","count":2},{"label":"Docusaurus","permalink":"/catenax-ev.github.io.new/blog/tags/docusaurus","description":"Docusaurus tag description","count":4},{"label":"Hola","permalink":"/catenax-ev.github.io.new/blog/tags/hola","description":"Hola tag description","count":1}]}')}}]); \ No newline at end of file diff --git a/assets/js/acecf23e.bc0ec99a.js b/assets/js/acecf23e.1323fa32.js similarity index 57% rename from assets/js/acecf23e.bc0ec99a.js rename to assets/js/acecf23e.1323fa32.js index 86e006f0..12ab423f 100644 --- a/assets/js/acecf23e.bc0ec99a.js +++ b/assets/js/acecf23e.1323fa32.js @@ -1 +1 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[1903],{1912:e=>{e.exports=JSON.parse('{"blogBasePath":"/blog","blogTitle":"Blog"}')}}]); \ No newline at end of file +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[1903],{1912:e=>{e.exports=JSON.parse('{"blogBasePath":"/catenax-ev.github.io.new/blog","blogTitle":"Blog"}')}}]); \ No newline at end of file diff --git a/assets/js/ae9ec75a.1b45b0b2.js b/assets/js/ae9ec75a.1b45b0b2.js new file mode 100644 index 00000000..9613e4d0 --- /dev/null +++ b/assets/js/ae9ec75a.1b45b0b2.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[5155],{8590:(e,t,i)=>{i.r(t),i.d(t,{assets:()=>c,contentTitle:()=>s,default:()=>h,frontMatter:()=>r,metadata:()=>a,toc:()=>d});var n=i(4848),o=i(8453);const r={sidebar_position:2,title:"Tractus-X"},s=void 0,a={id:"working-model/organizational-structure/overview-roles/tractus-x-roles",title:"Tractus-X",description:"Contributor",source:"@site/docs/working-model/02-organizational-structure/overview-roles/tractus-x-roles.md",sourceDirName:"working-model/02-organizational-structure/overview-roles",slug:"/working-model/organizational-structure/overview-roles/tractus-x-roles",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:2,frontMatter:{sidebar_position:2,title:"Tractus-X"},sidebar:"sidebar_working_model",previous:{title:"Catena-X association",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles"},next:{title:"Process Organization - From Idea to Release",permalink:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production"}},c={},d=[{value:"Contributor",id:"contributor",level:2},{value:"Engagement and Contributions",id:"engagement-and-contributions",level:3},{value:"Expectations and Growth",id:"expectations-and-growth",level:3},{value:"Committer",id:"committer",level:2},{value:"Core Responsibilities",id:"core-responsibilities",level:3},{value:"Expectations",id:"expectations",level:3},{value:"Fields of responsibility",id:"fields-of-responsibility",level:3}];function l(e){const t={a:"a",code:"code",h2:"h2",h3:"h3",li:"li",p:"p",strong:"strong",ul:"ul",...(0,o.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(t.h2,{id:"contributor",children:"Contributor"}),"\n",(0,n.jsx)(t.p,{children:"Contributor actively participating in the development process. They contribute code, documentation, bug fixes, and other resources to advance the project's objectives. Additionally, contributors engage in discussions, provide feedback, and collaborate with other members of the project community to improve the project's quality and functionality. Their efforts help drive innovation and ensure the success of the project within the Eclipse ecosystem."}),"\n",(0,n.jsx)(t.p,{children:"Contributors are the lifeblood of any open source project. They bring a project to life, infuse it with diversity, and drive its evolution. This role description outlines the various ways in which contributors can engage with and support the project. While the scope of a contributor's role is broad and can vary widely, the essence of their involvement centers around adding value through various means of participation."}),"\n",(0,n.jsxs)(t.p,{children:["It's important to recognize that the role of a contributor is not confined to this description alone. Open source is a realm of limitless possibilities, and contributors are encouraged to find unique ways to enhance the project based on their individual skills and creativity. The official description for a contributor within Tractus-X can be found ",(0,n.jsx)(t.a,{href:"https://eclipse-tractusx.github.io/docs/oss/contributor-committer#contributor",children:"here"}),"."]}),"\n",(0,n.jsx)(t.h3,{id:"engagement-and-contributions",children:"Engagement and Contributions"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Code Contributions"}),"\r\nContributors may write and submit code patches or new features to the project's codebase. They are encouraged to participate in code reviews and discussions to improve the quality and functionality of their submissions. Make sure you follow the ",(0,n.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-02-Contribution-Guideline",children:"code contribution guidelines"})]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Documentation"}),"\r\nQuality documentation is crucial for user adoption and the ongoing success of the project. Contributors can write, edit, or update documentation to ensure that it is clear, comprehensive, and accessible."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Bug Reports"}),"\r\nIdentifying and reporting bugs is a valuable form of contribution. Contributors help maintain the project's integrity by submitting detailed bug reports that facilitate quick resolutions."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Feature Suggestions"}),"\r\nInnovative ideas are always welcome. Contributors can suggest new features or enhancements that align with the project's vision and user needs."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Testing"}),"\r\nContributors play a critical role in testing new releases, features, and bug fixes. Their feedback is essential for maintaining a stable and reliable project."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Community Support"}),"\r\nEngaging with the community through forums, mailing lists, or chat platforms, contributors provide support, answer questions, and help users navigate the project."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Outreach and Education"}),"\r\nContributors can help promote the project by writing blog posts, conducting workshops, speaking at conferences, and creating educational materials."]}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"expectations-and-growth",children:"Expectations and Growth"}),"\n",(0,n.jsx)(t.p,{children:"Contributors are expected to adhere to the project's code of conduct, collaborate respectfully with other community members, and provide constructive feedback. While there is no formal commitment required, consistent and quality contributions can lead to recognition within the community and may open the door to additional roles, such as becoming a committer or joining an Expert Group."}),"\n",(0,n.jsx)(t.h2,{id:"committer",children:"Committer"}),"\n",(0,n.jsx)(t.p,{children:"Committer in an Eclipse project holds the authority to directly contribute changes to the project's source code repository. They are responsible for reviewing and integrating contributions from other community members, ensuring adherence to project standards and guidelines (in our case TRGs). Additionally, committers play a key role in decision-making processes within the project, actively participating in discussions and providing leadership to drive the project forward."}),"\n",(0,n.jsx)(t.p,{children:"Committers hold a position of trust and responsibility in an open source project. As seasoned contributors who have demonstrated commitment and expertise, they are granted write access to the project's code repository. This role description outlines the core responsibilities and expectations of a committer, but it is important to note that the scope of this role can extend beyond these parameters as the project evolves."}),"\n",(0,n.jsx)(t.p,{children:"While the role is defined by certain responsibilities, committers are also ambassadors of the project's values and culture, and they play a significant part in shaping the project's future."}),"\n",(0,n.jsxs)(t.p,{children:["The official description for a committer within Tractus-X can be found ",(0,n.jsx)(t.a,{href:"https://eclipse-tractusx.github.io/docs/oss/contributor-committer#committer",children:"here"}),"."]}),"\n",(0,n.jsx)(t.h3,{id:"core-responsibilities",children:"Core Responsibilities"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Code Review and Integration"}),"\r\nCommitters are responsible for reviewing code submissions from contributors. They ensure that contributions meet the project's standards for quality, adhere to its coding conventions, and align with its strategic goals. Committers merge accepted changes into the project's codebase."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Mentorship"}),"\r\nCommitters often mentor new contributors, helping them navigate the project's processes, understand its standards, and encouraging best practices. This mentorship helps grow the community and foster a welcoming environment for new participants."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Quality Assurance"}),"\r\nBy overseeing the integrity of the codebase, committers play a critical role in quality assurance. They are involved in testing, identifying, and fixing bugs, and they work to maintain the overall health of the project."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Documentation"}),"\r\nCommitters contribute to and maintain the project's documentation. They ensure that documentation is up-to-date, accurate, and provides clear guidance for users and contributors."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Release Management"}),"\r\nCommitters may be involved in the release process, which includes tagging releases, preparing changelogs, and ensuring that each release adheres to the project's standards."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Community Engagement"}),"\r\nCommitters actively participate in community discussions, offer support, and help resolve disputes. They act as representatives of the project in public forums and may engage in outreach activities."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Governance"}),"\r\nAs key stakeholders in the project, committers may have a role in its governance. They can be involved in strategic planning, decision-making processes, and setting the direction for the project."]}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"expectations",children:"Expectations"}),"\n",(0,n.jsx)(t.p,{children:"Committers are expected to:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Act with integrity and in accordance with the project's code of conduct."}),"\n",(0,n.jsx)(t.li,{children:"Be proactive in their contributions and responsive to community needs."}),"\n",(0,n.jsx)(t.li,{children:"Communicate effectively with other project members."}),"\n",(0,n.jsx)(t.li,{children:"Provide constructive feedback and be receptive to the input of others."}),"\n",(0,n.jsx)(t.li,{children:"Stay informed about the project's progress and participate in relevant discussions."}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"fields-of-responsibility",children:"Fields of responsibility"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.code,{children:"Core committer"})," (product committer) knows their product -> They work on their product and know the TRGs to accept PRs"]}),"\n",(0,n.jsx)(t.li,{children:"Overarching responsibility/view (integration)"}),"\n",(0,n.jsx)(t.li,{children:"Cross-functional fields of expertise, like SIG DevSecOps/Security"}),"\n"]})]})}function h(e={}){const{wrapper:t}={...(0,o.R)(),...e.components};return t?(0,n.jsx)(t,{...e,children:(0,n.jsx)(l,{...e})}):l(e)}},8453:(e,t,i)=>{i.d(t,{R:()=>s,x:()=>a});var n=i(6540);const o={},r=n.createContext(o);function s(e){const t=n.useContext(r);return n.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function a(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(o):e.components||o:s(e.components),n.createElement(r.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/ae9ec75a.c4c54758.js b/assets/js/ae9ec75a.c4c54758.js deleted file mode 100644 index 748825ba..00000000 --- a/assets/js/ae9ec75a.c4c54758.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[5155],{8590:(e,t,i)=>{i.r(t),i.d(t,{assets:()=>c,contentTitle:()=>s,default:()=>h,frontMatter:()=>r,metadata:()=>a,toc:()=>d});var n=i(4848),o=i(8453);const r={sidebar_position:2,title:"Tractus-X"},s=void 0,a={id:"working-model/organizational-structure/overview-roles/tractus-x-roles",title:"Tractus-X",description:"Contributor",source:"@site/docs/working-model/02-organizational-structure/overview-roles/tractus-x-roles.md",sourceDirName:"working-model/02-organizational-structure/overview-roles",slug:"/working-model/organizational-structure/overview-roles/tractus-x-roles",permalink:"/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:2,frontMatter:{sidebar_position:2,title:"Tractus-X"},sidebar:"sidebar_working_model",previous:{title:"Catena-X association",permalink:"/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles"},next:{title:"Process Organization - From Idea to Release",permalink:"/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production"}},c={},d=[{value:"Contributor",id:"contributor",level:2},{value:"Engagement and Contributions",id:"engagement-and-contributions",level:3},{value:"Expectations and Growth",id:"expectations-and-growth",level:3},{value:"Committer",id:"committer",level:2},{value:"Core Responsibilities",id:"core-responsibilities",level:3},{value:"Expectations",id:"expectations",level:3},{value:"Fields of responsibility",id:"fields-of-responsibility",level:3}];function l(e){const t={a:"a",code:"code",h2:"h2",h3:"h3",li:"li",p:"p",strong:"strong",ul:"ul",...(0,o.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(t.h2,{id:"contributor",children:"Contributor"}),"\n",(0,n.jsx)(t.p,{children:"Contributor actively participating in the development process. They contribute code, documentation, bug fixes, and other resources to advance the project's objectives. Additionally, contributors engage in discussions, provide feedback, and collaborate with other members of the project community to improve the project's quality and functionality. Their efforts help drive innovation and ensure the success of the project within the Eclipse ecosystem."}),"\n",(0,n.jsx)(t.p,{children:"Contributors are the lifeblood of any open source project. They bring a project to life, infuse it with diversity, and drive its evolution. This role description outlines the various ways in which contributors can engage with and support the project. While the scope of a contributor's role is broad and can vary widely, the essence of their involvement centers around adding value through various means of participation."}),"\n",(0,n.jsxs)(t.p,{children:["It's important to recognize that the role of a contributor is not confined to this description alone. Open source is a realm of limitless possibilities, and contributors are encouraged to find unique ways to enhance the project based on their individual skills and creativity. The official description for a contributor within Tractus-X can be found ",(0,n.jsx)(t.a,{href:"https://eclipse-tractusx.github.io/docs/oss/contributor-committer#contributor",children:"here"}),"."]}),"\n",(0,n.jsx)(t.h3,{id:"engagement-and-contributions",children:"Engagement and Contributions"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Code Contributions"}),"\r\nContributors may write and submit code patches or new features to the project's codebase. They are encouraged to participate in code reviews and discussions to improve the quality and functionality of their submissions. Make sure you follow the ",(0,n.jsx)(t.a,{href:"/docs/next/working-model/process-from-idea-to-production/03-02-Contribution-Guideline",children:"code contribution guidelines"})]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Documentation"}),"\r\nQuality documentation is crucial for user adoption and the ongoing success of the project. Contributors can write, edit, or update documentation to ensure that it is clear, comprehensive, and accessible."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Bug Reports"}),"\r\nIdentifying and reporting bugs is a valuable form of contribution. Contributors help maintain the project's integrity by submitting detailed bug reports that facilitate quick resolutions."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Feature Suggestions"}),"\r\nInnovative ideas are always welcome. Contributors can suggest new features or enhancements that align with the project's vision and user needs."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Testing"}),"\r\nContributors play a critical role in testing new releases, features, and bug fixes. Their feedback is essential for maintaining a stable and reliable project."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Community Support"}),"\r\nEngaging with the community through forums, mailing lists, or chat platforms, contributors provide support, answer questions, and help users navigate the project."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Outreach and Education"}),"\r\nContributors can help promote the project by writing blog posts, conducting workshops, speaking at conferences, and creating educational materials."]}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"expectations-and-growth",children:"Expectations and Growth"}),"\n",(0,n.jsx)(t.p,{children:"Contributors are expected to adhere to the project's code of conduct, collaborate respectfully with other community members, and provide constructive feedback. While there is no formal commitment required, consistent and quality contributions can lead to recognition within the community and may open the door to additional roles, such as becoming a committer or joining an Expert Group."}),"\n",(0,n.jsx)(t.h2,{id:"committer",children:"Committer"}),"\n",(0,n.jsx)(t.p,{children:"Committer in an Eclipse project holds the authority to directly contribute changes to the project's source code repository. They are responsible for reviewing and integrating contributions from other community members, ensuring adherence to project standards and guidelines (in our case TRGs). Additionally, committers play a key role in decision-making processes within the project, actively participating in discussions and providing leadership to drive the project forward."}),"\n",(0,n.jsx)(t.p,{children:"Committers hold a position of trust and responsibility in an open source project. As seasoned contributors who have demonstrated commitment and expertise, they are granted write access to the project's code repository. This role description outlines the core responsibilities and expectations of a committer, but it is important to note that the scope of this role can extend beyond these parameters as the project evolves."}),"\n",(0,n.jsx)(t.p,{children:"While the role is defined by certain responsibilities, committers are also ambassadors of the project's values and culture, and they play a significant part in shaping the project's future."}),"\n",(0,n.jsxs)(t.p,{children:["The official description for a committer within Tractus-X can be found ",(0,n.jsx)(t.a,{href:"https://eclipse-tractusx.github.io/docs/oss/contributor-committer#committer",children:"here"}),"."]}),"\n",(0,n.jsx)(t.h3,{id:"core-responsibilities",children:"Core Responsibilities"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Code Review and Integration"}),"\r\nCommitters are responsible for reviewing code submissions from contributors. They ensure that contributions meet the project's standards for quality, adhere to its coding conventions, and align with its strategic goals. Committers merge accepted changes into the project's codebase."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Mentorship"}),"\r\nCommitters often mentor new contributors, helping them navigate the project's processes, understand its standards, and encouraging best practices. This mentorship helps grow the community and foster a welcoming environment for new participants."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Quality Assurance"}),"\r\nBy overseeing the integrity of the codebase, committers play a critical role in quality assurance. They are involved in testing, identifying, and fixing bugs, and they work to maintain the overall health of the project."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Documentation"}),"\r\nCommitters contribute to and maintain the project's documentation. They ensure that documentation is up-to-date, accurate, and provides clear guidance for users and contributors."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Release Management"}),"\r\nCommitters may be involved in the release process, which includes tagging releases, preparing changelogs, and ensuring that each release adheres to the project's standards."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Community Engagement"}),"\r\nCommitters actively participate in community discussions, offer support, and help resolve disputes. They act as representatives of the project in public forums and may engage in outreach activities."]}),"\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.strong,{children:"Governance"}),"\r\nAs key stakeholders in the project, committers may have a role in its governance. They can be involved in strategic planning, decision-making processes, and setting the direction for the project."]}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"expectations",children:"Expectations"}),"\n",(0,n.jsx)(t.p,{children:"Committers are expected to:"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsx)(t.li,{children:"Act with integrity and in accordance with the project's code of conduct."}),"\n",(0,n.jsx)(t.li,{children:"Be proactive in their contributions and responsive to community needs."}),"\n",(0,n.jsx)(t.li,{children:"Communicate effectively with other project members."}),"\n",(0,n.jsx)(t.li,{children:"Provide constructive feedback and be receptive to the input of others."}),"\n",(0,n.jsx)(t.li,{children:"Stay informed about the project's progress and participate in relevant discussions."}),"\n"]}),"\n",(0,n.jsx)(t.h3,{id:"fields-of-responsibility",children:"Fields of responsibility"}),"\n",(0,n.jsxs)(t.ul,{children:["\n",(0,n.jsxs)(t.li,{children:[(0,n.jsx)(t.code,{children:"Core committer"})," (product committer) knows their product -> They work on their product and know the TRGs to accept PRs"]}),"\n",(0,n.jsx)(t.li,{children:"Overarching responsibility/view (integration)"}),"\n",(0,n.jsx)(t.li,{children:"Cross-functional fields of expertise, like SIG DevSecOps/Security"}),"\n"]})]})}function h(e={}){const{wrapper:t}={...(0,o.R)(),...e.components};return t?(0,n.jsx)(t,{...e,children:(0,n.jsx)(l,{...e})}):l(e)}},8453:(e,t,i)=>{i.d(t,{R:()=>s,x:()=>a});var n=i(6540);const o={},r=n.createContext(o);function s(e){const t=n.useContext(r);return n.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function a(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(o):e.components||o:s(e.components),n.createElement(r.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/b2cb1568.44a52af5.js b/assets/js/b2cb1568.44a52af5.js new file mode 100644 index 00000000..975e5b83 --- /dev/null +++ b/assets/js/b2cb1568.44a52af5.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[7220],{502:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>d,contentTitle:()=>s,default:()=>h,frontMatter:()=>r,metadata:()=>o,toc:()=>l});var t=i(4848),a=i(8453);const r={sidebar_position:1},s="Change Log",o={id:"operating-model/change-log/change-log",title:"Change Log",description:"Added",source:"@site/docs/operating-model/change-log/change-log.md",sourceDirName:"operating-model/change-log",slug:"/operating-model/change-log/",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/change-log/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Appendix",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/appendix/"}},d={},l=[{value:"Added",id:"added",level:2},{value:"Changed/Updated",id:"changedupdated",level:2},{value:"Unchanged",id:"unchanged",level:2}];function c(e){const n={h1:"h1",h2:"h2",li:"li",ul:"ul",...(0,a.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(n.h1,{id:"change-log",children:"Change Log"}),"\n",(0,t.jsx)(n.h2,{id:"added",children:"Added"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Role: Catena-X Automotive Network e.V."}),"\n",(0,t.jsx)(n.li,{children:"Service Map: Onboarding Service Category"}),"\n",(0,t.jsxs)(n.li,{children:["Data Space Operations: Providing information, guidelines, and premises on how to participate and exchange data in the data space:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"General Onboarding Process"}),"\n",(0,t.jsx)(n.li,{children:"Gaia-X Compliance"}),"\n",(0,t.jsx)(n.li,{children:"SSI Issuer Concept"}),"\n",(0,t.jsx)(n.li,{children:"Data Exchange based on SSI"}),"\n",(0,t.jsx)(n.li,{children:"EDC Deployment and Usage Premises"}),"\n"]}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["Life Cycle Management:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Versioning"}),"\n",(0,t.jsx)(n.li,{children:"Backward Compatibility"}),"\n"]}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["Data Space Governance:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Qualification Process"}),"\n",(0,t.jsx)(n.li,{children:"Exceptions"}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"changedupdated",children:"Changed/Updated"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Introduction: clarity and readability improvements"}),"\n",(0,t.jsxs)(n.li,{children:["Roles:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Re-naming of consulting provider to advisory provider"}),"\n",(0,t.jsx)(n.li,{children:"Detailing the description of all roles with responsibilities, respective relationships, prerequisites, and complements"}),"\n"]}),"\n"]}),"\n",(0,t.jsx)(n.li,{children:"Service Map: Update of service map according to Tractus-X release 23.09"}),"\n",(0,t.jsx)(n.li,{children:"Standardization process: reference provided to standardization policy that details the Catena-X standardization process further"}),"\n",(0,t.jsx)(n.li,{children:"Certification process: reference provided to Conformity Assessment Framework that details the Catena-X certification process further"}),"\n",(0,t.jsx)(n.li,{children:"Labels: Removed distinguishing factors between Certified Operating Company and Certified Partner"}),"\n",(0,t.jsx)(n.li,{children:"Outlook: updated according to release 23.09"}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"unchanged",children:"Unchanged"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Nomination Process"}),"\n"]})]})}function h(e={}){const{wrapper:n}={...(0,a.R)(),...e.components};return n?(0,t.jsx)(n,{...e,children:(0,t.jsx)(c,{...e})}):c(e)}},8453:(e,n,i)=>{i.d(n,{R:()=>s,x:()=>o});var t=i(6540);const a={},r=t.createContext(a);function s(e){const n=t.useContext(r);return t.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function o(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(a):e.components||a:s(e.components),t.createElement(r.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/b2cb1568.f099de7c.js b/assets/js/b2cb1568.f099de7c.js deleted file mode 100644 index 915b7574..00000000 --- a/assets/js/b2cb1568.f099de7c.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[7220],{502:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>d,contentTitle:()=>s,default:()=>h,frontMatter:()=>a,metadata:()=>o,toc:()=>l});var t=i(4848),r=i(8453);const a={sidebar_position:1},s="Change Log",o={id:"operating-model/change-log/change-log",title:"Change Log",description:"Added",source:"@site/docs/operating-model/change-log/change-log.md",sourceDirName:"operating-model/change-log",slug:"/operating-model/change-log/",permalink:"/docs/next/operating-model/change-log/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"Appendix",permalink:"/docs/next/operating-model/appendix/"}},d={},l=[{value:"Added",id:"added",level:2},{value:"Changed/Updated",id:"changedupdated",level:2},{value:"Unchanged",id:"unchanged",level:2}];function c(e){const n={h1:"h1",h2:"h2",li:"li",ul:"ul",...(0,r.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(n.h1,{id:"change-log",children:"Change Log"}),"\n",(0,t.jsx)(n.h2,{id:"added",children:"Added"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Role: Catena-X Automotive Network e.V."}),"\n",(0,t.jsx)(n.li,{children:"Service Map: Onboarding Service Category"}),"\n",(0,t.jsxs)(n.li,{children:["Data Space Operations: Providing information, guidelines, and premises on how to participate and exchange data in the data space:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"General Onboarding Process"}),"\n",(0,t.jsx)(n.li,{children:"Gaia-X Compliance"}),"\n",(0,t.jsx)(n.li,{children:"SSI Issuer Concept"}),"\n",(0,t.jsx)(n.li,{children:"Data Exchange based on SSI"}),"\n",(0,t.jsx)(n.li,{children:"EDC Deployment and Usage Premises"}),"\n"]}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["Life Cycle Management:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Versioning"}),"\n",(0,t.jsx)(n.li,{children:"Backward Compatibility"}),"\n"]}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["Data Space Governance:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Qualification Process"}),"\n",(0,t.jsx)(n.li,{children:"Exceptions"}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"changedupdated",children:"Changed/Updated"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Introduction: clarity and readability improvements"}),"\n",(0,t.jsxs)(n.li,{children:["Roles:","\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Re-naming of consulting provider to advisory provider"}),"\n",(0,t.jsx)(n.li,{children:"Detailing the description of all roles with responsibilities, respective relationships, prerequisites, and complements"}),"\n"]}),"\n"]}),"\n",(0,t.jsx)(n.li,{children:"Service Map: Update of service map according to Tractus-X release 23.09"}),"\n",(0,t.jsx)(n.li,{children:"Standardization process: reference provided to standardization policy that details the Catena-X standardization process further"}),"\n",(0,t.jsx)(n.li,{children:"Certification process: reference provided to Conformity Assessment Framework that details the Catena-X certification process further"}),"\n",(0,t.jsx)(n.li,{children:"Labels: Removed distinguishing factors between Certified Operating Company and Certified Partner"}),"\n",(0,t.jsx)(n.li,{children:"Outlook: updated according to release 23.09"}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"unchanged",children:"Unchanged"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"Nomination Process"}),"\n"]})]})}function h(e={}){const{wrapper:n}={...(0,r.R)(),...e.components};return n?(0,t.jsx)(n,{...e,children:(0,t.jsx)(c,{...e})}):c(e)}},8453:(e,n,i)=>{i.d(n,{R:()=>s,x:()=>o});var t=i(6540);const r={},a=t.createContext(r);function s(e){const n=t.useContext(a);return t.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function o(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(r):e.components||r:s(e.components),t.createElement(a.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/bf1307fc.113673dd.js b/assets/js/bf1307fc.113673dd.js deleted file mode 100644 index bd0d3b8b..00000000 --- a/assets/js/bf1307fc.113673dd.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9525],{1413:e=>{e.exports=JSON.parse('{"version":{"pluginId":"default","version":"current","label":"Next","banner":"unreleased","badge":true,"noIndex":false,"className":"docs-version-current","isLast":false,"docsSidebars":{"sidebar_standards":[{"type":"link","label":"Overview Standards","href":"/docs/next/standards/overview","docId":"standards/overview","unlisted":false}],"sidebar_op_model":[{"type":"link","label":"Operating Model","href":"/docs/next/operating-model/operating-model/","docId":"operating-model/operating-model/operating-model","unlisted":false},{"type":"link","label":"Who: Roles in the Catena-X ecosystem","href":"/docs/next/operating-model/why-introduction/","docId":"operating-model/why-introduction/why-introduction","unlisted":false},{"type":"link","label":"Why: Understanding the Catena-X Data Space","href":"/docs/next/operating-model/why-understanding-the-catena-x-data-space/","docId":"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space","unlisted":false},{"type":"link","label":"Who: Roles in the Catena-X ecosystem","href":"/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/","docId":"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem","unlisted":false},{"type":"link","label":"What: Service Map","href":"/docs/next/operating-model/what-service-map/","docId":"operating-model/what-service-map/what-service-map","unlisted":false},{"type":"link","label":"How: Data Space Operations","href":"/docs/next/operating-model/how-data-space-operations/","docId":"operating-model/how-data-space-operations/how-data-space-operations","unlisted":false},{"type":"link","label":"How: Data Space Governance","href":"/docs/next/operating-model/how-data-space-governance/","docId":"operating-model/how-data-space-governance/how-data-space-governance","unlisted":false},{"type":"link","label":"How: Life Cycle Management","href":"/docs/next/operating-model/how-life-cycle-management/","docId":"operating-model/how-life-cycle-management/how-life-cycle-management","unlisted":false},{"type":"link","label":"Outlook","href":"/docs/next/operating-model/outlook/","docId":"operating-model/outlook/outlook","unlisted":false},{"type":"link","label":"Glossary","href":"/docs/next/operating-model/glossary/","docId":"operating-model/glossary/glossary","unlisted":false},{"type":"link","label":"Appendix","href":"/docs/next/operating-model/appendix/","docId":"operating-model/appendix/appendix","unlisted":false},{"type":"link","label":"Change Log","href":"/docs/next/operating-model/change-log/","docId":"operating-model/change-log/change-log","unlisted":false}],"sidebar_working_model":[{"type":"link","label":"Overview","href":"/docs/next/working-model/overview","docId":"working-model/overview","unlisted":false},{"type":"link","label":"Catena-X Ecosystem","href":"/docs/next/working-model/ecosystem/","docId":"working-model/ecosystem/ecosystem","unlisted":false},{"type":"category","label":"Organizational Structure","collapsible":true,"collapsed":true,"items":[{"type":"link","label":"Tooling","href":"/docs/next/working-model/organizational-structure/02-03-tooling","docId":"working-model/organizational-structure/02-03-tooling","unlisted":false},{"type":"category","label":"Overview roles","collapsible":true,"collapsed":true,"items":[{"type":"link","label":"Catena-X association","href":"/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles","docId":"working-model/organizational-structure/overview-roles/catena-x-roles","unlisted":false},{"type":"link","label":"Tractus-X","href":"/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles","docId":"working-model/organizational-structure/overview-roles/tractus-x-roles","unlisted":false}],"href":"/docs/next/working-model/organizational-structure/overview-roles/"}],"href":"/docs/next/working-model/organizational-structure/"},{"type":"category","label":"Process Structure","collapsible":true,"collapsed":true,"items":[{"type":"link","label":"Process Organization - From Idea to Release","href":"/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production","docId":"working-model/process-from-idea-to-production/03-01-process-from-idea-to-production","unlisted":false},{"type":"link","label":"Tractus-X Open Source Project Contribution Guide","href":"/docs/next/working-model/process-from-idea-to-production/03-02-Contribution-Guideline","docId":"working-model/process-from-idea-to-production/03-02-Contribution-Guideline","unlisted":false},{"type":"link","label":"Contribution Levels","href":"/docs/next/working-model/process-from-idea-to-production/03-04-Issue-Process","docId":"working-model/process-from-idea-to-production/03-04-Issue-Process","unlisted":false}]},{"type":"link","label":"Glossary","href":"/docs/next/working-model/glossary","docId":"working-model/glossary","unlisted":false}]},"docs":{"operating-model/appendix/appendix":{"id":"operating-model/appendix/appendix","title":"Appendix","description":"Role Relationships","sidebar":"sidebar_op_model"},"operating-model/change-log/change-log":{"id":"operating-model/change-log/change-log","title":"Change Log","description":"Added","sidebar":"sidebar_op_model"},"operating-model/glossary/glossary":{"id":"operating-model/glossary/glossary","title":"Glossary","description":"| Abbreviation | Full form |","sidebar":"sidebar_op_model"},"operating-model/how-data-space-governance/how-data-space-governance":{"id":"operating-model/how-data-space-governance/how-data-space-governance","title":"How: Data Space Governance","description":"Standardization","sidebar":"sidebar_op_model"},"operating-model/how-data-space-operations/how-data-space-operations":{"id":"operating-model/how-data-space-operations/how-data-space-operations","title":"How: Data Space Operations","description":"This chapter outlines the overarching processes and premises to onboard and exchange","sidebar":"sidebar_op_model"},"operating-model/how-life-cycle-management/how-life-cycle-management":{"id":"operating-model/how-life-cycle-management/how-life-cycle-management","title":"How: Life Cycle Management","description":"Managing versions and changes of different artifacts in federated data spaces is critical to ensure compatibility, interoperability, and security. The life cycle management of the Catena-X ecosystem is coordinated by the Catena-X Association and includes the releases in the Catena-X Association and in the Eclipse Tractus-X Project (see Figure Overview Life Cycle Management). It is planned to provide quarterly releases including one major and three minor releases per year. Both releases follow calendar versioning (see CalVer), whereas their artifacts such as standards, normative documents, products, and KITs follow semantic versioning (see SemVer). To ensure backward compatibility in the future (see Chapter Backward Compatibility), versioning and passing of predefined test cases of each individual artifact is mandatory.","sidebar":"sidebar_op_model"},"operating-model/operating-model/operating-model":{"id":"operating-model/operating-model/operating-model","title":"Catena-X Operating Model","description":"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.","sidebar":"sidebar_op_model"},"operating-model/outlook/outlook":{"id":"operating-model/outlook/outlook","title":"Outlook","description":"The Catena-X Operating Model is a normative document within the regulatory framework, which is binding for all participants in the Catena-X data space. It describes the status of our data space artifacts, including roles, services, and processes along with their respective roadmaps. As Catena-X is an ongoing journey, all of these artifacts will continuously evolve to promote broader adoption and scalability, ensuring maximum interoperability, and (data) sovereignty.","sidebar":"sidebar_op_model"},"operating-model/what-service-map/what-service-map":{"id":"operating-model/what-service-map/what-service-map","title":"What: Service Map","description":"The architecture of the Catena-X Operating System (cxOS) is derived from the reference","sidebar":"sidebar_op_model"},"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem":{"id":"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem","title":"Who: Roles in the Catena-X ecosystem","description":"The Catena-X ecosystem operates on the principle of multiple distinct roles, designed to create an appealing and functional data space (see Figure Role Overview and Relationships). Participants can take on one or more roles in any combination, and multiple participants can fulfill the same role except for the CSP-B role. The CSP-B role can only exist once in the data space due to complexity and technical reasons. Provider roles receive a label through a certification or qualification process to demonstrate that they are trusted partners (see Chapter How: Life Cycle Management).","sidebar":"sidebar_op_model"},"operating-model/why-introduction/why-introduction":{"id":"operating-model/why-introduction/why-introduction","title":"Why: Introduction","description":"Relevance","sidebar":"sidebar_op_model"},"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space":{"id":"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space","title":"Why: Understanding the Catena-X Data Space","description":"Conceptual Foundations of the Catena-X Data Ecosystem","sidebar":"sidebar_op_model"},"standards/overview":{"id":"standards/overview","title":"Overview Standards","description":"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.","sidebar":"sidebar_standards"},"working-model/ecosystem/ecosystem":{"id":"working-model/ecosystem/ecosystem","title":"Catena-X Ecosystem","description":"The Catena-X ecosystem consists of three areas","sidebar":"sidebar_working_model"},"working-model/glossary":{"id":"working-model/glossary","title":"Glossary","description":"| Abbreviation | Full form |","sidebar":"sidebar_working_model"},"working-model/organizational-structure/02-03-tooling":{"id":"working-model/organizational-structure/02-03-tooling","title":"Tooling","description":"This is just a short description about the different tools. The usage of these tools is described in the coresponding sections.","sidebar":"sidebar_working_model"},"working-model/organizational-structure/organizational-structure":{"id":"working-model/organizational-structure/organizational-structure","title":"Catena-X Organizational Structure","description":"Catena-X OrgChart","sidebar":"sidebar_working_model"},"working-model/organizational-structure/overview-roles/catena-x-roles":{"id":"working-model/organizational-structure/overview-roles/catena-x-roles","title":"Catena-X association","description":"General","sidebar":"sidebar_working_model"},"working-model/organizational-structure/overview-roles/overview-roles":{"id":"working-model/organizational-structure/overview-roles/overview-roles","title":"Overview of roles and groups","description":"Welcome to the \\"Open Source Roles\\" section of our documentation. This chapter is dedicated to providing a comprehensive overview of the various roles that are integral to the success and sustainability of our open source project. Open source projects thrive on the collaboration and contributions of a diverse and active community. Understanding the different roles within this ecosystem is crucial for both current and prospective members who wish to engage with and contribute to the project.","sidebar":"sidebar_working_model"},"working-model/organizational-structure/overview-roles/tractus-x-roles":{"id":"working-model/organizational-structure/overview-roles/tractus-x-roles","title":"Tractus-X","description":"Contributor","sidebar":"sidebar_working_model"},"working-model/overview":{"id":"working-model/overview","title":"Overview","description":"Introduction","sidebar":"sidebar_working_model"},"working-model/process-from-idea-to-production/03-01-process-from-idea-to-production":{"id":"working-model/process-from-idea-to-production/03-01-process-from-idea-to-production","title":"Process Organization - From Idea to Release","description":"Coming soon....","sidebar":"sidebar_working_model"},"working-model/process-from-idea-to-production/03-02-Contribution-Guideline":{"id":"working-model/process-from-idea-to-production/03-02-Contribution-Guideline","title":"Tractus-X Open Source Project Contribution Guide","description":"Welcome to the Tractus-X open source project! This guide is designed to help you understand how you can contribute to the Tractus-X project. There are different levels of contributions you can make, such as standard contributions, feature contributions and improvements.","sidebar":"sidebar_working_model"},"working-model/process-from-idea-to-production/03-04-Issue-Process":{"id":"working-model/process-from-idea-to-production/03-04-Issue-Process","title":"Contribution Levels","description":"Table of Contents","sidebar":"sidebar_working_model"}}}}')}}]); \ No newline at end of file diff --git a/assets/js/c11d2165.6f42c32c.js b/assets/js/c11d2165.6f42c32c.js deleted file mode 100644 index c112f80b..00000000 --- a/assets/js/c11d2165.6f42c32c.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[440],{4270:(e,t,i)=>{i.r(t),i.d(t,{assets:()=>l,contentTitle:()=>s,default:()=>u,frontMatter:()=>r,metadata:()=>a,toc:()=>c});var o=i(4848),n=i(8453);const r={sidebar_position:3,title:"Tooling"},s=void 0,a={id:"working-model/organizational-structure/02-03-tooling",title:"Tooling",description:"This is just a short description about the different tools. The usage of these tools is described in the coresponding sections.",source:"@site/docs/working-model/02-organizational-structure/02-03-tooling.md",sourceDirName:"working-model/02-organizational-structure",slug:"/working-model/organizational-structure/02-03-tooling",permalink:"/docs/next/working-model/organizational-structure/02-03-tooling",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:3,frontMatter:{sidebar_position:3,title:"Tooling"},sidebar:"sidebar_working_model",previous:{title:"Catena-X Organizational Structure",permalink:"/docs/next/working-model/organizational-structure/"},next:{title:"Overview of roles and groups",permalink:"/docs/next/working-model/organizational-structure/overview-roles/"}},l={},c=[{value:"Microsoft Teams",id:"microsoft-teams",level:2},{value:"Main topic",id:"main-topic",level:3},{value:"GitHub",id:"github",level:2},{value:"Eclipse Tooling",id:"eclipse-tooling",level:2},{value:"Testtool",id:"testtool",level:2}];function d(e){const t={a:"a",admonition:"admonition",code:"code",h2:"h2",h3:"h3",li:"li",p:"p",ul:"ul",...(0,n.R)(),...e.components};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsxs)(t.p,{children:["This is just a short description about the different tools. The usage of these tools is described in the coresponding ",(0,o.jsx)(t.a,{href:"/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production",children:"sections"}),"."]}),"\n",(0,o.jsx)(t.h2,{id:"microsoft-teams",children:"Microsoft Teams"}),"\n",(0,o.jsx)(t.p,{children:"Microsoft Teams is a good starting point for Expert Groups and Committees. After they are built up, they can decide to use GitHub in a private repository, or MS Team in a private channel."}),"\n",(0,o.jsx)(t.admonition,{type:"warning",children:(0,o.jsx)(t.p,{children:"All open-source content has to be in Tractus-X. The privtae teams and repository are more for the day to day work, files and task planner/ issue tracker"})}),"\n",(0,o.jsx)(t.h3,{id:"main-topic",children:"Main topic"}),"\n",(0,o.jsxs)(t.ul,{children:["\n",(0,o.jsx)(t.li,{children:"Communication sytsem"}),"\n",(0,o.jsx)(t.li,{children:"Taskplanning"}),"\n",(0,o.jsx)(t.li,{children:"Filestorage"}),"\n",(0,o.jsx)(t.li,{children:'"Knowledgestore"'}),"\n"]}),"\n",(0,o.jsx)(t.h2,{id:"github",children:"GitHub"}),"\n",(0,o.jsx)(t.p,{children:"GitHub is the main tool for development, when we talk about the Eclipse Tractus-X Project, the open-source part. GitHub is also getting more and more relevant for the Committee and Expert Group work."}),"\n",(0,o.jsx)(t.p,{children:"There are two main organizations in GitHub:"}),"\n",(0,o.jsxs)(t.ul,{children:["\n",(0,o.jsxs)(t.li,{children:[(0,o.jsx)(t.a,{href:"https://github.com/catenax-eV/",children:"catenax-eV (Catena-X Automotive Network e.V.)"})," -> standards, Committee and Expert Group work"]}),"\n",(0,o.jsxs)(t.li,{children:[(0,o.jsx)(t.a,{href:"https://github.com/eclipse-tractusx",children:"eclipse-tractusx -> Eclipse Tractus-X Project"})," -> open-source"]}),"\n"]}),"\n",(0,o.jsx)(t.admonition,{type:"note",children:(0,o.jsxs)(t.ul,{children:["\n",(0,o.jsx)(t.li,{children:"for the open-source part (reference implementations and Kits) GitHub is mandatory. Its used for planning, issue tracking, discussions, development, reviews and release etc."}),"\n",(0,o.jsx)(t.li,{children:"for the standardization part, GitHub is also set as mandatory"}),"\n",(0,o.jsx)(t.li,{children:"for Committee work and Expert Groups the Association provides private repositories within the catenax-eV organization"}),"\n"]})}),"\n",(0,o.jsx)(t.h2,{id:"eclipse-tooling",children:"Eclipse Tooling"}),"\n",(0,o.jsxs)(t.p,{children:["In Eclipse Tractus-X we mainly use open-source tooling provided by the Eclipse Foundation ",(0,o.jsx)(t.a,{href:"https://eclipse-tractusx.github.io/community/intro",children:"https://eclipse-tractusx.github.io/community/intro"})]}),"\n",(0,o.jsxs)(t.p,{children:["The Eclipse Foundation provides a ",(0,o.jsx)(t.code,{children:"Matrix Chat"})," for open communication. It can be used via Eclipse account. There are several rooms available for different topics. The main room for Tractus-X is ",(0,o.jsxs)(t.a,{href:"https://matrix.to/#/#tractusx:matrix.eclipse.org",children:["#tractusx",":matrix",".eclipse.org"]}),"."]}),"\n",(0,o.jsxs)(t.p,{children:["There is also a ",(0,o.jsx)(t.a,{href:"https://accounts.eclipse.org/mailing-list/tractusx-dev",children:"tractusx-dev mailing list"})," available to reach out to all subscribed Tractus-X contributer. Within this list the importent open meetings are shared as also committer elections and other importnet information related to Tractus-X."]}),"\n",(0,o.jsx)(t.admonition,{type:"info",children:(0,o.jsx)(t.p,{children:"Please subscribe to the mailinglist."})}),"\n",(0,o.jsx)(t.h2,{id:"testtool",children:"Testtool"}),"\n",(0,o.jsx)(t.admonition,{type:"info",children:(0,o.jsx)(t.p,{children:"TBD"})})]})}function u(e={}){const{wrapper:t}={...(0,n.R)(),...e.components};return t?(0,o.jsx)(t,{...e,children:(0,o.jsx)(d,{...e})}):d(e)}},8453:(e,t,i)=>{i.d(t,{R:()=>s,x:()=>a});var o=i(6540);const n={},r=o.createContext(n);function s(e){const t=o.useContext(r);return o.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function a(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:s(e.components),o.createElement(r.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/c11d2165.a098c856.js b/assets/js/c11d2165.a098c856.js new file mode 100644 index 00000000..c399d4c5 --- /dev/null +++ b/assets/js/c11d2165.a098c856.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[440],{4270:(e,t,i)=>{i.r(t),i.d(t,{assets:()=>l,contentTitle:()=>s,default:()=>u,frontMatter:()=>r,metadata:()=>a,toc:()=>c});var o=i(4848),n=i(8453);const r={sidebar_position:3,title:"Tooling"},s=void 0,a={id:"working-model/organizational-structure/02-03-tooling",title:"Tooling",description:"This is just a short description about the different tools. The usage of these tools is described in the coresponding sections.",source:"@site/docs/working-model/02-organizational-structure/02-03-tooling.md",sourceDirName:"working-model/02-organizational-structure",slug:"/working-model/organizational-structure/02-03-tooling",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/02-03-tooling",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:3,frontMatter:{sidebar_position:3,title:"Tooling"},sidebar:"sidebar_working_model",previous:{title:"Catena-X Organizational Structure",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/"},next:{title:"Overview of roles and groups",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/"}},l={},c=[{value:"Microsoft Teams",id:"microsoft-teams",level:2},{value:"Main topic",id:"main-topic",level:3},{value:"GitHub",id:"github",level:2},{value:"Eclipse Tooling",id:"eclipse-tooling",level:2},{value:"Testtool",id:"testtool",level:2}];function d(e){const t={a:"a",admonition:"admonition",code:"code",h2:"h2",h3:"h3",li:"li",p:"p",ul:"ul",...(0,n.R)(),...e.components};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsxs)(t.p,{children:["This is just a short description about the different tools. The usage of these tools is described in the coresponding ",(0,o.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production",children:"sections"}),"."]}),"\n",(0,o.jsx)(t.h2,{id:"microsoft-teams",children:"Microsoft Teams"}),"\n",(0,o.jsx)(t.p,{children:"Microsoft Teams is a good starting point for Expert Groups and Committees. After they are built up, they can decide to use GitHub in a private repository, or MS Team in a private channel."}),"\n",(0,o.jsx)(t.admonition,{type:"warning",children:(0,o.jsx)(t.p,{children:"All open-source content has to be in Tractus-X. The privtae teams and repository are more for the day to day work, files and task planner/ issue tracker"})}),"\n",(0,o.jsx)(t.h3,{id:"main-topic",children:"Main topic"}),"\n",(0,o.jsxs)(t.ul,{children:["\n",(0,o.jsx)(t.li,{children:"Communication sytsem"}),"\n",(0,o.jsx)(t.li,{children:"Taskplanning"}),"\n",(0,o.jsx)(t.li,{children:"Filestorage"}),"\n",(0,o.jsx)(t.li,{children:'"Knowledgestore"'}),"\n"]}),"\n",(0,o.jsx)(t.h2,{id:"github",children:"GitHub"}),"\n",(0,o.jsx)(t.p,{children:"GitHub is the main tool for development, when we talk about the Eclipse Tractus-X Project, the open-source part. GitHub is also getting more and more relevant for the Committee and Expert Group work."}),"\n",(0,o.jsx)(t.p,{children:"There are two main organizations in GitHub:"}),"\n",(0,o.jsxs)(t.ul,{children:["\n",(0,o.jsxs)(t.li,{children:[(0,o.jsx)(t.a,{href:"https://github.com/catenax-eV/",children:"catenax-eV (Catena-X Automotive Network e.V.)"})," -> standards, Committee and Expert Group work"]}),"\n",(0,o.jsxs)(t.li,{children:[(0,o.jsx)(t.a,{href:"https://github.com/eclipse-tractusx",children:"eclipse-tractusx -> Eclipse Tractus-X Project"})," -> open-source"]}),"\n"]}),"\n",(0,o.jsx)(t.admonition,{type:"note",children:(0,o.jsxs)(t.ul,{children:["\n",(0,o.jsx)(t.li,{children:"for the open-source part (reference implementations and Kits) GitHub is mandatory. Its used for planning, issue tracking, discussions, development, reviews and release etc."}),"\n",(0,o.jsx)(t.li,{children:"for the standardization part, GitHub is also set as mandatory"}),"\n",(0,o.jsx)(t.li,{children:"for Committee work and Expert Groups the Association provides private repositories within the catenax-eV organization"}),"\n"]})}),"\n",(0,o.jsx)(t.h2,{id:"eclipse-tooling",children:"Eclipse Tooling"}),"\n",(0,o.jsxs)(t.p,{children:["In Eclipse Tractus-X we mainly use open-source tooling provided by the Eclipse Foundation ",(0,o.jsx)(t.a,{href:"https://eclipse-tractusx.github.io/community/intro",children:"https://eclipse-tractusx.github.io/community/intro"})]}),"\n",(0,o.jsxs)(t.p,{children:["The Eclipse Foundation provides a ",(0,o.jsx)(t.code,{children:"Matrix Chat"})," for open communication. It can be used via Eclipse account. There are several rooms available for different topics. The main room for Tractus-X is ",(0,o.jsxs)(t.a,{href:"https://matrix.to/#/#tractusx:matrix.eclipse.org",children:["#tractusx",":matrix",".eclipse.org"]}),"."]}),"\n",(0,o.jsxs)(t.p,{children:["There is also a ",(0,o.jsx)(t.a,{href:"https://accounts.eclipse.org/mailing-list/tractusx-dev",children:"tractusx-dev mailing list"})," available to reach out to all subscribed Tractus-X contributer. Within this list the importent open meetings are shared as also committer elections and other importnet information related to Tractus-X."]}),"\n",(0,o.jsx)(t.admonition,{type:"info",children:(0,o.jsx)(t.p,{children:"Please subscribe to the mailinglist."})}),"\n",(0,o.jsx)(t.h2,{id:"testtool",children:"Testtool"}),"\n",(0,o.jsx)(t.admonition,{type:"info",children:(0,o.jsx)(t.p,{children:"TBD"})})]})}function u(e={}){const{wrapper:t}={...(0,n.R)(),...e.components};return t?(0,o.jsx)(t,{...e,children:(0,o.jsx)(d,{...e})}):d(e)}},8453:(e,t,i)=>{i.d(t,{R:()=>s,x:()=>a});var o=i(6540);const n={},r=o.createContext(n);function s(e){const t=o.useContext(r);return o.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function a(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:s(e.components),o.createElement(r.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/c15d9823.2860de81.js b/assets/js/c15d9823.2860de81.js deleted file mode 100644 index f63a9463..00000000 --- a/assets/js/c15d9823.2860de81.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8146],{9328:e=>{e.exports=JSON.parse('{"metadata":{"permalink":"/blog","page":1,"postsPerPage":10,"totalPages":1,"totalCount":4,"blogDescription":"Blog","blogTitle":"Blog"}}')}}]); \ No newline at end of file diff --git a/assets/js/cd8fd8f7.49890ea6.js b/assets/js/cd8fd8f7.49890ea6.js new file mode 100644 index 00000000..c22b1d10 --- /dev/null +++ b/assets/js/cd8fd8f7.49890ea6.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[5145],{9265:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>a,contentTitle:()=>d,default:()=>h,frontMatter:()=>l,metadata:()=>r,toc:()=>o});var s=i(4848),t=i(8453);const l={},d="Catena-X e.V. Structure and Guidelines",r={type:"mdx",permalink:"/catenax-ev.github.io.new/markdown-guidelines",source:"@site/src/pages/markdown-guidelines.md",title:"Catena-X e.V. Structure and Guidelines",description:"Repository Structure and files",frontMatter:{},unlisted:!1},a={},o=[{value:"Repository Structure and files",id:"repository-structure-and-files",level:2},{value:"Folder and File structure",id:"folder-and-file-structure",level:3},{value:"Special & default files",id:"special--default-files",level:3},{value:"How to order MD files in a folder?",id:"how-to-order-md-files-in-a-folder",level:3},{value:"How to order the chapters?",id:"how-to-order-the-chapters",level:4},{value:"MD file guidelines and best practices",id:"md-file-guidelines-and-best-practices",level:2},{value:"Headings",id:"headings",level:3},{value:"DOs - Headings",id:"dos---headings",level:4},{value:"Don'ts - Headings",id:"donts---headings",level:4},{value:"Bolt",id:"bolt",level:3},{value:"DOs - Bolt",id:"dos---bolt",level:4},{value:"Don'ts - Bolt",id:"donts---bolt",level:4},{value:"Italic",id:"italic",level:3},{value:"DOs - Italic",id:"dos---italic",level:4},{value:"Don'ts - Italic",id:"donts---italic",level:4},{value:"Lists - unordered",id:"lists---unordered",level:3},{value:"DOs - Lists unordered",id:"dos---lists-unordered",level:4},{value:"Don'ts - Lists unordered",id:"donts---lists-unordered",level:4},{value:"Lists - ordered",id:"lists---ordered",level:3},{value:"DOs - Lists ordered",id:"dos---lists-ordered",level:4},{value:"Don'ts - Lists ordered",id:"donts---lists-ordered",level:4},{value:"Images/Figures",id:"imagesfigures",level:3},{value:"DOs - Images/Figures",id:"dos---imagesfigures",level:4},{value:"Code",id:"code",level:3},{value:"DOs - Code",id:"dos---code",level:4},{value:"Links/URLs/E-Mail/Phone numbers",id:"linksurlse-mailphone-numbers",level:3},{value:"DOs - Links/URLs/E-Mail/Phone numbers",id:"dos---linksurlse-mailphone-numbers",level:4},{value:"Don'ts - Links/URLs/E-Mail/Phone numbers",id:"donts---linksurlse-mailphone-numbers",level:4},{value:"Admonitions",id:"admonitions",level:3},{value:"DOs - Admonitions",id:"dos---admonitions",level:4},{value:"Link to chapters/headlines",id:"link-to-chaptersheadlines",level:2},{value:"DOs - chapters/headlines",id:"dos---chaptersheadlines",level:3}];function c(e){const n={a:"a",admonition:"admonition",br:"br",code:"code",em:"em",h1:"h1",h2:"h2",h3:"h3",h4:"h4",li:"li",ol:"ol",p:"p",pre:"pre",strong:"strong",ul:"ul",...(0,t.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsx)(n.h1,{id:"catena-x-ev-structure-and-guidelines",children:"Catena-X e.V. Structure and Guidelines"}),"\n",(0,s.jsx)(n.h2,{id:"repository-structure-and-files",children:"Repository Structure and files"}),"\n",(0,s.jsx)(n.p,{children:'The following shows the default structure of a given repository. All the files which will be released with the content are contained in the "docs" folder. All the folders, files and assets are named in the kebab-case convention.'}),"\n",(0,s.jsx)(n.h3,{id:"folder-and-file-structure",children:"Folder and File structure"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-md",children:"github-repo\n\u251c\u2500\u2500 .github\n\u251c\u2500\u2500 docs\n\u2502 \u251c\u2500\u2500 my-first-chapter\n\u2502 \u2502 \u251c\u2500\u2500 my-first-chapter.md\n\u2502 \u2502 \u251c\u2500\u2500 _category_.json\n\u2502 \u2502 \u2514\u2500\u2500 assets\n\u2502 \u2502 \u251c\u2500\u2500 my-image-for-the-chapter.jpg\n\u2502 \u2502 \u251c\u2500\u2500 nice-image.png\n\u2502 \u2502 \u2514\u2500\u2500 nice-asset.xyz\n\u2502 \u2514\u2500\u2500 my-second-chapter\n\u2502 \u251c\u2500\u2500 my-second-chapter.md\n\u2502 \u251c\u2500\u2500 my-subchapter-in-chapter-two.md\n\u2502 \u251c\u2500\u2500 _category_.json\n\u2502 \u2514\u2500\u2500 assets\n\u2502 \u251c\u2500\u2500 my-other-image-for-the-chapter.jpg\n\u2502 \u251c\u2500\u2500 nice-image-2.png\n\u2502 \u2514\u2500\u2500 nice-asset-4.xyz\n\u251c\u2500\u2500 .gitignore\n\u251c\u2500\u2500 .markdownlint.yaml\n\u251c\u2500\u2500 CHANGELOG.md\n\u251c\u2500\u2500 getting-started-github.md\n\u251c\u2500\u2500 LICENSE\n\u2514\u2500\u2500 README.md\n"})}),"\n",(0,s.jsx)(n.h3,{id:"special--default-files",children:"Special & default files"}),"\n",(0,s.jsx)(n.p,{children:'In order to display and render the "docs" folder successfully within docusaurus we need some special files e.g. to determine the order of the given content.'}),"\n",(0,s.jsx)(n.h3,{id:"how-to-order-md-files-in-a-folder",children:"How to order MD files in a folder?"}),"\n",(0,s.jsx)(n.p,{children:"To order multiple MD files in a given folder there must be a specific heading at the beginning of the file. This has to be added by default even is there aren't multiple files in a given folder."}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-md",children:"---\nsidebar_position: 1\n---\n# How: Data Space Governance\n"})}),"\n",(0,s.jsxs)(n.p,{children:["In the example above the title of the document is ",(0,s.jsx)(n.code,{children:"How: Data Space Governance"}),". In this case the name of the MD file and the folder would be ",(0,s.jsx)(n.code,{children:"how-data-space-governance"})," and the file would be ",(0,s.jsx)(n.code,{children:"how-data-space-governance.md"}),". In the example the files is the first one in the order within the folder. The order can be arranged by changing the number incrementally in the key ",(0,s.jsx)(n.code,{children:"sidebar_position"})," starting from ",(0,s.jsx)(n.code,{children:"1"}),"."]}),"\n",(0,s.jsx)(n.h4,{id:"how-to-order-the-chapters",children:"How to order the chapters?"}),"\n",(0,s.jsxs)(n.p,{children:["To order the folders and therefor the chapters in the correct order so they get displayed correctly, there must be a ",(0,s.jsx)(n.code,{children:"_category_.json"})," in each folder. This contains the following content:"]}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-json",children:'{\n "label": "How: Data Space Governance",\n "position": 4,\n "collapsible": true,\n "collapsed": true\n}\n'})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:[(0,s.jsx)(n.strong,{children:"label"}),": corresponds with the title of the file in this example ",(0,s.jsx)(n.code,{children:"How: Data Space Governance"}),"."]}),"\n",(0,s.jsxs)(n.li,{children:[(0,s.jsx)(n.strong,{children:"position"}),": position of the folder in the overall structure, in this example its the firth chapter."]}),"\n",(0,s.jsxs)(n.li,{children:[(0,s.jsx)(n.strong,{children:"collapsible"}),": is the list of chapters collapsible ",(0,s.jsx)(n.code,{children:"default=true"}),"."]}),"\n",(0,s.jsxs)(n.li,{children:[(0,s.jsx)(n.strong,{children:"collapsed"}),": is the default view collapsed ",(0,s.jsx)(n.code,{children:"default=true"}),"?"]}),"\n"]}),"\n",(0,s.jsx)(n.h2,{id:"md-file-guidelines-and-best-practices",children:"MD file guidelines and best practices"}),"\n",(0,s.jsx)(n.p,{children:"In the following section the best practices in writing MD files and guidelines on how we in Catena-X write MD files."}),"\n",(0,s.jsx)(n.h3,{id:"headings",children:"Headings"}),"\n",(0,s.jsx)(n.h4,{id:"dos---headings",children:"DOs - Headings"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"# This a heading in the first order\n## This a heading in the first order\n"})}),"\n",(0,s.jsx)(n.h4,{id:"donts---headings",children:"Don'ts - Headings"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"This a heading in the first order\n=================================\nThis a heading in the first order\n---------------------------------\n"})}),"\n",(0,s.jsx)(n.h3,{id:"bolt",children:"Bolt"}),"\n",(0,s.jsx)(n.h4,{id:"dos---bolt",children:"DOs - Bolt"}),"\n",(0,s.jsxs)(n.p,{children:["In this sentence ",(0,s.jsx)(n.strong,{children:"this part"})," is bolt."]}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"In this sentence **this part** is bolt.\n"})}),"\n",(0,s.jsx)(n.h4,{id:"donts---bolt",children:"Don'ts - Bolt"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"In this sentence **this** **part** is bolt.\nIn this sentence __this part__ is bolt.\nIn this sentence __this__ __part__ is bolt.\n"})}),"\n",(0,s.jsx)(n.h3,{id:"italic",children:"Italic"}),"\n",(0,s.jsx)(n.h4,{id:"dos---italic",children:"DOs - Italic"}),"\n",(0,s.jsxs)(n.p,{children:["In this sentence ",(0,s.jsx)(n.em,{children:"this part"})," is italic."]}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"In this sentence *this part* is italic.\n"})}),"\n",(0,s.jsx)(n.h4,{id:"donts---italic",children:"Don'ts - Italic"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"In this sentence *this* *part* is italic.\nIn this sentence _this part_ is italic.\nIn this sentence _this_ _part_ is italic.\n"})}),"\n",(0,s.jsx)(n.h3,{id:"lists---unordered",children:"Lists - unordered"}),"\n",(0,s.jsx)(n.h4,{id:"dos---lists-unordered",children:"DOs - Lists unordered"}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsx)(n.li,{children:"first item"}),"\n",(0,s.jsxs)(n.li,{children:["second item","\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsx)(n.li,{children:"sub item"}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"- first item\n- second item\n - sub item\n"})}),"\n",(0,s.jsx)(n.h4,{id:"donts---lists-unordered",children:"Don'ts - Lists unordered"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"- first item\n+ second item\n * sub item\n"})}),"\n",(0,s.jsx)(n.h3,{id:"lists---ordered",children:"Lists - ordered"}),"\n",(0,s.jsx)(n.h4,{id:"dos---lists-ordered",children:"DOs - Lists ordered"}),"\n",(0,s.jsxs)(n.ol,{children:["\n",(0,s.jsx)(n.li,{children:"first item"}),"\n",(0,s.jsxs)(n.li,{children:["second item","\n",(0,s.jsxs)(n.ol,{children:["\n",(0,s.jsx)(n.li,{children:"sub item"}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"1. first item\n2. second item\n 1. sub item\n"})}),"\n",(0,s.jsx)(n.h4,{id:"donts---lists-ordered",children:"Don'ts - Lists ordered"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"1) first item\n2) second item\n 1) sub item\n"})}),"\n",(0,s.jsx)(n.h3,{id:"imagesfigures",children:"Images/Figures"}),"\n",(0,s.jsx)(n.p,{children:'In addition to the image itself we also provide a alternatives text "alt" in the square brackets. In markdown captions are not supported. We will use the same text as the "alt" in italic writing directly under the image.'}),"\n",(0,s.jsx)(n.h4,{id:"dos---imagesfigures",children:"DOs - Images/Figures"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"![Nice Image](./assets/nice-image.png)\n*Nice Image*\n"})}),"\n",(0,s.jsx)(n.p,{children:'Alt text is the same as the "caption".'}),"\n",(0,s.jsx)(n.h3,{id:"code",children:"Code"}),"\n",(0,s.jsx)(n.h4,{id:"dos---code",children:"DOs - Code"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-java",children:"// the hello world program\nconsole.log('Hello World');\n"})}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-md",children:" ```java\n // the hello world program\n console.log('Hello World');\n"})}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{children:"\n### Text-Box\n\nA `text` in a box\n\n```md\n A `text` in a box\n"})}),"\n",(0,s.jsx)(n.h3,{id:"linksurlse-mailphone-numbers",children:"Links/URLs/E-Mail/Phone numbers"}),"\n",(0,s.jsx)(n.p,{children:"Due to to the use of docusaurus the convention is the following:"}),"\n",(0,s.jsx)(n.h4,{id:"dos---linksurlse-mailphone-numbers",children:"DOs - Links/URLs/E-Mail/Phone numbers"}),"\n",(0,s.jsxs)(n.p,{children:["Go and visit ",(0,s.jsx)(n.a,{href:"https://catena-x.net/en/",children:"Catena-X"}),(0,s.jsx)(n.br,{}),"\n","E-Mail is here: ",(0,s.jsx)(n.a,{href:"mailto:info@catena-x.net",children:"info@catena-x.net"}),(0,s.jsx)(n.br,{}),"\n","Phone number: ",(0,s.jsx)(n.a,{href:"tel:+49123456798",children:"+49 123 456798"})]}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-md",children:" Go and visit [Catena-X](https://catena-x.net/en/) \n E-Mail is here: [info@catena-x.net](mailto:info@catena-x.net) \n Phone number: [+49 123 456798](tel:+49123456798) \n"})}),"\n",(0,s.jsx)(n.h4,{id:"donts---linksurlse-mailphone-numbers",children:"Don'ts - Links/URLs/E-Mail/Phone numbers"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-md",children:" Go and visit Catena-X \n E-Mail ist here: \n"})}),"\n",(0,s.jsx)(n.h3,{id:"admonitions",children:"Admonitions"}),"\n",(0,s.jsxs)(n.p,{children:["They are not getting rendered correctly in the MD files but in docusaurus. Further information can be found ",(0,s.jsx)(n.a,{href:"https://docusaurus.io/docs/markdown-features/admonitions",children:"here"}),"."]}),"\n",(0,s.jsx)(n.h4,{id:"dos---admonitions",children:"DOs - Admonitions"}),"\n",(0,s.jsx)(n.admonition,{type:"tip",children:(0,s.jsxs)(n.p,{children:["Some ",(0,s.jsx)(n.strong,{children:"content"})," with ",(0,s.jsx)(n.em,{children:"Markdown"})," ",(0,s.jsx)(n.code,{children:"syntax"}),"."]})}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-md",children:":::tip\n\nSome **content** with *Markdown* `syntax`.\n\n:::\n"})}),"\n",(0,s.jsx)(n.h2,{id:"link-to-chaptersheadlines",children:"Link to chapters/headlines"}),"\n",(0,s.jsx)(n.h3,{id:"dos---chaptersheadlines",children:"DOs - chapters/headlines"}),"\n",(0,s.jsx)(n.p,{children:'Be aware if there is a "-" in the heading the IntelliSense in VS Code adds one "-" to many, which results in a error in the MDX linter. In addition if you want to link to the title of the file don\'t tag the heading with "#" it in the link, just link to the file itself. This would result in a error in the MDX linter.'}),"\n",(0,s.jsxs)(n.p,{children:["Jump back to the ",(0,s.jsx)(n.a,{href:"#catena-x-ev-structure-and-guidelines",children:"Top"}),(0,s.jsx)(n.br,{}),"\n","Jump to another ",(0,s.jsx)(n.a,{href:"/getting-started-github#branching",children:"file"})]}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-md",children:" Jump back to the [Top](#catena-x-ev-structure-and-guidelines) \n Jump to another [file](/getting-started-github#branching) \n"})})]})}function h(e={}){const{wrapper:n}={...(0,t.R)(),...e.components};return n?(0,s.jsx)(n,{...e,children:(0,s.jsx)(c,{...e})}):c(e)}},8453:(e,n,i)=>{i.d(n,{R:()=>d,x:()=>r});var s=i(6540);const t={},l=s.createContext(t);function d(e){const n=s.useContext(l);return s.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function r(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(t):e.components||t:d(e.components),s.createElement(l.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/cd8fd8f7.c9eb6ea1.js b/assets/js/cd8fd8f7.c9eb6ea1.js deleted file mode 100644 index 1be78162..00000000 --- a/assets/js/cd8fd8f7.c9eb6ea1.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[5145],{9265:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>a,contentTitle:()=>d,default:()=>h,frontMatter:()=>l,metadata:()=>r,toc:()=>o});var s=i(4848),t=i(8453);const l={},d="Catena-X e.V. Structure and Guidelines",r={type:"mdx",permalink:"/markdown-guidelines",source:"@site/src/pages/markdown-guidelines.md",title:"Catena-X e.V. Structure and Guidelines",description:"Repository Structure and files",frontMatter:{},unlisted:!1},a={},o=[{value:"Repository Structure and files",id:"repository-structure-and-files",level:2},{value:"Folder and File structure",id:"folder-and-file-structure",level:3},{value:"Special & default files",id:"special--default-files",level:3},{value:"How to order MD files in a folder?",id:"how-to-order-md-files-in-a-folder",level:3},{value:"How to order the chapters?",id:"how-to-order-the-chapters",level:4},{value:"MD file guidelines and best practices",id:"md-file-guidelines-and-best-practices",level:2},{value:"Headings",id:"headings",level:3},{value:"DOs - Headings",id:"dos---headings",level:4},{value:"Don'ts - Headings",id:"donts---headings",level:4},{value:"Bolt",id:"bolt",level:3},{value:"DOs - Bolt",id:"dos---bolt",level:4},{value:"Don'ts - Bolt",id:"donts---bolt",level:4},{value:"Italic",id:"italic",level:3},{value:"DOs - Italic",id:"dos---italic",level:4},{value:"Don'ts - Italic",id:"donts---italic",level:4},{value:"Lists - unordered",id:"lists---unordered",level:3},{value:"DOs - Lists unordered",id:"dos---lists-unordered",level:4},{value:"Don'ts - Lists unordered",id:"donts---lists-unordered",level:4},{value:"Lists - ordered",id:"lists---ordered",level:3},{value:"DOs - Lists ordered",id:"dos---lists-ordered",level:4},{value:"Don'ts - Lists ordered",id:"donts---lists-ordered",level:4},{value:"Images/Figures",id:"imagesfigures",level:3},{value:"DOs - Images/Figures",id:"dos---imagesfigures",level:4},{value:"Code",id:"code",level:3},{value:"DOs - Code",id:"dos---code",level:4},{value:"Links/URLs/E-Mail/Phone numbers",id:"linksurlse-mailphone-numbers",level:3},{value:"DOs - Links/URLs/E-Mail/Phone numbers",id:"dos---linksurlse-mailphone-numbers",level:4},{value:"Don'ts - Links/URLs/E-Mail/Phone numbers",id:"donts---linksurlse-mailphone-numbers",level:4},{value:"Admonitions",id:"admonitions",level:3},{value:"DOs - Admonitions",id:"dos---admonitions",level:4},{value:"Link to chapters/headlines",id:"link-to-chaptersheadlines",level:2},{value:"DOs - chapters/headlines",id:"dos---chaptersheadlines",level:3}];function c(e){const n={a:"a",admonition:"admonition",br:"br",code:"code",em:"em",h1:"h1",h2:"h2",h3:"h3",h4:"h4",li:"li",ol:"ol",p:"p",pre:"pre",strong:"strong",ul:"ul",...(0,t.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsx)(n.h1,{id:"catena-x-ev-structure-and-guidelines",children:"Catena-X e.V. Structure and Guidelines"}),"\n",(0,s.jsx)(n.h2,{id:"repository-structure-and-files",children:"Repository Structure and files"}),"\n",(0,s.jsx)(n.p,{children:'The following shows the default structure of a given repository. All the files which will be released with the content are contained in the "docs" folder. All the folders, files and assets are named in the kebab-case convention.'}),"\n",(0,s.jsx)(n.h3,{id:"folder-and-file-structure",children:"Folder and File structure"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-md",children:"github-repo\n\u251c\u2500\u2500 .github\n\u251c\u2500\u2500 docs\n\u2502 \u251c\u2500\u2500 my-first-chapter\n\u2502 \u2502 \u251c\u2500\u2500 my-first-chapter.md\n\u2502 \u2502 \u251c\u2500\u2500 _category_.json\n\u2502 \u2502 \u2514\u2500\u2500 assets\n\u2502 \u2502 \u251c\u2500\u2500 my-image-for-the-chapter.jpg\n\u2502 \u2502 \u251c\u2500\u2500 nice-image.png\n\u2502 \u2502 \u2514\u2500\u2500 nice-asset.xyz\n\u2502 \u2514\u2500\u2500 my-second-chapter\n\u2502 \u251c\u2500\u2500 my-second-chapter.md\n\u2502 \u251c\u2500\u2500 my-subchapter-in-chapter-two.md\n\u2502 \u251c\u2500\u2500 _category_.json\n\u2502 \u2514\u2500\u2500 assets\n\u2502 \u251c\u2500\u2500 my-other-image-for-the-chapter.jpg\n\u2502 \u251c\u2500\u2500 nice-image-2.png\n\u2502 \u2514\u2500\u2500 nice-asset-4.xyz\n\u251c\u2500\u2500 .gitignore\n\u251c\u2500\u2500 .markdownlint.yaml\n\u251c\u2500\u2500 CHANGELOG.md\n\u251c\u2500\u2500 getting-started-github.md\n\u251c\u2500\u2500 LICENSE\n\u2514\u2500\u2500 README.md\n"})}),"\n",(0,s.jsx)(n.h3,{id:"special--default-files",children:"Special & default files"}),"\n",(0,s.jsx)(n.p,{children:'In order to display and render the "docs" folder successfully within docusaurus we need some special files e.g. to determine the order of the given content.'}),"\n",(0,s.jsx)(n.h3,{id:"how-to-order-md-files-in-a-folder",children:"How to order MD files in a folder?"}),"\n",(0,s.jsx)(n.p,{children:"To order multiple MD files in a given folder there must be a specific heading at the beginning of the file. This has to be added by default even is there aren't multiple files in a given folder."}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-md",children:"---\nsidebar_position: 1\n---\n# How: Data Space Governance\n"})}),"\n",(0,s.jsxs)(n.p,{children:["In the example above the title of the document is ",(0,s.jsx)(n.code,{children:"How: Data Space Governance"}),". In this case the name of the MD file and the folder would be ",(0,s.jsx)(n.code,{children:"how-data-space-governance"})," and the file would be ",(0,s.jsx)(n.code,{children:"how-data-space-governance.md"}),". In the example the files is the first one in the order within the folder. The order can be arranged by changing the number incrementally in the key ",(0,s.jsx)(n.code,{children:"sidebar_position"})," starting from ",(0,s.jsx)(n.code,{children:"1"}),"."]}),"\n",(0,s.jsx)(n.h4,{id:"how-to-order-the-chapters",children:"How to order the chapters?"}),"\n",(0,s.jsxs)(n.p,{children:["To order the folders and therefor the chapters in the correct order so they get displayed correctly, there must be a ",(0,s.jsx)(n.code,{children:"_category_.json"})," in each folder. This contains the following content:"]}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-json",children:'{\n "label": "How: Data Space Governance",\n "position": 4,\n "collapsible": true,\n "collapsed": true\n}\n'})}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsxs)(n.li,{children:[(0,s.jsx)(n.strong,{children:"label"}),": corresponds with the title of the file in this example ",(0,s.jsx)(n.code,{children:"How: Data Space Governance"}),"."]}),"\n",(0,s.jsxs)(n.li,{children:[(0,s.jsx)(n.strong,{children:"position"}),": position of the folder in the overall structure, in this example its the firth chapter."]}),"\n",(0,s.jsxs)(n.li,{children:[(0,s.jsx)(n.strong,{children:"collapsible"}),": is the list of chapters collapsible ",(0,s.jsx)(n.code,{children:"default=true"}),"."]}),"\n",(0,s.jsxs)(n.li,{children:[(0,s.jsx)(n.strong,{children:"collapsed"}),": is the default view collapsed ",(0,s.jsx)(n.code,{children:"default=true"}),"?"]}),"\n"]}),"\n",(0,s.jsx)(n.h2,{id:"md-file-guidelines-and-best-practices",children:"MD file guidelines and best practices"}),"\n",(0,s.jsx)(n.p,{children:"In the following section the best practices in writing MD files and guidelines on how we in Catena-X write MD files."}),"\n",(0,s.jsx)(n.h3,{id:"headings",children:"Headings"}),"\n",(0,s.jsx)(n.h4,{id:"dos---headings",children:"DOs - Headings"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"# This a heading in the first order\n## This a heading in the first order\n"})}),"\n",(0,s.jsx)(n.h4,{id:"donts---headings",children:"Don'ts - Headings"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"This a heading in the first order\n=================================\nThis a heading in the first order\n---------------------------------\n"})}),"\n",(0,s.jsx)(n.h3,{id:"bolt",children:"Bolt"}),"\n",(0,s.jsx)(n.h4,{id:"dos---bolt",children:"DOs - Bolt"}),"\n",(0,s.jsxs)(n.p,{children:["In this sentence ",(0,s.jsx)(n.strong,{children:"this part"})," is bolt."]}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"In this sentence **this part** is bolt.\n"})}),"\n",(0,s.jsx)(n.h4,{id:"donts---bolt",children:"Don'ts - Bolt"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"In this sentence **this** **part** is bolt.\nIn this sentence __this part__ is bolt.\nIn this sentence __this__ __part__ is bolt.\n"})}),"\n",(0,s.jsx)(n.h3,{id:"italic",children:"Italic"}),"\n",(0,s.jsx)(n.h4,{id:"dos---italic",children:"DOs - Italic"}),"\n",(0,s.jsxs)(n.p,{children:["In this sentence ",(0,s.jsx)(n.em,{children:"this part"})," is italic."]}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"In this sentence *this part* is italic.\n"})}),"\n",(0,s.jsx)(n.h4,{id:"donts---italic",children:"Don'ts - Italic"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"In this sentence *this* *part* is italic.\nIn this sentence _this part_ is italic.\nIn this sentence _this_ _part_ is italic.\n"})}),"\n",(0,s.jsx)(n.h3,{id:"lists---unordered",children:"Lists - unordered"}),"\n",(0,s.jsx)(n.h4,{id:"dos---lists-unordered",children:"DOs - Lists unordered"}),"\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsx)(n.li,{children:"first item"}),"\n",(0,s.jsxs)(n.li,{children:["second item","\n",(0,s.jsxs)(n.ul,{children:["\n",(0,s.jsx)(n.li,{children:"sub item"}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"- first item\n- second item\n - sub item\n"})}),"\n",(0,s.jsx)(n.h4,{id:"donts---lists-unordered",children:"Don'ts - Lists unordered"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"- first item\n+ second item\n * sub item\n"})}),"\n",(0,s.jsx)(n.h3,{id:"lists---ordered",children:"Lists - ordered"}),"\n",(0,s.jsx)(n.h4,{id:"dos---lists-ordered",children:"DOs - Lists ordered"}),"\n",(0,s.jsxs)(n.ol,{children:["\n",(0,s.jsx)(n.li,{children:"first item"}),"\n",(0,s.jsxs)(n.li,{children:["second item","\n",(0,s.jsxs)(n.ol,{children:["\n",(0,s.jsx)(n.li,{children:"sub item"}),"\n"]}),"\n"]}),"\n"]}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"1. first item\n2. second item\n 1. sub item\n"})}),"\n",(0,s.jsx)(n.h4,{id:"donts---lists-ordered",children:"Don'ts - Lists ordered"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"1) first item\n2) second item\n 1) sub item\n"})}),"\n",(0,s.jsx)(n.h3,{id:"imagesfigures",children:"Images/Figures"}),"\n",(0,s.jsx)(n.p,{children:'In addition to the image itself we also provide a alternatives text "alt" in the square brackets. In markdown captions are not supported. We will use the same text as the "alt" in italic writing directly under the image.'}),"\n",(0,s.jsx)(n.h4,{id:"dos---imagesfigures",children:"DOs - Images/Figures"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-MD",children:"![Nice Image](./assets/nice-image.png)\n*Nice Image*\n"})}),"\n",(0,s.jsx)(n.p,{children:'Alt text is the same as the "caption".'}),"\n",(0,s.jsx)(n.h3,{id:"code",children:"Code"}),"\n",(0,s.jsx)(n.h4,{id:"dos---code",children:"DOs - Code"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-java",children:"// the hello world program\nconsole.log('Hello World');\n"})}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-md",children:" ```java\n // the hello world program\n console.log('Hello World');\n"})}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{children:"\n### Text-Box\n\nA `text` in a box\n\n```md\n A `text` in a box\n"})}),"\n",(0,s.jsx)(n.h3,{id:"linksurlse-mailphone-numbers",children:"Links/URLs/E-Mail/Phone numbers"}),"\n",(0,s.jsx)(n.p,{children:"Due to to the use of docusaurus the convention is the following:"}),"\n",(0,s.jsx)(n.h4,{id:"dos---linksurlse-mailphone-numbers",children:"DOs - Links/URLs/E-Mail/Phone numbers"}),"\n",(0,s.jsxs)(n.p,{children:["Go and visit ",(0,s.jsx)(n.a,{href:"https://catena-x.net/en/",children:"Catena-X"}),(0,s.jsx)(n.br,{}),"\n","E-Mail is here: ",(0,s.jsx)(n.a,{href:"mailto:info@catena-x.net",children:"info@catena-x.net"}),(0,s.jsx)(n.br,{}),"\n","Phone number: ",(0,s.jsx)(n.a,{href:"tel:+49123456798",children:"+49 123 456798"})]}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-md",children:" Go and visit [Catena-X](https://catena-x.net/en/) \n E-Mail is here: [info@catena-x.net](mailto:info@catena-x.net) \n Phone number: [+49 123 456798](tel:+49123456798) \n"})}),"\n",(0,s.jsx)(n.h4,{id:"donts---linksurlse-mailphone-numbers",children:"Don'ts - Links/URLs/E-Mail/Phone numbers"}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-md",children:" Go and visit Catena-X \n E-Mail ist here: \n"})}),"\n",(0,s.jsx)(n.h3,{id:"admonitions",children:"Admonitions"}),"\n",(0,s.jsxs)(n.p,{children:["They are not getting rendered correctly in the MD files but in docusaurus. Further information can be found ",(0,s.jsx)(n.a,{href:"https://docusaurus.io/docs/markdown-features/admonitions",children:"here"}),"."]}),"\n",(0,s.jsx)(n.h4,{id:"dos---admonitions",children:"DOs - Admonitions"}),"\n",(0,s.jsx)(n.admonition,{type:"tip",children:(0,s.jsxs)(n.p,{children:["Some ",(0,s.jsx)(n.strong,{children:"content"})," with ",(0,s.jsx)(n.em,{children:"Markdown"})," ",(0,s.jsx)(n.code,{children:"syntax"}),"."]})}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-md",children:":::tip\n\nSome **content** with *Markdown* `syntax`.\n\n:::\n"})}),"\n",(0,s.jsx)(n.h2,{id:"link-to-chaptersheadlines",children:"Link to chapters/headlines"}),"\n",(0,s.jsx)(n.h3,{id:"dos---chaptersheadlines",children:"DOs - chapters/headlines"}),"\n",(0,s.jsx)(n.p,{children:'Be aware if there is a "-" in the heading the IntelliSense in VS Code adds one "-" to many, which results in a error in the MDX linter. In addition if you want to link to the title of the file don\'t tag the heading with "#" it in the link, just link to the file itself. This would result in a error in the MDX linter.'}),"\n",(0,s.jsxs)(n.p,{children:["Jump back to the ",(0,s.jsx)(n.a,{href:"#catena-x-ev-structure-and-guidelines",children:"Top"}),(0,s.jsx)(n.br,{}),"\n","Jump to another ",(0,s.jsx)(n.a,{href:"/getting-started-github#branching",children:"file"})]}),"\n",(0,s.jsx)(n.pre,{children:(0,s.jsx)(n.code,{className:"language-md",children:" Jump back to the [Top](#catena-x-ev-structure-and-guidelines) \n Jump to another [file](/getting-started-github#branching) \n"})})]})}function h(e={}){const{wrapper:n}={...(0,t.R)(),...e.components};return n?(0,s.jsx)(n,{...e,children:(0,s.jsx)(c,{...e})}):c(e)}},8453:(e,n,i)=>{i.d(n,{R:()=>d,x:()=>r});var s=i(6540);const t={},l=s.createContext(t);function d(e){const n=s.useContext(l);return s.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function r(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(t):e.components||t:d(e.components),s.createElement(l.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/d85277d8.c8e6f117.js b/assets/js/d85277d8.c8e6f117.js new file mode 100644 index 00000000..058febdf --- /dev/null +++ b/assets/js/d85277d8.c8e6f117.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3732],{9155:e=>{e.exports=JSON.parse('{"archive":{"blogPosts":[{"id":"welcome","metadata":{"permalink":"/catenax-ev.github.io.new/blog/welcome","source":"@site/blog/2021-08-26-welcome/index.md","title":"Welcome","description":"Docusaurus blogging features are powered by the blog plugin.","date":"2021-08-26T00:00:00.000Z","tags":[{"inline":false,"label":"Facebook","permalink":"/catenax-ev.github.io.new/blog/tags/facebook","description":"Facebook tag description"},{"inline":false,"label":"Hello","permalink":"/catenax-ev.github.io.new/blog/tags/hello","description":"Hello tag description"},{"inline":false,"label":"Docusaurus","permalink":"/catenax-ev.github.io.new/blog/tags/docusaurus","description":"Docusaurus tag description"}],"readingTime":0.405,"hasTruncateMarker":false,"authors":[{"name":"S\xe9bastien Lorber","title":"Docusaurus maintainer","url":"https://sebastienlorber.com","imageURL":"https://github.com/slorber.png","key":"slorber"},{"name":"Yangshun Tay","title":"Front End Engineer @ Facebook","url":"https://github.com/yangshun","imageURL":"https://github.com/yangshun.png","key":"yangshun"}],"frontMatter":{"slug":"welcome","title":"Welcome","authors":["slorber","yangshun"],"tags":["facebook","hello","docusaurus"]},"unlisted":false,"nextItem":{"title":"MDX Blog Post","permalink":"/catenax-ev.github.io.new/blog/mdx-blog-post"}},"content":"[Docusaurus blogging features](https://docusaurus.io/docs/blog) are powered by the [blog plugin](https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog).\\n\\nSimply add Markdown files (or folders) to the `blog` directory.\\n\\nRegular blog authors can be added to `authors.yml`.\\n\\nThe blog post date can be extracted from filenames, such as:\\n\\n- `2019-05-30-welcome.md`\\n- `2019-05-30-welcome/index.md`\\n\\nA blog post folder can be convenient to co-locate blog post images:\\n\\n![Docusaurus Plushie](./docusaurus-plushie-banner.jpeg)\\n\\nThe blog supports tags as well!\\n\\n**And if you don\'t want a blog**: just delete this directory, and use `blog: false` in your Docusaurus config."},{"id":"mdx-blog-post","metadata":{"permalink":"/catenax-ev.github.io.new/blog/mdx-blog-post","source":"@site/blog/2021-08-01-mdx-blog-post.mdx","title":"MDX Blog Post","description":"Blog posts support Docusaurus Markdown features, such as MDX.","date":"2021-08-01T00:00:00.000Z","tags":[{"inline":false,"label":"Docusaurus","permalink":"/catenax-ev.github.io.new/blog/tags/docusaurus","description":"Docusaurus tag description"}],"readingTime":0.175,"hasTruncateMarker":false,"authors":[{"name":"S\xe9bastien Lorber","title":"Docusaurus maintainer","url":"https://sebastienlorber.com","imageURL":"https://github.com/slorber.png","key":"slorber"}],"frontMatter":{"slug":"mdx-blog-post","title":"MDX Blog Post","authors":["slorber"],"tags":["docusaurus"]},"unlisted":false,"prevItem":{"title":"Welcome","permalink":"/catenax-ev.github.io.new/blog/welcome"},"nextItem":{"title":"Long Blog Post","permalink":"/catenax-ev.github.io.new/blog/long-blog-post"}},"content":"Blog posts support [Docusaurus Markdown features](https://docusaurus.io/docs/markdown-features), such as [MDX](https://mdxjs.com/).\\n\\n:::tip\\n\\nUse the power of React to create interactive blog posts.\\n\\n```js\\n\\n```\\n\\n\\n\\n:::"},{"id":"long-blog-post","metadata":{"permalink":"/catenax-ev.github.io.new/blog/long-blog-post","source":"@site/blog/2019-05-29-long-blog-post.md","title":"Long Blog Post","description":"This is the summary of a very long blog post,","date":"2019-05-29T00:00:00.000Z","tags":[{"inline":false,"label":"Hello","permalink":"/catenax-ev.github.io.new/blog/tags/hello","description":"Hello tag description"},{"inline":false,"label":"Docusaurus","permalink":"/catenax-ev.github.io.new/blog/tags/docusaurus","description":"Docusaurus tag description"}],"readingTime":2.05,"hasTruncateMarker":true,"authors":[{"name":"Endilie Yacop Sucipto","title":"Maintainer of Docusaurus","url":"https://github.com/endiliey","imageURL":"https://github.com/endiliey.png","key":"endi"}],"frontMatter":{"slug":"long-blog-post","title":"Long Blog Post","authors":"endi","tags":["hello","docusaurus"]},"unlisted":false,"prevItem":{"title":"MDX Blog Post","permalink":"/catenax-ev.github.io.new/blog/mdx-blog-post"},"nextItem":{"title":"First Blog Post","permalink":"/catenax-ev.github.io.new/blog/first-blog-post"}},"content":"This is the summary of a very long blog post,\\n\\nUse a `\x3c!--` `truncate` `--\x3e` comment to limit blog post size in the list view.\\n\\n\x3c!--truncate--\x3e\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"},{"id":"first-blog-post","metadata":{"permalink":"/catenax-ev.github.io.new/blog/first-blog-post","source":"@site/blog/2019-05-28-first-blog-post.md","title":"First Blog Post","description":"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet","date":"2019-05-28T00:00:00.000Z","tags":[{"inline":false,"label":"Hola","permalink":"/catenax-ev.github.io.new/blog/tags/hola","description":"Hola tag description"},{"inline":false,"label":"Docusaurus","permalink":"/catenax-ev.github.io.new/blog/tags/docusaurus","description":"Docusaurus tag description"}],"readingTime":0.12,"hasTruncateMarker":false,"authors":[{"name":"Gao Wei","title":"Docusaurus Core Team","url":"https://github.com/wgao19","image_url":"https://github.com/wgao19.png","imageURL":"https://github.com/wgao19.png"}],"frontMatter":{"slug":"first-blog-post","title":"First Blog Post","authors":{"name":"Gao Wei","title":"Docusaurus Core Team","url":"https://github.com/wgao19","image_url":"https://github.com/wgao19.png","imageURL":"https://github.com/wgao19.png"},"tags":["hola","docusaurus"]},"unlisted":false,"prevItem":{"title":"Long Blog Post","permalink":"/catenax-ev.github.io.new/blog/long-blog-post"}},"content":"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}]}}')}}]); \ No newline at end of file diff --git a/assets/js/d9f32620.2c3364c5.js b/assets/js/d9f32620.2c3364c5.js deleted file mode 100644 index 054561e7..00000000 --- a/assets/js/d9f32620.2c3364c5.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[5557],{7447:(e,o,n)=>{n.r(o),n.d(o,{assets:()=>i,contentTitle:()=>l,default:()=>d,frontMatter:()=>r,metadata:()=>a,toc:()=>c});var s=n(4848),t=n(8453);const r={slug:"welcome",title:"Welcome",authors:["slorber","yangshun"],tags:["facebook","hello","docusaurus"]},l=void 0,a={permalink:"/blog/welcome",source:"@site/blog/2021-08-26-welcome/index.md",title:"Welcome",description:"Docusaurus blogging features are powered by the blog plugin.",date:"2021-08-26T00:00:00.000Z",tags:[{inline:!1,label:"Facebook",permalink:"/blog/tags/facebook",description:"Facebook tag description"},{inline:!1,label:"Hello",permalink:"/blog/tags/hello",description:"Hello tag description"},{inline:!1,label:"Docusaurus",permalink:"/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:.405,hasTruncateMarker:!1,authors:[{name:"S\xe9bastien Lorber",title:"Docusaurus maintainer",url:"https://sebastienlorber.com",imageURL:"https://github.com/slorber.png",key:"slorber"},{name:"Yangshun Tay",title:"Front End Engineer @ Facebook",url:"https://github.com/yangshun",imageURL:"https://github.com/yangshun.png",key:"yangshun"}],frontMatter:{slug:"welcome",title:"Welcome",authors:["slorber","yangshun"],tags:["facebook","hello","docusaurus"]},unlisted:!1,nextItem:{title:"MDX Blog Post",permalink:"/blog/mdx-blog-post"}},i={authorsImageUrls:[void 0,void 0]},c=[];function u(e){const o={a:"a",code:"code",img:"img",li:"li",p:"p",strong:"strong",ul:"ul",...(0,t.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsxs)(o.p,{children:[(0,s.jsx)(o.a,{href:"https://docusaurus.io/docs/blog",children:"Docusaurus blogging features"})," are powered by the ",(0,s.jsx)(o.a,{href:"https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog",children:"blog plugin"}),"."]}),"\n",(0,s.jsxs)(o.p,{children:["Simply add Markdown files (or folders) to the ",(0,s.jsx)(o.code,{children:"blog"})," directory."]}),"\n",(0,s.jsxs)(o.p,{children:["Regular blog authors can be added to ",(0,s.jsx)(o.code,{children:"authors.yml"}),"."]}),"\n",(0,s.jsx)(o.p,{children:"The blog post date can be extracted from filenames, such as:"}),"\n",(0,s.jsxs)(o.ul,{children:["\n",(0,s.jsx)(o.li,{children:(0,s.jsx)(o.code,{children:"2019-05-30-welcome.md"})}),"\n",(0,s.jsx)(o.li,{children:(0,s.jsx)(o.code,{children:"2019-05-30-welcome/index.md"})}),"\n"]}),"\n",(0,s.jsx)(o.p,{children:"A blog post folder can be convenient to co-locate blog post images:"}),"\n",(0,s.jsx)(o.p,{children:(0,s.jsx)(o.img,{alt:"Docusaurus Plushie",src:n(9465).A+"",width:"1500",height:"500"})}),"\n",(0,s.jsx)(o.p,{children:"The blog supports tags as well!"}),"\n",(0,s.jsxs)(o.p,{children:[(0,s.jsx)(o.strong,{children:"And if you don't want a blog"}),": just delete this directory, and use ",(0,s.jsx)(o.code,{children:"blog: false"})," in your Docusaurus config."]})]})}function d(e={}){const{wrapper:o}={...(0,t.R)(),...e.components};return o?(0,s.jsx)(o,{...e,children:(0,s.jsx)(u,{...e})}):u(e)}},9465:(e,o,n)=>{n.d(o,{A:()=>s});const s=n.p+"assets/images/docusaurus-plushie-banner-a60f7593abca1e3eef26a9afa244e4fb.jpeg"},8453:(e,o,n)=>{n.d(o,{R:()=>l,x:()=>a});var s=n(6540);const t={},r=s.createContext(t);function l(e){const o=s.useContext(r);return s.useMemo((function(){return"function"==typeof e?e(o):{...o,...e}}),[o,e])}function a(e){let o;return o=e.disableParentContext?"function"==typeof e.components?e.components(t):e.components||t:l(e.components),s.createElement(r.Provider,{value:o},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/d9f32620.e0a03946.js b/assets/js/d9f32620.e0a03946.js new file mode 100644 index 00000000..ab965914 --- /dev/null +++ b/assets/js/d9f32620.e0a03946.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[5557],{7447:(e,o,n)=>{n.r(o),n.d(o,{assets:()=>l,contentTitle:()=>i,default:()=>d,frontMatter:()=>a,metadata:()=>r,toc:()=>c});var t=n(4848),s=n(8453);const a={slug:"welcome",title:"Welcome",authors:["slorber","yangshun"],tags:["facebook","hello","docusaurus"]},i=void 0,r={permalink:"/catenax-ev.github.io.new/blog/welcome",source:"@site/blog/2021-08-26-welcome/index.md",title:"Welcome",description:"Docusaurus blogging features are powered by the blog plugin.",date:"2021-08-26T00:00:00.000Z",tags:[{inline:!1,label:"Facebook",permalink:"/catenax-ev.github.io.new/blog/tags/facebook",description:"Facebook tag description"},{inline:!1,label:"Hello",permalink:"/catenax-ev.github.io.new/blog/tags/hello",description:"Hello tag description"},{inline:!1,label:"Docusaurus",permalink:"/catenax-ev.github.io.new/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:.405,hasTruncateMarker:!1,authors:[{name:"S\xe9bastien Lorber",title:"Docusaurus maintainer",url:"https://sebastienlorber.com",imageURL:"https://github.com/slorber.png",key:"slorber"},{name:"Yangshun Tay",title:"Front End Engineer @ Facebook",url:"https://github.com/yangshun",imageURL:"https://github.com/yangshun.png",key:"yangshun"}],frontMatter:{slug:"welcome",title:"Welcome",authors:["slorber","yangshun"],tags:["facebook","hello","docusaurus"]},unlisted:!1,nextItem:{title:"MDX Blog Post",permalink:"/catenax-ev.github.io.new/blog/mdx-blog-post"}},l={authorsImageUrls:[void 0,void 0]},c=[];function u(e){const o={a:"a",code:"code",img:"img",li:"li",p:"p",strong:"strong",ul:"ul",...(0,s.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsxs)(o.p,{children:[(0,t.jsx)(o.a,{href:"https://docusaurus.io/docs/blog",children:"Docusaurus blogging features"})," are powered by the ",(0,t.jsx)(o.a,{href:"https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog",children:"blog plugin"}),"."]}),"\n",(0,t.jsxs)(o.p,{children:["Simply add Markdown files (or folders) to the ",(0,t.jsx)(o.code,{children:"blog"})," directory."]}),"\n",(0,t.jsxs)(o.p,{children:["Regular blog authors can be added to ",(0,t.jsx)(o.code,{children:"authors.yml"}),"."]}),"\n",(0,t.jsx)(o.p,{children:"The blog post date can be extracted from filenames, such as:"}),"\n",(0,t.jsxs)(o.ul,{children:["\n",(0,t.jsx)(o.li,{children:(0,t.jsx)(o.code,{children:"2019-05-30-welcome.md"})}),"\n",(0,t.jsx)(o.li,{children:(0,t.jsx)(o.code,{children:"2019-05-30-welcome/index.md"})}),"\n"]}),"\n",(0,t.jsx)(o.p,{children:"A blog post folder can be convenient to co-locate blog post images:"}),"\n",(0,t.jsx)(o.p,{children:(0,t.jsx)(o.img,{alt:"Docusaurus Plushie",src:n(9465).A+"",width:"1500",height:"500"})}),"\n",(0,t.jsx)(o.p,{children:"The blog supports tags as well!"}),"\n",(0,t.jsxs)(o.p,{children:[(0,t.jsx)(o.strong,{children:"And if you don't want a blog"}),": just delete this directory, and use ",(0,t.jsx)(o.code,{children:"blog: false"})," in your Docusaurus config."]})]})}function d(e={}){const{wrapper:o}={...(0,s.R)(),...e.components};return o?(0,t.jsx)(o,{...e,children:(0,t.jsx)(u,{...e})}):u(e)}},9465:(e,o,n)=>{n.d(o,{A:()=>t});const t=n.p+"assets/images/docusaurus-plushie-banner-a60f7593abca1e3eef26a9afa244e4fb.jpeg"},8453:(e,o,n)=>{n.d(o,{R:()=>i,x:()=>r});var t=n(6540);const s={},a=t.createContext(s);function i(e){const o=t.useContext(a);return t.useMemo((function(){return"function"==typeof e?e(o):{...o,...e}}),[o,e])}function r(e){let o;return o=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:i(e.components),t.createElement(a.Provider,{value:o},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/e18cfb11.6b3ca214.js b/assets/js/e18cfb11.6b3ca214.js new file mode 100644 index 00000000..acde9406 --- /dev/null +++ b/assets/js/e18cfb11.6b3ca214.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[4676],{5358:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>c,contentTitle:()=>s,default:()=>u,frontMatter:()=>r,metadata:()=>a,toc:()=>d});var o=i(4848),t=i(8453);const r={sidebar_position:1,title:"Overview"},s=void 0,a={id:"working-model/overview",title:"Overview",description:"Introduction",source:"@site/docs/working-model/overview.md",sourceDirName:"working-model",slug:"/working-model/overview",permalink:"/catenax-ev.github.io.new/docs/next/working-model/overview",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Overview"},sidebar:"sidebar_working_model",next:{title:"Catena-X Ecosystem",permalink:"/catenax-ev.github.io.new/docs/next/working-model/ecosystem/"}},c={},d=[{value:"Introduction",id:"introduction",level:2},{value:"Objectives",id:"objectives",level:2},{value:"Scope",id:"scope",level:2},{value:"Non-Normative",id:"non-normative",level:2}];function l(e){const n={a:"a",admonition:"admonition",h2:"h2",li:"li",p:"p",ul:"ul",...(0,t.R)(),...e.components};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsx)(n.h2,{id:"introduction",children:"Introduction"}),"\n",(0,o.jsxs)(n.ul,{children:["\n",(0,o.jsx)(n.li,{children:"The Catena-X ecosystem is driven by participants of the entire automotive value chain and many supporting companies across industries."}),"\n",(0,o.jsx)(n.li,{children:"Catena-X focusses on use cases from automotive for automotive and the data driven collaboration across multiple tiers"}),"\n",(0,o.jsx)(n.li,{children:"It covers the 3 basic dimensions plan, build and run"}),"\n",(0,o.jsx)(n.li,{children:"Joint and open collaboration (e.g., expert groups, tractus-x project) is a core principle of Catena-X"}),"\n"]}),"\n",(0,o.jsx)(n.h2,{id:"objectives",children:"Objectives"}),"\n",(0,o.jsxs)(n.ul,{children:["\n",(0,o.jsx)(n.li,{children:"Overview of our values and principles for development of software and standards"}),"\n",(0,o.jsx)(n.li,{children:"Definition of structure and process organization for the development area"}),"\n",(0,o.jsx)(n.li,{children:"Define the journey from idea to standards and code"}),"\n"]}),"\n",(0,o.jsx)(n.h2,{id:"scope",children:"Scope"}),"\n",(0,o.jsxs)(n.ul,{children:["\n",(0,o.jsxs)(n.li,{children:["Plan and Build (no Run)","\n",(0,o.jsxs)(n.ul,{children:["\n",(0,o.jsxs)(n.li,{children:["Whereas the ",(0,o.jsx)(n.a,{href:"https://catenax-ev.github.io/docs/next/operating-model/operating-model",children:"Operating model"})," describes the model for production / live environment (=Run)"]}),"\n"]}),"\n"]}),"\n",(0,o.jsx)(n.li,{children:"Roles, tasks, competence, and responsibility model"}),"\n",(0,o.jsx)(n.li,{children:"Interfaces between Catena-X association and other initiatives such as Tractus-X Project (Eclipse Foundation Project Handbook)"}),"\n"]}),"\n",(0,o.jsx)(n.h2,{id:"non-normative",children:"Non-Normative"}),"\n",(0,o.jsx)(n.admonition,{type:"info",children:(0,o.jsx)(n.p,{children:"This is not a normative Document!"})})]})}function u(e={}){const{wrapper:n}={...(0,t.R)(),...e.components};return n?(0,o.jsx)(n,{...e,children:(0,o.jsx)(l,{...e})}):l(e)}},8453:(e,n,i)=>{i.d(n,{R:()=>s,x:()=>a});var o=i(6540);const t={},r=o.createContext(t);function s(e){const n=o.useContext(r);return o.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function a(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(t):e.components||t:s(e.components),o.createElement(r.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/e18cfb11.c1b055af.js b/assets/js/e18cfb11.c1b055af.js deleted file mode 100644 index 6e91dd57..00000000 --- a/assets/js/e18cfb11.c1b055af.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[4676],{5358:(e,n,i)=>{i.r(n),i.d(n,{assets:()=>c,contentTitle:()=>s,default:()=>u,frontMatter:()=>r,metadata:()=>a,toc:()=>d});var o=i(4848),t=i(8453);const r={sidebar_position:1,title:"Overview"},s=void 0,a={id:"working-model/overview",title:"Overview",description:"Introduction",source:"@site/docs/working-model/overview.md",sourceDirName:"working-model",slug:"/working-model/overview",permalink:"/docs/next/working-model/overview",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Overview"},sidebar:"sidebar_working_model",next:{title:"Catena-X Ecosystem",permalink:"/docs/next/working-model/ecosystem/"}},c={},d=[{value:"Introduction",id:"introduction",level:2},{value:"Objectives",id:"objectives",level:2},{value:"Scope",id:"scope",level:2},{value:"Non-Normative",id:"non-normative",level:2}];function l(e){const n={a:"a",admonition:"admonition",h2:"h2",li:"li",p:"p",ul:"ul",...(0,t.R)(),...e.components};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsx)(n.h2,{id:"introduction",children:"Introduction"}),"\n",(0,o.jsxs)(n.ul,{children:["\n",(0,o.jsx)(n.li,{children:"The Catena-X ecosystem is driven by participants of the entire automotive value chain and many supporting companies across industries."}),"\n",(0,o.jsx)(n.li,{children:"Catena-X focusses on use cases from automotive for automotive and the data driven collaboration across multiple tiers"}),"\n",(0,o.jsx)(n.li,{children:"It covers the 3 basic dimensions plan, build and run"}),"\n",(0,o.jsx)(n.li,{children:"Joint and open collaboration (e.g., expert groups, tractus-x project) is a core principle of Catena-X"}),"\n"]}),"\n",(0,o.jsx)(n.h2,{id:"objectives",children:"Objectives"}),"\n",(0,o.jsxs)(n.ul,{children:["\n",(0,o.jsx)(n.li,{children:"Overview of our values and principles for development of software and standards"}),"\n",(0,o.jsx)(n.li,{children:"Definition of structure and process organization for the development area"}),"\n",(0,o.jsx)(n.li,{children:"Define the journey from idea to standards and code"}),"\n"]}),"\n",(0,o.jsx)(n.h2,{id:"scope",children:"Scope"}),"\n",(0,o.jsxs)(n.ul,{children:["\n",(0,o.jsxs)(n.li,{children:["Plan and Build (no Run)","\n",(0,o.jsxs)(n.ul,{children:["\n",(0,o.jsxs)(n.li,{children:["Whereas the ",(0,o.jsx)(n.a,{href:"https://catenax-ev.github.io/docs/next/operating-model/operating-model",children:"Operating model"})," describes the model for production / live environment (=Run)"]}),"\n"]}),"\n"]}),"\n",(0,o.jsx)(n.li,{children:"Roles, tasks, competence, and responsibility model"}),"\n",(0,o.jsx)(n.li,{children:"Interfaces between Catena-X association and other initiatives such as Tractus-X Project (Eclipse Foundation Project Handbook)"}),"\n"]}),"\n",(0,o.jsx)(n.h2,{id:"non-normative",children:"Non-Normative"}),"\n",(0,o.jsx)(n.admonition,{type:"info",children:(0,o.jsx)(n.p,{children:"This is not a normative Document!"})})]})}function u(e={}){const{wrapper:n}={...(0,t.R)(),...e.components};return n?(0,o.jsx)(n,{...e,children:(0,o.jsx)(l,{...e})}):l(e)}},8453:(e,n,i)=>{i.d(n,{R:()=>s,x:()=>a});var o=i(6540);const t={},r=o.createContext(t);function s(e){const n=o.useContext(r);return o.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function a(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(t):e.components||t:s(e.components),o.createElement(r.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/e273c56f.2ea068a8.js b/assets/js/e273c56f.2ea068a8.js deleted file mode 100644 index f4f5d3ea..00000000 --- a/assets/js/e273c56f.2ea068a8.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9328],{4014:(t,e,o)=>{o.r(e),o.d(e,{assets:()=>r,contentTitle:()=>a,default:()=>m,frontMatter:()=>n,metadata:()=>u,toc:()=>l});var s=o(4848),i=o(8453);const n={slug:"first-blog-post",title:"First Blog Post",authors:{name:"Gao Wei",title:"Docusaurus Core Team",url:"https://github.com/wgao19",image_url:"https://github.com/wgao19.png"},tags:["hola","docusaurus"]},a=void 0,u={permalink:"/blog/first-blog-post",source:"@site/blog/2019-05-28-first-blog-post.md",title:"First Blog Post",description:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet",date:"2019-05-28T00:00:00.000Z",tags:[{inline:!1,label:"Hola",permalink:"/blog/tags/hola",description:"Hola tag description"},{inline:!1,label:"Docusaurus",permalink:"/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:.12,hasTruncateMarker:!1,authors:[{name:"Gao Wei",title:"Docusaurus Core Team",url:"https://github.com/wgao19",image_url:"https://github.com/wgao19.png",imageURL:"https://github.com/wgao19.png"}],frontMatter:{slug:"first-blog-post",title:"First Blog Post",authors:{name:"Gao Wei",title:"Docusaurus Core Team",url:"https://github.com/wgao19",image_url:"https://github.com/wgao19.png",imageURL:"https://github.com/wgao19.png"},tags:["hola","docusaurus"]},unlisted:!1,prevItem:{title:"Long Blog Post",permalink:"/blog/long-blog-post"}},r={authorsImageUrls:[void 0]},l=[];function c(t){const e={p:"p",...(0,i.R)(),...t.components};return(0,s.jsx)(e.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"})}function m(t={}){const{wrapper:e}={...(0,i.R)(),...t.components};return e?(0,s.jsx)(e,{...t,children:(0,s.jsx)(c,{...t})}):c(t)}},8453:(t,e,o)=>{o.d(e,{R:()=>a,x:()=>u});var s=o(6540);const i={},n=s.createContext(i);function a(t){const e=s.useContext(n);return s.useMemo((function(){return"function"==typeof t?t(e):{...e,...t}}),[e,t])}function u(t){let e;return e=t.disableParentContext?"function"==typeof t.components?t.components(i):t.components||i:a(t.components),s.createElement(n.Provider,{value:e},t.children)}}}]); \ No newline at end of file diff --git a/assets/js/e273c56f.f5a0a811.js b/assets/js/e273c56f.f5a0a811.js new file mode 100644 index 00000000..a119485f --- /dev/null +++ b/assets/js/e273c56f.f5a0a811.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9328],{4014:(t,e,o)=>{o.r(e),o.d(e,{assets:()=>r,contentTitle:()=>a,default:()=>g,frontMatter:()=>n,metadata:()=>u,toc:()=>l});var s=o(4848),i=o(8453);const n={slug:"first-blog-post",title:"First Blog Post",authors:{name:"Gao Wei",title:"Docusaurus Core Team",url:"https://github.com/wgao19",image_url:"https://github.com/wgao19.png"},tags:["hola","docusaurus"]},a=void 0,u={permalink:"/catenax-ev.github.io.new/blog/first-blog-post",source:"@site/blog/2019-05-28-first-blog-post.md",title:"First Blog Post",description:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet",date:"2019-05-28T00:00:00.000Z",tags:[{inline:!1,label:"Hola",permalink:"/catenax-ev.github.io.new/blog/tags/hola",description:"Hola tag description"},{inline:!1,label:"Docusaurus",permalink:"/catenax-ev.github.io.new/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:.12,hasTruncateMarker:!1,authors:[{name:"Gao Wei",title:"Docusaurus Core Team",url:"https://github.com/wgao19",image_url:"https://github.com/wgao19.png",imageURL:"https://github.com/wgao19.png"}],frontMatter:{slug:"first-blog-post",title:"First Blog Post",authors:{name:"Gao Wei",title:"Docusaurus Core Team",url:"https://github.com/wgao19",image_url:"https://github.com/wgao19.png",imageURL:"https://github.com/wgao19.png"},tags:["hola","docusaurus"]},unlisted:!1,prevItem:{title:"Long Blog Post",permalink:"/catenax-ev.github.io.new/blog/long-blog-post"}},r={authorsImageUrls:[void 0]},l=[];function c(t){const e={p:"p",...(0,i.R)(),...t.components};return(0,s.jsx)(e.p,{children:"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"})}function g(t={}){const{wrapper:e}={...(0,i.R)(),...t.components};return e?(0,s.jsx)(e,{...t,children:(0,s.jsx)(c,{...t})}):c(t)}},8453:(t,e,o)=>{o.d(e,{R:()=>a,x:()=>u});var s=o(6540);const i={},n=s.createContext(i);function a(t){const e=s.useContext(n);return s.useMemo((function(){return"function"==typeof t?t(e):{...e,...t}}),[e,t])}function u(t){let e;return e=t.disableParentContext?"function"==typeof t.components?t.components(i):t.components||i:a(t.components),s.createElement(n.Provider,{value:e},t.children)}}}]); \ No newline at end of file diff --git a/assets/js/e5aefb32.5951bfd8.js b/assets/js/e5aefb32.5951bfd8.js deleted file mode 100644 index 84526e4f..00000000 --- a/assets/js/e5aefb32.5951bfd8.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3276],{8539:a=>{a.exports=JSON.parse('{"tag":{"label":"Facebook","permalink":"/blog/tags/facebook","description":"Facebook tag description","allTagsPath":"/blog/tags","count":1,"unlisted":false},"listMetadata":{"permalink":"/blog/tags/facebook","page":1,"postsPerPage":10,"totalPages":1,"totalCount":1,"blogDescription":"Blog","blogTitle":"Blog"}}')}}]); \ No newline at end of file diff --git a/assets/js/e6e7a2ca.3ced26fd.js b/assets/js/e6e7a2ca.3ced26fd.js new file mode 100644 index 00000000..840c36b3 --- /dev/null +++ b/assets/js/e6e7a2ca.3ced26fd.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[6699],{7875:(e,i,t)=>{t.r(i),t.d(i,{assets:()=>l,contentTitle:()=>s,default:()=>h,frontMatter:()=>o,metadata:()=>r,toc:()=>c});var a=t(4848),n=t(8453);const o={sidebar_position:1},s="Outlook",r={id:"operating-model/outlook/outlook",title:"Outlook",description:"The Catena-X Operating Model is a normative document within the regulatory framework, which is binding for all participants in the Catena-X data space. It describes the status of our data space artifacts, including roles, services, and processes along with their respective roadmaps. As Catena-X is an ongoing journey, all of these artifacts will continuously evolve to promote broader adoption and scalability, ensuring maximum interoperability, and (data) sovereignty.",source:"@site/versioned_docs/version-24.03/operating-model/outlook/outlook.md",sourceDirName:"operating-model/outlook",slug:"/operating-model/outlook/",permalink:"/catenax-ev.github.io.new/docs/operating-model/outlook/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"How: Life Cycle Management",permalink:"/catenax-ev.github.io.new/docs/operating-model/how-life-cycle-management/"},next:{title:"Glossary",permalink:"/catenax-ev.github.io.new/docs/operating-model/glossary/"}},l={},c=[{value:"Industry Core",id:"industry-core",level:2},{value:"Increase Decentralization of Core Services",id:"increase-decentralization-of-core-services",level:2},{value:"Release v23.09",id:"release-v2309",level:3},{value:"Release v23.12 (planned)",id:"release-v2312-planned",level:3},{value:"Releases 2024 (planned)",id:"releases-2024-planned",level:3},{value:"Further Integration of SSI Technologies",id:"further-integration-of-ssi-technologies",level:2},{value:"Data Space Interoperability",id:"data-space-interoperability",level:2},{value:"Backward Compatibility",id:"backward-compatibility",level:2},{value:"Sanctions",id:"sanctions",level:2}];function d(e){const i={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",img:"img",li:"li",p:"p",strong:"strong",ul:"ul",...(0,n.R)(),...e.components};return(0,a.jsxs)(a.Fragment,{children:[(0,a.jsx)(i.h1,{id:"outlook",children:"Outlook"}),"\n",(0,a.jsx)(i.p,{children:"The Catena-X Operating Model is a normative document within the regulatory framework, which is binding for all participants in the Catena-X data space. It describes the status of our data space artifacts, including roles, services, and processes along with their respective roadmaps. As Catena-X is an ongoing journey, all of these artifacts will continuously evolve to promote broader adoption and scalability, ensuring maximum interoperability, and (data) sovereignty."}),"\n",(0,a.jsx)(i.h2,{id:"industry-core",children:"Industry Core"}),"\n",(0,a.jsx)(i.p,{children:"The Industry Core aims to reduce the complexity of multi-tier connections within the decentralized Catena-X data space and to act as an enabler for data-driven use cases like tracking a product carbon footprint (PCF) value or circular economy. Reusing common components and standards (especially data provisioning of digital twins of parts) across different use cases promotes efficiency and interoperability. To enable onboarding for corporations that have different legal entities, concepts for a corporate BPNL are also created. This enables a simple participation via a company-group-wide BPNL. The industry core fosters the realization of seamless data chains, with one use case benefiting from another. As a result, cross-domain network effects and n-tier use cases become possible."}),"\n",(0,a.jsx)(i.h2,{id:"increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),"\n",(0,a.jsxs)(i.p,{children:["Catena-X follows a business-oriented decentralization approach that aims to achieve interoperability and data sovereignty while balancing manageability of complexity, and technical maturity. Therefore, Core Services B will gradually transition into onboarding services or Core Services A, if appropriate. Please find below the timeline for the upcoming decentralization of Core Services B (see Figure ",(0,a.jsx)(i.a,{href:"/catenax-ev.github.io.new/docs/operating-model/outlook/#increase-decentralization-of-core-services",children:"Timeline for further Decentralization"}),")."]}),"\n",(0,a.jsxs)(i.p,{children:[(0,a.jsx)(i.img,{alt:"Timeline for further Decentralization",src:t(4260).A+"",width:"991",height:"731"}),"\n",(0,a.jsx)(i.em,{children:"Timeline for further Decentralization"})]}),"\n",(0,a.jsx)(i.h3,{id:"release-v2309",children:"Release v23.09"}),"\n",(0,a.jsx)(i.p,{children:"Due to organizational and technical limitations, the services associated with the CSP-A and OSP roles can only be operated once and must therefore temporarily be offered by the nominated CSP-B."}),"\n",(0,a.jsx)(i.h3,{id:"release-v2312-planned",children:"Release v23.12 (planned)"}),"\n",(0,a.jsx)(i.p,{children:"With the introduction of new identity synchronization functions, multiple CSP-A and OSP can operate the corresponding services and collaborate. In addition, there will be new CSP-B services such as the Policy and Credential Hub."}),"\n",(0,a.jsx)(i.h3,{id:"releases-2024-planned",children:"Releases 2024 (planned)"}),"\n",(0,a.jsx)(i.p,{children:"With an increasing decentralization of services, Core Services B are shifted step by step to Core Services A and the decentralized portfolio of Onboarding Service Provider likewise increases. For future releases, committees, expert, and working groups will be coordinated to develop a detailed decentralization roadmap under the supervision of the Catena-X Association."}),"\n",(0,a.jsx)(i.h2,{id:"further-integration-of-ssi-technologies",children:"Further Integration of SSI Technologies"}),"\n",(0,a.jsxs)(i.p,{children:["To realize the Catena-X vision of a decentralized data space, we will further develop our SSI technologies. Future releases will enable the use of both managed identity wallets and self-provisioned identity wallets. To enable the technical enforcement of policies, it is planned to introduce a policy hub and policy code templates to also provide the information transparently to the participants. This also includes the decentralization of the issuer service and logging functionality for agreements. To further strengthen trust in the data space, we will introduce the option to define various root trust anchors (e.g., the Catena-X Association). This will also allow the identity wallet to be decentralized and allow multiple issuers. In addition, a chain of trust will be established to prove that a given credential comes from a trusted source according to the Catena-X Governance Framework. The concept is still under development and will be released in one of the next versions (by May 2024). While developing this concept, the concepts of the Policy Hub and the Certifications Hub will also be concretized. An illustration of this can be found in Chapter ",(0,a.jsx)(i.a,{href:"/catenax-ev.github.io.new/docs/operating-model/appendix/#data-exchange-based-on-ssi---next-steps",children:"Data Exchange based on SSI - Next Steps"}),"."]}),"\n",(0,a.jsx)(i.h2,{id:"data-space-interoperability",children:"Data Space Interoperability"}),"\n",(0,a.jsx)(i.p,{children:"The Catena-X Association is committed to promote and engage in various initiatives that focus on creating common guidelines and standards to ensure interoperability with other data space initiatives. Initiatives such as the Data Space Support Centre (DSSC) and Manufacturing-X will help establish an interoperable data space across different industry sectors. Furthermore, the Catena-X Association will drive technical initiatives, such as the Eclipse Tractus-X project and the Eclipse Dataspace Working Group (EDWG), which aim to align a common technical foundation, certification procedures and test/ security requirements."}),"\n",(0,a.jsx)(i.h2,{id:"backward-compatibility",children:"Backward Compatibility"}),"\n",(0,a.jsxs)(i.p,{children:["The vision of the Catena-X data space is to provide seamless data access and creation of data chains across multi-tier value chains. Initially, the data space can be operated and evolved by deployment of dedicated, synchronized releases (see Chapter ",(0,a.jsx)(i.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance/",children:"How: Data Space Governance"}),"). While initially, dedicated, synchronized releases (see Chapter ",(0,a.jsx)(i.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance/",children:"How: Data Space Governance"}),") may suffice, our goal of involving thousands of partners makes it impossible to maintain the same technical components across the board. To overcome this challenge, we must ensure that the release and upgrade of dedicated components can be executed independently, without causing disruptions in the network connectivity and data chains."]}),"\n",(0,a.jsx)(i.p,{children:"To achieve this in areas such as APIs, semantic models, and procedural specifications, the Catena-X Association promotes and supports adherence to the following principles:"}),"\n",(0,a.jsxs)(i.ul,{children:["\n",(0,a.jsxs)(i.li,{children:[(0,a.jsx)(i.strong,{children:"Continuous revising of standards"})," to ensure compatibility between different versions and releases."]}),"\n",(0,a.jsxs)(i.li,{children:[(0,a.jsx)(i.strong,{children:"Developing technical specifications"})," and ",(0,a.jsx)(i.strong,{children:"reference implementations"})," in Eclipse Tractus-X that follow the required standards to lay the technical foundation."]}),"\n",(0,a.jsxs)(i.li,{children:[(0,a.jsx)(i.strong,{children:"Coordinating"})," closely with different ",(0,a.jsx)(i.strong,{children:"operators"})," to execute rollout and implementation of the different versions and releases."]}),"\n"]}),"\n",(0,a.jsx)(i.h2,{id:"sanctions",children:"Sanctions"}),"\n",(0,a.jsx)(i.p,{children:"Following its GoLive, the Catena-X data space will grow in participants and complexity. Consequently, ensuring compliance of all participants with established rules, regulations, and standards becomes increasingly relevant."}),"\n",(0,a.jsx)(i.p,{children:"Moving forward, concepts of imposing restrictions or penalties on individuals, organizations, or entities that engage in actions or behaviors that are deemed harmful, illegal, or unethical within the context of data management, privacy, and security will be evaluated and developed. These sanctions will aim to deter, correct, or punish noncompliant behavior, thereby safeguarding data integrity, protecting individual rights, and maintaining the trust and credibility of the data ecosystem."})]})}function h(e={}){const{wrapper:i}={...(0,n.R)(),...e.components};return i?(0,a.jsx)(i,{...e,children:(0,a.jsx)(d,{...e})}):d(e)}},4260:(e,i,t)=>{t.d(i,{A:()=>a});const a=t.p+"assets/images/timeline-for-further-decentralization-1eff7b5a80c5ea1f5d6a99c537793c48.png"},8453:(e,i,t)=>{t.d(i,{R:()=>s,x:()=>r});var a=t(6540);const n={},o=a.createContext(n);function s(e){const i=a.useContext(o);return a.useMemo((function(){return"function"==typeof e?e(i):{...i,...e}}),[i,e])}function r(e){let i;return i=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:s(e.components),a.createElement(o.Provider,{value:i},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/e6e7a2ca.592f45cb.js b/assets/js/e6e7a2ca.592f45cb.js deleted file mode 100644 index 8b8eb816..00000000 --- a/assets/js/e6e7a2ca.592f45cb.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[6699],{7875:(e,i,t)=>{t.r(i),t.d(i,{assets:()=>l,contentTitle:()=>s,default:()=>h,frontMatter:()=>o,metadata:()=>r,toc:()=>c});var a=t(4848),n=t(8453);const o={sidebar_position:1},s="Outlook",r={id:"operating-model/outlook/outlook",title:"Outlook",description:"The Catena-X Operating Model is a normative document within the regulatory framework, which is binding for all participants in the Catena-X data space. It describes the status of our data space artifacts, including roles, services, and processes along with their respective roadmaps. As Catena-X is an ongoing journey, all of these artifacts will continuously evolve to promote broader adoption and scalability, ensuring maximum interoperability, and (data) sovereignty.",source:"@site/versioned_docs/version-24.03/operating-model/outlook/outlook.md",sourceDirName:"operating-model/outlook",slug:"/operating-model/outlook/",permalink:"/docs/operating-model/outlook/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"How: Life Cycle Management",permalink:"/docs/operating-model/how-life-cycle-management/"},next:{title:"Glossary",permalink:"/docs/operating-model/glossary/"}},l={},c=[{value:"Industry Core",id:"industry-core",level:2},{value:"Increase Decentralization of Core Services",id:"increase-decentralization-of-core-services",level:2},{value:"Release v23.09",id:"release-v2309",level:3},{value:"Release v23.12 (planned)",id:"release-v2312-planned",level:3},{value:"Releases 2024 (planned)",id:"releases-2024-planned",level:3},{value:"Further Integration of SSI Technologies",id:"further-integration-of-ssi-technologies",level:2},{value:"Data Space Interoperability",id:"data-space-interoperability",level:2},{value:"Backward Compatibility",id:"backward-compatibility",level:2},{value:"Sanctions",id:"sanctions",level:2}];function d(e){const i={a:"a",em:"em",h1:"h1",h2:"h2",h3:"h3",img:"img",li:"li",p:"p",strong:"strong",ul:"ul",...(0,n.R)(),...e.components};return(0,a.jsxs)(a.Fragment,{children:[(0,a.jsx)(i.h1,{id:"outlook",children:"Outlook"}),"\n",(0,a.jsx)(i.p,{children:"The Catena-X Operating Model is a normative document within the regulatory framework, which is binding for all participants in the Catena-X data space. It describes the status of our data space artifacts, including roles, services, and processes along with their respective roadmaps. As Catena-X is an ongoing journey, all of these artifacts will continuously evolve to promote broader adoption and scalability, ensuring maximum interoperability, and (data) sovereignty."}),"\n",(0,a.jsx)(i.h2,{id:"industry-core",children:"Industry Core"}),"\n",(0,a.jsx)(i.p,{children:"The Industry Core aims to reduce the complexity of multi-tier connections within the decentralized Catena-X data space and to act as an enabler for data-driven use cases like tracking a product carbon footprint (PCF) value or circular economy. Reusing common components and standards (especially data provisioning of digital twins of parts) across different use cases promotes efficiency and interoperability. To enable onboarding for corporations that have different legal entities, concepts for a corporate BPNL are also created. This enables a simple participation via a company-group-wide BPNL. The industry core fosters the realization of seamless data chains, with one use case benefiting from another. As a result, cross-domain network effects and n-tier use cases become possible."}),"\n",(0,a.jsx)(i.h2,{id:"increase-decentralization-of-core-services",children:"Increase Decentralization of Core Services"}),"\n",(0,a.jsxs)(i.p,{children:["Catena-X follows a business-oriented decentralization approach that aims to achieve interoperability and data sovereignty while balancing manageability of complexity, and technical maturity. Therefore, Core Services B will gradually transition into onboarding services or Core Services A, if appropriate. Please find below the timeline for the upcoming decentralization of Core Services B (see Figure ",(0,a.jsx)(i.a,{href:"/docs/operating-model/outlook/#increase-decentralization-of-core-services",children:"Timeline for further Decentralization"}),")."]}),"\n",(0,a.jsxs)(i.p,{children:[(0,a.jsx)(i.img,{alt:"Timeline for further Decentralization",src:t(4260).A+"",width:"991",height:"731"}),"\n",(0,a.jsx)(i.em,{children:"Timeline for further Decentralization"})]}),"\n",(0,a.jsx)(i.h3,{id:"release-v2309",children:"Release v23.09"}),"\n",(0,a.jsx)(i.p,{children:"Due to organizational and technical limitations, the services associated with the CSP-A and OSP roles can only be operated once and must therefore temporarily be offered by the nominated CSP-B."}),"\n",(0,a.jsx)(i.h3,{id:"release-v2312-planned",children:"Release v23.12 (planned)"}),"\n",(0,a.jsx)(i.p,{children:"With the introduction of new identity synchronization functions, multiple CSP-A and OSP can operate the corresponding services and collaborate. In addition, there will be new CSP-B services such as the Policy and Credential Hub."}),"\n",(0,a.jsx)(i.h3,{id:"releases-2024-planned",children:"Releases 2024 (planned)"}),"\n",(0,a.jsx)(i.p,{children:"With an increasing decentralization of services, Core Services B are shifted step by step to Core Services A and the decentralized portfolio of Onboarding Service Provider likewise increases. For future releases, committees, expert, and working groups will be coordinated to develop a detailed decentralization roadmap under the supervision of the Catena-X Association."}),"\n",(0,a.jsx)(i.h2,{id:"further-integration-of-ssi-technologies",children:"Further Integration of SSI Technologies"}),"\n",(0,a.jsxs)(i.p,{children:["To realize the Catena-X vision of a decentralized data space, we will further develop our SSI technologies. Future releases will enable the use of both managed identity wallets and self-provisioned identity wallets. To enable the technical enforcement of policies, it is planned to introduce a policy hub and policy code templates to also provide the information transparently to the participants. This also includes the decentralization of the issuer service and logging functionality for agreements. To further strengthen trust in the data space, we will introduce the option to define various root trust anchors (e.g., the Catena-X Association). This will also allow the identity wallet to be decentralized and allow multiple issuers. In addition, a chain of trust will be established to prove that a given credential comes from a trusted source according to the Catena-X Governance Framework. The concept is still under development and will be released in one of the next versions (by May 2024). While developing this concept, the concepts of the Policy Hub and the Certifications Hub will also be concretized. An illustration of this can be found in Chapter ",(0,a.jsx)(i.a,{href:"/docs/operating-model/appendix/#data-exchange-based-on-ssi---next-steps",children:"Data Exchange based on SSI - Next Steps"}),"."]}),"\n",(0,a.jsx)(i.h2,{id:"data-space-interoperability",children:"Data Space Interoperability"}),"\n",(0,a.jsx)(i.p,{children:"The Catena-X Association is committed to promote and engage in various initiatives that focus on creating common guidelines and standards to ensure interoperability with other data space initiatives. Initiatives such as the Data Space Support Centre (DSSC) and Manufacturing-X will help establish an interoperable data space across different industry sectors. Furthermore, the Catena-X Association will drive technical initiatives, such as the Eclipse Tractus-X project and the Eclipse Dataspace Working Group (EDWG), which aim to align a common technical foundation, certification procedures and test/ security requirements."}),"\n",(0,a.jsx)(i.h2,{id:"backward-compatibility",children:"Backward Compatibility"}),"\n",(0,a.jsxs)(i.p,{children:["The vision of the Catena-X data space is to provide seamless data access and creation of data chains across multi-tier value chains. Initially, the data space can be operated and evolved by deployment of dedicated, synchronized releases (see Chapter ",(0,a.jsx)(i.a,{href:"/docs/operating-model/how-data-space-governance/",children:"How: Data Space Governance"}),"). While initially, dedicated, synchronized releases (see Chapter ",(0,a.jsx)(i.a,{href:"/docs/operating-model/how-data-space-governance/",children:"How: Data Space Governance"}),") may suffice, our goal of involving thousands of partners makes it impossible to maintain the same technical components across the board. To overcome this challenge, we must ensure that the release and upgrade of dedicated components can be executed independently, without causing disruptions in the network connectivity and data chains."]}),"\n",(0,a.jsx)(i.p,{children:"To achieve this in areas such as APIs, semantic models, and procedural specifications, the Catena-X Association promotes and supports adherence to the following principles:"}),"\n",(0,a.jsxs)(i.ul,{children:["\n",(0,a.jsxs)(i.li,{children:[(0,a.jsx)(i.strong,{children:"Continuous revising of standards"})," to ensure compatibility between different versions and releases."]}),"\n",(0,a.jsxs)(i.li,{children:[(0,a.jsx)(i.strong,{children:"Developing technical specifications"})," and ",(0,a.jsx)(i.strong,{children:"reference implementations"})," in Eclipse Tractus-X that follow the required standards to lay the technical foundation."]}),"\n",(0,a.jsxs)(i.li,{children:[(0,a.jsx)(i.strong,{children:"Coordinating"})," closely with different ",(0,a.jsx)(i.strong,{children:"operators"})," to execute rollout and implementation of the different versions and releases."]}),"\n"]}),"\n",(0,a.jsx)(i.h2,{id:"sanctions",children:"Sanctions"}),"\n",(0,a.jsx)(i.p,{children:"Following its GoLive, the Catena-X data space will grow in participants and complexity. Consequently, ensuring compliance of all participants with established rules, regulations, and standards becomes increasingly relevant."}),"\n",(0,a.jsx)(i.p,{children:"Moving forward, concepts of imposing restrictions or penalties on individuals, organizations, or entities that engage in actions or behaviors that are deemed harmful, illegal, or unethical within the context of data management, privacy, and security will be evaluated and developed. These sanctions will aim to deter, correct, or punish noncompliant behavior, thereby safeguarding data integrity, protecting individual rights, and maintaining the trust and credibility of the data ecosystem."})]})}function h(e={}){const{wrapper:i}={...(0,n.R)(),...e.components};return i?(0,a.jsx)(i,{...e,children:(0,a.jsx)(d,{...e})}):d(e)}},4260:(e,i,t)=>{t.d(i,{A:()=>a});const a=t.p+"assets/images/timeline-for-further-decentralization-1eff7b5a80c5ea1f5d6a99c537793c48.png"},8453:(e,i,t)=>{t.d(i,{R:()=>s,x:()=>r});var a=t(6540);const n={},o=a.createContext(n);function s(e){const i=a.useContext(o);return a.useMemo((function(){return"function"==typeof e?e(i):{...i,...e}}),[i,e])}function r(e){let i;return i=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:s(e.components),a.createElement(o.Provider,{value:i},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/ec8f9750.7249b2c9.js b/assets/js/ec8f9750.7249b2c9.js new file mode 100644 index 00000000..b404dfbe --- /dev/null +++ b/assets/js/ec8f9750.7249b2c9.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[7278],{9997:e=>{e.exports=JSON.parse('{"tag":{"label":"Hello","permalink":"/catenax-ev.github.io.new/blog/tags/hello","description":"Hello tag description","allTagsPath":"/catenax-ev.github.io.new/blog/tags","count":2,"unlisted":false},"listMetadata":{"permalink":"/catenax-ev.github.io.new/blog/tags/hello","page":1,"postsPerPage":10,"totalPages":1,"totalCount":2,"blogDescription":"Blog","blogTitle":"Blog"}}')}}]); \ No newline at end of file diff --git a/assets/js/f2eba590.c1a1ec04.js b/assets/js/f2eba590.c1a1ec04.js new file mode 100644 index 00000000..03a380ac --- /dev/null +++ b/assets/js/f2eba590.c1a1ec04.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[6327],{7931:(e,n,a)=>{a.r(n),a.d(n,{assets:()=>c,contentTitle:()=>o,default:()=>h,frontMatter:()=>s,metadata:()=>r,toc:()=>d});var t=a(4848),i=a(8453);const s={sidebar_position:1},o="How: Data Space Operations",r={id:"operating-model/how-data-space-operations/how-data-space-operations",title:"How: Data Space Operations",description:"This chapter outlines the overarching processes and premises to onboard and exchange",source:"@site/versioned_docs/version-24.03/operating-model/how-data-space-operations/how-data-space-operations.md",sourceDirName:"operating-model/how-data-space-operations",slug:"/operating-model/how-data-space-operations/",permalink:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-operations/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"What: Service Map",permalink:"/catenax-ev.github.io.new/docs/operating-model/what-service-map/"},next:{title:"How: Data Space Governance",permalink:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance/"}},c={},d=[{value:"General Onboarding",id:"general-onboarding",level:2},{value:"Gaia-X Compliance",id:"gaia-x-compliance",level:2},{value:"SSI Issuer Concept",id:"ssi-issuer-concept",level:2},{value:"Data Exchange based on SSI",id:"data-exchange-based-on-ssi",level:2},{value:"EDC Deployment and Usage Premises",id:"edc-deployment-and-usage-premises",level:2}];function l(e){const n={a:"a",em:"em",h1:"h1",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",ul:"ul",...(0,i.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(n.h1,{id:"how-data-space-operations",children:"How: Data Space Operations"}),"\n",(0,t.jsx)(n.p,{children:"This chapter outlines the overarching processes and premises to onboard and exchange\ndata in the Catena-X data space. This includes the general onboarding process that all\nparticipants must complete to join the Catena-X data space. It involves registration and\ntechnical integration, as well as compliance with the regulatory framework and verification\nthrough the Gaia-X Digital Clearing House. The introduction of Self Sovereign Identities (SSI)\nin Tractus-X Release 23.09 updates the process for offering, exchanging, and using data,\nwhile the chapter also covers EDC deployment and usage premises and available support\noptions for participants."}),"\n",(0,t.jsx)(n.h2,{id:"general-onboarding",children:"General Onboarding"}),"\n",(0,t.jsxs)(n.p,{children:["To participate in the data space, all participants must complete the general registration process, which involves registration and can be extended by the technical integration (see Figure ",(0,t.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-operations/#general-onboarding",children:"General Onboarding Process"}),")."]}),"\n",(0,t.jsxs)(n.p,{children:[(0,t.jsx)(n.img,{alt:"General Onboarding Process",src:a(3077).A+"",width:"1465",height:"692"}),"\n",(0,t.jsx)(n.em,{children:"General Onboarding Process"})]}),"\n",(0,t.jsxs)(n.p,{children:["During ",(0,t.jsx)(n.strong,{children:"registration"}),", all participants must fill out their company data, select their data space role, and agree to the regulatory framework via one of the OSPs (see Chapter ",(0,t.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/who-roles-in-the-catena-x-ecosystem/#onboarding-service-provider",children:"Onboarding Service Provider"}),"). A BPNL (if not yet existing) as well as a Managed Wallet Tenant with BPNL Credential and CX membership Credential are created as part of the registration approval process, which is owned/managed by the operation company. Each participant can collect their identity proofs, certificates and other verifiable information, rights, or services in its identity wallet."]}),"\n",(0,t.jsxs)(n.p,{children:["During ",(0,t.jsx)(n.strong,{children:"technical integration"}),", the technical user creation and registration of the connectors are essential to enable the company communication with the data space. The technical user enables the customer company to connect the connector with the wallet and the connector registration is needed to ensure that the connector can get found by other data space members."]}),"\n",(0,t.jsxs)(n.p,{children:["The self-descriptions of newly registered legal entities and connectors are validated by the GXDCH (see Chapter ",(0,t.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-operations/#gaia-x-compliance",children:"Gaia-X Compliance"}),"). This involves signing and issuing credentials to the identity wallet of a DPC, providing proof of Gaia-X compliance and legal entity notarization. Detailed information about the Standard CX-0006 in the ",(0,t.jsx)(n.a,{href:"https://catena-x.net/de/standard-library",children:"Standard Library"})," of the Catena-X Association."]}),"\n",(0,t.jsx)(n.h2,{id:"gaia-x-compliance",children:"Gaia-X Compliance"}),"\n",(0,t.jsx)(n.p,{children:"The Gaia-X Digital Clearing House (GXDCH) is an external service that maximizes trust within the Catena-X data space and interoperability with other data space initiatives based on the Gaia-X Trust Framework. The GXDCH enables the validation of legal entities, ensures Gaia-X compliance, and creates an eIDAS conform digital signature (SelfDescription) 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, every OSP must connect to the GXDCH. OSP candidates can request more information during conformity assessment."}),"\n",(0,t.jsx)(n.h2,{id:"ssi-issuer-concept",children:"SSI Issuer Concept"}),"\n",(0,t.jsxs)(n.p,{children:["The Tractus-X Release 23.09 initiates the introduction of Self Sovereign Identities (SSI), replacing the Dynamic Attribute Provisioning Service (DAPS). The current release and version of SSI allows only one issuer and one centrally managed identity wallet operated by the CSP-B (see Chapter ",(0,t.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/what-service-map/",children:"What: Service Map"}),"). This also includes the revocation of issued certificates. This is done in cooperation with the Catena-X Association e.g., in case of conscious violation of legal and technical framework. With the 23.09. Release the CSP-B is the single issuer authority of Catena-X credentials. Multi-issuer concept is planned in the following releases. The BPNL can be found on the Catena-X Association website and the portal of the CSP-B. This concept will evolve in future releases, the details of which can be found in Chapter ",(0,t.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/outlook/#further-integration-of-ssi-technologies",children:"Further Integration of SSI Technologies"}),"."]}),"\n",(0,t.jsx)(n.h2,{id:"data-exchange-based-on-ssi",children:"Data Exchange based on SSI"}),"\n",(0,t.jsxs)(n.p,{children:["With the introduction of Self Sovereign Identities (SSI) in the Tractus-X Release 23.09, the processes to participate in a use case as well as offer, exchange, and use data are updated as follows (see Figure ",(0,t.jsx)(n.a,{href:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-operations/#data-exchange-based-on-ssi",children:"Data Exchange Process"}),"):"]}),"\n",(0,t.jsxs)(n.p,{children:[(0,t.jsx)(n.img,{alt:"Data Exchange Process",src:a(6309).A+"",width:"1037",height:"781"}),"\n",(0,t.jsx)(n.em,{children:"Data Exchange Process"})]}),"\n",(0,t.jsxs)(n.ol,{children:["\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Participant signs pre-defined use case framework conditions and requests credential via CSP-B"})}),"\n",(0,t.jsx)(n.p,{children:"The data consumer must sign and upload the respective use case framework conditions to request the use case participation credential."}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Issuer validates request and issues credential"})}),"\n",(0,t.jsx)(n.p,{children:"The request from the participant (e.g., data consumer) is sent to the issuer (operator) for validation (frame version and existing signature) and confirmation, which triggers the creation of the VC."}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Requests credential"})}),"\n",(0,t.jsx)(n.p,{children:"The customer EDC calls the MIW to retrieve the verified summary credentials, requests the signature and retrieves the verified presentation with the summary credential."}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Query catalogue/offers"})}),"\n",(0,t.jsx)(n.p,{children:"With the query of the data provider catalog, the consumer EDC submits the request with the VP in the request header. Upon successful validation, the issuer generates the verified credential using the MIW component and stores it in the wallet tenant of the customer company wallet. is recreated containing both the previous credentials and the newly added credential."}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Submit catalog"})}),"\n",(0,t.jsx)(n.p,{children:"The received offer catalog request and the submitted customer VP are validated by the provider EDC. All data offers where the data access policies set by the provider match the verified credentials owned by the data consumer are sent to the customer. Any data offers that require verified credentials that the data consumer does not have will not be sent/published to the data consumer."}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Manual checking of data offering policies"})}),"\n",(0,t.jsx)(n.p,{children:"Configured data offer policies must be manually checked by the data consumer."}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"If a purpose is specified, the purpose must be validated internally by the data consumer. The purpose may refer to an individual contract concluded between the data consumer and the data provider. The data consumer must review the contract and decide whether the policies are acceptable for the specific data offering based on the established policies (see next step 7)."}),"\n",(0,t.jsx)(n.li,{children:"If no purpose is specified, the negotiation can start immediately, as the access and usage policies are automatically technically enforced and validated by the EDCs."}),"\n"]}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Decision on the purpose of the data offer"})}),"\n",(0,t.jsx)(n.p,{children:"Based on step 6 individual data contract validation, the data consumer must decide whether to proceed with the negotiation or whether to disagree with the individual purpose. If there is disagreement, the negotiation should not be started. If there is consent, the data consumer can start the negotiation."}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Contract negotiation"})}),"\n",(0,t.jsx)(n.p,{children:"The data consumer starts the contract negotiation by sending a request for an agreement/contract"}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Contract conclusion/success"})}),"\n",(0,t.jsx)(n.p,{children:"The EDC of the data provider receives the negotiation requests, validates the access and usage policies of the specific data offer requested by the data provider, and matches it with the VP of the data consumer. If the data consumer has all relevant credentials, the agreement is successfully concluded, and an agreement log is stored in both EDCs."}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Data transfer"})}),"\n",(0,t.jsx)(n.p,{children:"Data transmission/access by the data consumer can take place as long as the contract is active."}),"\n"]}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"edc-deployment-and-usage-premises",children:"EDC Deployment and Usage Premises"}),"\n",(0,t.jsx)(n.p,{children:"Each data space participant has its own organizational structure, consisting of different legal entities and/or subsidiaries. Depending on the organizational structures, data space participants must consider how to organize the representation of their organization in the Catena-X data space. This includes considerations for setting up connector instances regarding organizational, technical, and legal conditions. The following premises apply:"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"The data exchange always takes place between two legal entities, as only their representatives can sign legally binding contracts."}),"\n",(0,t.jsx)(n.li,{children:"Legal entities must be registered and known in the data space."}),"\n",(0,t.jsx)(n.li,{children:"To represent a legal entity in the data space, an associated business partner number (BPNL) is required."}),"\n",(0,t.jsx)(n.li,{children:"The deployment and use of at least one connector (e.g., EDC) per legal entity for data exchange is mandatory."}),"\n",(0,t.jsx)(n.li,{children:"The connector negotiates data usage between endpoints (data plane) by synchronizing access and usage policies between data providers and data consumers."}),"\n",(0,t.jsx)(n.li,{children:"There is no data processing or reviewing of data within the connector itself."}),"\n",(0,t.jsx)(n.li,{children:"Data usage takes place instead at the endpoints of the data providers or data consumers, respectively."}),"\n",(0,t.jsx)(n.li,{children:"Data usage with respect to location and assignment to computer instances/platforms is independent of the runtime environment of the connector itself."}),"\n"]}),"\n",(0,t.jsxs)(n.p,{children:["There are various options for organizational structures and data exchange scenarios such as \u201cone legal entity and one site in one country\u201d, \u201cone legal entity and multiple sites in one country\u201d or \u201cone legal entity and multiple sites in different countries\u201d. For more details on possible connector usage scenarios, please refer to our ",(0,t.jsx)(n.a,{href:"https://catena-x.net/fileadmin/user_upload/Standard-Bibliothek/Update_PDF_Maerz/6_Onboarding/CX_-_0006_Registration_and_Initial_Onboarding_v_1.1.1.pdf",children:"Initial Onboarding Guide"}),". This includes also the different options to obtain a connector, e.g., it can be acquired via an ESP, it can be self-developed or adapted from open-source, or it can be part of a business application from a BAP. If the data exchange does not take place between several legal entities within Catena-X as defined above, no EDC is required. An example would be the connection of the OSP to the GXDCH. For this connection no connector is needed, because this is not an exchange of data between two legal entities within Catena-X."]})]})}function h(e={}){const{wrapper:n}={...(0,i.R)(),...e.components};return n?(0,t.jsx)(n,{...e,children:(0,t.jsx)(l,{...e})}):l(e)}},6309:(e,n,a)=>{a.d(n,{A:()=>t});const t=a.p+"assets/images/data-exchange-process-2de9e4cb18ad9602cb2ba975287579f6.png"},3077:(e,n,a)=>{a.d(n,{A:()=>t});const t=a.p+"assets/images/general-onboarding-process-756b55f51977bf98f2df2d9957704e90.png"},8453:(e,n,a)=>{a.d(n,{R:()=>o,x:()=>r});var t=a(6540);const i={},s=t.createContext(i);function o(e){const n=t.useContext(s);return t.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function r(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:o(e.components),t.createElement(s.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/f2eba590.e3ea43d6.js b/assets/js/f2eba590.e3ea43d6.js deleted file mode 100644 index 347bf5b9..00000000 --- a/assets/js/f2eba590.e3ea43d6.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[6327],{7931:(e,n,a)=>{a.r(n),a.d(n,{assets:()=>c,contentTitle:()=>o,default:()=>h,frontMatter:()=>s,metadata:()=>r,toc:()=>d});var t=a(4848),i=a(8453);const s={sidebar_position:1},o="How: Data Space Operations",r={id:"operating-model/how-data-space-operations/how-data-space-operations",title:"How: Data Space Operations",description:"This chapter outlines the overarching processes and premises to onboard and exchange",source:"@site/versioned_docs/version-24.03/operating-model/how-data-space-operations/how-data-space-operations.md",sourceDirName:"operating-model/how-data-space-operations",slug:"/operating-model/how-data-space-operations/",permalink:"/docs/operating-model/how-data-space-operations/",draft:!1,unlisted:!1,tags:[],version:"24.03",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",previous:{title:"What: Service Map",permalink:"/docs/operating-model/what-service-map/"},next:{title:"How: Data Space Governance",permalink:"/docs/operating-model/how-data-space-governance/"}},c={},d=[{value:"General Onboarding",id:"general-onboarding",level:2},{value:"Gaia-X Compliance",id:"gaia-x-compliance",level:2},{value:"SSI Issuer Concept",id:"ssi-issuer-concept",level:2},{value:"Data Exchange based on SSI",id:"data-exchange-based-on-ssi",level:2},{value:"EDC Deployment and Usage Premises",id:"edc-deployment-and-usage-premises",level:2}];function l(e){const n={a:"a",em:"em",h1:"h1",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",ul:"ul",...(0,i.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(n.h1,{id:"how-data-space-operations",children:"How: Data Space Operations"}),"\n",(0,t.jsx)(n.p,{children:"This chapter outlines the overarching processes and premises to onboard and exchange\ndata in the Catena-X data space. This includes the general onboarding process that all\nparticipants must complete to join the Catena-X data space. It involves registration and\ntechnical integration, as well as compliance with the regulatory framework and verification\nthrough the Gaia-X Digital Clearing House. The introduction of Self Sovereign Identities (SSI)\nin Tractus-X Release 23.09 updates the process for offering, exchanging, and using data,\nwhile the chapter also covers EDC deployment and usage premises and available support\noptions for participants."}),"\n",(0,t.jsx)(n.h2,{id:"general-onboarding",children:"General Onboarding"}),"\n",(0,t.jsxs)(n.p,{children:["To participate in the data space, all participants must complete the general registration process, which involves registration and can be extended by the technical integration (see Figure ",(0,t.jsx)(n.a,{href:"/docs/operating-model/how-data-space-operations/#general-onboarding",children:"General Onboarding Process"}),")."]}),"\n",(0,t.jsxs)(n.p,{children:[(0,t.jsx)(n.img,{alt:"General Onboarding Process",src:a(3077).A+"",width:"1465",height:"692"}),"\n",(0,t.jsx)(n.em,{children:"General Onboarding Process"})]}),"\n",(0,t.jsxs)(n.p,{children:["During ",(0,t.jsx)(n.strong,{children:"registration"}),", all participants must fill out their company data, select their data space role, and agree to the regulatory framework via one of the OSPs (see Chapter ",(0,t.jsx)(n.a,{href:"/docs/operating-model/who-roles-in-the-catena-x-ecosystem/#onboarding-service-provider",children:"Onboarding Service Provider"}),"). A BPNL (if not yet existing) as well as a Managed Wallet Tenant with BPNL Credential and CX membership Credential are created as part of the registration approval process, which is owned/managed by the operation company. Each participant can collect their identity proofs, certificates and other verifiable information, rights, or services in its identity wallet."]}),"\n",(0,t.jsxs)(n.p,{children:["During ",(0,t.jsx)(n.strong,{children:"technical integration"}),", the technical user creation and registration of the connectors are essential to enable the company communication with the data space. The technical user enables the customer company to connect the connector with the wallet and the connector registration is needed to ensure that the connector can get found by other data space members."]}),"\n",(0,t.jsxs)(n.p,{children:["The self-descriptions of newly registered legal entities and connectors are validated by the GXDCH (see Chapter ",(0,t.jsx)(n.a,{href:"/docs/operating-model/how-data-space-operations/#gaia-x-compliance",children:"Gaia-X Compliance"}),"). This involves signing and issuing credentials to the identity wallet of a DPC, providing proof of Gaia-X compliance and legal entity notarization. Detailed information about the Standard CX-0006 in the ",(0,t.jsx)(n.a,{href:"https://catena-x.net/de/standard-library",children:"Standard Library"})," of the Catena-X Association."]}),"\n",(0,t.jsx)(n.h2,{id:"gaia-x-compliance",children:"Gaia-X Compliance"}),"\n",(0,t.jsx)(n.p,{children:"The Gaia-X Digital Clearing House (GXDCH) is an external service that maximizes trust within the Catena-X data space and interoperability with other data space initiatives based on the Gaia-X Trust Framework. The GXDCH enables the validation of legal entities, ensures Gaia-X compliance, and creates an eIDAS conform digital signature (SelfDescription) 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, every OSP must connect to the GXDCH. OSP candidates can request more information during conformity assessment."}),"\n",(0,t.jsx)(n.h2,{id:"ssi-issuer-concept",children:"SSI Issuer Concept"}),"\n",(0,t.jsxs)(n.p,{children:["The Tractus-X Release 23.09 initiates the introduction of Self Sovereign Identities (SSI), replacing the Dynamic Attribute Provisioning Service (DAPS). The current release and version of SSI allows only one issuer and one centrally managed identity wallet operated by the CSP-B (see Chapter ",(0,t.jsx)(n.a,{href:"/docs/operating-model/what-service-map/",children:"What: Service Map"}),"). This also includes the revocation of issued certificates. This is done in cooperation with the Catena-X Association e.g., in case of conscious violation of legal and technical framework. With the 23.09. Release the CSP-B is the single issuer authority of Catena-X credentials. Multi-issuer concept is planned in the following releases. The BPNL can be found on the Catena-X Association website and the portal of the CSP-B. This concept will evolve in future releases, the details of which can be found in Chapter ",(0,t.jsx)(n.a,{href:"/docs/operating-model/outlook/#further-integration-of-ssi-technologies",children:"Further Integration of SSI Technologies"}),"."]}),"\n",(0,t.jsx)(n.h2,{id:"data-exchange-based-on-ssi",children:"Data Exchange based on SSI"}),"\n",(0,t.jsxs)(n.p,{children:["With the introduction of Self Sovereign Identities (SSI) in the Tractus-X Release 23.09, the processes to participate in a use case as well as offer, exchange, and use data are updated as follows (see Figure ",(0,t.jsx)(n.a,{href:"/docs/operating-model/how-data-space-operations/#data-exchange-based-on-ssi",children:"Data Exchange Process"}),"):"]}),"\n",(0,t.jsxs)(n.p,{children:[(0,t.jsx)(n.img,{alt:"Data Exchange Process",src:a(6309).A+"",width:"1037",height:"781"}),"\n",(0,t.jsx)(n.em,{children:"Data Exchange Process"})]}),"\n",(0,t.jsxs)(n.ol,{children:["\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Participant signs pre-defined use case framework conditions and requests credential via CSP-B"})}),"\n",(0,t.jsx)(n.p,{children:"The data consumer must sign and upload the respective use case framework conditions to request the use case participation credential."}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Issuer validates request and issues credential"})}),"\n",(0,t.jsx)(n.p,{children:"The request from the participant (e.g., data consumer) is sent to the issuer (operator) for validation (frame version and existing signature) and confirmation, which triggers the creation of the VC."}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Requests credential"})}),"\n",(0,t.jsx)(n.p,{children:"The customer EDC calls the MIW to retrieve the verified summary credentials, requests the signature and retrieves the verified presentation with the summary credential."}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Query catalogue/offers"})}),"\n",(0,t.jsx)(n.p,{children:"With the query of the data provider catalog, the consumer EDC submits the request with the VP in the request header. Upon successful validation, the issuer generates the verified credential using the MIW component and stores it in the wallet tenant of the customer company wallet. is recreated containing both the previous credentials and the newly added credential."}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Submit catalog"})}),"\n",(0,t.jsx)(n.p,{children:"The received offer catalog request and the submitted customer VP are validated by the provider EDC. All data offers where the data access policies set by the provider match the verified credentials owned by the data consumer are sent to the customer. Any data offers that require verified credentials that the data consumer does not have will not be sent/published to the data consumer."}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Manual checking of data offering policies"})}),"\n",(0,t.jsx)(n.p,{children:"Configured data offer policies must be manually checked by the data consumer."}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"If a purpose is specified, the purpose must be validated internally by the data consumer. The purpose may refer to an individual contract concluded between the data consumer and the data provider. The data consumer must review the contract and decide whether the policies are acceptable for the specific data offering based on the established policies (see next step 7)."}),"\n",(0,t.jsx)(n.li,{children:"If no purpose is specified, the negotiation can start immediately, as the access and usage policies are automatically technically enforced and validated by the EDCs."}),"\n"]}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Decision on the purpose of the data offer"})}),"\n",(0,t.jsx)(n.p,{children:"Based on step 6 individual data contract validation, the data consumer must decide whether to proceed with the negotiation or whether to disagree with the individual purpose. If there is disagreement, the negotiation should not be started. If there is consent, the data consumer can start the negotiation."}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Contract negotiation"})}),"\n",(0,t.jsx)(n.p,{children:"The data consumer starts the contract negotiation by sending a request for an agreement/contract"}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Contract conclusion/success"})}),"\n",(0,t.jsx)(n.p,{children:"The EDC of the data provider receives the negotiation requests, validates the access and usage policies of the specific data offer requested by the data provider, and matches it with the VP of the data consumer. If the data consumer has all relevant credentials, the agreement is successfully concluded, and an agreement log is stored in both EDCs."}),"\n"]}),"\n",(0,t.jsxs)(n.li,{children:["\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.strong,{children:"Data transfer"})}),"\n",(0,t.jsx)(n.p,{children:"Data transmission/access by the data consumer can take place as long as the contract is active."}),"\n"]}),"\n"]}),"\n",(0,t.jsx)(n.h2,{id:"edc-deployment-and-usage-premises",children:"EDC Deployment and Usage Premises"}),"\n",(0,t.jsx)(n.p,{children:"Each data space participant has its own organizational structure, consisting of different legal entities and/or subsidiaries. Depending on the organizational structures, data space participants must consider how to organize the representation of their organization in the Catena-X data space. This includes considerations for setting up connector instances regarding organizational, technical, and legal conditions. The following premises apply:"}),"\n",(0,t.jsxs)(n.ul,{children:["\n",(0,t.jsx)(n.li,{children:"The data exchange always takes place between two legal entities, as only their representatives can sign legally binding contracts."}),"\n",(0,t.jsx)(n.li,{children:"Legal entities must be registered and known in the data space."}),"\n",(0,t.jsx)(n.li,{children:"To represent a legal entity in the data space, an associated business partner number (BPNL) is required."}),"\n",(0,t.jsx)(n.li,{children:"The deployment and use of at least one connector (e.g., EDC) per legal entity for data exchange is mandatory."}),"\n",(0,t.jsx)(n.li,{children:"The connector negotiates data usage between endpoints (data plane) by synchronizing access and usage policies between data providers and data consumers."}),"\n",(0,t.jsx)(n.li,{children:"There is no data processing or reviewing of data within the connector itself."}),"\n",(0,t.jsx)(n.li,{children:"Data usage takes place instead at the endpoints of the data providers or data consumers, respectively."}),"\n",(0,t.jsx)(n.li,{children:"Data usage with respect to location and assignment to computer instances/platforms is independent of the runtime environment of the connector itself."}),"\n"]}),"\n",(0,t.jsxs)(n.p,{children:["There are various options for organizational structures and data exchange scenarios such as \u201cone legal entity and one site in one country\u201d, \u201cone legal entity and multiple sites in one country\u201d or \u201cone legal entity and multiple sites in different countries\u201d. For more details on possible connector usage scenarios, please refer to our ",(0,t.jsx)(n.a,{href:"https://catena-x.net/fileadmin/user_upload/Standard-Bibliothek/Update_PDF_Maerz/6_Onboarding/CX_-_0006_Registration_and_Initial_Onboarding_v_1.1.1.pdf",children:"Initial Onboarding Guide"}),". This includes also the different options to obtain a connector, e.g., it can be acquired via an ESP, it can be self-developed or adapted from open-source, or it can be part of a business application from a BAP. If the data exchange does not take place between several legal entities within Catena-X as defined above, no EDC is required. An example would be the connection of the OSP to the GXDCH. For this connection no connector is needed, because this is not an exchange of data between two legal entities within Catena-X."]})]})}function h(e={}){const{wrapper:n}={...(0,i.R)(),...e.components};return n?(0,t.jsx)(n,{...e,children:(0,t.jsx)(l,{...e})}):l(e)}},6309:(e,n,a)=>{a.d(n,{A:()=>t});const t=a.p+"assets/images/data-exchange-process-2de9e4cb18ad9602cb2ba975287579f6.png"},3077:(e,n,a)=>{a.d(n,{A:()=>t});const t=a.p+"assets/images/general-onboarding-process-756b55f51977bf98f2df2d9957704e90.png"},8453:(e,n,a)=>{a.d(n,{R:()=>o,x:()=>r});var t=a(6540);const i={},s=t.createContext(i);function o(e){const n=t.useContext(s);return t.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function r(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:o(e.components),t.createElement(s.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/f4f34a3a.41ee1bc9.js b/assets/js/f4f34a3a.41ee1bc9.js deleted file mode 100644 index e78a95b7..00000000 --- a/assets/js/f4f34a3a.41ee1bc9.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3637],{5512:(t,e,o)=>{o.r(e),o.d(e,{assets:()=>u,contentTitle:()=>a,default:()=>p,frontMatter:()=>r,metadata:()=>c,toc:()=>i});var s=o(4848),n=o(8453);const r={slug:"mdx-blog-post",title:"MDX Blog Post",authors:["slorber"],tags:["docusaurus"]},a=void 0,c={permalink:"/blog/mdx-blog-post",source:"@site/blog/2021-08-01-mdx-blog-post.mdx",title:"MDX Blog Post",description:"Blog posts support Docusaurus Markdown features, such as MDX.",date:"2021-08-01T00:00:00.000Z",tags:[{inline:!1,label:"Docusaurus",permalink:"/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:.175,hasTruncateMarker:!1,authors:[{name:"S\xe9bastien Lorber",title:"Docusaurus maintainer",url:"https://sebastienlorber.com",imageURL:"https://github.com/slorber.png",key:"slorber"}],frontMatter:{slug:"mdx-blog-post",title:"MDX Blog Post",authors:["slorber"],tags:["docusaurus"]},unlisted:!1,prevItem:{title:"Welcome",permalink:"/blog/welcome"},nextItem:{title:"Long Blog Post",permalink:"/blog/long-blog-post"}},u={authorsImageUrls:[void 0]},i=[];function l(t){const e={a:"a",admonition:"admonition",code:"code",p:"p",pre:"pre",...(0,n.R)(),...t.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsxs)(e.p,{children:["Blog posts support ",(0,s.jsx)(e.a,{href:"https://docusaurus.io/docs/markdown-features",children:"Docusaurus Markdown features"}),", such as ",(0,s.jsx)(e.a,{href:"https://mdxjs.com/",children:"MDX"}),"."]}),"\n",(0,s.jsxs)(e.admonition,{type:"tip",children:[(0,s.jsx)(e.p,{children:"Use the power of React to create interactive blog posts."}),(0,s.jsx)(e.pre,{children:(0,s.jsx)(e.code,{className:"language-js",children:"\n"})}),(0,s.jsx)("button",{onClick:()=>alert("button clicked!"),children:"Click me!"})]})]})}function p(t={}){const{wrapper:e}={...(0,n.R)(),...t.components};return e?(0,s.jsx)(e,{...t,children:(0,s.jsx)(l,{...t})}):l(t)}},8453:(t,e,o)=>{o.d(e,{R:()=>a,x:()=>c});var s=o(6540);const n={},r=s.createContext(n);function a(t){const e=s.useContext(r);return s.useMemo((function(){return"function"==typeof t?t(e):{...e,...t}}),[e,t])}function c(t){let e;return e=t.disableParentContext?"function"==typeof t.components?t.components(n):t.components||n:a(t.components),s.createElement(r.Provider,{value:e},t.children)}}}]); \ No newline at end of file diff --git a/assets/js/f4f34a3a.fe4a86c8.js b/assets/js/f4f34a3a.fe4a86c8.js new file mode 100644 index 00000000..6bf35cc1 --- /dev/null +++ b/assets/js/f4f34a3a.fe4a86c8.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[3637],{5512:(e,t,o)=>{o.r(t),o.d(t,{assets:()=>c,contentTitle:()=>a,default:()=>p,frontMatter:()=>r,metadata:()=>i,toc:()=>u});var s=o(4848),n=o(8453);const r={slug:"mdx-blog-post",title:"MDX Blog Post",authors:["slorber"],tags:["docusaurus"]},a=void 0,i={permalink:"/catenax-ev.github.io.new/blog/mdx-blog-post",source:"@site/blog/2021-08-01-mdx-blog-post.mdx",title:"MDX Blog Post",description:"Blog posts support Docusaurus Markdown features, such as MDX.",date:"2021-08-01T00:00:00.000Z",tags:[{inline:!1,label:"Docusaurus",permalink:"/catenax-ev.github.io.new/blog/tags/docusaurus",description:"Docusaurus tag description"}],readingTime:.175,hasTruncateMarker:!1,authors:[{name:"S\xe9bastien Lorber",title:"Docusaurus maintainer",url:"https://sebastienlorber.com",imageURL:"https://github.com/slorber.png",key:"slorber"}],frontMatter:{slug:"mdx-blog-post",title:"MDX Blog Post",authors:["slorber"],tags:["docusaurus"]},unlisted:!1,prevItem:{title:"Welcome",permalink:"/catenax-ev.github.io.new/blog/welcome"},nextItem:{title:"Long Blog Post",permalink:"/catenax-ev.github.io.new/blog/long-blog-post"}},c={authorsImageUrls:[void 0]},u=[];function l(e){const t={a:"a",admonition:"admonition",code:"code",p:"p",pre:"pre",...(0,n.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsxs)(t.p,{children:["Blog posts support ",(0,s.jsx)(t.a,{href:"https://docusaurus.io/docs/markdown-features",children:"Docusaurus Markdown features"}),", such as ",(0,s.jsx)(t.a,{href:"https://mdxjs.com/",children:"MDX"}),"."]}),"\n",(0,s.jsxs)(t.admonition,{type:"tip",children:[(0,s.jsx)(t.p,{children:"Use the power of React to create interactive blog posts."}),(0,s.jsx)(t.pre,{children:(0,s.jsx)(t.code,{className:"language-js",children:"\n"})}),(0,s.jsx)("button",{onClick:()=>alert("button clicked!"),children:"Click me!"})]})]})}function p(e={}){const{wrapper:t}={...(0,n.R)(),...e.components};return t?(0,s.jsx)(t,{...e,children:(0,s.jsx)(l,{...e})}):l(e)}},8453:(e,t,o)=>{o.d(t,{R:()=>a,x:()=>i});var s=o(6540);const n={},r=s.createContext(n);function a(e){const t=s.useContext(r);return s.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function i(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:a(e.components),s.createElement(r.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/f7adb76b.a4e31be2.js b/assets/js/f7adb76b.a4e31be2.js deleted file mode 100644 index 36688299..00000000 --- a/assets/js/f7adb76b.a4e31be2.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[4832],{4718:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>d,contentTitle:()=>r,default:()=>p,frontMatter:()=>a,metadata:()=>s,toc:()=>l});var o=t(4848),i=t(8453);const a={sidebar_position:1},r="Catena-X Operating Model",s={id:"operating-model/operating-model/operating-model",title:"Catena-X Operating Model",description:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.",source:"@site/docs/operating-model/operating-model/operating-model.md",sourceDirName:"operating-model/operating-model",slug:"/operating-model/operating-model/",permalink:"/docs/next/operating-model/operating-model/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",next:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/docs/next/operating-model/why-introduction/"}},d={},l=[];function c(e){const n={admonition:"admonition",em:"em",h1:"h1",img:"img",p:"p",...(0,i.R)(),...e.components};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsx)(n.h1,{id:"catena-x-operating-model",children:"Catena-X Operating Model"}),"\n",(0,o.jsx)(n.admonition,{type:"danger",children:(0,o.jsx)(n.p,{children:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation."})}),"\n",(0,o.jsxs)(n.p,{children:[(0,o.jsx)(n.img,{alt:"Operating Model",src:t(3787).A+"",width:"794",height:"948"}),"\n",(0,o.jsx)(n.em,{children:"Operating Model"})]})]})}function p(e={}){const{wrapper:n}={...(0,i.R)(),...e.components};return n?(0,o.jsx)(n,{...e,children:(0,o.jsx)(c,{...e})}):c(e)}},3787:(e,n,t)=>{t.d(n,{A:()=>o});const o=t.p+"assets/images/operating-model-bbc65b14aee53a64f303c2b891314512.png"},8453:(e,n,t)=>{t.d(n,{R:()=>r,x:()=>s});var o=t(6540);const i={},a=o.createContext(i);function r(e){const n=o.useContext(a);return o.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function s(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:r(e.components),o.createElement(a.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/f7adb76b.b6121aca.js b/assets/js/f7adb76b.b6121aca.js new file mode 100644 index 00000000..fd8fe1ae --- /dev/null +++ b/assets/js/f7adb76b.b6121aca.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[4832],{4718:(e,n,t)=>{t.r(n),t.d(n,{assets:()=>d,contentTitle:()=>r,default:()=>p,frontMatter:()=>a,metadata:()=>s,toc:()=>l});var o=t(4848),i=t(8453);const a={sidebar_position:1},r="Catena-X Operating Model",s={id:"operating-model/operating-model/operating-model",title:"Catena-X Operating Model",description:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation.",source:"@site/docs/operating-model/operating-model/operating-model.md",sourceDirName:"operating-model/operating-model",slug:"/operating-model/operating-model/",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/operating-model/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1},sidebar:"sidebar_op_model",next:{title:"Who: Roles in the Catena-X ecosystem",permalink:"/catenax-ev.github.io.new/docs/next/operating-model/why-introduction/"}},d={},l=[];function c(e){const n={admonition:"admonition",em:"em",h1:"h1",img:"img",p:"p",...(0,i.R)(),...e.components};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsx)(n.h1,{id:"catena-x-operating-model",children:"Catena-X Operating Model"}),"\n",(0,o.jsx)(n.admonition,{type:"danger",children:(0,o.jsx)(n.p,{children:"This page is currently an MVP and is under construction. The content shown here is also labelled exclusively as DRAFT and is for illustrative purposes only and may not be used in any way in productive operation."})}),"\n",(0,o.jsxs)(n.p,{children:[(0,o.jsx)(n.img,{alt:"Operating Model",src:t(3787).A+"",width:"794",height:"948"}),"\n",(0,o.jsx)(n.em,{children:"Operating Model"})]})]})}function p(e={}){const{wrapper:n}={...(0,i.R)(),...e.components};return n?(0,o.jsx)(n,{...e,children:(0,o.jsx)(c,{...e})}):c(e)}},3787:(e,n,t)=>{t.d(n,{A:()=>o});const o=t.p+"assets/images/operating-model-bbc65b14aee53a64f303c2b891314512.png"},8453:(e,n,t)=>{t.d(n,{R:()=>r,x:()=>s});var o=t(6540);const i={},a=o.createContext(i);function r(e){const n=o.useContext(a);return o.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function s(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:r(e.components),o.createElement(a.Provider,{value:n},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/f81c1134.c6423362.js b/assets/js/f81c1134.c6423362.js deleted file mode 100644 index 52284afb..00000000 --- a/assets/js/f81c1134.c6423362.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8130],{7735:e=>{e.exports=JSON.parse('{"archive":{"blogPosts":[{"id":"welcome","metadata":{"permalink":"/blog/welcome","source":"@site/blog/2021-08-26-welcome/index.md","title":"Welcome","description":"Docusaurus blogging features are powered by the blog plugin.","date":"2021-08-26T00:00:00.000Z","tags":[{"inline":false,"label":"Facebook","permalink":"/blog/tags/facebook","description":"Facebook tag description"},{"inline":false,"label":"Hello","permalink":"/blog/tags/hello","description":"Hello tag description"},{"inline":false,"label":"Docusaurus","permalink":"/blog/tags/docusaurus","description":"Docusaurus tag description"}],"readingTime":0.405,"hasTruncateMarker":false,"authors":[{"name":"S\xe9bastien Lorber","title":"Docusaurus maintainer","url":"https://sebastienlorber.com","imageURL":"https://github.com/slorber.png","key":"slorber"},{"name":"Yangshun Tay","title":"Front End Engineer @ Facebook","url":"https://github.com/yangshun","imageURL":"https://github.com/yangshun.png","key":"yangshun"}],"frontMatter":{"slug":"welcome","title":"Welcome","authors":["slorber","yangshun"],"tags":["facebook","hello","docusaurus"]},"unlisted":false,"nextItem":{"title":"MDX Blog Post","permalink":"/blog/mdx-blog-post"}},"content":"[Docusaurus blogging features](https://docusaurus.io/docs/blog) are powered by the [blog plugin](https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog).\\n\\nSimply add Markdown files (or folders) to the `blog` directory.\\n\\nRegular blog authors can be added to `authors.yml`.\\n\\nThe blog post date can be extracted from filenames, such as:\\n\\n- `2019-05-30-welcome.md`\\n- `2019-05-30-welcome/index.md`\\n\\nA blog post folder can be convenient to co-locate blog post images:\\n\\n![Docusaurus Plushie](./docusaurus-plushie-banner.jpeg)\\n\\nThe blog supports tags as well!\\n\\n**And if you don\'t want a blog**: just delete this directory, and use `blog: false` in your Docusaurus config."},{"id":"mdx-blog-post","metadata":{"permalink":"/blog/mdx-blog-post","source":"@site/blog/2021-08-01-mdx-blog-post.mdx","title":"MDX Blog Post","description":"Blog posts support Docusaurus Markdown features, such as MDX.","date":"2021-08-01T00:00:00.000Z","tags":[{"inline":false,"label":"Docusaurus","permalink":"/blog/tags/docusaurus","description":"Docusaurus tag description"}],"readingTime":0.175,"hasTruncateMarker":false,"authors":[{"name":"S\xe9bastien Lorber","title":"Docusaurus maintainer","url":"https://sebastienlorber.com","imageURL":"https://github.com/slorber.png","key":"slorber"}],"frontMatter":{"slug":"mdx-blog-post","title":"MDX Blog Post","authors":["slorber"],"tags":["docusaurus"]},"unlisted":false,"prevItem":{"title":"Welcome","permalink":"/blog/welcome"},"nextItem":{"title":"Long Blog Post","permalink":"/blog/long-blog-post"}},"content":"Blog posts support [Docusaurus Markdown features](https://docusaurus.io/docs/markdown-features), such as [MDX](https://mdxjs.com/).\\n\\n:::tip\\n\\nUse the power of React to create interactive blog posts.\\n\\n```js\\n\\n```\\n\\n\\n\\n:::"},{"id":"long-blog-post","metadata":{"permalink":"/blog/long-blog-post","source":"@site/blog/2019-05-29-long-blog-post.md","title":"Long Blog Post","description":"This is the summary of a very long blog post,","date":"2019-05-29T00:00:00.000Z","tags":[{"inline":false,"label":"Hello","permalink":"/blog/tags/hello","description":"Hello tag description"},{"inline":false,"label":"Docusaurus","permalink":"/blog/tags/docusaurus","description":"Docusaurus tag description"}],"readingTime":2.05,"hasTruncateMarker":true,"authors":[{"name":"Endilie Yacop Sucipto","title":"Maintainer of Docusaurus","url":"https://github.com/endiliey","imageURL":"https://github.com/endiliey.png","key":"endi"}],"frontMatter":{"slug":"long-blog-post","title":"Long Blog Post","authors":"endi","tags":["hello","docusaurus"]},"unlisted":false,"prevItem":{"title":"MDX Blog Post","permalink":"/blog/mdx-blog-post"},"nextItem":{"title":"First Blog Post","permalink":"/blog/first-blog-post"}},"content":"This is the summary of a very long blog post,\\n\\nUse a `\x3c!--` `truncate` `--\x3e` comment to limit blog post size in the list view.\\n\\n\x3c!--truncate--\x3e\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet\\n\\nLorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"},{"id":"first-blog-post","metadata":{"permalink":"/blog/first-blog-post","source":"@site/blog/2019-05-28-first-blog-post.md","title":"First Blog Post","description":"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet","date":"2019-05-28T00:00:00.000Z","tags":[{"inline":false,"label":"Hola","permalink":"/blog/tags/hola","description":"Hola tag description"},{"inline":false,"label":"Docusaurus","permalink":"/blog/tags/docusaurus","description":"Docusaurus tag description"}],"readingTime":0.12,"hasTruncateMarker":false,"authors":[{"name":"Gao Wei","title":"Docusaurus Core Team","url":"https://github.com/wgao19","image_url":"https://github.com/wgao19.png","imageURL":"https://github.com/wgao19.png"}],"frontMatter":{"slug":"first-blog-post","title":"First Blog Post","authors":{"name":"Gao Wei","title":"Docusaurus Core Team","url":"https://github.com/wgao19","image_url":"https://github.com/wgao19.png","imageURL":"https://github.com/wgao19.png"},"tags":["hola","docusaurus"]},"unlisted":false,"prevItem":{"title":"Long Blog Post","permalink":"/blog/long-blog-post"}},"content":"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet"}]}}')}}]); \ No newline at end of file diff --git a/assets/js/f82cd581.5ed7ba64.js b/assets/js/f82cd581.5ed7ba64.js deleted file mode 100644 index 4a9fba78..00000000 --- a/assets/js/f82cd581.5ed7ba64.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[4584],{4035:e=>{e.exports=JSON.parse('{"tag":{"label":"Hello","permalink":"/blog/tags/hello","description":"Hello tag description","allTagsPath":"/blog/tags","count":2,"unlisted":false},"listMetadata":{"permalink":"/blog/tags/hello","page":1,"postsPerPage":10,"totalPages":1,"totalCount":2,"blogDescription":"Blog","blogTitle":"Blog"}}')}}]); \ No newline at end of file diff --git a/assets/js/f898e4d1.19bbffaa.js b/assets/js/f898e4d1.19bbffaa.js deleted file mode 100644 index acabb7d0..00000000 --- a/assets/js/f898e4d1.19bbffaa.js +++ /dev/null @@ -1 +0,0 @@ -"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9748],{4592:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>c,contentTitle:()=>a,default:()=>h,frontMatter:()=>i,metadata:()=>r,toc:()=>d});var o=n(4848),s=n(8453);const i={sidebar_position:1,title:"Catena-X Ecosystem"},a=void 0,r={id:"working-model/ecosystem/ecosystem",title:"Catena-X Ecosystem",description:"The Catena-X ecosystem consists of three areas",source:"@site/docs/working-model/01-ecosystem/01-ecosystem.md",sourceDirName:"working-model/01-ecosystem",slug:"/working-model/ecosystem/",permalink:"/docs/next/working-model/ecosystem/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Catena-X Ecosystem"},sidebar:"sidebar_working_model",previous:{title:"Overview",permalink:"/docs/next/working-model/overview"},next:{title:"Catena-X Organizational Structure",permalink:"/docs/next/working-model/organizational-structure/"}},c={},d=[{value:"Catena-X Automotive Network e.V'.'",id:"catena-x-automotive-network-ev",level:2},{value:"Development environment",id:"development-environment",level:2},{value:"Operating environment",id:"operating-environment",level:2},{value:"How to contribute and shape the ecosystem?",id:"how-to-contribute-and-shape-the-ecosystem",level:2}];function l(e){const t={a:"a",em:"em",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",ul:"ul",...(0,s.R)(),...e.components};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsx)(t.p,{children:"The Catena-X ecosystem consists of three areas"}),"\n",(0,o.jsxs)(t.ol,{children:["\n",(0,o.jsx)(t.li,{children:(0,o.jsx)(t.a,{href:"/docs/next/working-model/ecosystem/#catena-x-automotive-network-ev",children:"Catena-X Automotive Network e.V."})}),"\n",(0,o.jsx)(t.li,{children:(0,o.jsx)(t.a,{href:"/docs/next/working-model/ecosystem/#development-environment",children:"Development Environment"})}),"\n",(0,o.jsx)(t.li,{children:(0,o.jsx)(t.a,{href:"/docs/next/working-model/ecosystem/#operating-environment",children:"Operating Environment"})}),"\n"]}),"\n",(0,o.jsx)(t.p,{children:(0,o.jsx)(t.img,{alt:"Catena-X Ecosystem",src:n(4404).A+"",width:"1274",height:"577"})}),"\n",(0,o.jsx)(t.h2,{id:"catena-x-automotive-network-ev",children:"Catena-X Automotive Network e.V'.'"}),"\n",(0,o.jsxs)(t.p,{children:["The ",(0,o.jsx)(t.strong,{children:"Catena-X Automotive Network e.V."})," (in the following called 'Association') is responsible for standardization, certifications, and governance of the Catena-X ecosystem. The Association embraces the following industry partners:"]}),"\n",(0,o.jsxs)(t.ul,{children:["\n",(0,o.jsx)(t.li,{children:"Direct partners (e.g., OEMs, suppliers, recyclers)"}),"\n",(0,o.jsx)(t.li,{children:"Indirect partners (e.g., business application and service providers)"}),"\n",(0,o.jsx)(t.li,{children:"Consulting partners (e.g., research institutes, transfer centers)"}),"\n"]}),"\n",(0,o.jsxs)(t.p,{children:["Members of the Association can participate in ",(0,o.jsx)(t.a,{href:"/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles#Committee",children:"Committees"})," and ",(0,o.jsx)(t.a,{href:"/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles#expert-group",children:"Expert Groups"}),"."]}),"\n",(0,o.jsx)(t.h2,{id:"development-environment",children:"Development environment"}),"\n",(0,o.jsxs)(t.p,{children:["The Association is complemented by the ",(0,o.jsx)(t.strong,{children:"development environment"}),". The focus of the development environment is on the one hand on the creation of standardization candidates that can be submitted into the standardization process of the Association, and on the other hand, the development of open-source reference implementations and other implementations for the dataspace."]}),"\n",(0,o.jsx)(t.p,{children:(0,o.jsx)(t.img,{alt:"Catena-X Development environment",src:n(497).A+""})}),"\n",(0,o.jsx)(t.h2,{id:"operating-environment",children:"Operating environment"}),"\n",(0,o.jsxs)(t.p,{children:["In the ",(0,o.jsx)(t.strong,{children:"operating environment"}),", the various open source and commercial services and business applications are operated by different providers. A detailed description of the ",(0,o.jsx)(t.a,{href:"https://catenax-ev.github.io/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem",children:"provider roles"})," and the associated ",(0,o.jsx)(t.a,{href:"https://catenax-ev.github.io/docs/next/operating-model/what-service-map",children:"software components"})," can be found in ",(0,o.jsx)(t.a,{href:"https://catenax-ev.github.io/docs/next/operating-model/operating-model",children:"Operating Model"}),"."]}),"\n",(0,o.jsxs)(t.p,{children:["The Catena-X Association publishes standards with the goal of enabling interoperability, data sovereignty, and security for all participants in the data space. The ecosystem participants must comply with the standards published by the Catena-X Association in order to work with the data space. Catena-X standards build on Gaia-X / ",(0,o.jsx)(t.em,{children:"International Data Space Association"})," (IDSA) concepts and principles, industry standards, and best practices, among others, and extends these by automotive domain and use case specific requirements. By certifying ecosystem participants and software components the Catena-X Association ensures transparency and trust in the ecosystem. A certification testifies, for example, that a software component is interoperable, data sovereign and safe to use in the Catena X data space."]}),"\n",(0,o.jsx)(t.h2,{id:"how-to-contribute-and-shape-the-ecosystem",children:"How to contribute and shape the ecosystem?"}),"\n",(0,o.jsx)(t.p,{children:"Contribute to..."}),"\n",(0,o.jsxs)(t.ul,{children:["\n",(0,o.jsxs)(t.li,{children:[(0,o.jsx)(t.strong,{children:"Specifications and Standards"})," in the Catena-X Association by working in ",(0,o.jsx)(t.a,{href:"/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles#Committee",children:"Committees"})," and ",(0,o.jsx)(t.a,{href:"/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles#expert-group",children:"Expert Groups"})]}),"\n",(0,o.jsxs)(t.li,{children:[(0,o.jsx)(t.strong,{children:"Reference Implementations"})," by implementing features, improvements, bugs, new service etc. in the ",(0,o.jsx)(t.a,{href:"https://eclipse-tractusx.github.io/",children:"Tractus-X"})," Project that comply with the Catena-X standards"]}),"\n"]})]})}function h(e={}){const{wrapper:t}={...(0,s.R)(),...e.components};return t?(0,o.jsx)(t,{...e,children:(0,o.jsx)(l,{...e})}):l(e)}},497:(e,t,n)=>{n.d(t,{A:()=>o});const o=n.p+"assets/images/CX-development-environment.drawio-e0ba8d9f6849118d38137bc35b1b2e11.svg"},4404:(e,t,n)=>{n.d(t,{A:()=>o});const o=n.p+"assets/images/catena-x-ecosytem-896aab15f2a2e2f039af5f8e0d3fff6c.png"},8453:(e,t,n)=>{n.d(t,{R:()=>a,x:()=>r});var o=n(6540);const s={},i=o.createContext(s);function a(e){const t=o.useContext(i);return o.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function r(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:a(e.components),o.createElement(i.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/f898e4d1.9f6c5925.js b/assets/js/f898e4d1.9f6c5925.js new file mode 100644 index 00000000..c99ffbe5 --- /dev/null +++ b/assets/js/f898e4d1.9f6c5925.js @@ -0,0 +1 @@ +"use strict";(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[9748],{4592:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>c,contentTitle:()=>a,default:()=>h,frontMatter:()=>s,metadata:()=>r,toc:()=>d});var o=n(4848),i=n(8453);const s={sidebar_position:1,title:"Catena-X Ecosystem"},a=void 0,r={id:"working-model/ecosystem/ecosystem",title:"Catena-X Ecosystem",description:"The Catena-X ecosystem consists of three areas",source:"@site/docs/working-model/01-ecosystem/01-ecosystem.md",sourceDirName:"working-model/01-ecosystem",slug:"/working-model/ecosystem/",permalink:"/catenax-ev.github.io.new/docs/next/working-model/ecosystem/",draft:!1,unlisted:!1,tags:[],version:"current",sidebarPosition:1,frontMatter:{sidebar_position:1,title:"Catena-X Ecosystem"},sidebar:"sidebar_working_model",previous:{title:"Overview",permalink:"/catenax-ev.github.io.new/docs/next/working-model/overview"},next:{title:"Catena-X Organizational Structure",permalink:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/"}},c={},d=[{value:"Catena-X Automotive Network e.V'.'",id:"catena-x-automotive-network-ev",level:2},{value:"Development environment",id:"development-environment",level:2},{value:"Operating environment",id:"operating-environment",level:2},{value:"How to contribute and shape the ecosystem?",id:"how-to-contribute-and-shape-the-ecosystem",level:2}];function l(e){const t={a:"a",em:"em",h2:"h2",img:"img",li:"li",ol:"ol",p:"p",strong:"strong",ul:"ul",...(0,i.R)(),...e.components};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsx)(t.p,{children:"The Catena-X ecosystem consists of three areas"}),"\n",(0,o.jsxs)(t.ol,{children:["\n",(0,o.jsx)(t.li,{children:(0,o.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/ecosystem/#catena-x-automotive-network-ev",children:"Catena-X Automotive Network e.V."})}),"\n",(0,o.jsx)(t.li,{children:(0,o.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/ecosystem/#development-environment",children:"Development Environment"})}),"\n",(0,o.jsx)(t.li,{children:(0,o.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/ecosystem/#operating-environment",children:"Operating Environment"})}),"\n"]}),"\n",(0,o.jsx)(t.p,{children:(0,o.jsx)(t.img,{alt:"Catena-X Ecosystem",src:n(4404).A+"",width:"1274",height:"577"})}),"\n",(0,o.jsx)(t.h2,{id:"catena-x-automotive-network-ev",children:"Catena-X Automotive Network e.V'.'"}),"\n",(0,o.jsxs)(t.p,{children:["The ",(0,o.jsx)(t.strong,{children:"Catena-X Automotive Network e.V."})," (in the following called 'Association') is responsible for standardization, certifications, and governance of the Catena-X ecosystem. The Association embraces the following industry partners:"]}),"\n",(0,o.jsxs)(t.ul,{children:["\n",(0,o.jsx)(t.li,{children:"Direct partners (e.g., OEMs, suppliers, recyclers)"}),"\n",(0,o.jsx)(t.li,{children:"Indirect partners (e.g., business application and service providers)"}),"\n",(0,o.jsx)(t.li,{children:"Consulting partners (e.g., research institutes, transfer centers)"}),"\n"]}),"\n",(0,o.jsxs)(t.p,{children:["Members of the Association can participate in ",(0,o.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles#Committee",children:"Committees"})," and ",(0,o.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles#expert-group",children:"Expert Groups"}),"."]}),"\n",(0,o.jsx)(t.h2,{id:"development-environment",children:"Development environment"}),"\n",(0,o.jsxs)(t.p,{children:["The Association is complemented by the ",(0,o.jsx)(t.strong,{children:"development environment"}),". The focus of the development environment is on the one hand on the creation of standardization candidates that can be submitted into the standardization process of the Association, and on the other hand, the development of open-source reference implementations and other implementations for the dataspace."]}),"\n",(0,o.jsx)(t.p,{children:(0,o.jsx)(t.img,{alt:"Catena-X Development environment",src:n(497).A+""})}),"\n",(0,o.jsx)(t.h2,{id:"operating-environment",children:"Operating environment"}),"\n",(0,o.jsxs)(t.p,{children:["In the ",(0,o.jsx)(t.strong,{children:"operating environment"}),", the various open source and commercial services and business applications are operated by different providers. A detailed description of the ",(0,o.jsx)(t.a,{href:"https://catenax-ev.github.io/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem",children:"provider roles"})," and the associated ",(0,o.jsx)(t.a,{href:"https://catenax-ev.github.io/docs/next/operating-model/what-service-map",children:"software components"})," can be found in ",(0,o.jsx)(t.a,{href:"https://catenax-ev.github.io/docs/next/operating-model/operating-model",children:"Operating Model"}),"."]}),"\n",(0,o.jsxs)(t.p,{children:["The Catena-X Association publishes standards with the goal of enabling interoperability, data sovereignty, and security for all participants in the data space. The ecosystem participants must comply with the standards published by the Catena-X Association in order to work with the data space. Catena-X standards build on Gaia-X / ",(0,o.jsx)(t.em,{children:"International Data Space Association"})," (IDSA) concepts and principles, industry standards, and best practices, among others, and extends these by automotive domain and use case specific requirements. By certifying ecosystem participants and software components the Catena-X Association ensures transparency and trust in the ecosystem. A certification testifies, for example, that a software component is interoperable, data sovereign and safe to use in the Catena X data space."]}),"\n",(0,o.jsx)(t.h2,{id:"how-to-contribute-and-shape-the-ecosystem",children:"How to contribute and shape the ecosystem?"}),"\n",(0,o.jsx)(t.p,{children:"Contribute to..."}),"\n",(0,o.jsxs)(t.ul,{children:["\n",(0,o.jsxs)(t.li,{children:[(0,o.jsx)(t.strong,{children:"Specifications and Standards"})," in the Catena-X Association by working in ",(0,o.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles#Committee",children:"Committees"})," and ",(0,o.jsx)(t.a,{href:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles#expert-group",children:"Expert Groups"})]}),"\n",(0,o.jsxs)(t.li,{children:[(0,o.jsx)(t.strong,{children:"Reference Implementations"})," by implementing features, improvements, bugs, new service etc. in the ",(0,o.jsx)(t.a,{href:"https://eclipse-tractusx.github.io/",children:"Tractus-X"})," Project that comply with the Catena-X standards"]}),"\n"]})]})}function h(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,o.jsx)(t,{...e,children:(0,o.jsx)(l,{...e})}):l(e)}},497:(e,t,n)=>{n.d(t,{A:()=>o});const o=n.p+"assets/images/CX-development-environment.drawio-e0ba8d9f6849118d38137bc35b1b2e11.svg"},4404:(e,t,n)=>{n.d(t,{A:()=>o});const o=n.p+"assets/images/catena-x-ecosytem-896aab15f2a2e2f039af5f8e0d3fff6c.png"},8453:(e,t,n)=>{n.d(t,{R:()=>a,x:()=>r});var o=n(6540);const i={},s=o.createContext(i);function a(e){const t=o.useContext(s);return o.useMemo((function(){return"function"==typeof e?e(t):{...t,...e}}),[t,e])}function r(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:a(e.components),o.createElement(s.Provider,{value:t},e.children)}}}]); \ No newline at end of file diff --git a/assets/js/main.5a2fcde4.js b/assets/js/main.5a2fcde4.js new file mode 100644 index 00000000..e7eb07c0 --- /dev/null +++ b/assets/js/main.5a2fcde4.js @@ -0,0 +1,2 @@ +/*! For license information please see main.5a2fcde4.js.LICENSE.txt */ +(self.webpackChunkcatenax_ev_github_io_new=self.webpackChunkcatenax_ev_github_io_new||[]).push([[8792],{5391:(e,t,n)=>{"use strict";function r(e){var t,n,o="";if("string"==typeof e||"number"==typeof e)o+=e;else if("object"==typeof e)if(Array.isArray(e))for(t=0;to});const o=function(){for(var e,t,n=0,o="";n{"use strict";n.d(t,{A:()=>p});n(6540);var r=n(3259),o=n.n(r),a=n(4054);const i={"01a85c17":[()=>Promise.all([n.e(1869),n.e(8209)]).then(n.bind(n,9158)),"@theme/BlogTagsListPage",9158],"0645984d":[()=>n.e(3923).then(n.bind(n,9459)),"@site/versioned_docs/version-24.03/operating-model/appendix/appendix.md",9459],"098dc4e6":[()=>n.e(3026).then(n.bind(n,3488)),"@site/versioned_docs/version-24.03/operating-model/what-service-map/what-service-map.md",3488],"0d7102ad":[()=>n.e(3738).then(n.t.bind(n,5248,19)),"@generated/docusaurus-plugin-content-docs/default/p/catenax-ev-github-io-new-docs-next-9fc.json",5248],"0df7deee":[()=>n.e(297).then(n.bind(n,1318)),"@site/docs/operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem.md",1318],"10f26ab1":[()=>n.e(2652).then(n.bind(n,4078)),"@site/docs/operating-model/appendix/appendix.md",4078],"138e0e15":[()=>n.e(4921).then(n.t.bind(n,1597,19)),"@generated/@easyops-cn/docusaurus-search-local/default/__plugin.json",1597],"14b69759":[()=>n.e(7026).then(n.bind(n,7563)),"@site/versioned_docs/version-24.03/operating-model/how-life-cycle-management/how-life-cycle-management.md",7563],17896441:[()=>Promise.all([n.e(1869),n.e(8498),n.e(8401)]).then(n.bind(n,2447)),"@theme/DocItem",2447],"1897e797":[()=>n.e(5740).then(n.bind(n,4885)),"@site/docs/standards/overview.md",4885],"1a4e3797":[()=>Promise.all([n.e(1869),n.e(2138)]).then(n.bind(n,1283)),"@theme/SearchPage",1283],"1df93b7f":[()=>Promise.all([n.e(1869),n.e(4583)]).then(n.bind(n,5579)),"@site/src/pages/index.tsx",5579],"1f391b9e":[()=>Promise.all([n.e(1869),n.e(8498),n.e(6061)]).then(n.bind(n,7973)),"@theme/MDXPage",7973],"2224ae46":[()=>n.e(4265).then(n.bind(n,2549)),"@site/docs/working-model/glossary.md",2549],"254e3ee1":[()=>n.e(8399).then(n.bind(n,6747)),"@site/versioned_docs/version-24.03/operating-model/why-introduction/why-introduction.md",6747],26649072:[()=>n.e(5077).then(n.t.bind(n,581,19)),"@generated/docusaurus-plugin-content-blog/default/p/catenax-ev-github-io-new-blog-9ee.json",581],"27525b73":[()=>n.e(3380).then(n.bind(n,8108)),"@site/docs/working-model/03-process-from-idea-to-production/03-01-process-from-idea-to-production.md",8108],"2856a3e9":[()=>n.e(9766).then(n.bind(n,4155)),"@site/versioned_docs/version-24.03/operating-model/operating-model/operating-model.md",4155],"2baaddb5":[()=>n.e(5018).then(n.bind(n,4591)),"@site/versioned_docs/version-24.03/operating-model/how-data-space-governance/how-data-space-governance.md",4591],"31f0b325":[()=>n.e(6559).then(n.bind(n,9110)),"@site/docs/operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space.md",9110],"33a2184c":[()=>n.e(9160).then(n.t.bind(n,2804,19)),"@generated/docusaurus-plugin-content-blog/default/p/catenax-ev-github-io-new-blog-tags-facebook-638.json",2804],"36994c47":[()=>n.e(9858).then(n.t.bind(n,5516,19)),"@generated/docusaurus-plugin-content-blog/default/__plugin.json",5516],"395bc0fb":[()=>n.e(8031).then(n.bind(n,3379)),"@site/versioned_docs/version-24.03/operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space.md",3379],"3a483871":[()=>n.e(9410).then(n.bind(n,2062)),"@site/docs/operating-model/why-introduction/why-introduction.md",2062],"3ce65734":[()=>n.e(2825).then(n.bind(n,4990)),"@site/docs/operating-model/what-service-map/what-service-map.md",4990],"48cc5724":[()=>n.e(855).then(n.bind(n,72)),"@site/src/pages/getting-started-github.md",72],"50f28384":[()=>n.e(3095).then(n.bind(n,1339)),"@site/versioned_docs/version-24.03/operating-model/change-log/change-log.md",1339],"5243e443":[()=>n.e(1941).then(n.bind(n,6832)),"@site/docs/operating-model/glossary/glossary.md",6832],"5440ed21":[()=>n.e(9520).then(n.bind(n,672)),"@site/versioned_docs/version-24.03/operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem.md",672],"560caf3c":[()=>n.e(6230).then(n.t.bind(n,2807,19)),"@generated/docusaurus-plugin-content-blog/default/p/catenax-ev-github-io-new-blog-tags-docusaurus-b33.json",2807],59362658:[()=>n.e(9325).then(n.bind(n,1180)),"@site/blog/2021-08-01-mdx-blog-post.mdx",1180],"5e95c892":[()=>n.e(9647).then(n.bind(n,7121)),"@theme/DocsRoot",7121],"5e9f5e1a":[()=>Promise.resolve().then(n.bind(n,4784)),"@generated/docusaurus.config",4784],"63fe0935":[()=>n.e(6144).then(n.bind(n,1314)),"@site/docs/working-model/02-organizational-structure/02-organizational-structure.md",1314],"66b22c07":[()=>n.e(9457).then(n.bind(n,6486)),"@site/docs/operating-model/how-life-cycle-management/how-life-cycle-management.md",6486],"6875c492":[()=>Promise.all([n.e(1869),n.e(8498),n.e(3242),n.e(4813)]).then(n.bind(n,3069)),"@theme/BlogTagsPostsPage",3069],"6e164704":[()=>n.e(4926).then(n.t.bind(n,7957,19)),"@generated/docusaurus-plugin-content-docs/default/p/catenax-ev-github-io-new-docs-bfc.json",7957],"6e427521":[()=>n.e(7177).then(n.bind(n,8803)),"@site/src/pages/copyright.md",8803],"726bd3c0":[()=>n.e(8254).then(n.bind(n,7718)),"@site/docs/operating-model/outlook/outlook.md",7718],"73664a40":[()=>n.e(1972).then(n.bind(n,9581)),"@site/blog/2019-05-29-long-blog-post.md",9581],"7661071f":[()=>n.e(8737).then(n.bind(n,4137)),"@site/blog/2021-08-26-welcome/index.md?truncated=true",4137],"814f3328":[()=>n.e(7472).then(n.t.bind(n,5513,19)),"~blog/default/blog-post-list-prop-default.json",5513],"8389dc22":[()=>n.e(94).then(n.bind(n,5206)),"@site/docs/operating-model/how-data-space-operations/how-data-space-operations.md",5206],"851dcdeb":[()=>n.e(8545).then(n.bind(n,470)),"@site/docs/working-model/03-process-from-idea-to-production/03-02-Contribution-Guideline.md",470],"86cc9362":[()=>n.e(423).then(n.bind(n,2474)),"@site/versioned_docs/version-24.03/standards/overview.md",2474],"8717b14a":[()=>n.e(3694).then(n.bind(n,1615)),"@site/blog/2019-05-29-long-blog-post.md?truncated=true",1615],"8843b0b9":[()=>n.e(1721).then(n.bind(n,6474)),"@site/docs/operating-model/how-data-space-governance/how-data-space-governance.md",6474],"8acd709f":[()=>n.e(4047).then(n.bind(n,6989)),"@site/versioned_docs/version-24.03/working-model/overview.md",6989],"925b3f96":[()=>n.e(8609).then(n.bind(n,5026)),"@site/blog/2019-05-28-first-blog-post.md?truncated=true",5026],"9bc6bf15":[()=>n.e(7803).then(n.bind(n,1066)),"@site/docs/working-model/02-organizational-structure/overview-roles/catena-x-roles.md",1066],"9c06b359":[()=>n.e(7790).then(n.bind(n,7862)),"@site/docs/working-model/02-organizational-structure/overview-roles/overview-roles.md",7862],"9e4087bc":[()=>n.e(2711).then(n.bind(n,9331)),"@theme/BlogArchivePage",9331],"9e6fa7e7":[()=>n.e(421).then(n.t.bind(n,6463,19)),"@generated/docusaurus-plugin-content-blog/default/p/catenax-ev-github-io-new-blog-tags-hola-354.json",6463],a618e3e0:[()=>n.e(4182).then(n.bind(n,7854)),"@site/docs/working-model/03-process-from-idea-to-production/03-04-Issue-Process.md",7854],a6aa9e1f:[()=>Promise.all([n.e(1869),n.e(8498),n.e(3242),n.e(7643)]).then(n.bind(n,5124)),"@theme/BlogListPage",5124],a7456010:[()=>n.e(1235).then(n.t.bind(n,8552,19)),"@generated/docusaurus-plugin-content-pages/default/__plugin.json",8552],a7bd4aaa:[()=>n.e(7098).then(n.bind(n,4532)),"@theme/DocVersionRoot",4532],a80828e2:[()=>n.e(9371).then(n.bind(n,2873)),"@site/versioned_docs/version-24.03/operating-model/glossary/glossary.md",2873],a94703ab:[()=>Promise.all([n.e(1869),n.e(9048)]).then(n.bind(n,2559)),"@theme/DocRoot",2559],aabcef9f:[()=>n.e(3252).then(n.t.bind(n,337,19)),"@generated/docusaurus-plugin-content-blog/default/p/catenax-ev-github-io-new-blog-tags-faf.json",337],aba21aa0:[()=>n.e(5742).then(n.t.bind(n,7093,19)),"@generated/docusaurus-plugin-content-docs/default/__plugin.json",7093],acecf23e:[()=>n.e(1903).then(n.t.bind(n,1912,19)),"~blog/default/blogMetadata-default.json",1912],ae9ec75a:[()=>n.e(5155).then(n.bind(n,8590)),"@site/docs/working-model/02-organizational-structure/overview-roles/tractus-x-roles.md",8590],b2cb1568:[()=>n.e(7220).then(n.bind(n,502)),"@site/docs/operating-model/change-log/change-log.md",502],c11d2165:[()=>n.e(440).then(n.bind(n,4270)),"@site/docs/working-model/02-organizational-structure/02-03-tooling.md",4270],ccc49370:[()=>Promise.all([n.e(1869),n.e(8498),n.e(3242),n.e(3249)]).then(n.bind(n,3858)),"@theme/BlogPostPage",3858],cd8fd8f7:[()=>n.e(5145).then(n.bind(n,9265)),"@site/src/pages/markdown-guidelines.md",9265],d85277d8:[()=>n.e(3732).then(n.t.bind(n,9155,19)),"@generated/docusaurus-plugin-content-blog/default/p/catenax-ev-github-io-new-blog-archive-ae2.json",9155],d9f32620:[()=>n.e(5557).then(n.bind(n,7447)),"@site/blog/2021-08-26-welcome/index.md",7447],e18cfb11:[()=>n.e(4676).then(n.bind(n,5358)),"@site/docs/working-model/overview.md",5358],e273c56f:[()=>n.e(9328).then(n.bind(n,4014)),"@site/blog/2019-05-28-first-blog-post.md",4014],e6e7a2ca:[()=>n.e(6699).then(n.bind(n,7875)),"@site/versioned_docs/version-24.03/operating-model/outlook/outlook.md",7875],ec8f9750:[()=>n.e(7278).then(n.t.bind(n,9997,19)),"@generated/docusaurus-plugin-content-blog/default/p/catenax-ev-github-io-new-blog-tags-hello-a4a.json",9997],f2eba590:[()=>n.e(6327).then(n.bind(n,7931)),"@site/versioned_docs/version-24.03/operating-model/how-data-space-operations/how-data-space-operations.md",7931],f4f34a3a:[()=>n.e(3637).then(n.bind(n,5512)),"@site/blog/2021-08-01-mdx-blog-post.mdx?truncated=true",5512],f7adb76b:[()=>n.e(4832).then(n.bind(n,4718)),"@site/docs/operating-model/operating-model/operating-model.md",4718],f898e4d1:[()=>n.e(9748).then(n.bind(n,4592)),"@site/docs/working-model/01-ecosystem/01-ecosystem.md",4592]};var l=n(4848);function s(e){let{error:t,retry:n,pastDelay:r}=e;return t?(0,l.jsxs)("div",{style:{textAlign:"center",color:"#fff",backgroundColor:"#fa383e",borderColor:"#fa383e",borderStyle:"solid",borderRadius:"0.25rem",borderWidth:"1px",boxSizing:"border-box",display:"block",padding:"1rem",flex:"0 0 50%",marginLeft:"25%",marginRight:"25%",marginTop:"5rem",maxWidth:"50%",width:"100%"},children:[(0,l.jsx)("p",{children:String(t)}),(0,l.jsx)("div",{children:(0,l.jsx)("button",{type:"button",onClick:n,children:"Retry"})})]}):r?(0,l.jsx)("div",{style:{display:"flex",justifyContent:"center",alignItems:"center",height:"100vh"},children:(0,l.jsx)("svg",{id:"loader",style:{width:128,height:110,position:"absolute",top:"calc(100vh - 64%)"},viewBox:"0 0 45 45",xmlns:"http://www.w3.org/2000/svg",stroke:"#61dafb",children:(0,l.jsxs)("g",{fill:"none",fillRule:"evenodd",transform:"translate(1 1)",strokeWidth:"2",children:[(0,l.jsxs)("circle",{cx:"22",cy:"22",r:"6",strokeOpacity:"0",children:[(0,l.jsx)("animate",{attributeName:"r",begin:"1.5s",dur:"3s",values:"6;22",calcMode:"linear",repeatCount:"indefinite"}),(0,l.jsx)("animate",{attributeName:"stroke-opacity",begin:"1.5s",dur:"3s",values:"1;0",calcMode:"linear",repeatCount:"indefinite"}),(0,l.jsx)("animate",{attributeName:"stroke-width",begin:"1.5s",dur:"3s",values:"2;0",calcMode:"linear",repeatCount:"indefinite"})]}),(0,l.jsxs)("circle",{cx:"22",cy:"22",r:"6",strokeOpacity:"0",children:[(0,l.jsx)("animate",{attributeName:"r",begin:"3s",dur:"3s",values:"6;22",calcMode:"linear",repeatCount:"indefinite"}),(0,l.jsx)("animate",{attributeName:"stroke-opacity",begin:"3s",dur:"3s",values:"1;0",calcMode:"linear",repeatCount:"indefinite"}),(0,l.jsx)("animate",{attributeName:"stroke-width",begin:"3s",dur:"3s",values:"2;0",calcMode:"linear",repeatCount:"indefinite"})]}),(0,l.jsx)("circle",{cx:"22",cy:"22",r:"8",children:(0,l.jsx)("animate",{attributeName:"r",begin:"0s",dur:"1.5s",values:"6;1;2;3;4;5;6",calcMode:"linear",repeatCount:"indefinite"})})]})})}):null}var c=n(6921),u=n(3102);function d(e,t){if("*"===e)return o()({loading:s,loader:()=>n.e(2237).then(n.bind(n,2237)),modules:["@theme/NotFound"],webpack:()=>[2237],render(e,t){const n=e.default;return(0,l.jsx)(u.W,{value:{plugin:{name:"native",id:"default"}},children:(0,l.jsx)(n,{...t})})}});const r=a[`${e}-${t}`],d={},p=[],f=[],h=(0,c.A)(r);return Object.entries(h).forEach((e=>{let[t,n]=e;const r=i[n];r&&(d[t]=r[0],p.push(r[1]),f.push(r[2]))})),o().Map({loading:s,loader:d,modules:p,webpack:()=>f,render(t,n){const o=JSON.parse(JSON.stringify(r));Object.entries(t).forEach((t=>{let[n,r]=t;const a=r.default;if(!a)throw new Error(`The page component at ${e} doesn't have a default export. This makes it impossible to render anything. Consider default-exporting a React component.`);"object"!=typeof a&&"function"!=typeof a||Object.keys(r).filter((e=>"default"!==e)).forEach((e=>{a[e]=r[e]}));let i=o;const l=n.split(".");l.slice(0,-1).forEach((e=>{i=i[e]})),i[l[l.length-1]]=a}));const a=o.__comp;delete o.__comp;const i=o.__context;delete o.__context;const s=o.__props;return delete o.__props,(0,l.jsx)(u.W,{value:i,children:(0,l.jsx)(a,{...o,...s,...n})})}})}const p=[{path:"/catenax-ev.github.io.new/blog",component:d("/catenax-ev.github.io.new/blog","055"),exact:!0},{path:"/catenax-ev.github.io.new/blog/archive",component:d("/catenax-ev.github.io.new/blog/archive","ce3"),exact:!0},{path:"/catenax-ev.github.io.new/blog/first-blog-post",component:d("/catenax-ev.github.io.new/blog/first-blog-post","caf"),exact:!0},{path:"/catenax-ev.github.io.new/blog/long-blog-post",component:d("/catenax-ev.github.io.new/blog/long-blog-post","089"),exact:!0},{path:"/catenax-ev.github.io.new/blog/mdx-blog-post",component:d("/catenax-ev.github.io.new/blog/mdx-blog-post","74c"),exact:!0},{path:"/catenax-ev.github.io.new/blog/tags",component:d("/catenax-ev.github.io.new/blog/tags","fcb"),exact:!0},{path:"/catenax-ev.github.io.new/blog/tags/docusaurus",component:d("/catenax-ev.github.io.new/blog/tags/docusaurus","d3b"),exact:!0},{path:"/catenax-ev.github.io.new/blog/tags/facebook",component:d("/catenax-ev.github.io.new/blog/tags/facebook","1bc"),exact:!0},{path:"/catenax-ev.github.io.new/blog/tags/hello",component:d("/catenax-ev.github.io.new/blog/tags/hello","532"),exact:!0},{path:"/catenax-ev.github.io.new/blog/tags/hola",component:d("/catenax-ev.github.io.new/blog/tags/hola","d83"),exact:!0},{path:"/catenax-ev.github.io.new/blog/welcome",component:d("/catenax-ev.github.io.new/blog/welcome","360"),exact:!0},{path:"/catenax-ev.github.io.new/copyright",component:d("/catenax-ev.github.io.new/copyright","2b4"),exact:!0},{path:"/catenax-ev.github.io.new/getting-started-github",component:d("/catenax-ev.github.io.new/getting-started-github","f3b"),exact:!0},{path:"/catenax-ev.github.io.new/markdown-guidelines",component:d("/catenax-ev.github.io.new/markdown-guidelines","729"),exact:!0},{path:"/catenax-ev.github.io.new/search",component:d("/catenax-ev.github.io.new/search","040"),exact:!0},{path:"/catenax-ev.github.io.new/docs",component:d("/catenax-ev.github.io.new/docs","982"),routes:[{path:"/catenax-ev.github.io.new/docs/next",component:d("/catenax-ev.github.io.new/docs/next","b3a"),routes:[{path:"/catenax-ev.github.io.new/docs/next",component:d("/catenax-ev.github.io.new/docs/next","425"),routes:[{path:"/catenax-ev.github.io.new/docs/next/operating-model/appendix",component:d("/catenax-ev.github.io.new/docs/next/operating-model/appendix","25d"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/next/operating-model/change-log",component:d("/catenax-ev.github.io.new/docs/next/operating-model/change-log","4b8"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/next/operating-model/glossary",component:d("/catenax-ev.github.io.new/docs/next/operating-model/glossary","7d5"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance",component:d("/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance","5c7"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-operations",component:d("/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-operations","88d"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/next/operating-model/how-life-cycle-management",component:d("/catenax-ev.github.io.new/docs/next/operating-model/how-life-cycle-management","d18"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/next/operating-model/operating-model",component:d("/catenax-ev.github.io.new/docs/next/operating-model/operating-model","4c7"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/next/operating-model/outlook",component:d("/catenax-ev.github.io.new/docs/next/operating-model/outlook","2c8"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/next/operating-model/what-service-map",component:d("/catenax-ev.github.io.new/docs/next/operating-model/what-service-map","e5f"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem",component:d("/catenax-ev.github.io.new/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem","c9d"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/next/operating-model/why-introduction",component:d("/catenax-ev.github.io.new/docs/next/operating-model/why-introduction","08e"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/next/operating-model/why-understanding-the-catena-x-data-space",component:d("/catenax-ev.github.io.new/docs/next/operating-model/why-understanding-the-catena-x-data-space","e90"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/next/standards/overview",component:d("/catenax-ev.github.io.new/docs/next/standards/overview","395"),exact:!0,sidebar:"sidebar_standards"},{path:"/catenax-ev.github.io.new/docs/next/working-model/ecosystem",component:d("/catenax-ev.github.io.new/docs/next/working-model/ecosystem","552"),exact:!0,sidebar:"sidebar_working_model"},{path:"/catenax-ev.github.io.new/docs/next/working-model/glossary",component:d("/catenax-ev.github.io.new/docs/next/working-model/glossary","6ae"),exact:!0,sidebar:"sidebar_working_model"},{path:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure",component:d("/catenax-ev.github.io.new/docs/next/working-model/organizational-structure","602"),exact:!0,sidebar:"sidebar_working_model"},{path:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/02-03-tooling",component:d("/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/02-03-tooling","8d8"),exact:!0,sidebar:"sidebar_working_model"},{path:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles",component:d("/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles","245"),exact:!0,sidebar:"sidebar_working_model"},{path:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles",component:d("/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles","142"),exact:!0,sidebar:"sidebar_working_model"},{path:"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles",component:d("/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles","222"),exact:!0,sidebar:"sidebar_working_model"},{path:"/catenax-ev.github.io.new/docs/next/working-model/overview",component:d("/catenax-ev.github.io.new/docs/next/working-model/overview","57c"),exact:!0,sidebar:"sidebar_working_model"},{path:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production",component:d("/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production","3cf"),exact:!0,sidebar:"sidebar_working_model"},{path:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-02-Contribution-Guideline",component:d("/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-02-Contribution-Guideline","557"),exact:!0,sidebar:"sidebar_working_model"},{path:"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-04-Issue-Process",component:d("/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-04-Issue-Process","034"),exact:!0,sidebar:"sidebar_working_model"}]}]},{path:"/catenax-ev.github.io.new/docs",component:d("/catenax-ev.github.io.new/docs","2e8"),routes:[{path:"/catenax-ev.github.io.new/docs",component:d("/catenax-ev.github.io.new/docs","0dd"),routes:[{path:"/catenax-ev.github.io.new/docs/operating-model/appendix",component:d("/catenax-ev.github.io.new/docs/operating-model/appendix","406"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/operating-model/change-log",component:d("/catenax-ev.github.io.new/docs/operating-model/change-log","8dc"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/operating-model/glossary",component:d("/catenax-ev.github.io.new/docs/operating-model/glossary","0b2"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance",component:d("/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance","456"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/operating-model/how-data-space-operations",component:d("/catenax-ev.github.io.new/docs/operating-model/how-data-space-operations","dc0"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/operating-model/how-life-cycle-management",component:d("/catenax-ev.github.io.new/docs/operating-model/how-life-cycle-management","b97"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/operating-model/operating-model",component:d("/catenax-ev.github.io.new/docs/operating-model/operating-model","9ed"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/operating-model/outlook",component:d("/catenax-ev.github.io.new/docs/operating-model/outlook","8d9"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/operating-model/what-service-map",component:d("/catenax-ev.github.io.new/docs/operating-model/what-service-map","d71"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/operating-model/who-roles-in-the-catena-x-ecosystem",component:d("/catenax-ev.github.io.new/docs/operating-model/who-roles-in-the-catena-x-ecosystem","9ef"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/operating-model/why-introduction",component:d("/catenax-ev.github.io.new/docs/operating-model/why-introduction","ae1"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/operating-model/why-understanding-the-catena-x-data-space",component:d("/catenax-ev.github.io.new/docs/operating-model/why-understanding-the-catena-x-data-space","5fa"),exact:!0,sidebar:"sidebar_op_model"},{path:"/catenax-ev.github.io.new/docs/standards/overview",component:d("/catenax-ev.github.io.new/docs/standards/overview","fca"),exact:!0,sidebar:"sidebar_standards"},{path:"/catenax-ev.github.io.new/docs/working-model/overview",component:d("/catenax-ev.github.io.new/docs/working-model/overview","798"),exact:!0,sidebar:"sidebar_working_model"}]}]}]},{path:"/catenax-ev.github.io.new/",component:d("/catenax-ev.github.io.new/","f28"),exact:!0},{path:"*",component:d("*")}]},6125:(e,t,n)=>{"use strict";n.d(t,{o:()=>a,x:()=>i});var r=n(6540),o=n(4848);const a=r.createContext(!1);function i(e){let{children:t}=e;const[n,i]=(0,r.useState)(!1);return(0,r.useEffect)((()=>{i(!0)}),[]),(0,o.jsx)(a.Provider,{value:n,children:t})}},8536:(e,t,n)=>{"use strict";var r=n(6540),o=n(5338),a=n(545),i=n(4625),l=n(4784),s=n(8193);const c=[n(119),n(6134),n(6294),n(1043),n(3796)];var u=n(8328),d=n(6347),p=n(2831),f=n(4848);function h(e){let{children:t}=e;return(0,f.jsx)(f.Fragment,{children:t})}var m=n(5260),g=n(4586),b=n(6025),y=n(6342),v=n(1213),w=n(2131),x=n(4090),k=n(2967),S=n(440),_=n(1463);function E(){const{i18n:{currentLocale:e,defaultLocale:t,localeConfigs:n}}=(0,g.A)(),r=(0,w.o)(),o=n[e].htmlLang,a=e=>e.replace("-","_");return(0,f.jsxs)(m.A,{children:[Object.entries(n).map((e=>{let[t,{htmlLang:n}]=e;return(0,f.jsx)("link",{rel:"alternate",href:r.createUrl({locale:t,fullyQualified:!0}),hrefLang:n},t)})),(0,f.jsx)("link",{rel:"alternate",href:r.createUrl({locale:t,fullyQualified:!0}),hrefLang:"x-default"}),(0,f.jsx)("meta",{property:"og:locale",content:a(o)}),Object.values(n).filter((e=>o!==e.htmlLang)).map((e=>(0,f.jsx)("meta",{property:"og:locale:alternate",content:a(e.htmlLang)},`meta-og-${e.htmlLang}`)))]})}function C(e){let{permalink:t}=e;const{siteConfig:{url:n}}=(0,g.A)(),r=function(){const{siteConfig:{url:e,baseUrl:t,trailingSlash:n}}=(0,g.A)(),{pathname:r}=(0,d.zy)();return e+(0,S.applyTrailingSlash)((0,b.Ay)(r),{trailingSlash:n,baseUrl:t})}(),o=t?`${n}${t}`:r;return(0,f.jsxs)(m.A,{children:[(0,f.jsx)("meta",{property:"og:url",content:o}),(0,f.jsx)("link",{rel:"canonical",href:o})]})}function T(){const{i18n:{currentLocale:e}}=(0,g.A)(),{metadata:t,image:n}=(0,y.p)();return(0,f.jsxs)(f.Fragment,{children:[(0,f.jsxs)(m.A,{children:[(0,f.jsx)("meta",{name:"twitter:card",content:"summary_large_image"}),(0,f.jsx)("body",{className:x.w})]}),n&&(0,f.jsx)(v.be,{image:n}),(0,f.jsx)(C,{}),(0,f.jsx)(E,{}),(0,f.jsx)(_.A,{tag:k.Cy,locale:e}),(0,f.jsx)(m.A,{children:t.map(((e,t)=>(0,f.jsx)("meta",{...e},t)))})]})}const A=new Map;var L=n(6125),j=n(6988),P=n(205);function R(e){for(var t=arguments.length,n=new Array(t>1?t-1:0),r=1;r{const r=t.default?.[e]??t[e];return r?.(...n)}));return()=>o.forEach((e=>e?.()))}const N=function(e){let{children:t,location:n,previousLocation:r}=e;return(0,P.A)((()=>{r!==n&&(!function(e){let{location:t,previousLocation:n}=e;if(!n)return;const r=t.pathname===n.pathname,o=t.hash===n.hash,a=t.search===n.search;if(r&&o&&!a)return;const{hash:i}=t;if(i){const e=decodeURIComponent(i.substring(1)),t=document.getElementById(e);t?.scrollIntoView()}else window.scrollTo(0,0)}({location:n,previousLocation:r}),R("onRouteDidUpdate",{previousLocation:r,location:n}))}),[r,n]),t};function O(e){const t=Array.from(new Set([e,decodeURI(e)])).map((e=>(0,p.u)(u.A,e))).flat();return Promise.all(t.map((e=>e.route.component.preload?.())))}class I extends r.Component{previousLocation;routeUpdateCleanupCb;constructor(e){super(e),this.previousLocation=null,this.routeUpdateCleanupCb=s.A.canUseDOM?R("onRouteUpdate",{previousLocation:null,location:this.props.location}):()=>{},this.state={nextRouteHasLoaded:!0}}shouldComponentUpdate(e,t){if(e.location===this.props.location)return t.nextRouteHasLoaded;const n=e.location;return this.previousLocation=this.props.location,this.setState({nextRouteHasLoaded:!1}),this.routeUpdateCleanupCb=R("onRouteUpdate",{previousLocation:this.previousLocation,location:n}),O(n.pathname).then((()=>{this.routeUpdateCleanupCb(),this.setState({nextRouteHasLoaded:!0})})).catch((e=>{console.warn(e),window.location.reload()})),!1}render(){const{children:e,location:t}=this.props;return(0,f.jsx)(N,{previousLocation:this.previousLocation,location:t,children:(0,f.jsx)(d.qh,{location:t,render:()=>e})})}}const D=I,z="__docusaurus-base-url-issue-banner-container",F="__docusaurus-base-url-issue-banner",M="__docusaurus-base-url-issue-banner-suggestion-container";function B(e){return`\ndocument.addEventListener('DOMContentLoaded', function maybeInsertBanner() {\n var shouldInsert = typeof window['docusaurus'] === 'undefined';\n shouldInsert && insertBanner();\n});\n\nfunction insertBanner() {\n var bannerContainer = document.createElement('div');\n bannerContainer.id = '${z}';\n var bannerHtml = ${JSON.stringify(function(e){return`\n
\n

Your Docusaurus site did not load properly.

\n

A very common reason is a wrong site baseUrl configuration.

\n

Current configured baseUrl = ${e} ${"/"===e?" (default value)":""}

\n

We suggest trying baseUrl =

\n
\n`}(e)).replace(/{let{route:t}=e;return!0===t.exact})))return A.set(e.pathname,e.pathname),e;const t=e.pathname.trim().replace(/(?:\/index)?\.html$/,"")||"/";return A.set(e.pathname,t),{...e,pathname:t}}((0,d.zy)());return(0,f.jsx)(D,{location:e,children:W})}function K(){return(0,f.jsx)(q.A,{children:(0,f.jsx)(j.l,{children:(0,f.jsxs)(L.x,{children:[(0,f.jsxs)(h,{children:[(0,f.jsx)(H,{}),(0,f.jsx)(T,{}),(0,f.jsx)(U,{}),(0,f.jsx)(G,{})]}),(0,f.jsx)(V,{})]})})})}var Y=n(4054);const Z=function(e){try{return document.createElement("link").relList.supports(e)}catch{return!1}}("prefetch")?function(e){return new Promise(((t,n)=>{if("undefined"==typeof document)return void n();const r=document.createElement("link");r.setAttribute("rel","prefetch"),r.setAttribute("href",e),r.onload=()=>t(),r.onerror=()=>n();const o=document.getElementsByTagName("head")[0]??document.getElementsByName("script")[0]?.parentNode;o?.appendChild(r)}))}:function(e){return new Promise(((t,n)=>{const r=new XMLHttpRequest;r.open("GET",e,!0),r.withCredentials=!0,r.onload=()=>{200===r.status?t():n()},r.send(null)}))};var X=n(6921);const J=new Set,ee=new Set,te=()=>navigator.connection?.effectiveType.includes("2g")||navigator.connection?.saveData,ne={prefetch:e=>{if(!(e=>!te()&&!ee.has(e)&&!J.has(e))(e))return!1;J.add(e);const t=(0,p.u)(u.A,e).flatMap((e=>{return t=e.route.path,Object.entries(Y).filter((e=>{let[n]=e;return n.replace(/-[^-]+$/,"")===t})).flatMap((e=>{let[,t]=e;return Object.values((0,X.A)(t))}));var t}));return Promise.all(t.map((e=>{const t=n.gca(e);return t&&!t.includes("undefined")?Z(t).catch((()=>{})):Promise.resolve()})))},preload:e=>!!(e=>!te()&&!ee.has(e))(e)&&(ee.add(e),O(e))},re=Object.freeze(ne);function oe(e){let{children:t}=e;return"hash"===l.default.future.experimental_router?(0,f.jsx)(i.I9,{children:t}):(0,f.jsx)(i.Kd,{children:t})}const ae=Boolean(!0);if(s.A.canUseDOM){window.docusaurus=re;const e=document.getElementById("__docusaurus"),t=(0,f.jsx)(a.vd,{children:(0,f.jsx)(oe,{children:(0,f.jsx)(K,{})})}),n=(e,t)=>{console.error("Docusaurus React Root onRecoverableError:",e,t)},i=()=>{if(window.docusaurusRoot)window.docusaurusRoot.render(t);else if(ae)window.docusaurusRoot=o.hydrateRoot(e,t,{onRecoverableError:n});else{const r=o.createRoot(e,{onRecoverableError:n});r.render(t),window.docusaurusRoot=r}};O(window.location.pathname).then((()=>{(0,r.startTransition)(i)}))}},6988:(e,t,n)=>{"use strict";n.d(t,{o:()=>d,l:()=>p});var r=n(6540),o=n(4784);const a=JSON.parse('{"docusaurus-plugin-content-docs":{"default":{"path":"/catenax-ev.github.io.new/docs","versions":[{"name":"current","label":"Next","isLast":false,"path":"/catenax-ev.github.io.new/docs/next","mainDocId":"standards/overview","docs":[{"id":"operating-model/appendix/appendix","path":"/catenax-ev.github.io.new/docs/next/operating-model/appendix/","sidebar":"sidebar_op_model"},{"id":"operating-model/change-log/change-log","path":"/catenax-ev.github.io.new/docs/next/operating-model/change-log/","sidebar":"sidebar_op_model"},{"id":"operating-model/glossary/glossary","path":"/catenax-ev.github.io.new/docs/next/operating-model/glossary/","sidebar":"sidebar_op_model"},{"id":"operating-model/how-data-space-governance/how-data-space-governance","path":"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-governance/","sidebar":"sidebar_op_model"},{"id":"operating-model/how-data-space-operations/how-data-space-operations","path":"/catenax-ev.github.io.new/docs/next/operating-model/how-data-space-operations/","sidebar":"sidebar_op_model"},{"id":"operating-model/how-life-cycle-management/how-life-cycle-management","path":"/catenax-ev.github.io.new/docs/next/operating-model/how-life-cycle-management/","sidebar":"sidebar_op_model"},{"id":"operating-model/operating-model/operating-model","path":"/catenax-ev.github.io.new/docs/next/operating-model/operating-model/","sidebar":"sidebar_op_model"},{"id":"operating-model/outlook/outlook","path":"/catenax-ev.github.io.new/docs/next/operating-model/outlook/","sidebar":"sidebar_op_model"},{"id":"operating-model/what-service-map/what-service-map","path":"/catenax-ev.github.io.new/docs/next/operating-model/what-service-map/","sidebar":"sidebar_op_model"},{"id":"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem","path":"/catenax-ev.github.io.new/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/","sidebar":"sidebar_op_model"},{"id":"operating-model/why-introduction/why-introduction","path":"/catenax-ev.github.io.new/docs/next/operating-model/why-introduction/","sidebar":"sidebar_op_model"},{"id":"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space","path":"/catenax-ev.github.io.new/docs/next/operating-model/why-understanding-the-catena-x-data-space/","sidebar":"sidebar_op_model"},{"id":"standards/overview","path":"/catenax-ev.github.io.new/docs/next/standards/overview","sidebar":"sidebar_standards"},{"id":"working-model/ecosystem/ecosystem","path":"/catenax-ev.github.io.new/docs/next/working-model/ecosystem/","sidebar":"sidebar_working_model"},{"id":"working-model/glossary","path":"/catenax-ev.github.io.new/docs/next/working-model/glossary","sidebar":"sidebar_working_model"},{"id":"working-model/organizational-structure/02-03-tooling","path":"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/02-03-tooling","sidebar":"sidebar_working_model"},{"id":"working-model/organizational-structure/organizational-structure","path":"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/","sidebar":"sidebar_working_model"},{"id":"working-model/organizational-structure/overview-roles/catena-x-roles","path":"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/catena-x-roles","sidebar":"sidebar_working_model"},{"id":"working-model/organizational-structure/overview-roles/overview-roles","path":"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/","sidebar":"sidebar_working_model"},{"id":"working-model/organizational-structure/overview-roles/tractus-x-roles","path":"/catenax-ev.github.io.new/docs/next/working-model/organizational-structure/overview-roles/tractus-x-roles","sidebar":"sidebar_working_model"},{"id":"working-model/overview","path":"/catenax-ev.github.io.new/docs/next/working-model/overview","sidebar":"sidebar_working_model"},{"id":"working-model/process-from-idea-to-production/03-01-process-from-idea-to-production","path":"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-01-process-from-idea-to-production","sidebar":"sidebar_working_model"},{"id":"working-model/process-from-idea-to-production/03-02-Contribution-Guideline","path":"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-02-Contribution-Guideline","sidebar":"sidebar_working_model"},{"id":"working-model/process-from-idea-to-production/03-04-Issue-Process","path":"/catenax-ev.github.io.new/docs/next/working-model/process-from-idea-to-production/03-04-Issue-Process","sidebar":"sidebar_working_model"}],"draftIds":[],"sidebars":{"sidebar_standards":{"link":{"path":"/catenax-ev.github.io.new/docs/next/standards/overview","label":"standards/overview"}},"sidebar_op_model":{"link":{"path":"/catenax-ev.github.io.new/docs/next/operating-model/operating-model/","label":"Operating Model"}},"sidebar_working_model":{"link":{"path":"/catenax-ev.github.io.new/docs/next/working-model/overview","label":"working-model/overview"}}}},{"name":"24.03","label":"24.03","isLast":true,"path":"/catenax-ev.github.io.new/docs","mainDocId":"standards/overview","docs":[{"id":"operating-model/appendix/appendix","path":"/catenax-ev.github.io.new/docs/operating-model/appendix/","sidebar":"sidebar_op_model"},{"id":"operating-model/change-log/change-log","path":"/catenax-ev.github.io.new/docs/operating-model/change-log/","sidebar":"sidebar_op_model"},{"id":"operating-model/glossary/glossary","path":"/catenax-ev.github.io.new/docs/operating-model/glossary/","sidebar":"sidebar_op_model"},{"id":"operating-model/how-data-space-governance/how-data-space-governance","path":"/catenax-ev.github.io.new/docs/operating-model/how-data-space-governance/","sidebar":"sidebar_op_model"},{"id":"operating-model/how-data-space-operations/how-data-space-operations","path":"/catenax-ev.github.io.new/docs/operating-model/how-data-space-operations/","sidebar":"sidebar_op_model"},{"id":"operating-model/how-life-cycle-management/how-life-cycle-management","path":"/catenax-ev.github.io.new/docs/operating-model/how-life-cycle-management/","sidebar":"sidebar_op_model"},{"id":"operating-model/operating-model/operating-model","path":"/catenax-ev.github.io.new/docs/operating-model/operating-model/","sidebar":"sidebar_op_model"},{"id":"operating-model/outlook/outlook","path":"/catenax-ev.github.io.new/docs/operating-model/outlook/","sidebar":"sidebar_op_model"},{"id":"operating-model/what-service-map/what-service-map","path":"/catenax-ev.github.io.new/docs/operating-model/what-service-map/","sidebar":"sidebar_op_model"},{"id":"operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem","path":"/catenax-ev.github.io.new/docs/operating-model/who-roles-in-the-catena-x-ecosystem/","sidebar":"sidebar_op_model"},{"id":"operating-model/why-introduction/why-introduction","path":"/catenax-ev.github.io.new/docs/operating-model/why-introduction/","sidebar":"sidebar_op_model"},{"id":"operating-model/why-understanding-the-catena-x-data-space/why-understanding-the-catena-x-data-space","path":"/catenax-ev.github.io.new/docs/operating-model/why-understanding-the-catena-x-data-space/","sidebar":"sidebar_op_model"},{"id":"standards/overview","path":"/catenax-ev.github.io.new/docs/standards/overview","sidebar":"sidebar_standards"},{"id":"working-model/overview","path":"/catenax-ev.github.io.new/docs/working-model/overview","sidebar":"sidebar_working_model"}],"draftIds":[],"sidebars":{"sidebar_standards":{"link":{"path":"/catenax-ev.github.io.new/docs/standards/overview","label":"standards/overview"}},"sidebar_op_model":{"link":{"path":"/catenax-ev.github.io.new/docs/operating-model/operating-model/","label":"Operating Model"}},"sidebar_working_model":{"link":{"path":"/catenax-ev.github.io.new/docs/working-model/overview","label":"working-model/overview"}}}}],"breadcrumbs":true}}}'),i=JSON.parse('{"defaultLocale":"en","locales":["en"],"path":"i18n","currentLocale":"en","localeConfigs":{"en":{"label":"English","direction":"ltr","htmlLang":"en","calendar":"gregory","path":"en"}}}');var l=n(2654);const s=JSON.parse('{"docusaurusVersion":"3.4.0","siteVersion":"0.0.0","pluginVersions":{"docusaurus-plugin-content-docs":{"type":"package","name":"@docusaurus/plugin-content-docs","version":"3.4.0"},"docusaurus-plugin-content-blog":{"type":"package","name":"@docusaurus/plugin-content-blog","version":"3.4.0"},"docusaurus-plugin-content-pages":{"type":"package","name":"@docusaurus/plugin-content-pages","version":"3.4.0"},"docusaurus-plugin-sitemap":{"type":"package","name":"@docusaurus/plugin-sitemap","version":"3.4.0"},"docusaurus-theme-classic":{"type":"package","name":"@docusaurus/theme-classic","version":"3.4.0"},"docusaurus-plugin-image-zoom":{"type":"package","name":"docusaurus-plugin-image-zoom","version":"2.0.0"},"@easyops-cn/docusaurus-search-local":{"type":"package","name":"@easyops-cn/docusaurus-search-local","version":"0.44.0"}}}');var c=n(4848);const u={siteConfig:o.default,siteMetadata:s,globalData:a,i18n:i,codeTranslations:l},d=r.createContext(u);function p(e){let{children:t}=e;return(0,c.jsx)(d.Provider,{value:u,children:t})}},7489:(e,t,n)=>{"use strict";n.d(t,{A:()=>m});var r=n(6540),o=n(8193),a=n(5260),i=n(440),l=n(5476),s=n(3102),c=n(4848);function u(e){let{error:t,tryAgain:n}=e;return(0,c.jsxs)("div",{style:{display:"flex",flexDirection:"column",justifyContent:"center",alignItems:"flex-start",minHeight:"100vh",width:"100%",maxWidth:"80ch",fontSize:"20px",margin:"0 auto",padding:"1rem"},children:[(0,c.jsx)("h1",{style:{fontSize:"3rem"},children:"This page crashed"}),(0,c.jsx)("button",{type:"button",onClick:n,style:{margin:"1rem 0",fontSize:"2rem",cursor:"pointer",borderRadius:20,padding:"1rem"},children:"Try again"}),(0,c.jsx)(d,{error:t})]})}function d(e){let{error:t}=e;const n=(0,i.getErrorCausalChain)(t).map((e=>e.message)).join("\n\nCause:\n");return(0,c.jsx)("p",{style:{whiteSpace:"pre-wrap"},children:n})}function p(e){let{children:t}=e;return(0,c.jsx)(s.W,{value:{plugin:{name:"docusaurus-core-error-boundary",id:"default"}},children:t})}function f(e){let{error:t,tryAgain:n}=e;return(0,c.jsx)(p,{children:(0,c.jsxs)(m,{fallback:()=>(0,c.jsx)(u,{error:t,tryAgain:n}),children:[(0,c.jsx)(a.A,{children:(0,c.jsx)("title",{children:"Page Error"})}),(0,c.jsx)(l.A,{children:(0,c.jsx)(u,{error:t,tryAgain:n})})]})})}const h=e=>(0,c.jsx)(f,{...e});class m extends r.Component{constructor(e){super(e),this.state={error:null}}componentDidCatch(e){o.A.canUseDOM&&this.setState({error:e})}render(){const{children:e}=this.props,{error:t}=this.state;if(t){const e={error:t,tryAgain:()=>this.setState({error:null})};return(this.props.fallback??h)(e)}return e??null}}},8193:(e,t,n)=>{"use strict";n.d(t,{A:()=>o});const r="undefined"!=typeof window&&"document"in window&&"createElement"in window.document,o={canUseDOM:r,canUseEventListeners:r&&("addEventListener"in window||"attachEvent"in window),canUseIntersectionObserver:r&&"IntersectionObserver"in window,canUseViewport:r&&"screen"in window}},5260:(e,t,n)=>{"use strict";n.d(t,{A:()=>a});n(6540);var r=n(545),o=n(4848);function a(e){return(0,o.jsx)(r.mg,{...e})}},8774:(e,t,n)=>{"use strict";n.d(t,{A:()=>f});var r=n(6540),o=n(4625),a=n(440),i=n(4586),l=n(6654),s=n(8193),c=n(3427),u=n(6025),d=n(4848);function p(e,t){let{isNavLink:n,to:p,href:f,activeClassName:h,isActive:m,"data-noBrokenLinkCheck":g,autoAddBaseUrl:b=!0,...y}=e;const{siteConfig:v}=(0,i.A)(),{trailingSlash:w,baseUrl:x}=v,k=v.future.experimental_router,{withBaseUrl:S}=(0,u.hH)(),_=(0,c.A)(),E=(0,r.useRef)(null);(0,r.useImperativeHandle)(t,(()=>E.current));const C=p||f;const T=(0,l.A)(C),A=C?.replace("pathname://","");let L=void 0!==A?(j=A,b&&(e=>e.startsWith("/"))(j)?S(j):j):void 0;var j;"hash"===k&&L?.startsWith("./")&&(L=L?.slice(1)),L&&T&&(L=(0,a.applyTrailingSlash)(L,{trailingSlash:w,baseUrl:x}));const P=(0,r.useRef)(!1),R=n?o.k2:o.N_,N=s.A.canUseIntersectionObserver,O=(0,r.useRef)(),I=()=>{P.current||null==L||(window.docusaurus.preload(L),P.current=!0)};(0,r.useEffect)((()=>(!N&&T&&null!=L&&window.docusaurus.prefetch(L),()=>{N&&O.current&&O.current.disconnect()})),[O,L,N,T]);const D=L?.startsWith("#")??!1,z=!y.target||"_self"===y.target,F=!L||!T||!z;return g||!D&&F||_.collectLink(L),y.id&&_.collectAnchor(y.id),F?(0,d.jsx)("a",{ref:E,href:L,...C&&!T&&{target:"_blank",rel:"noopener noreferrer"},...y}):(0,d.jsx)(R,{...y,onMouseEnter:I,onTouchStart:I,innerRef:e=>{E.current=e,N&&e&&T&&(O.current=new window.IntersectionObserver((t=>{t.forEach((t=>{e===t.target&&(t.isIntersecting||t.intersectionRatio>0)&&(O.current.unobserve(e),O.current.disconnect(),null!=L&&window.docusaurus.prefetch(L))}))})),O.current.observe(e))},to:L,...n&&{isActive:m,activeClassName:h}})}const f=r.forwardRef(p)},1312:(e,t,n)=>{"use strict";n.d(t,{A:()=>c,T:()=>s});var r=n(6540),o=n(4848);function a(e,t){const n=e.split(/(\{\w+\})/).map(((e,n)=>{if(n%2==1){const n=t?.[e.slice(1,-1)];if(void 0!==n)return n}return e}));return n.some((e=>(0,r.isValidElement)(e)))?n.map(((e,t)=>(0,r.isValidElement)(e)?r.cloneElement(e,{key:t}):e)).filter((e=>""!==e)):n.join("")}var i=n(2654);function l(e){let{id:t,message:n}=e;if(void 0===t&&void 0===n)throw new Error("Docusaurus translation declarations must have at least a translation id or a default translation message");return i[t??n]??n??t}function s(e,t){let{message:n,id:r}=e;return a(l({message:n,id:r}),t)}function c(e){let{children:t,id:n,values:r}=e;if(t&&"string"!=typeof t)throw console.warn("Illegal children",t),new Error("The Docusaurus component only accept simple string values");const i=l({message:t,id:n});return(0,o.jsx)(o.Fragment,{children:a(i,r)})}},7065:(e,t,n)=>{"use strict";n.d(t,{W:()=>r});const r="default"},6654:(e,t,n)=>{"use strict";function r(e){return/^(?:\w*:|\/\/)/.test(e)}function o(e){return void 0!==e&&!r(e)}n.d(t,{A:()=>o,z:()=>r})},6025:(e,t,n)=>{"use strict";n.d(t,{Ay:()=>l,hH:()=>i});var r=n(6540),o=n(4586),a=n(6654);function i(){const{siteConfig:e}=(0,o.A)(),{baseUrl:t,url:n}=e,i=e.future.experimental_router,l=(0,r.useCallback)(((e,r)=>function(e){let{siteUrl:t,baseUrl:n,url:r,options:{forcePrependBaseUrl:o=!1,absolute:i=!1}={},router:l}=e;if(!r||r.startsWith("#")||(0,a.z)(r))return r;if("hash"===l)return r.startsWith("/")?`.${r}`:`./${r}`;if(o)return n+r.replace(/^\//,"");if(r===n.replace(/\/$/,""))return n;const s=r.startsWith(n)?r:n+r.replace(/^\//,"");return i?t+s:s}({siteUrl:n,baseUrl:t,url:e,options:r,router:i})),[n,t,i]);return{withBaseUrl:l}}function l(e,t){void 0===t&&(t={});const{withBaseUrl:n}=i();return n(e,t)}},3427:(e,t,n)=>{"use strict";n.d(t,{A:()=>i});var r=n(6540);n(4848);const o=r.createContext({collectAnchor:()=>{},collectLink:()=>{}}),a=()=>(0,r.useContext)(o);function i(){return a()}},4586:(e,t,n)=>{"use strict";n.d(t,{A:()=>a});var r=n(6540),o=n(6988);function a(){return(0,r.useContext)(o.o)}},2303:(e,t,n)=>{"use strict";n.d(t,{A:()=>a});var r=n(6540),o=n(6125);function a(){return(0,r.useContext)(o.o)}},205:(e,t,n)=>{"use strict";n.d(t,{A:()=>o});var r=n(6540);const o=n(8193).A.canUseDOM?r.useLayoutEffect:r.useEffect},6803:(e,t,n)=>{"use strict";n.d(t,{A:()=>a});var r=n(6540),o=n(3102);function a(){const e=r.useContext(o.o);if(!e)throw new Error("Unexpected: no Docusaurus route context found");return e}},6921:(e,t,n)=>{"use strict";n.d(t,{A:()=>o});const r=e=>"object"==typeof e&&!!e&&Object.keys(e).length>0;function o(e){const t={};return function e(n,o){Object.entries(n).forEach((n=>{let[a,i]=n;const l=o?`${o}.${a}`:a;r(i)?e(i,l):t[l]=i}))}(e),t}},3102:(e,t,n)=>{"use strict";n.d(t,{W:()=>i,o:()=>a});var r=n(6540),o=n(4848);const a=r.createContext(null);function i(e){let{children:t,value:n}=e;const i=r.useContext(a),l=(0,r.useMemo)((()=>function(e){let{parent:t,value:n}=e;if(!t){if(!n)throw new Error("Unexpected: no Docusaurus route context found");if(!("plugin"in n))throw new Error("Unexpected: Docusaurus topmost route context has no `plugin` attribute");return n}const r={...t.data,...n?.data};return{plugin:t.plugin,data:r}}({parent:i,value:n})),[i,n]);return(0,o.jsx)(a.Provider,{value:l,children:t})}},4070:(e,t,n)=>{"use strict";n.d(t,{zK:()=>m,vT:()=>p,Gy:()=>u,HW:()=>g,ht:()=>d,r7:()=>h,jh:()=>f});var r=n(6347),o=n(4586),a=n(7065);function i(e,t){void 0===t&&(t={});const n=function(){const{globalData:e}=(0,o.A)();return e}()[e];if(!n&&t.failfast)throw new Error(`Docusaurus plugin global data not found for "${e}" plugin.`);return n}const l=e=>e.versions.find((e=>e.isLast));function s(e,t){const n=function(e,t){const n=l(e);return[...e.versions.filter((e=>e!==n)),n].find((e=>!!(0,r.B6)(t,{path:e.path,exact:!1,strict:!1})))}(e,t),o=n?.docs.find((e=>!!(0,r.B6)(t,{path:e.path,exact:!0,strict:!1})));return{activeVersion:n,activeDoc:o,alternateDocVersions:o?function(t){const n={};return e.versions.forEach((e=>{e.docs.forEach((r=>{r.id===t&&(n[e.name]=r)}))})),n}(o.id):{}}}const c={},u=()=>i("docusaurus-plugin-content-docs")??c,d=e=>{try{return function(e,t,n){void 0===t&&(t=a.W),void 0===n&&(n={});const r=i(e),o=r?.[t];if(!o&&n.failfast)throw new Error(`Docusaurus plugin global data not found for "${e}" plugin with id "${t}".`);return o}("docusaurus-plugin-content-docs",e,{failfast:!0})}catch(t){throw new Error("You are using a feature of the Docusaurus docs plugin, but this plugin does not seem to be enabled"+("Default"===e?"":` (pluginId=${e}`),{cause:t})}};function p(e){void 0===e&&(e={});const t=u(),{pathname:n}=(0,r.zy)();return function(e,t,n){void 0===n&&(n={});const o=Object.entries(e).sort(((e,t)=>t[1].path.localeCompare(e[1].path))).find((e=>{let[,n]=e;return!!(0,r.B6)(t,{path:n.path,exact:!1,strict:!1})})),a=o?{pluginId:o[0],pluginData:o[1]}:void 0;if(!a&&n.failfast)throw new Error(`Can't find active docs plugin for "${t}" pathname, while it was expected to be found. Maybe you tried to use a docs feature that can only be used on a docs-related page? Existing docs plugin paths are: ${Object.values(e).map((e=>e.path)).join(", ")}`);return a}(t,n,e)}function f(e){return d(e).versions}function h(e){const t=d(e);return l(t)}function m(e){const t=d(e),{pathname:n}=(0,r.zy)();return s(t,n)}function g(e){const t=d(e),{pathname:n}=(0,r.zy)();return function(e,t){const n=l(e);return{latestDocSuggestion:s(e,t).alternateDocVersions[n.name],latestVersionSuggestion:n}}(t,n)}},6294:(e,t,n)=>{"use strict";n.r(t),n.d(t,{default:()=>a});var r=n(5947),o=n.n(r);o().configure({showSpinner:!1});const a={onRouteUpdate(e){let{location:t,previousLocation:n}=e;if(n&&t.pathname!==n.pathname){const e=window.setTimeout((()=>{o().start()}),200);return()=>window.clearTimeout(e)}},onRouteDidUpdate(){o().done()}}},6134:(e,t,n)=>{"use strict";n.r(t);var r=n(1765),o=n(4784);!function(e){const{themeConfig:{prism:t}}=o.default,{additionalLanguages:r}=t;globalThis.Prism=e,r.forEach((e=>{"php"===e&&n(9700),n(8692)(`./prism-${e}`)})),delete globalThis.Prism}(r.My)},1107:(e,t,n)=>{"use strict";n.d(t,{A:()=>u});n(6540);var r=n(4164),o=n(1312),a=n(6342),i=n(8774),l=n(3427);const s={anchorWithStickyNavbar:"anchorWithStickyNavbar_LWe7",anchorWithHideOnScrollNavbar:"anchorWithHideOnScrollNavbar_WYt5"};var c=n(4848);function u(e){let{as:t,id:n,...u}=e;const d=(0,l.A)(),{navbar:{hideOnScroll:p}}=(0,a.p)();if("h1"===t||!n)return(0,c.jsx)(t,{...u,id:void 0});d.collectAnchor(n);const f=(0,o.T)({id:"theme.common.headingLinkTitle",message:"Direct link to {heading}",description:"Title for link to heading"},{heading:"string"==typeof u.children?u.children:n});return(0,c.jsxs)(t,{...u,className:(0,r.A)("anchor",p?s.anchorWithHideOnScrollNavbar:s.anchorWithStickyNavbar,u.className),id:n,children:[u.children,(0,c.jsx)(i.A,{className:"hash-link",to:`#${n}`,"aria-label":f,title:f,children:"\u200b"})]})}},3186:(e,t,n)=>{"use strict";n.d(t,{A:()=>a});n(6540);const r={iconExternalLink:"iconExternalLink_nPIU"};var o=n(4848);function a(e){let{width:t=13.5,height:n=13.5}=e;return(0,o.jsx)("svg",{width:t,height:n,"aria-hidden":"true",viewBox:"0 0 24 24",className:r.iconExternalLink,children:(0,o.jsx)("path",{fill:"currentColor",d:"M21 13v10h-21v-19h12v2h-10v15h17v-8h2zm3-12h-10.988l4.035 4-6.977 7.07 2.828 2.828 6.977-7.07 4.125 4.172v-11z"})})}},5476:(e,t,n)=>{"use strict";n.d(t,{A:()=>Dt});var r=n(6540),o=n(4164),a=n(7489),i=n(1213),l=n(6347),s=n(1312),c=n(5062),u=n(4848);const d="__docusaurus_skipToContent_fallback";function p(e){e.setAttribute("tabindex","-1"),e.focus(),e.removeAttribute("tabindex")}function f(){const e=(0,r.useRef)(null),{action:t}=(0,l.W6)(),n=(0,r.useCallback)((e=>{e.preventDefault();const t=document.querySelector("main:first-of-type")??document.getElementById(d);t&&p(t)}),[]);return(0,c.$)((n=>{let{location:r}=n;e.current&&!r.hash&&"PUSH"===t&&p(e.current)})),{containerRef:e,onClick:n}}const h=(0,s.T)({id:"theme.common.skipToMainContent",description:"The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation",message:"Skip to main content"});function m(e){const t=e.children??h,{containerRef:n,onClick:r}=f();return(0,u.jsx)("div",{ref:n,role:"region","aria-label":h,children:(0,u.jsx)("a",{...e,href:`#${d}`,onClick:r,children:t})})}var g=n(7559),b=n(4090);const y={skipToContent:"skipToContent_fXgn"};function v(){return(0,u.jsx)(m,{className:y.skipToContent})}var w=n(6342),x=n(5041);function k(e){let{width:t=21,height:n=21,color:r="currentColor",strokeWidth:o=1.2,className:a,...i}=e;return(0,u.jsx)("svg",{viewBox:"0 0 15 15",width:t,height:n,...i,children:(0,u.jsx)("g",{stroke:r,strokeWidth:o,children:(0,u.jsx)("path",{d:"M.75.75l13.5 13.5M14.25.75L.75 14.25"})})})}const S={closeButton:"closeButton_CVFx"};function _(e){return(0,u.jsx)("button",{type:"button","aria-label":(0,s.T)({id:"theme.AnnouncementBar.closeButtonAriaLabel",message:"Close",description:"The ARIA label for close button of announcement bar"}),...e,className:(0,o.A)("clean-btn close",S.closeButton,e.className),children:(0,u.jsx)(k,{width:14,height:14,strokeWidth:3.1})})}const E={content:"content_knG7"};function C(e){const{announcementBar:t}=(0,w.p)(),{content:n}=t;return(0,u.jsx)("div",{...e,className:(0,o.A)(E.content,e.className),dangerouslySetInnerHTML:{__html:n}})}const T={announcementBar:"announcementBar_mb4j",announcementBarPlaceholder:"announcementBarPlaceholder_vyr4",announcementBarClose:"announcementBarClose_gvF7",announcementBarContent:"announcementBarContent_xLdY"};function A(){const{announcementBar:e}=(0,w.p)(),{isActive:t,close:n}=(0,x.M)();if(!t)return null;const{backgroundColor:r,textColor:o,isCloseable:a}=e;return(0,u.jsxs)("div",{className:T.announcementBar,style:{backgroundColor:r,color:o},role:"banner",children:[a&&(0,u.jsx)("div",{className:T.announcementBarPlaceholder}),(0,u.jsx)(C,{className:T.announcementBarContent}),a&&(0,u.jsx)(_,{onClick:n,className:T.announcementBarClose})]})}var L=n(9876),j=n(3104);var P=n(9532),R=n(5600);const N=r.createContext(null);function O(e){let{children:t}=e;const n=function(){const e=(0,L.M)(),t=(0,R.YL)(),[n,o]=(0,r.useState)(!1),a=null!==t.component,i=(0,P.ZC)(a);return(0,r.useEffect)((()=>{a&&!i&&o(!0)}),[a,i]),(0,r.useEffect)((()=>{a?e.shown||o(!0):o(!1)}),[e.shown,a]),(0,r.useMemo)((()=>[n,o]),[n])}();return(0,u.jsx)(N.Provider,{value:n,children:t})}function I(e){if(e.component){const t=e.component;return(0,u.jsx)(t,{...e.props})}}function D(){const e=(0,r.useContext)(N);if(!e)throw new P.dV("NavbarSecondaryMenuDisplayProvider");const[t,n]=e,o=(0,r.useCallback)((()=>n(!1)),[n]),a=(0,R.YL)();return(0,r.useMemo)((()=>({shown:t,hide:o,content:I(a)})),[o,a,t])}function z(e){let{header:t,primaryMenu:n,secondaryMenu:r}=e;const{shown:a}=D();return(0,u.jsxs)("div",{className:"navbar-sidebar",children:[t,(0,u.jsxs)("div",{className:(0,o.A)("navbar-sidebar__items",{"navbar-sidebar__items--show-secondary":a}),children:[(0,u.jsx)("div",{className:"navbar-sidebar__item menu",children:n}),(0,u.jsx)("div",{className:"navbar-sidebar__item menu",children:r})]})]})}var F=n(5293),M=n(2303);function B(e){return(0,u.jsx)("svg",{viewBox:"0 0 24 24",width:24,height:24,...e,children:(0,u.jsx)("path",{fill:"currentColor",d:"M12,9c1.65,0,3,1.35,3,3s-1.35,3-3,3s-3-1.35-3-3S10.35,9,12,9 M12,7c-2.76,0-5,2.24-5,5s2.24,5,5,5s5-2.24,5-5 S14.76,7,12,7L12,7z M2,13l2,0c0.55,0,1-0.45,1-1s-0.45-1-1-1l-2,0c-0.55,0-1,0.45-1,1S1.45,13,2,13z M20,13l2,0c0.55,0,1-0.45,1-1 s-0.45-1-1-1l-2,0c-0.55,0-1,0.45-1,1S19.45,13,20,13z M11,2v2c0,0.55,0.45,1,1,1s1-0.45,1-1V2c0-0.55-0.45-1-1-1S11,1.45,11,2z M11,20v2c0,0.55,0.45,1,1,1s1-0.45,1-1v-2c0-0.55-0.45-1-1-1C11.45,19,11,19.45,11,20z M5.99,4.58c-0.39-0.39-1.03-0.39-1.41,0 c-0.39,0.39-0.39,1.03,0,1.41l1.06,1.06c0.39,0.39,1.03,0.39,1.41,0s0.39-1.03,0-1.41L5.99,4.58z M18.36,16.95 c-0.39-0.39-1.03-0.39-1.41,0c-0.39,0.39-0.39,1.03,0,1.41l1.06,1.06c0.39,0.39,1.03,0.39,1.41,0c0.39-0.39,0.39-1.03,0-1.41 L18.36,16.95z M19.42,5.99c0.39-0.39,0.39-1.03,0-1.41c-0.39-0.39-1.03-0.39-1.41,0l-1.06,1.06c-0.39,0.39-0.39,1.03,0,1.41 s1.03,0.39,1.41,0L19.42,5.99z M7.05,18.36c0.39-0.39,0.39-1.03,0-1.41c-0.39-0.39-1.03-0.39-1.41,0l-1.06,1.06 c-0.39,0.39-0.39,1.03,0,1.41s1.03,0.39,1.41,0L7.05,18.36z"})})}function $(e){return(0,u.jsx)("svg",{viewBox:"0 0 24 24",width:24,height:24,...e,children:(0,u.jsx)("path",{fill:"currentColor",d:"M9.37,5.51C9.19,6.15,9.1,6.82,9.1,7.5c0,4.08,3.32,7.4,7.4,7.4c0.68,0,1.35-0.09,1.99-0.27C17.45,17.19,14.93,19,12,19 c-3.86,0-7-3.14-7-7C5,9.07,6.81,6.55,9.37,5.51z M12,3c-4.97,0-9,4.03-9,9s4.03,9,9,9s9-4.03,9-9c0-0.46-0.04-0.92-0.1-1.36 c-0.98,1.37-2.58,2.26-4.4,2.26c-2.98,0-5.4-2.42-5.4-5.4c0-1.81,0.89-3.42,2.26-4.4C12.92,3.04,12.46,3,12,3L12,3z"})})}const U={toggle:"toggle_vylO",toggleButton:"toggleButton_gllP",darkToggleIcon:"darkToggleIcon_wfgR",lightToggleIcon:"lightToggleIcon_pyhR",toggleButtonDisabled:"toggleButtonDisabled_aARS"};function H(e){let{className:t,buttonClassName:n,value:r,onChange:a}=e;const i=(0,M.A)(),l=(0,s.T)({message:"Switch between dark and light mode (currently {mode})",id:"theme.colorToggle.ariaLabel",description:"The ARIA label for the navbar color mode toggle"},{mode:"dark"===r?(0,s.T)({message:"dark mode",id:"theme.colorToggle.ariaLabel.mode.dark",description:"The name for the dark color mode"}):(0,s.T)({message:"light mode",id:"theme.colorToggle.ariaLabel.mode.light",description:"The name for the light color mode"})});return(0,u.jsx)("div",{className:(0,o.A)(U.toggle,t),children:(0,u.jsxs)("button",{className:(0,o.A)("clean-btn",U.toggleButton,!i&&U.toggleButtonDisabled,n),type:"button",onClick:()=>a("dark"===r?"light":"dark"),disabled:!i,title:l,"aria-label":l,"aria-live":"polite",children:[(0,u.jsx)(B,{className:(0,o.A)(U.toggleIcon,U.lightToggleIcon)}),(0,u.jsx)($,{className:(0,o.A)(U.toggleIcon,U.darkToggleIcon)})]})})}const q=r.memo(H),Q={darkNavbarColorModeToggle:"darkNavbarColorModeToggle_X3D1"};function V(e){let{className:t}=e;const n=(0,w.p)().navbar.style,r=(0,w.p)().colorMode.disableSwitch,{colorMode:o,setColorMode:a}=(0,F.G)();return r?null:(0,u.jsx)(q,{className:t,buttonClassName:"dark"===n?Q.darkNavbarColorModeToggle:void 0,value:o,onChange:a})}var W=n(3465);function G(){return(0,u.jsx)(W.A,{className:"navbar__brand",imageClassName:"navbar__logo",titleClassName:"navbar__title text--truncate"})}function K(){const e=(0,L.M)();return(0,u.jsx)("button",{type:"button","aria-label":(0,s.T)({id:"theme.docs.sidebar.closeSidebarButtonAriaLabel",message:"Close navigation bar",description:"The ARIA label for close button of mobile sidebar"}),className:"clean-btn navbar-sidebar__close",onClick:()=>e.toggle(),children:(0,u.jsx)(k,{color:"var(--ifm-color-emphasis-600)"})})}function Y(){return(0,u.jsxs)("div",{className:"navbar-sidebar__brand",children:[(0,u.jsx)(G,{}),(0,u.jsx)(V,{className:"margin-right--md"}),(0,u.jsx)(K,{})]})}var Z=n(8774),X=n(6025),J=n(6654);function ee(e,t){return void 0!==e&&void 0!==t&&new RegExp(e,"gi").test(t)}var te=n(3186);function ne(e){let{activeBasePath:t,activeBaseRegex:n,to:r,href:o,label:a,html:i,isDropdownLink:l,prependBaseUrlToHref:s,...c}=e;const d=(0,X.Ay)(r),p=(0,X.Ay)(t),f=(0,X.Ay)(o,{forcePrependBaseUrl:!0}),h=a&&o&&!(0,J.A)(o),m=i?{dangerouslySetInnerHTML:{__html:i}}:{children:(0,u.jsxs)(u.Fragment,{children:[a,h&&(0,u.jsx)(te.A,{...l&&{width:12,height:12}})]})};return o?(0,u.jsx)(Z.A,{href:s?f:o,...c,...m}):(0,u.jsx)(Z.A,{to:d,isNavLink:!0,...(t||n)&&{isActive:(e,t)=>n?ee(n,t.pathname):t.pathname.startsWith(p)},...c,...m})}function re(e){let{className:t,isDropdownItem:n=!1,...r}=e;const a=(0,u.jsx)(ne,{className:(0,o.A)(n?"dropdown__link":"navbar__item navbar__link",t),isDropdownLink:n,...r});return n?(0,u.jsx)("li",{children:a}):a}function oe(e){let{className:t,isDropdownItem:n,...r}=e;return(0,u.jsx)("li",{className:"menu__list-item",children:(0,u.jsx)(ne,{className:(0,o.A)("menu__link",t),...r})})}function ae(e){let{mobile:t=!1,position:n,...r}=e;const o=t?oe:re;return(0,u.jsx)(o,{...r,activeClassName:r.activeClassName??(t?"menu__link--active":"navbar__link--active")})}var ie=n(1422),le=n(9169),se=n(4586);const ce={dropdownNavbarItemMobile:"dropdownNavbarItemMobile_S0Fm"};function ue(e,t){return e.some((e=>function(e,t){return!!(0,le.ys)(e.to,t)||!!ee(e.activeBaseRegex,t)||!(!e.activeBasePath||!t.startsWith(e.activeBasePath))}(e,t)))}function de(e){let{items:t,position:n,className:a,onClick:i,...l}=e;const s=(0,r.useRef)(null),[c,d]=(0,r.useState)(!1);return(0,r.useEffect)((()=>{const e=e=>{s.current&&!s.current.contains(e.target)&&d(!1)};return document.addEventListener("mousedown",e),document.addEventListener("touchstart",e),document.addEventListener("focusin",e),()=>{document.removeEventListener("mousedown",e),document.removeEventListener("touchstart",e),document.removeEventListener("focusin",e)}}),[s]),(0,u.jsxs)("div",{ref:s,className:(0,o.A)("navbar__item","dropdown","dropdown--hoverable",{"dropdown--right":"right"===n,"dropdown--show":c}),children:[(0,u.jsx)(ne,{"aria-haspopup":"true","aria-expanded":c,role:"button",href:l.to?void 0:"#",className:(0,o.A)("navbar__link",a),...l,onClick:l.to?void 0:e=>e.preventDefault(),onKeyDown:e=>{"Enter"===e.key&&(e.preventDefault(),d(!c))},children:l.children??l.label}),(0,u.jsx)("ul",{className:"dropdown__menu",children:t.map(((e,t)=>(0,r.createElement)(Ge,{isDropdownItem:!0,activeClassName:"dropdown__link--active",...e,key:t})))})]})}function pe(e){let{items:t,className:n,position:a,onClick:i,...s}=e;const c=function(){const{siteConfig:{baseUrl:e}}=(0,se.A)(),{pathname:t}=(0,l.zy)();return t.replace(e,"/")}(),d=ue(t,c),{collapsed:p,toggleCollapsed:f,setCollapsed:h}=(0,ie.u)({initialState:()=>!d});return(0,r.useEffect)((()=>{d&&h(!d)}),[c,d,h]),(0,u.jsxs)("li",{className:(0,o.A)("menu__list-item",{"menu__list-item--collapsed":p}),children:[(0,u.jsx)(ne,{role:"button",className:(0,o.A)(ce.dropdownNavbarItemMobile,"menu__link menu__link--sublist menu__link--sublist-caret",n),...s,onClick:e=>{e.preventDefault(),f()},children:s.children??s.label}),(0,u.jsx)(ie.N,{lazy:!0,as:"ul",className:"menu__list",collapsed:p,children:t.map(((e,t)=>(0,r.createElement)(Ge,{mobile:!0,isDropdownItem:!0,onClick:i,activeClassName:"menu__link--active",...e,key:t})))})]})}function fe(e){let{mobile:t=!1,...n}=e;const r=t?pe:de;return(0,u.jsx)(r,{...n})}var he=n(2131);function me(e){let{width:t=20,height:n=20,...r}=e;return(0,u.jsx)("svg",{viewBox:"0 0 24 24",width:t,height:n,"aria-hidden":!0,...r,children:(0,u.jsx)("path",{fill:"currentColor",d:"M12.87 15.07l-2.54-2.51.03-.03c1.74-1.94 2.98-4.17 3.71-6.53H17V4h-7V2H8v2H1v1.99h11.17C11.5 7.92 10.44 9.75 9 11.35 8.07 10.32 7.3 9.19 6.69 8h-2c.73 1.63 1.73 3.17 2.98 4.56l-5.09 5.02L4 19l5-5 3.11 3.11.76-2.04zM18.5 10h-2L12 22h2l1.12-3h4.75L21 22h2l-4.5-12zm-2.62 7l1.62-4.33L19.12 17h-3.24z"})})}const ge="iconLanguage_nlXk";var be=n(1088),ye=n(5391),ve=n(5597),we=n(4070),xe=n(5891),ke=n(2384),Se=n(9913),_e=n(4471),Ee=n(7674),Ce=n(6841),Te=n(3810);const Ae='',Le='',je='',Pe='',Re='',Ne='',Oe='',Ie={searchBar:"searchBar_RVTs",dropdownMenu:"dropdownMenu_qbY6",searchBarLeft:"searchBarLeft_MXDe",suggestion:"suggestion_fB_2",cursor:"cursor_eG29",hitTree:"hitTree_kk6K",hitIcon:"hitIcon_a7Zy",hitPath:"hitPath_ieM4",noResultsIcon:"noResultsIcon_EBY5",hitFooter:"hitFooter_E9YW",hitWrapper:"hitWrapper_sAK8",hitTitle:"hitTitle_vyVt",hitAction:"hitAction_NqkB",hideAction:"hideAction_vcyE",noResults:"noResults_l6Q3",searchBarContainer:"searchBarContainer_NW3z",searchBarLoadingRing:"searchBarLoadingRing_YnHq",searchClearButton:"searchClearButton_qk4g",searchIndexLoading:"searchIndexLoading_EJ1f",searchHintContainer:"searchHintContainer_Pkmr",searchHint:"searchHint_iIMx",focused:"focused_OWtg",input:"input_FOTf",hint:"hint_URu1",suggestions:"suggestions_X8XU",dataset:"dataset_QiCy",empty:"empty_eITn"};function De(e){let{document:t,type:n,page:r,metadata:o,tokens:a,isInterOfTree:i,isLastOfTree:l}=e;const s=n===Se.i.Title,c=n===Se.i.Keywords,u=s||c,d=n===Se.i.Heading,p=[];i?p.push(Ne):l&&p.push(Oe);const f=p.map((e=>`${e}`)),h=`${u?Ae:d?Le:je}`,m=[`${c?(0,Ce.Z)(t.s,a):(0,Te.C)(t.t,(0,Ee.g)(o,"t"),a)}`];if(!i&&!l&&be.tb){const e=r?r.b?.concat(r.t).concat(t.s&&t.s!==r.t?t.s:[]):t.b;m.push(`${(0,_e.$)(e??[])}`)}else u||m.push(`${(0,Ce.Z)(r.t||(t.u.startsWith("/docs/api-reference/")?"API Reference":""),a)}`);const g=`${Pe}`;return[...f,h,``,...m,"",g].join("")}function ze(){return`${Re}${(0,s.T)({id:"theme.SearchBar.noResultsText",message:"No results"})}`}var Fe=n(2849),Me=n(3385);async function Be(){const e=await Promise.all([n.e(489),n.e(5741)]).then(n.t.bind(n,489,23)),t=e.default;return t.noConflict?t.noConflict():e.noConflict&&e.noConflict(),t}const $e="_highlight";const Ue=function(e){let{handleSearchBarToggle:t}=e;const n=(0,M.A)(),{siteConfig:{baseUrl:o},i18n:{currentLocale:a}}=(0,se.A)(),i=(0,we.vT)();let c=o;try{const{preferredVersion:e}=(0,ve.g1)(i?.pluginId??be.UB);e&&!e.isLast&&(c=e.path+"/")}catch(z){if(be.I$&&!(z instanceof P.dV))throw z}const d=(0,l.W6)(),p=(0,l.zy)(),f=(0,r.useRef)(null),h=(0,r.useRef)(new Map),m=(0,r.useRef)(!1),[g,b]=(0,r.useState)(!1),[y,v]=(0,r.useState)(!1),[w,x]=(0,r.useState)(""),k=(0,r.useRef)(null),S=(0,r.useRef)(""),[_,E]=(0,r.useState)("");(0,r.useEffect)((()=>{if(!Array.isArray(be.Hg))return;let e="";if(p.pathname.startsWith(c)){const t=p.pathname.substring(c.length);let n;for(const e of be.Hg){const r="string"==typeof e?e:e.path;if(t===r||t.startsWith(`${r}/`)){n=r;break}}n&&(e=n)}S.current!==e&&(h.current.delete(e),S.current=e),E(e)}),[p.pathname,c]);const C=!!be.O6&&Array.isArray(be.Hg)&&""===_,T=(0,r.useCallback)((async()=>{if(C||h.current.get(_))return;h.current.set(_,"loading"),k.current?.autocomplete.destroy(),b(!0);const[{wrappedIndexes:e,zhDictionary:t},n]=await Promise.all([(0,xe.Z)(c,_),Be()]);if(k.current=n(f.current,{hint:!1,autoselect:!0,openOnFocus:!0,cssClasses:{root:(0,ye.A)(Ie.searchBar,{[Ie.searchBarLeft]:"left"===be.ZG}),noPrefix:!0,dropdownMenu:Ie.dropdownMenu,input:Ie.input,hint:Ie.hint,suggestions:Ie.suggestions,suggestion:Ie.suggestion,cursor:Ie.cursor,dataset:Ie.dataset,empty:Ie.empty}},[{source:(0,ke.m)(e,t,be.AT),templates:{suggestion:De,empty:ze,footer:e=>{let{query:t,isEmpty:n}=e;if(n&&(!_||!be.dz))return;const r=(e=>{let{query:t,isEmpty:n}=e;const r=document.createElement("a"),i=new URLSearchParams;let l;if(i.set("q",t),_){const e=_&&Array.isArray(be.Hg)?be.Hg.find((e=>"string"==typeof e?e===_:e.path===_)):_,t=e?(0,Me.p)(e,a).label:_;l=be.dz&&n?(0,s.T)({id:"theme.SearchBar.seeAllOutsideContext",message:'See all results outside "{context}"'},{context:t}):(0,s.T)({id:"theme.SearchBar.searchInContext",message:'See all results within "{context}"'},{context:t})}else l=(0,s.T)({id:"theme.SearchBar.seeAll",message:"See all results"});if(!_||!Array.isArray(be.Hg)||be.dz&&n||i.set("ctx",_),c!==o){if(!c.startsWith(o))throw new Error(`Version url '${c}' does not start with base url '${o}', this is a bug of \`@easyops-cn/docusaurus-search-local\`, please report it.`);i.set("version",c.substring(o.length))}const u=`${o}search?${i.toString()}`;return r.href=u,r.textContent=l,r.addEventListener("click",(e=>{e.ctrlKey||e.metaKey||(e.preventDefault(),k.current?.autocomplete.close(),d.push(u))})),r})({query:t,isEmpty:n}),i=document.createElement("div");return i.className=Ie.hitFooter,i.appendChild(r),i}}}]).on("autocomplete:selected",(function(e,t){let{document:{u:n,h:r},tokens:o}=t;f.current?.blur();let a=n;if(be.CU&&o.length>0){const e=new URLSearchParams;for(const t of o)e.append($e,t);a+=`?${e.toString()}`}r&&(a+=r),d.push(a)})).on("autocomplete:closed",(()=>{f.current?.blur()})),h.current.set(_,"done"),b(!1),m.current){const e=f.current;e.value&&k.current?.autocomplete.open(),e.focus()}}),[C,_,c,o,d]);(0,r.useEffect)((()=>{if(!be.CU)return;const e=n?new URLSearchParams(p.search).getAll($e):[];setTimeout((()=>{const t=document.querySelector("article");if(!t)return;const n=new be.CU(t);n.unmark(),0!==e.length&&n.mark(e),x(e.join(" ")),k.current?.autocomplete.setVal(e.join(" "))}))}),[n,p.search,p.pathname]);const[A,L]=(0,r.useState)(!1),j=(0,r.useCallback)((()=>{m.current=!0,T(),L(!0),t?.(!0)}),[t,T]),R=(0,r.useCallback)((()=>{L(!1),t?.(!1)}),[t]),N=(0,r.useCallback)((()=>{T()}),[T]),O=(0,r.useCallback)((e=>{x(e.target.value),e.target.value&&v(!0)}),[]),I=!!n&&/mac/i.test(navigator.userAgentData?.platform??navigator.platform);(0,r.useEffect)((()=>{if(!be.WW)return;const e=e=>{!(I?e.metaKey:e.ctrlKey)||"k"!==e.key&&"K"!==e.key||(e.preventDefault(),f.current?.focus(),j())};return document.addEventListener("keydown",e),()=>{document.removeEventListener("keydown",e)}}),[I,j]);const D=(0,r.useCallback)((()=>{const e=new URLSearchParams(p.search);e.delete($e);const t=e.toString(),n=p.pathname+(""!=t?`?${t}`:"")+p.hash;n!=p.pathname+p.search+p.hash&&d.push(n),x(""),k.current?.autocomplete.setVal("")}),[p.pathname,p.search,p.hash,d]);return(0,u.jsxs)("div",{className:(0,ye.A)("navbar__search",Ie.searchBarContainer,{[Ie.searchIndexLoading]:g&&y,[Ie.focused]:A}),hidden:C,children:[(0,u.jsx)("input",{placeholder:(0,s.T)({id:"theme.SearchBar.label",message:"Search",description:"The ARIA label and placeholder for search button"}),"aria-label":"Search",className:"navbar__search-input",onMouseEnter:N,onFocus:j,onBlur:R,onChange:O,ref:f,value:w}),(0,u.jsx)(Fe.A,{className:Ie.searchBarLoadingRing}),be.WW&&be.pk&&(""!==w?(0,u.jsx)("button",{className:Ie.searchClearButton,onClick:D,children:"\u2715"}):n&&(0,u.jsxs)("div",{className:Ie.searchHintContainer,children:[(0,u.jsx)("kbd",{className:Ie.searchHint,children:I?"\u2318":"ctrl"}),(0,u.jsx)("kbd",{className:Ie.searchHint,children:"K"})]}))]})},He={navbarSearchContainer:"navbarSearchContainer_Bca1"};function qe(e){let{children:t,className:n}=e;return(0,u.jsx)("div",{className:(0,o.A)(n,He.navbarSearchContainer),children:t})}var Qe=n(1754);const Ve=e=>e.docs.find((t=>t.id===e.mainDocId));const We={default:ae,localeDropdown:function(e){let{mobile:t,dropdownItemsBefore:n,dropdownItemsAfter:r,queryString:o="",...a}=e;const{i18n:{currentLocale:i,locales:c,localeConfigs:d}}=(0,se.A)(),p=(0,he.o)(),{search:f,hash:h}=(0,l.zy)(),m=[...n,...c.map((e=>{const n=`${`pathname://${p.createUrl({locale:e,fullyQualified:!1})}`}${f}${h}${o}`;return{label:d[e].label,lang:d[e].htmlLang,to:n,target:"_self",autoAddBaseUrl:!1,className:e===i?t?"menu__link--active":"dropdown__link--active":""}})),...r],g=t?(0,s.T)({message:"Languages",id:"theme.navbar.mobileLanguageDropdown.label",description:"The label for the mobile language switcher dropdown"}):d[i].label;return(0,u.jsx)(fe,{...a,mobile:t,label:(0,u.jsxs)(u.Fragment,{children:[(0,u.jsx)(me,{className:ge}),g]}),items:m})},search:function(e){let{mobile:t,className:n}=e;return t?null:(0,u.jsx)(qe,{className:n,children:(0,u.jsx)(Ue,{})})},dropdown:fe,html:function(e){let{value:t,className:n,mobile:r=!1,isDropdownItem:a=!1}=e;const i=a?"li":"div";return(0,u.jsx)(i,{className:(0,o.A)({navbar__item:!r&&!a,"menu__list-item":r},n),dangerouslySetInnerHTML:{__html:t}})},doc:function(e){let{docId:t,label:n,docsPluginId:r,...o}=e;const{activeDoc:a}=(0,we.zK)(r),i=(0,Qe.QB)(t,r),l=a?.path===i?.path;return null===i||i.unlisted&&!l?null:(0,u.jsx)(ae,{exact:!0,...o,isActive:()=>l||!!a?.sidebar&&a.sidebar===i.sidebar,label:n??i.id,to:i.path})},docSidebar:function(e){let{sidebarId:t,label:n,docsPluginId:r,...o}=e;const{activeDoc:a}=(0,we.zK)(r),i=(0,Qe.fW)(t,r).link;if(!i)throw new Error(`DocSidebarNavbarItem: Sidebar with ID "${t}" doesn't have anything to be linked to.`);return(0,u.jsx)(ae,{exact:!0,...o,isActive:()=>a?.sidebar===t,label:n??i.label,to:i.path})},docsVersion:function(e){let{label:t,to:n,docsPluginId:r,...o}=e;const a=(0,Qe.Vd)(r)[0],i=t??a.label,l=n??(e=>e.docs.find((t=>t.id===e.mainDocId)))(a).path;return(0,u.jsx)(ae,{...o,label:i,to:l})},docsVersionDropdown:function(e){let{mobile:t,docsPluginId:n,dropdownActiveClassDisabled:r,dropdownItemsBefore:o,dropdownItemsAfter:a,...i}=e;const{search:c,hash:d}=(0,l.zy)(),p=(0,we.zK)(n),f=(0,we.jh)(n),{savePreferredVersionName:h}=(0,ve.g1)(n),m=[...o,...f.map((e=>{const t=p.alternateDocVersions[e.name]??Ve(e);return{label:e.label,to:`${t.path}${c}${d}`,isActive:()=>e===p.activeVersion,onClick:()=>h(e.name)}})),...a],g=(0,Qe.Vd)(n)[0],b=t&&m.length>1?(0,s.T)({id:"theme.navbar.mobileVersionsDropdown.label",message:"Versions",description:"The label for the navbar versions dropdown on mobile view"}):g.label,y=t&&m.length>1?void 0:Ve(g).path;return m.length<=1?(0,u.jsx)(ae,{...i,mobile:t,label:b,to:y,isActive:r?()=>!1:void 0}):(0,u.jsx)(fe,{...i,mobile:t,label:b,to:y,items:m,isActive:r?()=>!1:void 0})}};function Ge(e){let{type:t,...n}=e;const r=function(e,t){return e&&"default"!==e?e:"items"in t?"dropdown":"default"}(t,n),o=We[r];if(!o)throw new Error(`No NavbarItem component found for type "${t}".`);return(0,u.jsx)(o,{...n})}function Ke(){const e=(0,L.M)(),t=(0,w.p)().navbar.items;return(0,u.jsx)("ul",{className:"menu__list",children:t.map(((t,n)=>(0,r.createElement)(Ge,{mobile:!0,...t,onClick:()=>e.toggle(),key:n})))})}function Ye(e){return(0,u.jsx)("button",{...e,type:"button",className:"clean-btn navbar-sidebar__back",children:(0,u.jsx)(s.A,{id:"theme.navbar.mobileSidebarSecondaryMenu.backButtonLabel",description:"The label of the back button to return to main menu, inside the mobile navbar sidebar secondary menu (notably used to display the docs sidebar)",children:"\u2190 Back to main menu"})})}function Ze(){const e=0===(0,w.p)().navbar.items.length,t=D();return(0,u.jsxs)(u.Fragment,{children:[!e&&(0,u.jsx)(Ye,{onClick:()=>t.hide()}),t.content]})}function Xe(){const e=(0,L.M)();var t;return void 0===(t=e.shown)&&(t=!0),(0,r.useEffect)((()=>(document.body.style.overflow=t?"hidden":"visible",()=>{document.body.style.overflow="visible"})),[t]),e.shouldRender?(0,u.jsx)(z,{header:(0,u.jsx)(Y,{}),primaryMenu:(0,u.jsx)(Ke,{}),secondaryMenu:(0,u.jsx)(Ze,{})}):null}const Je={navbarHideable:"navbarHideable_m1mJ",navbarHidden:"navbarHidden_jGov"};function et(e){return(0,u.jsx)("div",{role:"presentation",...e,className:(0,o.A)("navbar-sidebar__backdrop",e.className)})}function tt(e){let{children:t}=e;const{navbar:{hideOnScroll:n,style:a}}=(0,w.p)(),i=(0,L.M)(),{navbarRef:l,isNavbarVisible:d}=function(e){const[t,n]=(0,r.useState)(e),o=(0,r.useRef)(!1),a=(0,r.useRef)(0),i=(0,r.useCallback)((e=>{null!==e&&(a.current=e.getBoundingClientRect().height)}),[]);return(0,j.Mq)(((t,r)=>{let{scrollY:i}=t;if(!e)return;if(i=l?n(!1):i+c{if(!e)return;const r=t.location.hash;if(r?document.getElementById(r.substring(1)):void 0)return o.current=!0,void n(!1);n(!0)})),{navbarRef:i,isNavbarVisible:t}}(n);return(0,u.jsxs)("nav",{ref:l,"aria-label":(0,s.T)({id:"theme.NavBar.navAriaLabel",message:"Main",description:"The ARIA label for the main navigation"}),className:(0,o.A)("navbar","navbar--fixed-top",n&&[Je.navbarHideable,!d&&Je.navbarHidden],{"navbar--dark":"dark"===a,"navbar--primary":"primary"===a,"navbar-sidebar--show":i.shown}),children:[t,(0,u.jsx)(et,{onClick:i.toggle}),(0,u.jsx)(Xe,{})]})}var nt=n(440);const rt={errorBoundaryError:"errorBoundaryError_a6uf",errorBoundaryFallback:"errorBoundaryFallback_VBag"};function ot(e){return(0,u.jsx)("button",{type:"button",...e,children:(0,u.jsx)(s.A,{id:"theme.ErrorPageContent.tryAgain",description:"The label of the button to try again rendering when the React error boundary captures an error",children:"Try again"})})}function at(e){let{error:t}=e;const n=(0,nt.getErrorCausalChain)(t).map((e=>e.message)).join("\n\nCause:\n");return(0,u.jsx)("p",{className:rt.errorBoundaryError,children:n})}class it extends r.Component{componentDidCatch(e,t){throw this.props.onError(e,t)}render(){return this.props.children}}const lt="right";function st(e){let{width:t=30,height:n=30,className:r,...o}=e;return(0,u.jsx)("svg",{className:r,width:t,height:n,viewBox:"0 0 30 30","aria-hidden":"true",...o,children:(0,u.jsx)("path",{stroke:"currentColor",strokeLinecap:"round",strokeMiterlimit:"10",strokeWidth:"2",d:"M4 7h22M4 15h22M4 23h22"})})}function ct(){const{toggle:e,shown:t}=(0,L.M)();return(0,u.jsx)("button",{onClick:e,"aria-label":(0,s.T)({id:"theme.docs.sidebar.toggleSidebarButtonAriaLabel",message:"Toggle navigation bar",description:"The ARIA label for hamburger menu button of mobile navigation"}),"aria-expanded":t,className:"navbar__toggle clean-btn",type:"button",children:(0,u.jsx)(st,{})})}const ut={colorModeToggle:"colorModeToggle_DEke"};function dt(e){let{items:t}=e;return(0,u.jsx)(u.Fragment,{children:t.map(((e,t)=>(0,u.jsx)(it,{onError:t=>new Error(`A theme navbar item failed to render.\nPlease double-check the following navbar item (themeConfig.navbar.items) of your Docusaurus config:\n${JSON.stringify(e,null,2)}`,{cause:t}),children:(0,u.jsx)(Ge,{...e})},t)))})}function pt(e){let{left:t,right:n}=e;return(0,u.jsxs)("div",{className:"navbar__inner",children:[(0,u.jsx)("div",{className:"navbar__items",children:t}),(0,u.jsx)("div",{className:"navbar__items navbar__items--right",children:n})]})}function ft(){const e=(0,L.M)(),t=(0,w.p)().navbar.items,[n,r]=function(e){function t(e){return"left"===(e.position??lt)}return[e.filter(t),e.filter((e=>!t(e)))]}(t),o=t.find((e=>"search"===e.type));return(0,u.jsx)(pt,{left:(0,u.jsxs)(u.Fragment,{children:[!e.disabled&&(0,u.jsx)(ct,{}),(0,u.jsx)(G,{}),(0,u.jsx)(dt,{items:n})]}),right:(0,u.jsxs)(u.Fragment,{children:[(0,u.jsx)(dt,{items:r}),(0,u.jsx)(V,{className:ut.colorModeToggle}),!o&&(0,u.jsx)(qe,{children:(0,u.jsx)(Ue,{})})]})})}function ht(){return(0,u.jsx)(tt,{children:(0,u.jsx)(ft,{})})}function mt(e){let{item:t}=e;const{to:n,href:r,label:o,prependBaseUrlToHref:a,...i}=t,l=(0,X.Ay)(n),s=(0,X.Ay)(r,{forcePrependBaseUrl:!0});return(0,u.jsxs)(Z.A,{className:"footer__link-item",...r?{href:a?s:r}:{to:l},...i,children:[o,r&&!(0,J.A)(r)&&(0,u.jsx)(te.A,{})]})}function gt(e){let{item:t}=e;return t.html?(0,u.jsx)("li",{className:"footer__item",dangerouslySetInnerHTML:{__html:t.html}}):(0,u.jsx)("li",{className:"footer__item",children:(0,u.jsx)(mt,{item:t})},t.href??t.to)}function bt(e){let{column:t}=e;return(0,u.jsxs)("div",{className:"col footer__col",children:[(0,u.jsx)("div",{className:"footer__title",children:t.title}),(0,u.jsx)("ul",{className:"footer__items clean-list",children:t.items.map(((e,t)=>(0,u.jsx)(gt,{item:e},t)))})]})}function yt(e){let{columns:t}=e;return(0,u.jsx)("div",{className:"row footer__links",children:t.map(((e,t)=>(0,u.jsx)(bt,{column:e},t)))})}function vt(){return(0,u.jsx)("span",{className:"footer__link-separator",children:"\xb7"})}function wt(e){let{item:t}=e;return t.html?(0,u.jsx)("span",{className:"footer__link-item",dangerouslySetInnerHTML:{__html:t.html}}):(0,u.jsx)(mt,{item:t})}function xt(e){let{links:t}=e;return(0,u.jsx)("div",{className:"footer__links text--center",children:(0,u.jsx)("div",{className:"footer__links",children:t.map(((e,n)=>(0,u.jsxs)(r.Fragment,{children:[(0,u.jsx)(wt,{item:e}),t.length!==n+1&&(0,u.jsx)(vt,{})]},n)))})})}function kt(e){let{links:t}=e;return function(e){return"title"in e[0]}(t)?(0,u.jsx)(yt,{columns:t}):(0,u.jsx)(xt,{links:t})}var St=n(1122);const _t={footerLogoLink:"footerLogoLink_BH7S"};function Et(e){let{logo:t}=e;const{withBaseUrl:n}=(0,X.hH)(),r={light:n(t.src),dark:n(t.srcDark??t.src)};return(0,u.jsx)(St.A,{className:(0,o.A)("footer__logo",t.className),alt:t.alt,sources:r,width:t.width,height:t.height,style:t.style})}function Ct(e){let{logo:t}=e;return t.href?(0,u.jsx)(Z.A,{href:t.href,className:_t.footerLogoLink,target:t.target,children:(0,u.jsx)(Et,{logo:t})}):(0,u.jsx)(Et,{logo:t})}function Tt(e){let{copyright:t}=e;return(0,u.jsx)("div",{className:"footer__copyright",dangerouslySetInnerHTML:{__html:t}})}function At(e){let{style:t,links:n,logo:r,copyright:a}=e;return(0,u.jsx)("footer",{className:(0,o.A)("footer",{"footer--dark":"dark"===t}),children:(0,u.jsxs)("div",{className:"container container-fluid",children:[n,(r||a)&&(0,u.jsxs)("div",{className:"footer__bottom text--center",children:[r&&(0,u.jsx)("div",{className:"margin-bottom--sm",children:r}),a]})]})})}function Lt(){const{footer:e}=(0,w.p)();if(!e)return null;const{copyright:t,links:n,logo:r,style:o}=e;return(0,u.jsx)(At,{style:o,links:n&&n.length>0&&(0,u.jsx)(kt,{links:n}),logo:r&&(0,u.jsx)(Ct,{logo:r}),copyright:t&&(0,u.jsx)(Tt,{copyright:t})})}const jt=r.memo(Lt),Pt=(0,P.fM)([F.a,x.o,j.Tv,ve.VQ,i.Jx,function(e){let{children:t}=e;return(0,u.jsx)(R.y_,{children:(0,u.jsx)(L.e,{children:(0,u.jsx)(O,{children:t})})})}]);function Rt(e){let{children:t}=e;return(0,u.jsx)(Pt,{children:t})}var Nt=n(1107);function Ot(e){let{error:t,tryAgain:n}=e;return(0,u.jsx)("main",{className:"container margin-vert--xl",children:(0,u.jsx)("div",{className:"row",children:(0,u.jsxs)("div",{className:"col col--6 col--offset-3",children:[(0,u.jsx)(Nt.A,{as:"h1",className:"hero__title",children:(0,u.jsx)(s.A,{id:"theme.ErrorPageContent.title",description:"The title of the fallback page when the page crashed",children:"This page crashed."})}),(0,u.jsx)("div",{className:"margin-vert--lg",children:(0,u.jsx)(ot,{onClick:n,className:"button button--primary shadow--lw"})}),(0,u.jsx)("hr",{}),(0,u.jsx)("div",{className:"margin-vert--md",children:(0,u.jsx)(at,{error:t})})]})})})}const It={mainWrapper:"mainWrapper_z2l0"};function Dt(e){const{children:t,noFooter:n,wrapperClassName:r,title:l,description:s}=e;return(0,b.J)(),(0,u.jsxs)(Rt,{children:[(0,u.jsx)(i.be,{title:l,description:s}),(0,u.jsx)(v,{}),(0,u.jsx)(A,{}),(0,u.jsx)(ht,{}),(0,u.jsx)("div",{id:d,className:(0,o.A)(g.G.wrapper.main,It.mainWrapper,r),children:(0,u.jsx)(a.A,{fallback:e=>(0,u.jsx)(Ot,{...e}),children:t})}),!n&&(0,u.jsx)(jt,{})]})}},3465:(e,t,n)=>{"use strict";n.d(t,{A:()=>u});n(6540);var r=n(8774),o=n(6025),a=n(4586),i=n(6342),l=n(1122),s=n(4848);function c(e){let{logo:t,alt:n,imageClassName:r}=e;const a={light:(0,o.Ay)(t.src),dark:(0,o.Ay)(t.srcDark||t.src)},i=(0,s.jsx)(l.A,{className:t.className,sources:a,height:t.height,width:t.width,alt:n,style:t.style});return r?(0,s.jsx)("div",{className:r,children:i}):i}function u(e){const{siteConfig:{title:t}}=(0,a.A)(),{navbar:{title:n,logo:l}}=(0,i.p)(),{imageClassName:u,titleClassName:d,...p}=e,f=(0,o.Ay)(l?.href||"/"),h=n?"":t,m=l?.alt??h;return(0,s.jsxs)(r.A,{to:f,...p,...l?.target&&{target:l.target},children:[l&&(0,s.jsx)(c,{logo:l,alt:m,imageClassName:u}),null!=n&&(0,s.jsx)("b",{className:d,children:n})]})}},1463:(e,t,n)=>{"use strict";n.d(t,{A:()=>a});n(6540);var r=n(5260),o=n(4848);function a(e){let{locale:t,version:n,tag:a}=e;const i=t;return(0,o.jsxs)(r.A,{children:[t&&(0,o.jsx)("meta",{name:"docusaurus_locale",content:t}),n&&(0,o.jsx)("meta",{name:"docusaurus_version",content:n}),a&&(0,o.jsx)("meta",{name:"docusaurus_tag",content:a}),i&&(0,o.jsx)("meta",{name:"docsearch:language",content:i}),n&&(0,o.jsx)("meta",{name:"docsearch:version",content:n}),a&&(0,o.jsx)("meta",{name:"docsearch:docusaurus_tag",content:a})]})}},1122:(e,t,n)=>{"use strict";n.d(t,{A:()=>u});var r=n(6540),o=n(4164),a=n(2303),i=n(5293);const l={themedComponent:"themedComponent_mlkZ","themedComponent--light":"themedComponent--light_NVdE","themedComponent--dark":"themedComponent--dark_xIcU"};var s=n(4848);function c(e){let{className:t,children:n}=e;const c=(0,a.A)(),{colorMode:u}=(0,i.G)();return(0,s.jsx)(s.Fragment,{children:(c?"dark"===u?["dark"]:["light"]:["light","dark"]).map((e=>{const a=n({theme:e,className:(0,o.A)(t,l.themedComponent,l[`themedComponent--${e}`])});return(0,s.jsx)(r.Fragment,{children:a},e)}))})}function u(e){const{sources:t,className:n,alt:r,...o}=e;return(0,s.jsx)(c,{className:n,children:e=>{let{theme:n,className:a}=e;return(0,s.jsx)("img",{src:t[n],alt:r,className:a,...o})}})}},1422:(e,t,n)=>{"use strict";n.d(t,{N:()=>b,u:()=>c});var r=n(6540),o=n(8193),a=n(205),i=n(3109),l=n(4848);const s="ease-in-out";function c(e){let{initialState:t}=e;const[n,o]=(0,r.useState)(t??!1),a=(0,r.useCallback)((()=>{o((e=>!e))}),[]);return{collapsed:n,setCollapsed:o,toggleCollapsed:a}}const u={display:"none",overflow:"hidden",height:"0px"},d={display:"block",overflow:"visible",height:"auto"};function p(e,t){const n=t?u:d;e.style.display=n.display,e.style.overflow=n.overflow,e.style.height=n.height}function f(e){let{collapsibleRef:t,collapsed:n,animation:o}=e;const a=(0,r.useRef)(!1);(0,r.useEffect)((()=>{const e=t.current;function r(){const t=e.scrollHeight,n=o?.duration??function(e){if((0,i.O)())return 1;const t=e/36;return Math.round(10*(4+15*t**.25+t/5))}(t);return{transition:`height ${n}ms ${o?.easing??s}`,height:`${t}px`}}function l(){const t=r();e.style.transition=t.transition,e.style.height=t.height}if(!a.current)return p(e,n),void(a.current=!0);return e.style.willChange="height",function(){const t=requestAnimationFrame((()=>{n?(l(),requestAnimationFrame((()=>{e.style.height=u.height,e.style.overflow=u.overflow}))):(e.style.display="block",requestAnimationFrame((()=>{l()})))}));return()=>cancelAnimationFrame(t)}()}),[t,n,o])}function h(e){if(!o.A.canUseDOM)return e?u:d}function m(e){let{as:t="div",collapsed:n,children:o,animation:a,onCollapseTransitionEnd:i,className:s,disableSSRStyle:c}=e;const u=(0,r.useRef)(null);return f({collapsibleRef:u,collapsed:n,animation:a}),(0,l.jsx)(t,{ref:u,style:c?void 0:h(n),onTransitionEnd:e=>{"height"===e.propertyName&&(p(u.current,n),i?.(n))},className:s,children:o})}function g(e){let{collapsed:t,...n}=e;const[o,i]=(0,r.useState)(!t),[s,c]=(0,r.useState)(t);return(0,a.A)((()=>{t||i(!0)}),[t]),(0,a.A)((()=>{o&&c(t)}),[o,t]),o?(0,l.jsx)(m,{...n,collapsed:s}):null}function b(e){let{lazy:t,...n}=e;const r=t?g:m;return(0,l.jsx)(r,{...n})}},5041:(e,t,n)=>{"use strict";n.d(t,{M:()=>m,o:()=>h});var r=n(6540),o=n(2303),a=n(679),i=n(9532),l=n(6342),s=n(4848);const c=(0,a.Wf)("docusaurus.announcement.dismiss"),u=(0,a.Wf)("docusaurus.announcement.id"),d=()=>"true"===c.get(),p=e=>c.set(String(e)),f=r.createContext(null);function h(e){let{children:t}=e;const n=function(){const{announcementBar:e}=(0,l.p)(),t=(0,o.A)(),[n,a]=(0,r.useState)((()=>!!t&&d()));(0,r.useEffect)((()=>{a(d())}),[]);const i=(0,r.useCallback)((()=>{p(!0),a(!0)}),[]);return(0,r.useEffect)((()=>{if(!e)return;const{id:t}=e;let n=u.get();"annoucement-bar"===n&&(n="announcement-bar");const r=t!==n;u.set(t),r&&p(!1),!r&&d()||a(!1)}),[e]),(0,r.useMemo)((()=>({isActive:!!e&&!n,close:i})),[e,n,i])}();return(0,s.jsx)(f.Provider,{value:n,children:t})}function m(){const e=(0,r.useContext)(f);if(!e)throw new i.dV("AnnouncementBarProvider");return e}},5293:(e,t,n)=>{"use strict";n.d(t,{G:()=>b,a:()=>g});var r=n(6540),o=n(8193),a=n(9532),i=n(679),l=n(6342),s=n(4848);const c=r.createContext(void 0),u="theme",d=(0,i.Wf)(u),p={light:"light",dark:"dark"},f=e=>e===p.dark?p.dark:p.light,h=e=>o.A.canUseDOM?f(document.documentElement.getAttribute("data-theme")):f(e),m=e=>{d.set(f(e))};function g(e){let{children:t}=e;const n=function(){const{colorMode:{defaultMode:e,disableSwitch:t,respectPrefersColorScheme:n}}=(0,l.p)(),[o,a]=(0,r.useState)(h(e));(0,r.useEffect)((()=>{t&&d.del()}),[t]);const i=(0,r.useCallback)((function(t,r){void 0===r&&(r={});const{persist:o=!0}=r;t?(a(t),o&&m(t)):(a(n?window.matchMedia("(prefers-color-scheme: dark)").matches?p.dark:p.light:e),d.del())}),[n,e]);(0,r.useEffect)((()=>{document.documentElement.setAttribute("data-theme",f(o))}),[o]),(0,r.useEffect)((()=>{if(t)return;const e=e=>{if(e.key!==u)return;const t=d.get();null!==t&&i(f(t))};return window.addEventListener("storage",e),()=>window.removeEventListener("storage",e)}),[t,i]);const s=(0,r.useRef)(!1);return(0,r.useEffect)((()=>{if(t&&!n)return;const e=window.matchMedia("(prefers-color-scheme: dark)"),r=()=>{window.matchMedia("print").matches||s.current?s.current=window.matchMedia("print").matches:i(null)};return e.addListener(r),()=>e.removeListener(r)}),[i,t,n]),(0,r.useMemo)((()=>({colorMode:o,setColorMode:i,get isDarkTheme(){return o===p.dark},setLightTheme(){i(p.light)},setDarkTheme(){i(p.dark)}})),[o,i])}();return(0,s.jsx)(c.Provider,{value:n,children:t})}function b(){const e=(0,r.useContext)(c);if(null==e)throw new a.dV("ColorModeProvider","Please see https://docusaurus.io/docs/api/themes/configuration#use-color-mode.");return e}},5597:(e,t,n)=>{"use strict";n.d(t,{VQ:()=>b,g1:()=>v});var r=n(6540),o=n(4070),a=n(7065),i=n(6342),l=n(1754),s=n(9532),c=n(679),u=n(4848);const d=e=>`docs-preferred-version-${e}`,p={save:(e,t,n)=>{(0,c.Wf)(d(e),{persistence:t}).set(n)},read:(e,t)=>(0,c.Wf)(d(e),{persistence:t}).get(),clear:(e,t)=>{(0,c.Wf)(d(e),{persistence:t}).del()}},f=e=>Object.fromEntries(e.map((e=>[e,{preferredVersionName:null}])));const h=r.createContext(null);function m(){const e=(0,o.Gy)(),t=(0,i.p)().docs.versionPersistence,n=(0,r.useMemo)((()=>Object.keys(e)),[e]),[a,l]=(0,r.useState)((()=>f(n)));(0,r.useEffect)((()=>{l(function(e){let{pluginIds:t,versionPersistence:n,allDocsData:r}=e;function o(e){const t=p.read(e,n);return r[e].versions.some((e=>e.name===t))?{preferredVersionName:t}:(p.clear(e,n),{preferredVersionName:null})}return Object.fromEntries(t.map((e=>[e,o(e)])))}({allDocsData:e,versionPersistence:t,pluginIds:n}))}),[e,t,n]);return[a,(0,r.useMemo)((()=>({savePreferredVersion:function(e,n){p.save(e,t,n),l((t=>({...t,[e]:{preferredVersionName:n}})))}})),[t])]}function g(e){let{children:t}=e;const n=m();return(0,u.jsx)(h.Provider,{value:n,children:t})}function b(e){let{children:t}=e;return l.C5?(0,u.jsx)(g,{children:t}):(0,u.jsx)(u.Fragment,{children:t})}function y(){const e=(0,r.useContext)(h);if(!e)throw new s.dV("DocsPreferredVersionContextProvider");return e}function v(e){void 0===e&&(e=a.W);const t=(0,o.ht)(e),[n,i]=y(),{preferredVersionName:l}=n[e];return{preferredVersion:t.versions.find((e=>e.name===l))??null,savePreferredVersionName:(0,r.useCallback)((t=>{i.savePreferredVersion(e,t)}),[i,e])}}},6588:(e,t,n)=>{"use strict";n.d(t,{V:()=>s,t:()=>c});var r=n(6540),o=n(9532),a=n(4848);const i=Symbol("EmptyContext"),l=r.createContext(i);function s(e){let{children:t,name:n,items:o}=e;const i=(0,r.useMemo)((()=>n&&o?{name:n,items:o}:null),[n,o]);return(0,a.jsx)(l.Provider,{value:i,children:t})}function c(){const e=(0,r.useContext)(l);if(e===i)throw new o.dV("DocsSidebarProvider");return e}},2252:(e,t,n)=>{"use strict";n.d(t,{n:()=>l,r:()=>s});var r=n(6540),o=n(9532),a=n(4848);const i=r.createContext(null);function l(e){let{children:t,version:n}=e;return(0,a.jsx)(i.Provider,{value:n,children:t})}function s(){const e=(0,r.useContext)(i);if(null===e)throw new o.dV("DocsVersionProvider");return e}},9876:(e,t,n)=>{"use strict";n.d(t,{e:()=>f,M:()=>h});var r=n(6540),o=n(5600),a=n(4581),i=n(6347),l=n(9532);function s(e){!function(e){const t=(0,i.W6)(),n=(0,l._q)(e);(0,r.useEffect)((()=>t.block(((e,t)=>n(e,t)))),[t,n])}(((t,n)=>{if("POP"===n)return e(t,n)}))}var c=n(6342),u=n(4848);const d=r.createContext(void 0);function p(){const e=function(){const e=(0,o.YL)(),{items:t}=(0,c.p)().navbar;return 0===t.length&&!e.component}(),t=(0,a.l)(),n=!e&&"mobile"===t,[i,l]=(0,r.useState)(!1);s((()=>{if(i)return l(!1),!1}));const u=(0,r.useCallback)((()=>{l((e=>!e))}),[]);return(0,r.useEffect)((()=>{"desktop"===t&&l(!1)}),[t]),(0,r.useMemo)((()=>({disabled:e,shouldRender:n,toggle:u,shown:i})),[e,n,u,i])}function f(e){let{children:t}=e;const n=p();return(0,u.jsx)(d.Provider,{value:n,children:t})}function h(){const e=r.useContext(d);if(void 0===e)throw new l.dV("NavbarMobileSidebarProvider");return e}},5600:(e,t,n)=>{"use strict";n.d(t,{GX:()=>c,YL:()=>s,y_:()=>l});var r=n(6540),o=n(9532),a=n(4848);const i=r.createContext(null);function l(e){let{children:t}=e;const n=(0,r.useState)({component:null,props:null});return(0,a.jsx)(i.Provider,{value:n,children:t})}function s(){const e=(0,r.useContext)(i);if(!e)throw new o.dV("NavbarSecondaryMenuContentProvider");return e[0]}function c(e){let{component:t,props:n}=e;const a=(0,r.useContext)(i);if(!a)throw new o.dV("NavbarSecondaryMenuContentProvider");const[,l]=a,s=(0,o.Be)(n);return(0,r.useEffect)((()=>{l({component:t,props:s})}),[l,t,s]),(0,r.useEffect)((()=>()=>l({component:null,props:null})),[l]),null}},4090:(e,t,n)=>{"use strict";n.d(t,{w:()=>o,J:()=>a});var r=n(6540);const o="navigation-with-keyboard";function a(){(0,r.useEffect)((()=>{function e(e){"keydown"===e.type&&"Tab"===e.key&&document.body.classList.add(o),"mousedown"===e.type&&document.body.classList.remove(o)}return document.addEventListener("keydown",e),document.addEventListener("mousedown",e),()=>{document.body.classList.remove(o),document.removeEventListener("keydown",e),document.removeEventListener("mousedown",e)}}),[])}},4581:(e,t,n)=>{"use strict";n.d(t,{l:()=>l});var r=n(6540),o=n(8193);const a={desktop:"desktop",mobile:"mobile",ssr:"ssr"},i=996;function l(e){let{desktopBreakpoint:t=i}=void 0===e?{}:e;const[n,l]=(0,r.useState)((()=>"ssr"));return(0,r.useEffect)((()=>{function e(){l(function(e){if(!o.A.canUseDOM)throw new Error("getWindowSize() should only be called after React hydration");return window.innerWidth>e?a.desktop:a.mobile}(t))}return e(),window.addEventListener("resize",e),()=>{window.removeEventListener("resize",e)}}),[t]),n}},7559:(e,t,n)=>{"use strict";n.d(t,{G:()=>r});const r={page:{blogListPage:"blog-list-page",blogPostPage:"blog-post-page",blogTagsListPage:"blog-tags-list-page",blogTagPostListPage:"blog-tags-post-list-page",docsDocPage:"docs-doc-page",docsTagsListPage:"docs-tags-list-page",docsTagDocListPage:"docs-tags-doc-list-page",mdxPage:"mdx-page"},wrapper:{main:"main-wrapper",blogPages:"blog-wrapper",docsPages:"docs-wrapper",mdxPages:"mdx-wrapper"},common:{editThisPage:"theme-edit-this-page",lastUpdated:"theme-last-updated",backToTopButton:"theme-back-to-top-button",codeBlock:"theme-code-block",admonition:"theme-admonition",unlistedBanner:"theme-unlisted-banner",admonitionType:e=>`theme-admonition-${e}`},layout:{},docs:{docVersionBanner:"theme-doc-version-banner",docVersionBadge:"theme-doc-version-badge",docBreadcrumbs:"theme-doc-breadcrumbs",docMarkdown:"theme-doc-markdown",docTocMobile:"theme-doc-toc-mobile",docTocDesktop:"theme-doc-toc-desktop",docFooter:"theme-doc-footer",docFooterTagsRow:"theme-doc-footer-tags-row",docFooterEditMetaRow:"theme-doc-footer-edit-meta-row",docSidebarContainer:"theme-doc-sidebar-container",docSidebarMenu:"theme-doc-sidebar-menu",docSidebarItemCategory:"theme-doc-sidebar-item-category",docSidebarItemLink:"theme-doc-sidebar-item-link",docSidebarItemCategoryLevel:e=>`theme-doc-sidebar-item-category-level-${e}`,docSidebarItemLinkLevel:e=>`theme-doc-sidebar-item-link-level-${e}`},blog:{blogFooterTagsRow:"theme-blog-footer-tags-row",blogFooterEditMetaRow:"theme-blog-footer-edit-meta-row"},pages:{pageFooterEditMetaRow:"theme-pages-footer-edit-meta-row"}}},3109:(e,t,n)=>{"use strict";function r(){return window.matchMedia("(prefers-reduced-motion: reduce)").matches}n.d(t,{O:()=>r})},1754:(e,t,n)=>{"use strict";n.d(t,{Nr:()=>f,w8:()=>g,C5:()=>p,B5:()=>_,Vd:()=>x,QB:()=>S,fW:()=>k,OF:()=>w,Y:()=>y});var r=n(6540),o=n(6347),a=n(2831),i=n(4070),l=n(5597),s=n(2252),c=n(6588);function u(e){return Array.from(new Set(e))}var d=n(9169);const p=!!i.Gy;function f(e){return"link"!==e.type||e.unlisted?"category"===e.type?function(e){if(e.href&&!e.linkUnlisted)return e.href;for(const t of e.items){const e=f(t);if(e)return e}}(e):void 0:e.href}const h=(e,t)=>void 0!==e&&(0,d.ys)(e,t),m=(e,t)=>e.some((e=>g(e,t)));function g(e,t){return"link"===e.type?h(e.href,t):"category"===e.type&&(h(e.href,t)||m(e.items,t))}function b(e,t){switch(e.type){case"category":return g(e,t)||e.items.some((e=>b(e,t)));case"link":return!e.unlisted||g(e,t);default:return!0}}function y(e,t){return(0,r.useMemo)((()=>e.filter((e=>b(e,t)))),[e,t])}function v(e){let{sidebarItems:t,pathname:n,onlyCategories:r=!1}=e;const o=[];return function e(t){for(const a of t)if("category"===a.type&&((0,d.ys)(a.href,n)||e(a.items))||"link"===a.type&&(0,d.ys)(a.href,n)){return r&&"category"!==a.type||o.unshift(a),!0}return!1}(t),o}function w(){const e=(0,c.t)(),{pathname:t}=(0,o.zy)(),n=(0,i.vT)()?.pluginData.breadcrumbs;return!1!==n&&e?v({sidebarItems:e.items,pathname:t}):null}function x(e){const{activeVersion:t}=(0,i.zK)(e),{preferredVersion:n}=(0,l.g1)(e),o=(0,i.r7)(e);return(0,r.useMemo)((()=>u([t,n,o].filter(Boolean))),[t,n,o])}function k(e,t){const n=x(t);return(0,r.useMemo)((()=>{const t=n.flatMap((e=>e.sidebars?Object.entries(e.sidebars):[])),r=t.find((t=>t[0]===e));if(!r)throw new Error(`Can't find any sidebar with id "${e}" in version${n.length>1?"s":""} ${n.map((e=>e.name)).join(", ")}".\nAvailable sidebar ids are:\n- ${t.map((e=>e[0])).join("\n- ")}`);return r[1]}),[e,n])}function S(e,t){const n=x(t);return(0,r.useMemo)((()=>{const t=n.flatMap((e=>e.docs)),r=t.find((t=>t.id===e));if(!r){if(n.flatMap((e=>e.draftIds)).includes(e))return null;throw new Error(`Couldn't find any doc with id "${e}" in version${n.length>1?"s":""} "${n.map((e=>e.name)).join(", ")}".\nAvailable doc ids are:\n- ${u(t.map((e=>e.id))).join("\n- ")}`)}return r}),[e,n])}function _(e){let{route:t}=e;const n=(0,o.zy)(),r=(0,s.r)(),i=t.routes,l=i.find((e=>(0,o.B6)(n.pathname,e)));if(!l)return null;const c=l.sidebar,u=c?r.docsSidebars[c]:void 0;return{docElement:(0,a.v)(i),sidebarName:c,sidebarItems:u}}},1213:(e,t,n)=>{"use strict";n.d(t,{e3:()=>p,be:()=>u,Jx:()=>f});var r=n(6540),o=n(4164),a=n(5260),i=n(6803),l=n(6025),s=n(4586);var c=n(4848);function u(e){let{title:t,description:n,keywords:r,image:o,children:i}=e;const u=function(e){const{siteConfig:t}=(0,s.A)(),{title:n,titleDelimiter:r}=t;return e?.trim().length?`${e.trim()} ${r} ${n}`:n}(t),{withBaseUrl:d}=(0,l.hH)(),p=o?d(o,{absolute:!0}):void 0;return(0,c.jsxs)(a.A,{children:[t&&(0,c.jsx)("title",{children:u}),t&&(0,c.jsx)("meta",{property:"og:title",content:u}),n&&(0,c.jsx)("meta",{name:"description",content:n}),n&&(0,c.jsx)("meta",{property:"og:description",content:n}),r&&(0,c.jsx)("meta",{name:"keywords",content:Array.isArray(r)?r.join(","):r}),p&&(0,c.jsx)("meta",{property:"og:image",content:p}),p&&(0,c.jsx)("meta",{name:"twitter:image",content:p}),i]})}const d=r.createContext(void 0);function p(e){let{className:t,children:n}=e;const i=r.useContext(d),l=(0,o.A)(i,t);return(0,c.jsxs)(d.Provider,{value:l,children:[(0,c.jsx)(a.A,{children:(0,c.jsx)("html",{className:l})}),n]})}function f(e){let{children:t}=e;const n=(0,i.A)(),r=`plugin-${n.plugin.name.replace(/docusaurus-(?:plugin|theme)-(?:content-)?/gi,"")}`;const a=`plugin-id-${n.plugin.id}`;return(0,c.jsx)(p,{className:(0,o.A)(r,a),children:t})}},9532:(e,t,n)=>{"use strict";n.d(t,{Be:()=>c,ZC:()=>l,_q:()=>i,dV:()=>s,fM:()=>u});var r=n(6540),o=n(205),a=n(4848);function i(e){const t=(0,r.useRef)(e);return(0,o.A)((()=>{t.current=e}),[e]),(0,r.useCallback)((function(){return t.current(...arguments)}),[])}function l(e){const t=(0,r.useRef)();return(0,o.A)((()=>{t.current=e})),t.current}class s extends Error{constructor(e,t){super(),this.name="ReactContextError",this.message=`Hook ${this.stack?.split("\n")[1]?.match(/at (?:\w+\.)?(?\w+)/)?.groups.name??""} is called outside the <${e}>. ${t??""}`}}function c(e){const t=Object.entries(e);return t.sort(((e,t)=>e[0].localeCompare(t[0]))),(0,r.useMemo)((()=>e),t.flat())}function u(e){return t=>{let{children:n}=t;return(0,a.jsx)(a.Fragment,{children:e.reduceRight(((e,t)=>(0,a.jsx)(t,{children:e})),n)})}}},9169:(e,t,n)=>{"use strict";n.d(t,{Dt:()=>l,ys:()=>i});var r=n(6540),o=n(8328),a=n(4586);function i(e,t){const n=e=>(!e||e.endsWith("/")?e:`${e}/`)?.toLowerCase();return n(e)===n(t)}function l(){const{baseUrl:e}=(0,a.A)().siteConfig;return(0,r.useMemo)((()=>function(e){let{baseUrl:t,routes:n}=e;function r(e){return e.path===t&&!0===e.exact}function o(e){return e.path===t&&!e.exact}return function e(t){if(0===t.length)return;return t.find(r)||e(t.filter(o).flatMap((e=>e.routes??[])))}(n)}({routes:o.A,baseUrl:e})),[e])}},3104:(e,t,n)=>{"use strict";n.d(t,{Mq:()=>p,Tv:()=>c,gk:()=>f});var r=n(6540),o=n(8193),a=n(2303),i=(n(205),n(9532)),l=n(4848);const s=r.createContext(void 0);function c(e){let{children:t}=e;const n=function(){const e=(0,r.useRef)(!0);return(0,r.useMemo)((()=>({scrollEventsEnabledRef:e,enableScrollEvents:()=>{e.current=!0},disableScrollEvents:()=>{e.current=!1}})),[])}();return(0,l.jsx)(s.Provider,{value:n,children:t})}function u(){const e=(0,r.useContext)(s);if(null==e)throw new i.dV("ScrollControllerProvider");return e}const d=()=>o.A.canUseDOM?{scrollX:window.pageXOffset,scrollY:window.pageYOffset}:null;function p(e,t){void 0===t&&(t=[]);const{scrollEventsEnabledRef:n}=u(),o=(0,r.useRef)(d()),a=(0,i._q)(e);(0,r.useEffect)((()=>{const e=()=>{if(!n.current)return;const e=d();a(e,o.current),o.current=e},t={passive:!0};return e(),window.addEventListener("scroll",e,t),()=>window.removeEventListener("scroll",e,t)}),[a,n,...t])}function f(){const e=(0,r.useRef)(null),t=(0,a.A)()&&"smooth"===getComputedStyle(document.documentElement).scrollBehavior;return{startScroll:n=>{e.current=t?function(e){return window.scrollTo({top:e,behavior:"smooth"}),()=>{}}(n):function(e){let t=null;const n=document.documentElement.scrollTop>e;return function r(){const o=document.documentElement.scrollTop;(n&&o>e||!n&&ot&&cancelAnimationFrame(t)}(n)},cancelScroll:()=>e.current?.()}}},2967:(e,t,n)=>{"use strict";n.d(t,{Cy:()=>r,tU:()=>o});n(4586);const r="default";function o(e,t){return`docs-${e}-${t}`}},679:(e,t,n)=>{"use strict";n.d(t,{Wf:()=>c});n(6540);const r=JSON.parse('{"N":"localStorage","M":""}'),o=r.N;function a(e){let{key:t,oldValue:n,newValue:r,storage:o}=e;if(n===r)return;const a=document.createEvent("StorageEvent");a.initStorageEvent("storage",!1,!1,t,n,r,window.location.href,o),window.dispatchEvent(a)}function i(e){if(void 0===e&&(e=o),"undefined"==typeof window)throw new Error("Browser storage is not available on Node.js/Docusaurus SSR process.");if("none"===e)return null;try{return window[e]}catch(n){return t=n,l||(console.warn("Docusaurus browser storage is not available.\nPossible reasons: running Docusaurus in an iframe, in an incognito browser session, or using too strict browser privacy settings.",t),l=!0),null}var t}let l=!1;const s={get:()=>null,set:()=>{},del:()=>{},listen:()=>()=>{}};function c(e,t){const n=`${e}${r.M}`;if("undefined"==typeof window)return function(e){function t(){throw new Error(`Illegal storage API usage for storage key "${e}".\nDocusaurus storage APIs are not supposed to be called on the server-rendering process.\nPlease only call storage APIs in effects and event handlers.`)}return{get:t,set:t,del:t,listen:t}}(n);const o=i(t?.persistence);return null===o?s:{get:()=>{try{return o.getItem(n)}catch(e){return console.error(`Docusaurus storage error, can't get key=${n}`,e),null}},set:e=>{try{const t=o.getItem(n);o.setItem(n,e),a({key:n,oldValue:t,newValue:e,storage:o})}catch(t){console.error(`Docusaurus storage error, can't set ${n}=${e}`,t)}},del:()=>{try{const e=o.getItem(n);o.removeItem(n),a({key:n,oldValue:e,newValue:null,storage:o})}catch(e){console.error(`Docusaurus storage error, can't delete key=${n}`,e)}},listen:e=>{try{const t=t=>{t.storageArea===o&&t.key===n&&e(t)};return window.addEventListener("storage",t),()=>window.removeEventListener("storage",t)}catch(t){return console.error(`Docusaurus storage error, can't listen for changes of key=${n}`,t),()=>{}}}}}},2131:(e,t,n)=>{"use strict";n.d(t,{o:()=>i});var r=n(4586),o=n(6347),a=n(440);function i(){const{siteConfig:{baseUrl:e,url:t,trailingSlash:n},i18n:{defaultLocale:i,currentLocale:l}}=(0,r.A)(),{pathname:s}=(0,o.zy)(),c=(0,a.applyTrailingSlash)(s,{trailingSlash:n,baseUrl:e}),u=l===i?e:e.replace(`/${l}/`,"/"),d=c.replace(e,"");return{createUrl:function(e){let{locale:n,fullyQualified:r}=e;return`${r?t:""}${function(e){return e===i?`${u}`:`${u}${e}/`}(n)}${d}`}}}},5062:(e,t,n)=>{"use strict";n.d(t,{$:()=>i});var r=n(6540),o=n(6347),a=n(9532);function i(e){const t=(0,o.zy)(),n=(0,a.ZC)(t),i=(0,a._q)(e);(0,r.useEffect)((()=>{n&&t!==n&&i({location:t,previousLocation:n})}),[i,t,n])}},6342:(e,t,n)=>{"use strict";n.d(t,{p:()=>o});var r=n(4586);function o(){return(0,r.A)().siteConfig.themeConfig}},2983:(e,t,n)=>{"use strict";Object.defineProperty(t,"__esModule",{value:!0}),t.removeTrailingSlash=t.addLeadingSlash=t.addTrailingSlash=void 0;const r=n(2566);function o(e){return e.endsWith("/")?e:`${e}/`}function a(e){return(0,r.removeSuffix)(e,"/")}t.addTrailingSlash=o,t.default=function(e,t){const{trailingSlash:n,baseUrl:r}=t;if(e.startsWith("#"))return e;if(void 0===n)return e;const[i]=e.split(/[#?]/),l="/"===i||i===r?i:(s=i,n?o(s):a(s));var s;return e.replace(i,l)},t.addLeadingSlash=function(e){return(0,r.addPrefix)(e,"/")},t.removeTrailingSlash=a},253:(e,t)=>{"use strict";Object.defineProperty(t,"__esModule",{value:!0}),t.getErrorCausalChain=void 0,t.getErrorCausalChain=function e(t){return t.cause?[t,...e(t.cause)]:[t]}},440:function(e,t,n){"use strict";var r=this&&this.__importDefault||function(e){return e&&e.__esModule?e:{default:e}};Object.defineProperty(t,"__esModule",{value:!0}),t.getErrorCausalChain=t.removePrefix=t.addSuffix=t.removeSuffix=t.addPrefix=t.removeTrailingSlash=t.addLeadingSlash=t.addTrailingSlash=t.applyTrailingSlash=t.blogPostContainerID=void 0,t.blogPostContainerID="__blog-post-container";var o=n(2983);Object.defineProperty(t,"applyTrailingSlash",{enumerable:!0,get:function(){return r(o).default}}),Object.defineProperty(t,"addTrailingSlash",{enumerable:!0,get:function(){return o.addTrailingSlash}}),Object.defineProperty(t,"addLeadingSlash",{enumerable:!0,get:function(){return o.addLeadingSlash}}),Object.defineProperty(t,"removeTrailingSlash",{enumerable:!0,get:function(){return o.removeTrailingSlash}});var a=n(2566);Object.defineProperty(t,"addPrefix",{enumerable:!0,get:function(){return a.addPrefix}}),Object.defineProperty(t,"removeSuffix",{enumerable:!0,get:function(){return a.removeSuffix}}),Object.defineProperty(t,"addSuffix",{enumerable:!0,get:function(){return a.addSuffix}}),Object.defineProperty(t,"removePrefix",{enumerable:!0,get:function(){return a.removePrefix}});var i=n(253);Object.defineProperty(t,"getErrorCausalChain",{enumerable:!0,get:function(){return i.getErrorCausalChain}})},2566:(e,t)=>{"use strict";Object.defineProperty(t,"__esModule",{value:!0}),t.removePrefix=t.addSuffix=t.removeSuffix=t.addPrefix=void 0,t.addPrefix=function(e,t){return e.startsWith(t)?e:`${t}${e}`},t.removeSuffix=function(e,t){return""===t?e:e.endsWith(t)?e.slice(0,-t.length):e},t.addSuffix=function(e,t){return e.endsWith(t)?e:`${e}${t}`},t.removePrefix=function(e,t){return e.startsWith(t)?e.slice(t.length):e}},2849:(e,t,n)=>{"use strict";n.d(t,{A:()=>i});n(6540);var r=n(5391);const o={loadingRing:"loadingRing_RJI3","loading-ring":"loading-ring_FB5o"};var a=n(4848);function i(e){let{className:t}=e;return(0,a.jsxs)("div",{className:(0,r.A)(o.loadingRing,t),children:[(0,a.jsx)("div",{}),(0,a.jsx)("div",{}),(0,a.jsx)("div",{}),(0,a.jsx)("div",{})]})}},5891:(e,t,n)=>{"use strict";n.d(t,{Z:()=>l});var r=n(8291),o=n.n(r),a=n(1088);const i=new Map;function l(e,t){const n=`${e}${t}`;let r=i.get(n);return r||(r=async function(e,t){{const n=`${e}${a.IH.replace("{dir}",t?`-${t.replace(/\//g,"-")}`:"")}`;if(new URL(n,location.origin).origin!==location.origin)throw new Error("Unexpected version url");const r=await(await fetch(n)).json(),i=r.map(((e,t)=>{let{documents:n,index:r}=e;return{type:t,documents:n,index:o().Index.load(r)}})),l=r.reduce(((e,t)=>{for(const n of t.index.invertedIndex)/\p{Unified_Ideograph}/u.test(n[0][0])&&e.add(n[0]);return e}),new Set);return{wrappedIndexes:i,zhDictionary:Array.from(l)}}return{wrappedIndexes:[],zhDictionary:[]}}(e,t),i.set(n,r)),r}},2384:(e,t,n)=>{"use strict";n.d(t,{m:()=>c});var r=n(8291),o=n.n(r);var a=n(1088);function i(e){return l(e).concat(l(e.filter((e=>{const t=e[e.length-1];return!t.trailing&&t.maybeTyping})),!0))}function l(e,t){return e.map((e=>({tokens:e.map((e=>e.value)),term:e.map((e=>({value:e.value,presence:o().Query.presence.REQUIRED,wildcard:(t?e.trailing||e.maybeTyping:e.trailing)?o().Query.wildcard.TRAILING:o().Query.wildcard.NONE})))})))}var s=n(9913);function c(e,t,n){return function(r,l){const c=function(e,t){if(1===t.length&&["ja","jp","th"].includes(t[0]))return o()[t[0]].tokenizer(e).map((e=>e.toString()));let n=/[^-\s]+/g;return t.includes("zh")&&(n=/\w+|\p{Unified_Ideograph}+/gu),e.toLowerCase().match(n)||[]}(r,a.BH);if(0===c.length)return void l([]);const u=function(e,t){const n=function(e,t){const n=[];return function e(r,o){if(0===r.length)return void n.push(o);const a=r[0];if(/\p{Unified_Ideograph}/u.test(a)){const n=function(e,t){const n=[];return function e(r,o){let a=0,i=!1;for(const l of t)if(r.substr(0,l.length)===l){const t={missed:o.missed,term:o.term.concat({value:l})};r.length>l.length?e(r.substr(l.length),t):n.push(t),i=!0}else for(let t=l.length-1;t>a;t-=1){const s=l.substr(0,t);if(r.substr(0,t)===s){a=t;const l={missed:o.missed,term:o.term.concat({value:s,trailing:!0})};r.length>t?e(r.substr(t),l):n.push(l),i=!0;break}}i||(r.length>0?e(r.substr(1),{missed:o.missed+1,term:o.term}):o.term.length>0&&n.push(o))}(e,{missed:0,term:[]}),n.sort(((e,t)=>{const n=e.missed>0?1:0,r=t.missed>0?1:0;return n!==r?n-r:e.term.length-t.term.length})).map((e=>e.term))}(a,t);for(const t of n){const n=o.concat(...t);e(r.slice(1),n)}}else{const t=o.concat({value:a});e(r.slice(1),t)}}(e,[]),n}(e,t);if(0===n.length)return[{tokens:e,term:e.map((e=>({value:e,presence:o().Query.presence.REQUIRED,wildcard:o().Query.wildcard.LEADING|o().Query.wildcard.TRAILING})))}];for(const o of n)o[o.length-1].maybeTyping=!0;const r=[];for(const i of a.BH)if("en"===i)a.sx||r.unshift(o().stopWordFilter);else{const e=o()[i];e.stopWordFilter&&r.unshift(e.stopWordFilter)}let l;if(r.length>0){const e=e=>r.reduce(((e,t)=>e.filter((e=>t(e.value)))),e);l=[];const t=[];for(const r of n){const n=e(r);l.push(n),n.length0&&t.push(n)}n.push(...t)}else l=n.slice();const s=[];for(const o of l)if(o.length>2)for(let e=o.length-1;e>=0;e-=1)s.push(o.slice(0,e).concat(o.slice(e+1)));return i(n).concat(i(s))}(c,t),d=[];e:for(const{term:t,tokens:o}of u)for(const{documents:r,index:a,type:i}of e)if(d.push(...a.query((e=>{for(const n of t)e.term(n.value,{wildcard:n.wildcard,presence:n.presence})})).slice(0,n).filter((e=>!d.some((t=>t.document.i.toString()===e.ref)))).slice(0,n-d.length).map((t=>{const n=r.find((e=>e.i.toString()===t.ref));return{document:n,type:i,page:i!==s.i.Title&&e[0].documents.find((e=>e.i===n.p)),metadata:t.matchData.metadata,tokens:o,score:t.score}}))),d.length>=n)break e;!function(e){e.forEach(((e,t)=>{e.index=t})),e.sort(((t,n)=>{let r=t.type!==s.i.Heading&&t.type!==s.i.Content&&t.type!==s.i.Description||!t.page?t.index:e.findIndex((e=>e.document===t.page)),o=n.type!==s.i.Heading&&n.type!==s.i.Content&&n.type!==s.i.Description||!n.page?n.index:e.findIndex((e=>e.document===n.page));if(-1===r&&(r=t.index),-1===o&&(o=n.index),r===o){const e=(0===n.type?1:0)-(0===t.type?1:0);return 0===e?t.index-n.index:e}return r-o}))}(d),function(e){e.forEach(((t,n)=>{n>0&&t.page&&e.slice(0,n).some((e=>(e.type===s.i.Keywords?e.page:e.document)===t.page))&&(n{"use strict";function r(e){return e.join(" \u203a ")}n.d(t,{$:()=>r})},3103:(e,t,n)=>{"use strict";function r(e){return e.replace(/&/g,"&").replace(//g,">").replace(/"/g,""").replace(/'/g,"'")}n.d(t,{Z:()=>r})},7674:(e,t,n)=>{"use strict";function r(e,t){const n=[];for(const r of Object.values(e))r[t]&&n.push(...r[t].position);return n.sort(((e,t)=>e[0]-t[0]||t[1]-e[1]))}n.d(t,{g:()=>r})},6841:(e,t,n)=>{"use strict";n.d(t,{Z:()=>o});var r=n(3103);function o(e,t,n){const a=[];for(const i of t){const n=e.toLowerCase().indexOf(i);if(n>=0){n>0&&a.push(o(e.substr(0,n),t)),a.push(`${(0,r.Z)(e.substr(n,i.length))}`);const l=n+i.length;l${(0,r.Z)(e)}`:(0,r.Z)(e):a.join("")}},3810:(e,t,n)=>{"use strict";n.d(t,{C:()=>s});var r=n(3103),o=n(6841);const a=/\w+|\p{Unified_Ideograph}/u;function i(e){const t=[];let n=0,r=e;for(;r.length>0;){const o=r.match(a);if(!o){t.push(r);break}o.index>0&&t.push(r.substring(0,o.index)),t.push(o[0]),n+=o.index+o[0].length,r=e.substring(n)}return t}var l=n(1088);function s(e,t,n,a){void 0===a&&(a=l.rG);const{chunkIndex:s,chunks:c}=function(e,t,n){const a=[];let l=0,s=0,c=-1;for(;ls){const t=i(e.substring(s,u)).map((e=>({html:(0,r.Z)(e),textLength:e.length})));for(const e of t)a.push(e)}-1===c&&(c=a.length),s=u+d,a.push({html:(0,o.Z)(e.substring(u,s),n,!0),textLength:d})}}if(s({html:(0,r.Z)(e),textLength:e.length})));for(const e of t)a.push(e)}return{chunkIndex:c,chunks:a}}(e,t,n),u=c.slice(0,s),d=c[s],p=[d.html],f=c.slice(s+1);let h=d.textLength,m=0,g=0,b=!1,y=!1;for(;h0){const e=u.pop();h+e.textLength<=a?(p.unshift(e.html),m+=e.textLength,h+=e.textLength):(b=!0,u.length=0)}else{if(!(f.length>0))break;{const e=f.shift();h+e.textLength<=a?(p.push(e.html),g+=e.textLength,h+=e.textLength):(y=!0,f.length=0)}}return(b||u.length>0)&&p.unshift("\u2026"),(y||f.length>0)&&p.push("\u2026"),p.join("")}},3385:(e,t,n)=>{"use strict";function r(e,t){if("string"==typeof e)return{label:e,path:e};{const{label:n,path:r}=e;return"string"==typeof n?{label:n,path:r}:Object.prototype.hasOwnProperty.call(n,t)?{label:n[t],path:r}:{label:r,path:r}}}n.d(t,{p:()=>r})},1088:(e,t,n)=>{"use strict";n.d(t,{CU:()=>a,UB:()=>f,tb:()=>c,O6:()=>g,I$:()=>h,BH:()=>r,sx:()=>o,ZG:()=>p,WW:()=>u,pk:()=>d,Hg:()=>m,IH:()=>i,rG:()=>s,AT:()=>l,dz:()=>b});n(8291);const r=["en"],o=!1,a=null,i="search-index{dir}.json?_=b93ef5af",l=8,s=50,c=!1,u=!0,d=!0,p="right",f=void 0,h=!0,m=null,g=!1,b=!1},9913:(e,t,n)=>{"use strict";var r;n.d(t,{i:()=>r}),function(e){e[e.Title=0]="Title",e[e.Heading=1]="Heading",e[e.Description=2]="Description",e[e.Keywords=3]="Keywords",e[e.Content=4]="Content"}(r||(r={}))},3796:(e,t,n)=>{"use strict";n.r(t),n.d(t,{default:()=>f});var r=n(4784),o=Object.assign||function(e){for(var t=1;t1&&void 0!==arguments[1]?arguments[1]:{},r=window.Promise||function(e){function t(){}e(t,t)},a=function(){for(var e=arguments.length,t=Array(e),n=0;n0&&void 0!==arguments[0]?arguments[0]:{}).target,t=function(){var e={width:document.documentElement.clientWidth,height:document.documentElement.clientHeight,left:0,top:0,right:0,bottom:0},t=void 0,n=void 0;if(b.container)if(b.container instanceof Object)t=(e=o({},e,b.container)).width-e.left-e.right-2*b.margin,n=e.height-e.top-e.bottom-2*b.margin;else{var r=(i(b.container)?b.container:document.querySelector(b.container)).getBoundingClientRect(),a=r.width,s=r.height,c=r.left,u=r.top;e=o({},e,{width:a,height:s,left:c,top:u})}t=t||e.width-2*b.margin,n=n||e.height-2*b.margin;var d=y.zoomedHd||y.original,p=l(d)?t:d.naturalWidth||t,f=l(d)?n:d.naturalHeight||n,h=d.getBoundingClientRect(),m=h.top,g=h.left,v=h.width,w=h.height,x=Math.min(Math.max(v,p),t)/v,k=Math.min(Math.max(w,f),n)/w,S=Math.min(x,k),_="scale("+S+") translate3d("+((t-v)/2-g+b.margin+e.left)/S+"px, "+((n-w)/2-m+b.margin+e.top)/S+"px, 0)";y.zoomed.style.transform=_,y.zoomedHd&&(y.zoomedHd.style.transform=_)};return new r((function(n){if(e&&-1===f.indexOf(e))n(w);else{if(y.zoomed)n(w);else{if(e)y.original=e;else{if(!(f.length>0))return void n(w);var r=f;y.original=r[0]}if(y.original.dispatchEvent(c("medium-zoom:open",{detail:{zoom:w}})),g=window.pageYOffset||document.documentElement.scrollTop||document.body.scrollTop||0,m=!0,y.zoomed=function(e){var t=e.getBoundingClientRect(),n=t.top,r=t.left,o=t.width,a=t.height,i=e.cloneNode(),l=window.pageYOffset||document.documentElement.scrollTop||document.body.scrollTop||0,s=window.pageXOffset||document.documentElement.scrollLeft||document.body.scrollLeft||0;return i.removeAttribute("id"),i.style.position="absolute",i.style.top=n+l+"px",i.style.left=r+s+"px",i.style.width=o+"px",i.style.height=a+"px",i.style.transform="",i}(y.original),document.body.appendChild(v),b.template){var o=i(b.template)?b.template:document.querySelector(b.template);y.template=document.createElement("div"),y.template.appendChild(o.content.cloneNode(!0)),document.body.appendChild(y.template)}if(y.original.parentElement&&"PICTURE"===y.original.parentElement.tagName&&y.original.currentSrc&&(y.zoomed.src=y.original.currentSrc),document.body.appendChild(y.zoomed),window.requestAnimationFrame((function(){document.body.classList.add("medium-zoom--opened")})),y.original.classList.add("medium-zoom-image--hidden"),y.zoomed.classList.add("medium-zoom-image--opened"),y.zoomed.addEventListener("click",d),y.zoomed.addEventListener("transitionend",(function e(){m=!1,y.zoomed.removeEventListener("transitionend",e),y.original.dispatchEvent(c("medium-zoom:opened",{detail:{zoom:w}})),n(w)})),y.original.getAttribute("data-zoom-src")){y.zoomedHd=y.zoomed.cloneNode(),y.zoomedHd.removeAttribute("srcset"),y.zoomedHd.removeAttribute("sizes"),y.zoomedHd.removeAttribute("loading"),y.zoomedHd.src=y.zoomed.getAttribute("data-zoom-src"),y.zoomedHd.onerror=function(){clearInterval(a),console.warn("Unable to reach the zoom image target "+y.zoomedHd.src),y.zoomedHd=null,t()};var a=setInterval((function(){y.zoomedHd.complete&&(clearInterval(a),y.zoomedHd.classList.add("medium-zoom-image--opened"),y.zoomedHd.addEventListener("click",d),document.body.appendChild(y.zoomedHd),t())}),10)}else if(y.original.hasAttribute("srcset")){y.zoomedHd=y.zoomed.cloneNode(),y.zoomedHd.removeAttribute("sizes"),y.zoomedHd.removeAttribute("loading");var l=y.zoomedHd.addEventListener("load",(function(){y.zoomedHd.removeEventListener("load",l),y.zoomedHd.classList.add("medium-zoom-image--opened"),y.zoomedHd.addEventListener("click",d),document.body.appendChild(y.zoomedHd),t()}))}else t()}}}))},d=function(){return new r((function(e){if(!m&&y.original){m=!0,document.body.classList.remove("medium-zoom--opened"),y.zoomed.style.transform="",y.zoomedHd&&(y.zoomedHd.style.transform=""),y.template&&(y.template.style.transition="opacity 150ms",y.template.style.opacity=0),y.original.dispatchEvent(c("medium-zoom:close",{detail:{zoom:w}})),y.zoomed.addEventListener("transitionend",(function t(){y.original.classList.remove("medium-zoom-image--hidden"),document.body.removeChild(y.zoomed),y.zoomedHd&&document.body.removeChild(y.zoomedHd),document.body.removeChild(v),y.zoomed.classList.remove("medium-zoom-image--opened"),y.template&&document.body.removeChild(y.template),m=!1,y.zoomed.removeEventListener("transitionend",t),y.original.dispatchEvent(c("medium-zoom:closed",{detail:{zoom:w}})),y.original=null,y.zoomed=null,y.zoomedHd=null,y.template=null,e(w)}))}else e(w)}))},p=function(){var e=(arguments.length>0&&void 0!==arguments[0]?arguments[0]:{}).target;return y.original?d():u({target:e})},f=[],h=[],m=!1,g=0,b=n,y={original:null,zoomed:null,zoomedHd:null,template:null};"[object Object]"===Object.prototype.toString.call(t)?b=t:(t||"string"==typeof t)&&a(t);var v=function(e){var t=document.createElement("div");return t.classList.add("medium-zoom-overlay"),t.style.background=e,t}((b=o({margin:0,background:"#fff",scrollOffset:40,container:null,template:null},b)).background);document.addEventListener("click",(function(e){var t=e.target;t!==v?-1!==f.indexOf(t)&&p({target:t}):d()})),document.addEventListener("keyup",(function(e){var t=e.key||e.keyCode;"Escape"!==t&&"Esc"!==t&&27!==t||d()})),document.addEventListener("scroll",(function(){if(!m&&y.original){var e=window.pageYOffset||document.documentElement.scrollTop||document.body.scrollTop||0;Math.abs(g-e)>b.scrollOffset&&setTimeout(d,150)}})),window.addEventListener("resize",d);var w={open:u,close:d,toggle:p,update:function(){var e=arguments.length>0&&void 0!==arguments[0]?arguments[0]:{},t=e;if(e.background&&(v.style.background=e.background),e.container&&e.container instanceof Object&&(t.container=o({},b.container,e.container)),e.template){var n=i(e.template)?e.template:document.querySelector(e.template);t.template=n}return b=o({},b,t),f.forEach((function(e){e.dispatchEvent(c("medium-zoom:update",{detail:{zoom:w}}))})),w},clone:function(){return e(o({},b,arguments.length>0&&void 0!==arguments[0]?arguments[0]:{}))},attach:a,detach:function(){for(var e=arguments.length,t=Array(e),n=0;n0?t.reduce((function(e,t){return[].concat(e,s(t))}),[]):f;return r.forEach((function(e){e.classList.remove("medium-zoom-image"),e.dispatchEvent(c("medium-zoom:detach",{detail:{zoom:w}}))})),f=f.filter((function(e){return-1===r.indexOf(e)})),w},on:function(e,t){var n=arguments.length>2&&void 0!==arguments[2]?arguments[2]:{};return f.forEach((function(r){r.addEventListener("medium-zoom:"+e,t,n)})),h.push({type:"medium-zoom:"+e,listener:t,options:n}),w},off:function(e,t){var n=arguments.length>2&&void 0!==arguments[2]?arguments[2]:{};return f.forEach((function(r){r.removeEventListener("medium-zoom:"+e,t,n)})),h=h.filter((function(n){return!(n.type==="medium-zoom:"+e&&n.listener.toString()===t.toString())})),w},getOptions:function(){return b},getImages:function(){return f},getZoomedImage:function(){return y.original}};return w},{themeConfig:d}=r.default;function p(e){var t,n;return document.querySelector('html[data-theme="dark"]')?(null===(t=e.background)||void 0===t?void 0:t.dark)||"rgb(50, 50, 50)":(null===(n=e.background)||void 0===n?void 0:n.light)||"rgb(255, 255, 255)"}const f=function(){if("undefined"==typeof window)return null;let e;const{zoom:t}=d,{selector:n=".markdown img",config:r={}}=t||{};if(!t)return null;r.background=p(t);var o=new MutationObserver((function(){e&&e.update({background:p(t)})}));const a=document.querySelector("html");return o.observe(a,{attributes:!0,attributeFilter:["data-theme"]}),setTimeout((()=>{e&&e.detach(),e=u(n,r)}),1e3),{onRouteUpdate(){setTimeout((()=>{e&&e.detach(),e=u(n,r)}),1e3)}}}()},1513:(e,t,n)=>{"use strict";n.d(t,{zR:()=>w,TM:()=>C,yJ:()=>f,sC:()=>A,AO:()=>p});var r=n(8168);function o(e){return"/"===e.charAt(0)}function a(e,t){for(var n=t,r=n+1,o=e.length;r=0;p--){var f=i[p];"."===f?a(i,p):".."===f?(a(i,p),d++):d&&(a(i,p),d--)}if(!c)for(;d--;d)i.unshift("..");!c||""===i[0]||i[0]&&o(i[0])||i.unshift("");var h=i.join("/");return n&&"/"!==h.substr(-1)&&(h+="/"),h};var l=n(1561);function s(e){return"/"===e.charAt(0)?e:"/"+e}function c(e){return"/"===e.charAt(0)?e.substr(1):e}function u(e,t){return function(e,t){return 0===e.toLowerCase().indexOf(t.toLowerCase())&&-1!=="/?#".indexOf(e.charAt(t.length))}(e,t)?e.substr(t.length):e}function d(e){return"/"===e.charAt(e.length-1)?e.slice(0,-1):e}function p(e){var t=e.pathname,n=e.search,r=e.hash,o=t||"/";return n&&"?"!==n&&(o+="?"===n.charAt(0)?n:"?"+n),r&&"#"!==r&&(o+="#"===r.charAt(0)?r:"#"+r),o}function f(e,t,n,o){var a;"string"==typeof e?(a=function(e){var t=e||"/",n="",r="",o=t.indexOf("#");-1!==o&&(r=t.substr(o),t=t.substr(0,o));var a=t.indexOf("?");return-1!==a&&(n=t.substr(a),t=t.substr(0,a)),{pathname:t,search:"?"===n?"":n,hash:"#"===r?"":r}}(e),a.state=t):(void 0===(a=(0,r.A)({},e)).pathname&&(a.pathname=""),a.search?"?"!==a.search.charAt(0)&&(a.search="?"+a.search):a.search="",a.hash?"#"!==a.hash.charAt(0)&&(a.hash="#"+a.hash):a.hash="",void 0!==t&&void 0===a.state&&(a.state=t));try{a.pathname=decodeURI(a.pathname)}catch(l){throw l instanceof URIError?new URIError('Pathname "'+a.pathname+'" could not be decoded. This is likely caused by an invalid percent-encoding.'):l}return n&&(a.key=n),o?a.pathname?"/"!==a.pathname.charAt(0)&&(a.pathname=i(a.pathname,o.pathname)):a.pathname=o.pathname:a.pathname||(a.pathname="/"),a}function h(){var e=null;var t=[];return{setPrompt:function(t){return e=t,function(){e===t&&(e=null)}},confirmTransitionTo:function(t,n,r,o){if(null!=e){var a="function"==typeof e?e(t,n):e;"string"==typeof a?"function"==typeof r?r(a,o):o(!0):o(!1!==a)}else o(!0)},appendListener:function(e){var n=!0;function r(){n&&e.apply(void 0,arguments)}return t.push(r),function(){n=!1,t=t.filter((function(e){return e!==r}))}},notifyListeners:function(){for(var e=arguments.length,n=new Array(e),r=0;rt?n.splice(t,n.length-t,o):n.push(o),d({action:r,location:o,index:t,entries:n})}}))},replace:function(e,t){var r="REPLACE",o=f(e,t,m(),w.location);u.confirmTransitionTo(o,r,n,(function(e){e&&(w.entries[w.index]=o,d({action:r,location:o}))}))},go:v,goBack:function(){v(-1)},goForward:function(){v(1)},canGo:function(e){var t=w.index+e;return t>=0&&t{"use strict";var r=n(4363),o={childContextTypes:!0,contextType:!0,contextTypes:!0,defaultProps:!0,displayName:!0,getDefaultProps:!0,getDerivedStateFromError:!0,getDerivedStateFromProps:!0,mixins:!0,propTypes:!0,type:!0},a={name:!0,length:!0,prototype:!0,caller:!0,callee:!0,arguments:!0,arity:!0},i={$$typeof:!0,compare:!0,defaultProps:!0,displayName:!0,propTypes:!0,type:!0},l={};function s(e){return r.isMemo(e)?i:l[e.$$typeof]||o}l[r.ForwardRef]={$$typeof:!0,render:!0,defaultProps:!0,displayName:!0,propTypes:!0},l[r.Memo]=i;var c=Object.defineProperty,u=Object.getOwnPropertyNames,d=Object.getOwnPropertySymbols,p=Object.getOwnPropertyDescriptor,f=Object.getPrototypeOf,h=Object.prototype;e.exports=function e(t,n,r){if("string"!=typeof n){if(h){var o=f(n);o&&o!==h&&e(t,o,r)}var i=u(n);d&&(i=i.concat(d(n)));for(var l=s(t),m=s(n),g=0;g{"use strict";e.exports=function(e,t,n,r,o,a,i,l){if(!e){var s;if(void 0===t)s=new Error("Minified exception occurred; use the non-minified dev environment for the full error message and additional helpful warnings.");else{var c=[n,r,o,a,i,l],u=0;(s=new Error(t.replace(/%s/g,(function(){return c[u++]})))).name="Invariant Violation"}throw s.framesToPop=1,s}}},4634:e=>{e.exports=Array.isArray||function(e){return"[object Array]"==Object.prototype.toString.call(e)}},8291:(e,t,n)=>{var r,o;!function(){var a,i,l,s,c,u,d,p,f,h,m,g,b,y,v,w,x,k,S,_,E,C,T,A,L,j,P,R,N,O,I=function(e){var t=new I.Builder;return t.pipeline.add(I.trimmer,I.stopWordFilter,I.stemmer),t.searchPipeline.add(I.stemmer),e.call(t,t),t.build()};I.version="2.3.9",I.utils={},I.utils.warn=(a=this,function(e){a.console&&console.warn&&console.warn(e)}),I.utils.asString=function(e){return null==e?"":e.toString()},I.utils.clone=function(e){if(null==e)return e;for(var t=Object.create(null),n=Object.keys(e),r=0;r0){var s=I.utils.clone(t)||{};s.position=[i,l],s.index=o.length,o.push(new I.Token(n.slice(i,a),s))}i=a+1}}return o},I.tokenizer.separator=/[\s\-]+/,I.Pipeline=function(){this._stack=[]},I.Pipeline.registeredFunctions=Object.create(null),I.Pipeline.registerFunction=function(e,t){t in this.registeredFunctions&&I.utils.warn("Overwriting existing registered function: "+t),e.label=t,I.Pipeline.registeredFunctions[e.label]=e},I.Pipeline.warnIfFunctionNotRegistered=function(e){e.label&&e.label in this.registeredFunctions||I.utils.warn("Function is not registered with pipeline. This may cause problems when serialising the index.\n",e)},I.Pipeline.load=function(e){var t=new I.Pipeline;return e.forEach((function(e){var n=I.Pipeline.registeredFunctions[e];if(!n)throw new Error("Cannot load unregistered function: "+e);t.add(n)})),t},I.Pipeline.prototype.add=function(){Array.prototype.slice.call(arguments).forEach((function(e){I.Pipeline.warnIfFunctionNotRegistered(e),this._stack.push(e)}),this)},I.Pipeline.prototype.after=function(e,t){I.Pipeline.warnIfFunctionNotRegistered(t);var n=this._stack.indexOf(e);if(-1==n)throw new Error("Cannot find existingFn");n+=1,this._stack.splice(n,0,t)},I.Pipeline.prototype.before=function(e,t){I.Pipeline.warnIfFunctionNotRegistered(t);var n=this._stack.indexOf(e);if(-1==n)throw new Error("Cannot find existingFn");this._stack.splice(n,0,t)},I.Pipeline.prototype.remove=function(e){var t=this._stack.indexOf(e);-1!=t&&this._stack.splice(t,1)},I.Pipeline.prototype.run=function(e){for(var t=this._stack.length,n=0;n1&&(ae&&(n=o),a!=e);)r=n-t,o=t+Math.floor(r/2),a=this.elements[2*o];return a==e||a>e?2*o:al?c+=2:i==l&&(t+=n[s+1]*r[c+1],s+=2,c+=2);return t},I.Vector.prototype.similarity=function(e){return this.dot(e)/this.magnitude()||0},I.Vector.prototype.toArray=function(){for(var e=new Array(this.elements.length/2),t=1,n=0;t0){var a,i=o.str.charAt(0);i in o.node.edges?a=o.node.edges[i]:(a=new I.TokenSet,o.node.edges[i]=a),1==o.str.length&&(a.final=!0),r.push({node:a,editsRemaining:o.editsRemaining,str:o.str.slice(1)})}if(0!=o.editsRemaining){if("*"in o.node.edges)var l=o.node.edges["*"];else{l=new I.TokenSet;o.node.edges["*"]=l}if(0==o.str.length&&(l.final=!0),r.push({node:l,editsRemaining:o.editsRemaining-1,str:o.str}),o.str.length>1&&r.push({node:o.node,editsRemaining:o.editsRemaining-1,str:o.str.slice(1)}),1==o.str.length&&(o.node.final=!0),o.str.length>=1){if("*"in o.node.edges)var s=o.node.edges["*"];else{s=new I.TokenSet;o.node.edges["*"]=s}1==o.str.length&&(s.final=!0),r.push({node:s,editsRemaining:o.editsRemaining-1,str:o.str.slice(1)})}if(o.str.length>1){var c,u=o.str.charAt(0),d=o.str.charAt(1);d in o.node.edges?c=o.node.edges[d]:(c=new I.TokenSet,o.node.edges[d]=c),1==o.str.length&&(c.final=!0),r.push({node:c,editsRemaining:o.editsRemaining-1,str:u+o.str.slice(2)})}}}return n},I.TokenSet.fromString=function(e){for(var t=new I.TokenSet,n=t,r=0,o=e.length;r=e;t--){var n=this.uncheckedNodes[t],r=n.child.toString();r in this.minimizedNodes?n.parent.edges[n.char]=this.minimizedNodes[r]:(n.child._str=r,this.minimizedNodes[r]=n.child),this.uncheckedNodes.pop()}},I.Index=function(e){this.invertedIndex=e.invertedIndex,this.fieldVectors=e.fieldVectors,this.tokenSet=e.tokenSet,this.fields=e.fields,this.pipeline=e.pipeline},I.Index.prototype.search=function(e){return this.query((function(t){new I.QueryParser(e,t).parse()}))},I.Index.prototype.query=function(e){for(var t=new I.Query(this.fields),n=Object.create(null),r=Object.create(null),o=Object.create(null),a=Object.create(null),i=Object.create(null),l=0;l1?1:e},I.Builder.prototype.k1=function(e){this._k1=e},I.Builder.prototype.add=function(e,t){var n=e[this._ref],r=Object.keys(this._fields);this._documents[n]=t||{},this.documentCount+=1;for(var o=0;o=this.length)return I.QueryLexer.EOS;var e=this.str.charAt(this.pos);return this.pos+=1,e},I.QueryLexer.prototype.width=function(){return this.pos-this.start},I.QueryLexer.prototype.ignore=function(){this.start==this.pos&&(this.pos+=1),this.start=this.pos},I.QueryLexer.prototype.backup=function(){this.pos-=1},I.QueryLexer.prototype.acceptDigitRun=function(){var e,t;do{t=(e=this.next()).charCodeAt(0)}while(t>47&&t<58);e!=I.QueryLexer.EOS&&this.backup()},I.QueryLexer.prototype.more=function(){return this.pos1&&(e.backup(),e.emit(I.QueryLexer.TERM)),e.ignore(),e.more())return I.QueryLexer.lexText},I.QueryLexer.lexEditDistance=function(e){return e.ignore(),e.acceptDigitRun(),e.emit(I.QueryLexer.EDIT_DISTANCE),I.QueryLexer.lexText},I.QueryLexer.lexBoost=function(e){return e.ignore(),e.acceptDigitRun(),e.emit(I.QueryLexer.BOOST),I.QueryLexer.lexText},I.QueryLexer.lexEOS=function(e){e.width()>0&&e.emit(I.QueryLexer.TERM)},I.QueryLexer.termSeparator=I.tokenizer.separator,I.QueryLexer.lexText=function(e){for(;;){var t=e.next();if(t==I.QueryLexer.EOS)return I.QueryLexer.lexEOS;if(92!=t.charCodeAt(0)){if(":"==t)return I.QueryLexer.lexField;if("~"==t)return e.backup(),e.width()>0&&e.emit(I.QueryLexer.TERM),I.QueryLexer.lexEditDistance;if("^"==t)return e.backup(),e.width()>0&&e.emit(I.QueryLexer.TERM),I.QueryLexer.lexBoost;if("+"==t&&1===e.width())return e.emit(I.QueryLexer.PRESENCE),I.QueryLexer.lexText;if("-"==t&&1===e.width())return e.emit(I.QueryLexer.PRESENCE),I.QueryLexer.lexText;if(t.match(I.QueryLexer.termSeparator))return I.QueryLexer.lexTerm}else e.escapeCharacter()}},I.QueryParser=function(e,t){this.lexer=new I.QueryLexer(e),this.query=t,this.currentClause={},this.lexemeIdx=0},I.QueryParser.prototype.parse=function(){this.lexer.run(),this.lexemes=this.lexer.lexemes;for(var e=I.QueryParser.parseClause;e;)e=e(this);return this.query},I.QueryParser.prototype.peekLexeme=function(){return this.lexemes[this.lexemeIdx]},I.QueryParser.prototype.consumeLexeme=function(){var e=this.peekLexeme();return this.lexemeIdx+=1,e},I.QueryParser.prototype.nextClause=function(){var e=this.currentClause;this.query.clause(e),this.currentClause={}},I.QueryParser.parseClause=function(e){var t=e.peekLexeme();if(null!=t)switch(t.type){case I.QueryLexer.PRESENCE:return I.QueryParser.parsePresence;case I.QueryLexer.FIELD:return I.QueryParser.parseField;case I.QueryLexer.TERM:return I.QueryParser.parseTerm;default:var n="expected either a field or a term, found "+t.type;throw t.str.length>=1&&(n+=" with value '"+t.str+"'"),new I.QueryParseError(n,t.start,t.end)}},I.QueryParser.parsePresence=function(e){var t=e.consumeLexeme();if(null!=t){switch(t.str){case"-":e.currentClause.presence=I.Query.presence.PROHIBITED;break;case"+":e.currentClause.presence=I.Query.presence.REQUIRED;break;default:var n="unrecognised presence operator'"+t.str+"'";throw new I.QueryParseError(n,t.start,t.end)}var r=e.peekLexeme();if(null==r){n="expecting term or field, found nothing";throw new I.QueryParseError(n,t.start,t.end)}switch(r.type){case I.QueryLexer.FIELD:return I.QueryParser.parseField;case I.QueryLexer.TERM:return I.QueryParser.parseTerm;default:n="expecting term or field, found '"+r.type+"'";throw new I.QueryParseError(n,r.start,r.end)}}},I.QueryParser.parseField=function(e){var t=e.consumeLexeme();if(null!=t){if(-1==e.query.allFields.indexOf(t.str)){var n=e.query.allFields.map((function(e){return"'"+e+"'"})).join(", "),r="unrecognised field '"+t.str+"', possible fields: "+n;throw new I.QueryParseError(r,t.start,t.end)}e.currentClause.fields=[t.str];var o=e.peekLexeme();if(null==o){r="expecting term, found nothing";throw new I.QueryParseError(r,t.start,t.end)}if(o.type===I.QueryLexer.TERM)return I.QueryParser.parseTerm;r="expecting term, found '"+o.type+"'";throw new I.QueryParseError(r,o.start,o.end)}},I.QueryParser.parseTerm=function(e){var t=e.consumeLexeme();if(null!=t){e.currentClause.term=t.str.toLowerCase(),-1!=t.str.indexOf("*")&&(e.currentClause.usePipeline=!1);var n=e.peekLexeme();if(null!=n)switch(n.type){case I.QueryLexer.TERM:return e.nextClause(),I.QueryParser.parseTerm;case I.QueryLexer.FIELD:return e.nextClause(),I.QueryParser.parseField;case I.QueryLexer.EDIT_DISTANCE:return I.QueryParser.parseEditDistance;case I.QueryLexer.BOOST:return I.QueryParser.parseBoost;case I.QueryLexer.PRESENCE:return e.nextClause(),I.QueryParser.parsePresence;default:var r="Unexpected lexeme type '"+n.type+"'";throw new I.QueryParseError(r,n.start,n.end)}else e.nextClause()}},I.QueryParser.parseEditDistance=function(e){var t=e.consumeLexeme();if(null!=t){var n=parseInt(t.str,10);if(isNaN(n)){var r="edit distance must be numeric";throw new I.QueryParseError(r,t.start,t.end)}e.currentClause.editDistance=n;var o=e.peekLexeme();if(null!=o)switch(o.type){case I.QueryLexer.TERM:return e.nextClause(),I.QueryParser.parseTerm;case I.QueryLexer.FIELD:return e.nextClause(),I.QueryParser.parseField;case I.QueryLexer.EDIT_DISTANCE:return I.QueryParser.parseEditDistance;case I.QueryLexer.BOOST:return I.QueryParser.parseBoost;case I.QueryLexer.PRESENCE:return e.nextClause(),I.QueryParser.parsePresence;default:r="Unexpected lexeme type '"+o.type+"'";throw new I.QueryParseError(r,o.start,o.end)}else e.nextClause()}},I.QueryParser.parseBoost=function(e){var t=e.consumeLexeme();if(null!=t){var n=parseInt(t.str,10);if(isNaN(n)){var r="boost must be numeric";throw new I.QueryParseError(r,t.start,t.end)}e.currentClause.boost=n;var o=e.peekLexeme();if(null!=o)switch(o.type){case I.QueryLexer.TERM:return e.nextClause(),I.QueryParser.parseTerm;case I.QueryLexer.FIELD:return e.nextClause(),I.QueryParser.parseField;case I.QueryLexer.EDIT_DISTANCE:return I.QueryParser.parseEditDistance;case I.QueryLexer.BOOST:return I.QueryParser.parseBoost;case I.QueryLexer.PRESENCE:return e.nextClause(),I.QueryParser.parsePresence;default:r="Unexpected lexeme type '"+o.type+"'";throw new I.QueryParseError(r,o.start,o.end)}else e.nextClause()}},void 0===(o="function"==typeof(r=function(){return I})?r.call(t,n,t,e):r)||(e.exports=o)}()},119:(e,t,n)=>{"use strict";n.r(t)},1043:(e,t,n)=>{"use strict";n.r(t)},5947:function(e,t,n){var r,o;r=function(){var e,t,n={version:"0.2.0"},r=n.settings={minimum:.08,easing:"ease",positionUsing:"",speed:200,trickle:!0,trickleRate:.02,trickleSpeed:800,showSpinner:!0,barSelector:'[role="bar"]',spinnerSelector:'[role="spinner"]',parent:"body",template:'
'};function o(e,t,n){return en?n:e}function a(e){return 100*(-1+e)}function i(e,t,n){var o;return(o="translate3d"===r.positionUsing?{transform:"translate3d("+a(e)+"%,0,0)"}:"translate"===r.positionUsing?{transform:"translate("+a(e)+"%,0)"}:{"margin-left":a(e)+"%"}).transition="all "+t+"ms "+n,o}n.configure=function(e){var t,n;for(t in e)void 0!==(n=e[t])&&e.hasOwnProperty(t)&&(r[t]=n);return this},n.status=null,n.set=function(e){var t=n.isStarted();e=o(e,r.minimum,1),n.status=1===e?null:e;var a=n.render(!t),c=a.querySelector(r.barSelector),u=r.speed,d=r.easing;return a.offsetWidth,l((function(t){""===r.positionUsing&&(r.positionUsing=n.getPositioningCSS()),s(c,i(e,u,d)),1===e?(s(a,{transition:"none",opacity:1}),a.offsetWidth,setTimeout((function(){s(a,{transition:"all "+u+"ms linear",opacity:0}),setTimeout((function(){n.remove(),t()}),u)}),u)):setTimeout(t,u)})),this},n.isStarted=function(){return"number"==typeof n.status},n.start=function(){n.status||n.set(0);var e=function(){setTimeout((function(){n.status&&(n.trickle(),e())}),r.trickleSpeed)};return r.trickle&&e(),this},n.done=function(e){return e||n.status?n.inc(.3+.5*Math.random()).set(1):this},n.inc=function(e){var t=n.status;return t?("number"!=typeof e&&(e=(1-t)*o(Math.random()*t,.1,.95)),t=o(t+e,0,.994),n.set(t)):n.start()},n.trickle=function(){return n.inc(Math.random()*r.trickleRate)},e=0,t=0,n.promise=function(r){return r&&"resolved"!==r.state()?(0===t&&n.start(),e++,t++,r.always((function(){0==--t?(e=0,n.done()):n.set((e-t)/e)})),this):this},n.render=function(e){if(n.isRendered())return document.getElementById("nprogress");u(document.documentElement,"nprogress-busy");var t=document.createElement("div");t.id="nprogress",t.innerHTML=r.template;var o,i=t.querySelector(r.barSelector),l=e?"-100":a(n.status||0),c=document.querySelector(r.parent);return s(i,{transition:"all 0 linear",transform:"translate3d("+l+"%,0,0)"}),r.showSpinner||(o=t.querySelector(r.spinnerSelector))&&f(o),c!=document.body&&u(c,"nprogress-custom-parent"),c.appendChild(t),t},n.remove=function(){d(document.documentElement,"nprogress-busy"),d(document.querySelector(r.parent),"nprogress-custom-parent");var e=document.getElementById("nprogress");e&&f(e)},n.isRendered=function(){return!!document.getElementById("nprogress")},n.getPositioningCSS=function(){var e=document.body.style,t="WebkitTransform"in e?"Webkit":"MozTransform"in e?"Moz":"msTransform"in e?"ms":"OTransform"in e?"O":"";return t+"Perspective"in e?"translate3d":t+"Transform"in e?"translate":"margin"};var l=function(){var e=[];function t(){var n=e.shift();n&&n(t)}return function(n){e.push(n),1==e.length&&t()}}(),s=function(){var e=["Webkit","O","Moz","ms"],t={};function n(e){return e.replace(/^-ms-/,"ms-").replace(/-([\da-z])/gi,(function(e,t){return t.toUpperCase()}))}function r(t){var n=document.body.style;if(t in n)return t;for(var r,o=e.length,a=t.charAt(0).toUpperCase()+t.slice(1);o--;)if((r=e[o]+a)in n)return r;return t}function o(e){return e=n(e),t[e]||(t[e]=r(e))}function a(e,t,n){t=o(t),e.style[t]=n}return function(e,t){var n,r,o=arguments;if(2==o.length)for(n in t)void 0!==(r=t[n])&&t.hasOwnProperty(n)&&a(e,n,r);else a(e,o[1],o[2])}}();function c(e,t){return("string"==typeof e?e:p(e)).indexOf(" "+t+" ")>=0}function u(e,t){var n=p(e),r=n+t;c(n,t)||(e.className=r.substring(1))}function d(e,t){var n,r=p(e);c(e,t)&&(n=r.replace(" "+t+" "," "),e.className=n.substring(1,n.length-1))}function p(e){return(" "+(e.className||"")+" ").replace(/\s+/gi," ")}function f(e){e&&e.parentNode&&e.parentNode.removeChild(e)}return n},void 0===(o="function"==typeof r?r.call(t,n,t,e):r)||(e.exports=o)},5302:(e,t,n)=>{var r=n(4634);e.exports=f,e.exports.parse=a,e.exports.compile=function(e,t){return l(a(e,t),t)},e.exports.tokensToFunction=l,e.exports.tokensToRegExp=p;var o=new RegExp(["(\\\\.)","([\\/.])?(?:(?:\\:(\\w+)(?:\\(((?:\\\\.|[^\\\\()])+)\\))?|\\(((?:\\\\.|[^\\\\()])+)\\))([+*?])?|(\\*))"].join("|"),"g");function a(e,t){for(var n,r=[],a=0,i=0,l="",u=t&&t.delimiter||"/";null!=(n=o.exec(e));){var d=n[0],p=n[1],f=n.index;if(l+=e.slice(i,f),i=f+d.length,p)l+=p[1];else{var h=e[i],m=n[2],g=n[3],b=n[4],y=n[5],v=n[6],w=n[7];l&&(r.push(l),l="");var x=null!=m&&null!=h&&h!==m,k="+"===v||"*"===v,S="?"===v||"*"===v,_=n[2]||u,E=b||y;r.push({name:g||a++,prefix:m||"",delimiter:_,optional:S,repeat:k,partial:x,asterisk:!!w,pattern:E?c(E):w?".*":"[^"+s(_)+"]+?"})}}return i{e.exports&&(e.exports={core:{meta:{path:"components/prism-core.js",option:"mandatory"},core:"Core"},themes:{meta:{path:"themes/{id}.css",link:"index.html?theme={id}",exclusive:!0},prism:{title:"Default",option:"default"},"prism-dark":"Dark","prism-funky":"Funky","prism-okaidia":{title:"Okaidia",owner:"ocodia"},"prism-twilight":{title:"Twilight",owner:"remybach"},"prism-coy":{title:"Coy",owner:"tshedor"},"prism-solarizedlight":{title:"Solarized Light",owner:"hectormatos2011 "},"prism-tomorrow":{title:"Tomorrow Night",owner:"Rosey"}},languages:{meta:{path:"components/prism-{id}",noCSS:!0,examplesPath:"examples/prism-{id}",addCheckAll:!0},markup:{title:"Markup",alias:["html","xml","svg","mathml","ssml","atom","rss"],aliasTitles:{html:"HTML",xml:"XML",svg:"SVG",mathml:"MathML",ssml:"SSML",atom:"Atom",rss:"RSS"},option:"default"},css:{title:"CSS",option:"default",modify:"markup"},clike:{title:"C-like",option:"default"},javascript:{title:"JavaScript",require:"clike",modify:"markup",optional:"regex",alias:"js",option:"default"},abap:{title:"ABAP",owner:"dellagustin"},abnf:{title:"ABNF",owner:"RunDevelopment"},actionscript:{title:"ActionScript",require:"javascript",modify:"markup",owner:"Golmote"},ada:{title:"Ada",owner:"Lucretia"},agda:{title:"Agda",owner:"xy-ren"},al:{title:"AL",owner:"RunDevelopment"},antlr4:{title:"ANTLR4",alias:"g4",owner:"RunDevelopment"},apacheconf:{title:"Apache Configuration",owner:"GuiTeK"},apex:{title:"Apex",require:["clike","sql"],owner:"RunDevelopment"},apl:{title:"APL",owner:"ngn"},applescript:{title:"AppleScript",owner:"Golmote"},aql:{title:"AQL",owner:"RunDevelopment"},arduino:{title:"Arduino",require:"cpp",alias:"ino",owner:"dkern"},arff:{title:"ARFF",owner:"Golmote"},armasm:{title:"ARM Assembly",alias:"arm-asm",owner:"RunDevelopment"},arturo:{title:"Arturo",alias:"art",optional:["bash","css","javascript","markup","markdown","sql"],owner:"drkameleon"},asciidoc:{alias:"adoc",title:"AsciiDoc",owner:"Golmote"},aspnet:{title:"ASP.NET (C#)",require:["markup","csharp"],owner:"nauzilus"},asm6502:{title:"6502 Assembly",owner:"kzurawel"},asmatmel:{title:"Atmel AVR Assembly",owner:"cerkit"},autohotkey:{title:"AutoHotkey",owner:"aviaryan"},autoit:{title:"AutoIt",owner:"Golmote"},avisynth:{title:"AviSynth",alias:"avs",owner:"Zinfidel"},"avro-idl":{title:"Avro IDL",alias:"avdl",owner:"RunDevelopment"},awk:{title:"AWK",alias:"gawk",aliasTitles:{gawk:"GAWK"},owner:"RunDevelopment"},bash:{title:"Bash",alias:["sh","shell"],aliasTitles:{sh:"Shell",shell:"Shell"},owner:"zeitgeist87"},basic:{title:"BASIC",owner:"Golmote"},batch:{title:"Batch",owner:"Golmote"},bbcode:{title:"BBcode",alias:"shortcode",aliasTitles:{shortcode:"Shortcode"},owner:"RunDevelopment"},bbj:{title:"BBj",owner:"hyyan"},bicep:{title:"Bicep",owner:"johnnyreilly"},birb:{title:"Birb",require:"clike",owner:"Calamity210"},bison:{title:"Bison",require:"c",owner:"Golmote"},bnf:{title:"BNF",alias:"rbnf",aliasTitles:{rbnf:"RBNF"},owner:"RunDevelopment"},bqn:{title:"BQN",owner:"yewscion"},brainfuck:{title:"Brainfuck",owner:"Golmote"},brightscript:{title:"BrightScript",owner:"RunDevelopment"},bro:{title:"Bro",owner:"wayward710"},bsl:{title:"BSL (1C:Enterprise)",alias:"oscript",aliasTitles:{oscript:"OneScript"},owner:"Diversus23"},c:{title:"C",require:"clike",owner:"zeitgeist87"},csharp:{title:"C#",require:"clike",alias:["cs","dotnet"],owner:"mvalipour"},cpp:{title:"C++",require:"c",owner:"zeitgeist87"},cfscript:{title:"CFScript",require:"clike",alias:"cfc",owner:"mjclemente"},chaiscript:{title:"ChaiScript",require:["clike","cpp"],owner:"RunDevelopment"},cil:{title:"CIL",owner:"sbrl"},cilkc:{title:"Cilk/C",require:"c",alias:"cilk-c",owner:"OpenCilk"},cilkcpp:{title:"Cilk/C++",require:"cpp",alias:["cilk-cpp","cilk"],owner:"OpenCilk"},clojure:{title:"Clojure",owner:"troglotit"},cmake:{title:"CMake",owner:"mjrogozinski"},cobol:{title:"COBOL",owner:"RunDevelopment"},coffeescript:{title:"CoffeeScript",require:"javascript",alias:"coffee",owner:"R-osey"},concurnas:{title:"Concurnas",alias:"conc",owner:"jasontatton"},csp:{title:"Content-Security-Policy",owner:"ScottHelme"},cooklang:{title:"Cooklang",owner:"ahue"},coq:{title:"Coq",owner:"RunDevelopment"},crystal:{title:"Crystal",require:"ruby",owner:"MakeNowJust"},"css-extras":{title:"CSS Extras",require:"css",modify:"css",owner:"milesj"},csv:{title:"CSV",owner:"RunDevelopment"},cue:{title:"CUE",owner:"RunDevelopment"},cypher:{title:"Cypher",owner:"RunDevelopment"},d:{title:"D",require:"clike",owner:"Golmote"},dart:{title:"Dart",require:"clike",owner:"Golmote"},dataweave:{title:"DataWeave",owner:"machaval"},dax:{title:"DAX",owner:"peterbud"},dhall:{title:"Dhall",owner:"RunDevelopment"},diff:{title:"Diff",owner:"uranusjr"},django:{title:"Django/Jinja2",require:"markup-templating",alias:"jinja2",owner:"romanvm"},"dns-zone-file":{title:"DNS zone file",owner:"RunDevelopment",alias:"dns-zone"},docker:{title:"Docker",alias:"dockerfile",owner:"JustinBeckwith"},dot:{title:"DOT (Graphviz)",alias:"gv",optional:"markup",owner:"RunDevelopment"},ebnf:{title:"EBNF",owner:"RunDevelopment"},editorconfig:{title:"EditorConfig",owner:"osipxd"},eiffel:{title:"Eiffel",owner:"Conaclos"},ejs:{title:"EJS",require:["javascript","markup-templating"],owner:"RunDevelopment",alias:"eta",aliasTitles:{eta:"Eta"}},elixir:{title:"Elixir",owner:"Golmote"},elm:{title:"Elm",owner:"zwilias"},etlua:{title:"Embedded Lua templating",require:["lua","markup-templating"],owner:"RunDevelopment"},erb:{title:"ERB",require:["ruby","markup-templating"],owner:"Golmote"},erlang:{title:"Erlang",owner:"Golmote"},"excel-formula":{title:"Excel Formula",alias:["xlsx","xls"],owner:"RunDevelopment"},fsharp:{title:"F#",require:"clike",owner:"simonreynolds7"},factor:{title:"Factor",owner:"catb0t"},false:{title:"False",owner:"edukisto"},"firestore-security-rules":{title:"Firestore security rules",require:"clike",owner:"RunDevelopment"},flow:{title:"Flow",require:"javascript",owner:"Golmote"},fortran:{title:"Fortran",owner:"Golmote"},ftl:{title:"FreeMarker Template Language",require:"markup-templating",owner:"RunDevelopment"},gml:{title:"GameMaker Language",alias:"gamemakerlanguage",require:"clike",owner:"LiarOnce"},gap:{title:"GAP (CAS)",owner:"RunDevelopment"},gcode:{title:"G-code",owner:"RunDevelopment"},gdscript:{title:"GDScript",owner:"RunDevelopment"},gedcom:{title:"GEDCOM",owner:"Golmote"},gettext:{title:"gettext",alias:"po",owner:"RunDevelopment"},gherkin:{title:"Gherkin",owner:"hason"},git:{title:"Git",owner:"lgiraudel"},glsl:{title:"GLSL",require:"c",owner:"Golmote"},gn:{title:"GN",alias:"gni",owner:"RunDevelopment"},"linker-script":{title:"GNU Linker Script",alias:"ld",owner:"RunDevelopment"},go:{title:"Go",require:"clike",owner:"arnehormann"},"go-module":{title:"Go module",alias:"go-mod",owner:"RunDevelopment"},gradle:{title:"Gradle",require:"clike",owner:"zeabdelkhalek-badido18"},graphql:{title:"GraphQL",optional:"markdown",owner:"Golmote"},groovy:{title:"Groovy",require:"clike",owner:"robfletcher"},haml:{title:"Haml",require:"ruby",optional:["css","css-extras","coffeescript","erb","javascript","less","markdown","scss","textile"],owner:"Golmote"},handlebars:{title:"Handlebars",require:"markup-templating",alias:["hbs","mustache"],aliasTitles:{mustache:"Mustache"},owner:"Golmote"},haskell:{title:"Haskell",alias:"hs",owner:"bholst"},haxe:{title:"Haxe",require:"clike",optional:"regex",owner:"Golmote"},hcl:{title:"HCL",owner:"outsideris"},hlsl:{title:"HLSL",require:"c",owner:"RunDevelopment"},hoon:{title:"Hoon",owner:"matildepark"},http:{title:"HTTP",optional:["csp","css","hpkp","hsts","javascript","json","markup","uri"],owner:"danielgtaylor"},hpkp:{title:"HTTP Public-Key-Pins",owner:"ScottHelme"},hsts:{title:"HTTP Strict-Transport-Security",owner:"ScottHelme"},ichigojam:{title:"IchigoJam",owner:"BlueCocoa"},icon:{title:"Icon",owner:"Golmote"},"icu-message-format":{title:"ICU Message Format",owner:"RunDevelopment"},idris:{title:"Idris",alias:"idr",owner:"KeenS",require:"haskell"},ignore:{title:".ignore",owner:"osipxd",alias:["gitignore","hgignore","npmignore"],aliasTitles:{gitignore:".gitignore",hgignore:".hgignore",npmignore:".npmignore"}},inform7:{title:"Inform 7",owner:"Golmote"},ini:{title:"Ini",owner:"aviaryan"},io:{title:"Io",owner:"AlesTsurko"},j:{title:"J",owner:"Golmote"},java:{title:"Java",require:"clike",owner:"sherblot"},javadoc:{title:"JavaDoc",require:["markup","java","javadoclike"],modify:"java",optional:"scala",owner:"RunDevelopment"},javadoclike:{title:"JavaDoc-like",modify:["java","javascript","php"],owner:"RunDevelopment"},javastacktrace:{title:"Java stack trace",owner:"RunDevelopment"},jexl:{title:"Jexl",owner:"czosel"},jolie:{title:"Jolie",require:"clike",owner:"thesave"},jq:{title:"JQ",owner:"RunDevelopment"},jsdoc:{title:"JSDoc",require:["javascript","javadoclike","typescript"],modify:"javascript",optional:["actionscript","coffeescript"],owner:"RunDevelopment"},"js-extras":{title:"JS Extras",require:"javascript",modify:"javascript",optional:["actionscript","coffeescript","flow","n4js","typescript"],owner:"RunDevelopment"},json:{title:"JSON",alias:"webmanifest",aliasTitles:{webmanifest:"Web App Manifest"},owner:"CupOfTea696"},json5:{title:"JSON5",require:"json",owner:"RunDevelopment"},jsonp:{title:"JSONP",require:"json",owner:"RunDevelopment"},jsstacktrace:{title:"JS stack trace",owner:"sbrl"},"js-templates":{title:"JS Templates",require:"javascript",modify:"javascript",optional:["css","css-extras","graphql","markdown","markup","sql"],owner:"RunDevelopment"},julia:{title:"Julia",owner:"cdagnino"},keepalived:{title:"Keepalived Configure",owner:"dev-itsheng"},keyman:{title:"Keyman",owner:"mcdurdin"},kotlin:{title:"Kotlin",alias:["kt","kts"],aliasTitles:{kts:"Kotlin Script"},require:"clike",owner:"Golmote"},kumir:{title:"KuMir (\u041a\u0443\u041c\u0438\u0440)",alias:"kum",owner:"edukisto"},kusto:{title:"Kusto",owner:"RunDevelopment"},latex:{title:"LaTeX",alias:["tex","context"],aliasTitles:{tex:"TeX",context:"ConTeXt"},owner:"japborst"},latte:{title:"Latte",require:["clike","markup-templating","php"],owner:"nette"},less:{title:"Less",require:"css",optional:"css-extras",owner:"Golmote"},lilypond:{title:"LilyPond",require:"scheme",alias:"ly",owner:"RunDevelopment"},liquid:{title:"Liquid",require:"markup-templating",owner:"cinhtau"},lisp:{title:"Lisp",alias:["emacs","elisp","emacs-lisp"],owner:"JuanCaicedo"},livescript:{title:"LiveScript",owner:"Golmote"},llvm:{title:"LLVM IR",owner:"porglezomp"},log:{title:"Log file",optional:"javastacktrace",owner:"RunDevelopment"},lolcode:{title:"LOLCODE",owner:"Golmote"},lua:{title:"Lua",owner:"Golmote"},magma:{title:"Magma (CAS)",owner:"RunDevelopment"},makefile:{title:"Makefile",owner:"Golmote"},markdown:{title:"Markdown",require:"markup",optional:"yaml",alias:"md",owner:"Golmote"},"markup-templating":{title:"Markup templating",require:"markup",owner:"Golmote"},mata:{title:"Mata",owner:"RunDevelopment"},matlab:{title:"MATLAB",owner:"Golmote"},maxscript:{title:"MAXScript",owner:"RunDevelopment"},mel:{title:"MEL",owner:"Golmote"},mermaid:{title:"Mermaid",owner:"RunDevelopment"},metafont:{title:"METAFONT",owner:"LaeriExNihilo"},mizar:{title:"Mizar",owner:"Golmote"},mongodb:{title:"MongoDB",owner:"airs0urce",require:"javascript"},monkey:{title:"Monkey",owner:"Golmote"},moonscript:{title:"MoonScript",alias:"moon",owner:"RunDevelopment"},n1ql:{title:"N1QL",owner:"TMWilds"},n4js:{title:"N4JS",require:"javascript",optional:"jsdoc",alias:"n4jsd",owner:"bsmith-n4"},"nand2tetris-hdl":{title:"Nand To Tetris HDL",owner:"stephanmax"},naniscript:{title:"Naninovel Script",owner:"Elringus",alias:"nani"},nasm:{title:"NASM",owner:"rbmj"},neon:{title:"NEON",owner:"nette"},nevod:{title:"Nevod",owner:"nezaboodka"},nginx:{title:"nginx",owner:"volado"},nim:{title:"Nim",owner:"Golmote"},nix:{title:"Nix",owner:"Golmote"},nsis:{title:"NSIS",owner:"idleberg"},objectivec:{title:"Objective-C",require:"c",alias:"objc",owner:"uranusjr"},ocaml:{title:"OCaml",owner:"Golmote"},odin:{title:"Odin",owner:"edukisto"},opencl:{title:"OpenCL",require:"c",modify:["c","cpp"],owner:"Milania1"},openqasm:{title:"OpenQasm",alias:"qasm",owner:"RunDevelopment"},oz:{title:"Oz",owner:"Golmote"},parigp:{title:"PARI/GP",owner:"Golmote"},parser:{title:"Parser",require:"markup",owner:"Golmote"},pascal:{title:"Pascal",alias:"objectpascal",aliasTitles:{objectpascal:"Object Pascal"},owner:"Golmote"},pascaligo:{title:"Pascaligo",owner:"DefinitelyNotAGoat"},psl:{title:"PATROL Scripting Language",owner:"bertysentry"},pcaxis:{title:"PC-Axis",alias:"px",owner:"RunDevelopment"},peoplecode:{title:"PeopleCode",alias:"pcode",owner:"RunDevelopment"},perl:{title:"Perl",owner:"Golmote"},php:{title:"PHP",require:"markup-templating",owner:"milesj"},phpdoc:{title:"PHPDoc",require:["php","javadoclike"],modify:"php",owner:"RunDevelopment"},"php-extras":{title:"PHP Extras",require:"php",modify:"php",owner:"milesj"},"plant-uml":{title:"PlantUML",alias:"plantuml",owner:"RunDevelopment"},plsql:{title:"PL/SQL",require:"sql",owner:"Golmote"},powerquery:{title:"PowerQuery",alias:["pq","mscript"],owner:"peterbud"},powershell:{title:"PowerShell",owner:"nauzilus"},processing:{title:"Processing",require:"clike",owner:"Golmote"},prolog:{title:"Prolog",owner:"Golmote"},promql:{title:"PromQL",owner:"arendjr"},properties:{title:".properties",owner:"Golmote"},protobuf:{title:"Protocol Buffers",require:"clike",owner:"just-boris"},pug:{title:"Pug",require:["markup","javascript"],optional:["coffeescript","ejs","handlebars","less","livescript","markdown","scss","stylus","twig"],owner:"Golmote"},puppet:{title:"Puppet",owner:"Golmote"},pure:{title:"Pure",optional:["c","cpp","fortran"],owner:"Golmote"},purebasic:{title:"PureBasic",require:"clike",alias:"pbfasm",owner:"HeX0R101"},purescript:{title:"PureScript",require:"haskell",alias:"purs",owner:"sriharshachilakapati"},python:{title:"Python",alias:"py",owner:"multipetros"},qsharp:{title:"Q#",require:"clike",alias:"qs",owner:"fedonman"},q:{title:"Q (kdb+ database)",owner:"Golmote"},qml:{title:"QML",require:"javascript",owner:"RunDevelopment"},qore:{title:"Qore",require:"clike",owner:"temnroegg"},r:{title:"R",owner:"Golmote"},racket:{title:"Racket",require:"scheme",alias:"rkt",owner:"RunDevelopment"},cshtml:{title:"Razor C#",alias:"razor",require:["markup","csharp"],optional:["css","css-extras","javascript","js-extras"],owner:"RunDevelopment"},jsx:{title:"React JSX",require:["markup","javascript"],optional:["jsdoc","js-extras","js-templates"],owner:"vkbansal"},tsx:{title:"React TSX",require:["jsx","typescript"]},reason:{title:"Reason",require:"clike",owner:"Golmote"},regex:{title:"Regex",owner:"RunDevelopment"},rego:{title:"Rego",owner:"JordanSh"},renpy:{title:"Ren'py",alias:"rpy",owner:"HyuchiaDiego"},rescript:{title:"ReScript",alias:"res",owner:"vmarcosp"},rest:{title:"reST (reStructuredText)",owner:"Golmote"},rip:{title:"Rip",owner:"ravinggenius"},roboconf:{title:"Roboconf",owner:"Golmote"},robotframework:{title:"Robot Framework",alias:"robot",owner:"RunDevelopment"},ruby:{title:"Ruby",require:"clike",alias:"rb",owner:"samflores"},rust:{title:"Rust",owner:"Golmote"},sas:{title:"SAS",optional:["groovy","lua","sql"],owner:"Golmote"},sass:{title:"Sass (Sass)",require:"css",optional:"css-extras",owner:"Golmote"},scss:{title:"Sass (SCSS)",require:"css",optional:"css-extras",owner:"MoOx"},scala:{title:"Scala",require:"java",owner:"jozic"},scheme:{title:"Scheme",owner:"bacchus123"},"shell-session":{title:"Shell session",require:"bash",alias:["sh-session","shellsession"],owner:"RunDevelopment"},smali:{title:"Smali",owner:"RunDevelopment"},smalltalk:{title:"Smalltalk",owner:"Golmote"},smarty:{title:"Smarty",require:"markup-templating",optional:"php",owner:"Golmote"},sml:{title:"SML",alias:"smlnj",aliasTitles:{smlnj:"SML/NJ"},owner:"RunDevelopment"},solidity:{title:"Solidity (Ethereum)",alias:"sol",require:"clike",owner:"glachaud"},"solution-file":{title:"Solution file",alias:"sln",owner:"RunDevelopment"},soy:{title:"Soy (Closure Template)",require:"markup-templating",owner:"Golmote"},sparql:{title:"SPARQL",require:"turtle",owner:"Triply-Dev",alias:"rq"},"splunk-spl":{title:"Splunk SPL",owner:"RunDevelopment"},sqf:{title:"SQF: Status Quo Function (Arma 3)",require:"clike",owner:"RunDevelopment"},sql:{title:"SQL",owner:"multipetros"},squirrel:{title:"Squirrel",require:"clike",owner:"RunDevelopment"},stan:{title:"Stan",owner:"RunDevelopment"},stata:{title:"Stata Ado",require:["mata","java","python"],owner:"RunDevelopment"},iecst:{title:"Structured Text (IEC 61131-3)",owner:"serhioromano"},stylus:{title:"Stylus",owner:"vkbansal"},supercollider:{title:"SuperCollider",alias:"sclang",owner:"RunDevelopment"},swift:{title:"Swift",owner:"chrischares"},systemd:{title:"Systemd configuration file",owner:"RunDevelopment"},"t4-templating":{title:"T4 templating",owner:"RunDevelopment"},"t4-cs":{title:"T4 Text Templates (C#)",require:["t4-templating","csharp"],alias:"t4",owner:"RunDevelopment"},"t4-vb":{title:"T4 Text Templates (VB)",require:["t4-templating","vbnet"],owner:"RunDevelopment"},tap:{title:"TAP",owner:"isaacs",require:"yaml"},tcl:{title:"Tcl",owner:"PeterChaplin"},tt2:{title:"Template Toolkit 2",require:["clike","markup-templating"],owner:"gflohr"},textile:{title:"Textile",require:"markup",optional:"css",owner:"Golmote"},toml:{title:"TOML",owner:"RunDevelopment"},tremor:{title:"Tremor",alias:["trickle","troy"],owner:"darach",aliasTitles:{trickle:"trickle",troy:"troy"}},turtle:{title:"Turtle",alias:"trig",aliasTitles:{trig:"TriG"},owner:"jakubklimek"},twig:{title:"Twig",require:"markup-templating",owner:"brandonkelly"},typescript:{title:"TypeScript",require:"javascript",optional:"js-templates",alias:"ts",owner:"vkbansal"},typoscript:{title:"TypoScript",alias:"tsconfig",aliasTitles:{tsconfig:"TSConfig"},owner:"dkern"},unrealscript:{title:"UnrealScript",alias:["uscript","uc"],owner:"RunDevelopment"},uorazor:{title:"UO Razor Script",owner:"jaseowns"},uri:{title:"URI",alias:"url",aliasTitles:{url:"URL"},owner:"RunDevelopment"},v:{title:"V",require:"clike",owner:"taggon"},vala:{title:"Vala",require:"clike",optional:"regex",owner:"TemplarVolk"},vbnet:{title:"VB.Net",require:"basic",owner:"Bigsby"},velocity:{title:"Velocity",require:"markup",owner:"Golmote"},verilog:{title:"Verilog",owner:"a-rey"},vhdl:{title:"VHDL",owner:"a-rey"},vim:{title:"vim",owner:"westonganger"},"visual-basic":{title:"Visual Basic",alias:["vb","vba"],aliasTitles:{vba:"VBA"},owner:"Golmote"},warpscript:{title:"WarpScript",owner:"RunDevelopment"},wasm:{title:"WebAssembly",owner:"Golmote"},"web-idl":{title:"Web IDL",alias:"webidl",owner:"RunDevelopment"},wgsl:{title:"WGSL",owner:"Dr4gonthree"},wiki:{title:"Wiki markup",require:"markup",owner:"Golmote"},wolfram:{title:"Wolfram language",alias:["mathematica","nb","wl"],aliasTitles:{mathematica:"Mathematica",nb:"Mathematica Notebook"},owner:"msollami"},wren:{title:"Wren",owner:"clsource"},xeora:{title:"Xeora",require:"markup",alias:"xeoracube",aliasTitles:{xeoracube:"XeoraCube"},owner:"freakmaxi"},"xml-doc":{title:"XML doc (.net)",require:"markup",modify:["csharp","fsharp","vbnet"],owner:"RunDevelopment"},xojo:{title:"Xojo (REALbasic)",owner:"Golmote"},xquery:{title:"XQuery",require:"markup",owner:"Golmote"},yaml:{title:"YAML",alias:"yml",owner:"hason"},yang:{title:"YANG",owner:"RunDevelopment"},zig:{title:"Zig",owner:"RunDevelopment"}},plugins:{meta:{path:"plugins/{id}/prism-{id}",link:"plugins/{id}/"},"line-highlight":{title:"Line Highlight",description:"Highlights specific lines and/or line ranges."},"line-numbers":{title:"Line Numbers",description:"Line number at the beginning of code lines.",owner:"kuba-kubula"},"show-invisibles":{title:"Show Invisibles",description:"Show hidden characters such as tabs and line breaks.",optional:["autolinker","data-uri-highlight"]},autolinker:{title:"Autolinker",description:"Converts URLs and emails in code to clickable links. Parses Markdown links in comments."},wpd:{title:"WebPlatform Docs",description:'Makes tokens link to WebPlatform.org documentation. The links open in a new tab.'},"custom-class":{title:"Custom Class",description:"This plugin allows you to prefix Prism's default classes (.comment can become .namespace--comment) or replace them with your defined ones (like .editor__comment). You can even add new classes.",owner:"dvkndn",noCSS:!0},"file-highlight":{title:"File Highlight",description:"Fetch external files and highlight them with Prism. Used on the Prism website itself.",noCSS:!0},"show-language":{title:"Show Language",description:"Display the highlighted language in code blocks (inline code does not show the label).",owner:"nauzilus",noCSS:!0,require:"toolbar"},"jsonp-highlight":{title:"JSONP Highlight",description:"Fetch content with JSONP and highlight some interesting content (e.g. GitHub/Gists or Bitbucket API).",noCSS:!0,owner:"nauzilus"},"highlight-keywords":{title:"Highlight Keywords",description:"Adds special CSS classes for each keyword for fine-grained highlighting.",owner:"vkbansal",noCSS:!0},"remove-initial-line-feed":{title:"Remove initial line feed",description:"Removes the initial line feed in code blocks.",owner:"Golmote",noCSS:!0},"inline-color":{title:"Inline color",description:"Adds a small inline preview for colors in style sheets.",require:"css-extras",owner:"RunDevelopment"},previewers:{title:"Previewers",description:"Previewers for angles, colors, gradients, easing and time.",require:"css-extras",owner:"Golmote"},autoloader:{title:"Autoloader",description:"Automatically loads the needed languages to highlight the code blocks.",owner:"Golmote",noCSS:!0},"keep-markup":{title:"Keep Markup",description:"Prevents custom markup from being dropped out during highlighting.",owner:"Golmote",optional:"normalize-whitespace",noCSS:!0},"command-line":{title:"Command Line",description:"Display a command line with a prompt and, optionally, the output/response from the commands.",owner:"chriswells0"},"unescaped-markup":{title:"Unescaped Markup",description:"Write markup without having to escape anything."},"normalize-whitespace":{title:"Normalize Whitespace",description:"Supports multiple operations to normalize whitespace in code blocks.",owner:"zeitgeist87",optional:"unescaped-markup",noCSS:!0},"data-uri-highlight":{title:"Data-URI Highlight",description:"Highlights data-URI contents.",owner:"Golmote",noCSS:!0},toolbar:{title:"Toolbar",description:"Attach a toolbar for plugins to easily register buttons on the top of a code block.",owner:"mAAdhaTTah"},"copy-to-clipboard":{title:"Copy to Clipboard Button",description:"Add a button that copies the code block to the clipboard when clicked.",owner:"mAAdhaTTah",require:"toolbar",noCSS:!0},"download-button":{title:"Download Button",description:"A button in the toolbar of a code block adding a convenient way to download a code file.",owner:"Golmote",require:"toolbar",noCSS:!0},"match-braces":{title:"Match braces",description:"Highlights matching braces.",owner:"RunDevelopment"},"diff-highlight":{title:"Diff Highlight",description:"Highlights the code inside diff blocks.",owner:"RunDevelopment",require:"diff"},"filter-highlight-all":{title:"Filter highlightAll",description:"Filters the elements the highlightAll and highlightAllUnder methods actually highlight.",owner:"RunDevelopment",noCSS:!0},treeview:{title:"Treeview",description:"A language with special styles to highlight file system tree structures.",owner:"Golmote"}}})},8722:(e,t,n)=>{const r=n(6969),o=n(8380),a=new Set;function i(e){void 0===e?e=Object.keys(r.languages).filter((e=>"meta"!=e)):Array.isArray(e)||(e=[e]);const t=[...a,...Object.keys(Prism.languages)];o(r,e,t).load((e=>{if(!(e in r.languages))return void(i.silent||console.warn("Language does not exist: "+e));const t="./prism-"+e;delete n.c[n(3157).resolve(t)],delete Prism.languages[e],n(3157)(t),a.add(e)}))}i.silent=!1,e.exports=i},9700:()=>{!function(e){function t(e,t){return"___"+e.toUpperCase()+t+"___"}Object.defineProperties(e.languages["markup-templating"]={},{buildPlaceholders:{value:function(n,r,o,a){if(n.language===r){var i=n.tokenStack=[];n.code=n.code.replace(o,(function(e){if("function"==typeof a&&!a(e))return e;for(var o,l=i.length;-1!==n.code.indexOf(o=t(r,l));)++l;return i[l]=e,o})),n.grammar=e.languages.markup}}},tokenizePlaceholders:{value:function(n,r){if(n.language===r&&n.tokenStack){n.grammar=e.languages[r];var o=0,a=Object.keys(n.tokenStack);!function i(l){for(var s=0;s=a.length);s++){var c=l[s];if("string"==typeof c||c.content&&"string"==typeof c.content){var u=a[o],d=n.tokenStack[u],p="string"==typeof c?c:c.content,f=t(r,u),h=p.indexOf(f);if(h>-1){++o;var m=p.substring(0,h),g=new e.Token(r,e.tokenize(d,n.grammar),"language-"+r,d),b=p.substring(h+f.length),y=[];m&&y.push.apply(y,i([m])),y.push(g),b&&y.push.apply(y,i([b])),"string"==typeof c?l.splice.apply(l,[s,1].concat(y)):c.content=y}}else c.content&&i(c.content)}return l}(n.tokens)}}}})}(Prism)},8692:(e,t,n)=>{var r={"./":8722};function o(e){var t=a(e);return n(t)}function a(e){if(!n.o(r,e)){var t=new Error("Cannot find module '"+e+"'");throw t.code="MODULE_NOT_FOUND",t}return r[e]}o.keys=function(){return Object.keys(r)},o.resolve=a,e.exports=o,o.id=8692},3157:(e,t,n)=>{var r={"./":8722};function o(e){var t=a(e);return n(t)}function a(e){if(!n.o(r,e)){var t=new Error("Cannot find module '"+e+"'");throw t.code="MODULE_NOT_FOUND",t}return r[e]}o.keys=function(){return Object.keys(r)},o.resolve=a,e.exports=o,o.id=3157},8380:e=>{"use strict";var t=function(){var e=function(){};function t(e,t){Array.isArray(e)?e.forEach(t):null!=e&&t(e,0)}function n(e){for(var t={},n=0,r=e.length;n "));var l={},s=e[r];if(s){function c(t){if(!(t in e))throw new Error(r+" depends on an unknown component "+t);if(!(t in l))for(var i in o(t,a),l[t]=!0,n[t])l[i]=!0}t(s.require,c),t(s.optional,c),t(s.modify,c)}n[r]=l,a.pop()}}return function(e){var t=n[e];return t||(o(e,r),t=n[e]),t}}function o(e){for(var t in e)return!0;return!1}return function(a,i,l){var s=function(e){var t={};for(var n in e){var r=e[n];for(var o in r)if("meta"!=o){var a=r[o];t[o]="string"==typeof a?{title:a}:a}}return t}(a),c=function(e){var n;return function(r){if(r in e)return r;if(!n)for(var o in n={},e){var a=e[o];t(a&&a.alias,(function(t){if(t in n)throw new Error(t+" cannot be alias for both "+o+" and "+n[t]);if(t in e)throw new Error(t+" cannot be alias of "+o+" because it is a component.");n[t]=o}))}return n[r]||r}}(s);i=i.map(c),l=(l||[]).map(c);var u=n(i),d=n(l);i.forEach((function e(n){var r=s[n];t(r&&r.require,(function(t){t in d||(u[t]=!0,e(t))}))}));for(var p,f=r(s),h=u;o(h);){for(var m in p={},h){var g=s[m];t(g&&g.modify,(function(e){e in d&&(p[e]=!0)}))}for(var b in d)if(!(b in u))for(var y in f(b))if(y in u){p[b]=!0;break}for(var v in h=p)u[v]=!0}var w={getIds:function(){var e=[];return w.load((function(t){e.push(t)})),e},load:function(t,n){return function(t,n,r,o){var a=o?o.series:void 0,i=o?o.parallel:e,l={},s={};function c(e){if(e in l)return l[e];s[e]=!0;var o,u=[];for(var d in t(e))d in n&&u.push(d);if(0===u.length)o=r(e);else{var p=i(u.map((function(e){var t=c(e);return delete s[e],t})));a?o=a(p,(function(){return r(e)})):r(e)}return l[e]=o}for(var u in n)c(u);var d=[];for(var p in s)d.push(l[p]);return i(d)}(f,u,t,n)}};return w}}();e.exports=t},2694:(e,t,n)=>{"use strict";var r=n(6925);function o(){}function a(){}a.resetWarningCache=o,e.exports=function(){function e(e,t,n,o,a,i){if(i!==r){var l=new Error("Calling PropTypes validators directly is not supported by the `prop-types` package. Use PropTypes.checkPropTypes() to call them. Read more at http://fb.me/use-check-prop-types");throw l.name="Invariant Violation",l}}function t(){return e}e.isRequired=e;var n={array:e,bigint:e,bool:e,func:e,number:e,object:e,string:e,symbol:e,any:e,arrayOf:t,element:e,elementType:e,instanceOf:t,node:e,objectOf:t,oneOf:t,oneOfType:t,shape:t,exact:t,checkPropTypes:a,resetWarningCache:o};return n.PropTypes=n,n}},5556:(e,t,n)=>{e.exports=n(2694)()},6925:e=>{"use strict";e.exports="SECRET_DO_NOT_PASS_THIS_OR_YOU_WILL_BE_FIRED"},2551:(e,t,n)=>{"use strict";var r=n(6540),o=n(9982);function a(e){for(var t="https://reactjs.org/docs/error-decoder.html?invariant="+e,n=1;n