Merge branch 'main' into add/light-theme-styles

.tractusx

@@ -7,3 +7,7 @@ repositories:
   url: "https://github.com/eclipse-tractusx/eclipse-tractusx.github.io"
 openApiSpecs:
 - "https://raw.githubusercontent.com/eclipse-tractusx/eclipse-tractusx.github.io/main/openApi/dt/kit_digital-twin-kit-submodel-api_openAPI.yaml"
+- "https://raw.githubusercontent.com/eclipse-tractusx/eclipse-tractusx.github.io/main/openApi/dcm/IdBasedComment.yaml"
+- "https://raw.githubusercontent.com/eclipse-tractusx/eclipse-tractusx.github.io/main/openApi/dcm/IdBasedRequestForUpdate.yaml"
+- "https://raw.githubusercontent.com/eclipse-tractusx/eclipse-tractusx.github.io/main/openApi/dcm/WeekBasedCapacityGroup.yaml"
+- "https://raw.githubusercontent.com/eclipse-tractusx/eclipse-tractusx.github.io/main/openApi/dcm/WeekBasedMaterialDemand.yaml"

DEPENDENCIES

@@ -730,7 +730,7 @@ npm/npmjs/-/react-live/3.1.1, MIT, approved, clearlydefined
 npm/npmjs/-/react-loadable-ssr-addon-v5-slorber/1.0.1, MIT, approved, clearlydefined
 npm/npmjs/-/react-magic-dropzone/1.0.1, MIT, approved, #6622
 npm/npmjs/-/react-markdown/8.0.5, MIT, approved, #6635
-npm/npmjs/-/react-modal/3.16.1, MIT, approved, clearlydefined
+npm/npmjs/-/react-modal/3.16.1, MIT, approved, #18547
 npm/npmjs/-/react-redux/7.2.9, MIT, approved, #2978
 npm/npmjs/-/react-router-config/5.1.1, MIT, approved, clearlydefined
 npm/npmjs/-/react-router-dom/5.3.4, MIT AND BSD-3-Clause, approved, #3023
@@ -908,7 +908,7 @@ npm/npmjs/-/type-fest/2.19.0, CC0-1.0 OR MIT OR (CC0-1.0 AND MIT), approved, cle
 npm/npmjs/-/type-is/1.6.18, MIT, approved, clearlydefined
 npm/npmjs/-/typedarray-to-buffer/3.1.5, MIT, approved, clearlydefined
 npm/npmjs/-/typescript/4.9.4, Apache-2.0 AND (CC-BY-4.0 AND LicenseRef-scancode-khronos AND LicenseRef-scancode-unicode AND MIT AND W3C-20150513), approved, #4979
-npm/npmjs/-/ua-parser-js/0.7.32, MIT, approved, clearlydefined
+npm/npmjs/-/ua-parser-js/0.7.32, MIT, approved, #18507
 npm/npmjs/-/uc.micro/1.0.6, MIT, approved, #1022
 npm/npmjs/-/unherit/1.1.3, MIT, approved, clearlydefined
 npm/npmjs/-/unicode-canonical-property-names-ecmascript/2.0.0, MIT, approved, clearlydefined

blog/2024-12-16-community-days-recap.mdx

@@ -0,0 +1,112 @@
+---
+title: Third Eclipse Tractus-X Community Days Recap
+description: A comprehensive overview of the Third Eclipse Tractus-X Community Days held on December 5 and 6, 2024, at ARENA2036 in Stuttgart.
+slug: community-days-recap-12-2024
+date: 2024-12-16T11:00
+hide_table_of_contents: false
+authors:
+  - name: Stephan Bauer
+    title: Eclipse Tractus-X Project Lead
+    url: https://github.com/stephanbcbauer
+    image_url: https://github.com/stephanbcbauer.png
+    email: [email protected]
+---
+
+import RenderImage from './RenderImage'
+
+[![eclipse tractus x logo](@site/static/img/tractus-x-community-days-24-12-group.png)](@site/static/img/tractus-x-community-days-24-12-group.png)
+
+Dear Tractus-X- and Dataspace-Community,
+
+The Third Eclipse Tractus-X Community Days, held on December 5 and 6, 2024, at ARENA2036 in Stuttgart, marked a significant milestone in our journey towards fostering
+open-source collaboration within the automotive and manufacturing sectors. Building upon the successes of previous events, this edition attracted over 220 participants
+from diverse regions, including Japan, Spain, the USA, and India, underscoring the growing global interest in the Tractus-X initiative.
+
+A notable highlight was the increased participation from representatives of Manufacturing-X projects such as Factory-X, Aerospace-X, Semiconductor-X, Chem-X, and Construction-X.
+Their involvement enriched the discussions with fresh perspectives, fostering a broader ecosystem for networking and collaborative development.
+
+This year's event introduced an updated format tailored to various interests and experience levels, featuring multiple streams, presentations, workshops and challenges.
+This setup provided a comprehensive Tractus-X environment with federated services and use cases, enhancing the hands-on experience for attendees.
+
+<!--truncate-->
+
+## Day 1 Highlights
+
+### Welcome and Keynote
+
+- **[Opening](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io.largefiles/raw/refs/heads/main/presentations/24-12-community-days/241205-opening.pdf)**
+  - *Claus Cremers, Siemens AG and member of the Management Board of Catena-X Automotive Network e.V.*
+- **[Keynote: State of Eclipse Tractus-X](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io.largefiles/raw/refs/heads/main/presentations/24-12-community-days/241205-keynote-stateof-eclipse-tractus-x.pdf)**
+  - *Evelyn Gurschler, BMW AG and Member of the Self-Sovereign Identity Expert Group*
+  - *Mathias Brunkow Moser, Catena-X Automotive Network e.V.*
+
+### Stream #1 - Business Perspective Presentations
+
+- **[Introduction of Catena-X and its Ecosystem](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io.largefiles/raw/refs/heads/main/presentations/24-12-community-days/241205-catena-x-ecosystem.pdf)**
+  - *Michael Hahn, Catena-X Automotive Network e.V.*
+- **[Catena-X and Tractus-X - The technical features of Catena-X and its implmentation with Tractus-X](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io.largefiles/raw/refs/heads/main/presentations/24-12-community-days/241205-technical-features-of-catena-x-implementation-in-tractus-x.pdf)**
+  - *Johannes Diemer, ARENA2036 e.V.*
+- **[Introduction to Industry Core - Building data chains for vehicles](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io.largefiles/raw/refs/heads/main/presentations/24-12-community-days/241205-industry-core.pdf)**
+  - *Gabriele Eckardt, BASF Digital Solutions GmbH and Lead of the Industry Core Committee*
+- **[Customer Involvement: Why Feedback Matters](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io.largefiles/raw/refs/heads/main/presentations/24-12-community-days/241205-customer-involvement-why-feedback-matters.pdf)**
+  - *Heiko Musa, BMW AG and Lead of the Customer Involvement Expert Group*
+- **[How Sovity Builds Features on Top of Eclipse Tractus-X](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io.largefiles/raw/refs/heads/main/presentations/24-12-community-days/241205-build-features-on-top-of-open-source.pdf)**
+  - *Sebastian Opriel, Sovity GmbH and Member of the Dataspace Connectivity Expert Group*
+- **[Realize Instant Value for SMEs with Dataspace OS NOVA](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io.largefiles/raw/refs/heads/main/presentations/24-12-community-days/241205-realize-value-dataspace-os-nova.pdf)**
+  - *Niklas Midolo, Cofinity-X*
+- **[Tractus-X Meets Wiring Harness](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io.largefiles/raw/refs/heads/main/presentations/24-12-community-days/241206-aas-tractus-x-meets-wiring-harness.pdf)**
+  - *Christian Kosel, ARENA2036 e.V.*
+- **[Catena-X PCF Data Exchange Use Case : FORD - Flex Success Story](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io.largefiles/raw/refs/heads/main/presentations/24-12-community-days/241205-catena-x-pcf-data-exchange-usecase-ford.pdf)**
+  - *Stan Faldin, Catena-X Automotive Network e.V*
+
+### Stream #2 - Workshops/Tutorials
+
+- **EDC Tutorial / Dataspace Connectivity**
+  - *led by Stephan Bauer, Catena-X Automotive Network e.V.*
+- **Digital Product Passport 2.0**
+  - *led by Mathias Brunkow Moser, Catena-X Automotive Network e.V.*
+- **Successful Test Automation with Open-Source Methods**
+  - *led by Harald Zimmer, doubleSlash and Test Manager*
+- **Modelling for SAMM and AAS with ESMF Editor and AASX Package Explorer**
+  - *led by Dr. Birgit Boss, Robert Bosch GmbH and Lead of the Technical Committee for Modelling*
+
+### Stream #3 - Challenges: Coding
+
+- **Challenge #1: Industry Core - FOSS IRS App**
+  - *led by Gabriele Eckardt, BASF Digital Solutions GmbH and Lead of the Industry Core Committee*
+- **Challenge #2: Hackathon - Develop a Tutorial for an EDC-based Chat App**
+  - *led by Sebastian Opriel, Sovity GmbH and Member of the Dataspace Connectivity Expert Group*
+- **Challenge #3: BaSyx as Digital Twin Registry**
+  - *led by Frank Schnicke, Fraunhofer IESE*
+
+### Developer Panel
+
+- **Tractus-X, The Place to Come Together**
+  - *Daniel Miehle, BMW AG*
+  - *Maximilian Ong, Mercedes-Benz AG*
+
+### Evening Event
+
+- **Networking and discussions continued** at the ARENA2036, fostering community building and collaboration.
+
+## Day 2 Highlights
+
+### Tech Talk
+
+- **[The Future of the EDC, decentral Wallets and other Domain Topics](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io.largefiles/raw/refs/heads/main/presentations/24-12-community-days/241206-tech-talk-the-dataspace-future.pdf)** - *by Lars Geyer-Blaumeiser, Senior Software Architect Cofinity-X.*
+
+### Continuation of Streams
+
+- **Participants engaged in advanced workshops**, tutorials, and coding challenges, deepening their understanding and application of Tractus-X tools and concepts.
+
+### Closing Session
+
+- **Summarization of key takeaways** and discussions on future directions for the Tractus-X community.
+
+The Third Eclipse Tractus-X Community Days not only showcased the rapid advancements in open-source solutions for the automotive industry but also highlighted the importance
+of community engagement in driving innovation. The collaborative spirit and shared vision exhibited during the event set a promising trajectory for the future of Tractus-X and its expanding ecosystem.
+
+As the community continues to grow, the insights and connections made during these days will undoubtedly play a pivotal role in shaping the next generation of digital ecosystems and collaborative
+data exchanges.
+
+*Stay tuned for announcements regarding future events and opportunities to engage with the Eclipse Tractus-X community.*

community/open-meetings.mdx

@@ -23,7 +23,7 @@ All the times are shown in:
 />
 
 <MeetingInfo title="Community Office Hour"
-             schedule="Every Friday effective 16. Feb 2024 until 31. Dec 2024 from 01:05 pm to 02:00 pm"
+             schedule="Every Friday effective 01. Jan 2025 until 31. Dec 2025 from 10:05 am to 11:00 am"
              description="Open hour meeting for all interests. The goal of the meeting is to inform and share information about different topics."
              contact="[email protected]"
              sessionLink="https://teams.microsoft.com/l/meetup-join/19%3ameeting_MDFiNDJjMmQtNjFkYi00ODdjLTk2NDgtZGMwNTRmYzg3NzM0%40thread.v2/0?context=%7b%22Tid%22%3a%221ad22c6d-2f08-4f05-a0ba-e17f6ce88380%22%2c%22Oid%22%3a%22a8b7a5ee-66ff-4695-afa2-08f893d8aaf6%22%7d"
@@ -44,7 +44,7 @@ All the times are shown in:
 />
 
 <MeetingInfo title="Committer Meeting"
-             schedule="Every 2 weeks on Friday effective 16. Feb 2024 until 31. Dec 2024 from 02:05 pm to 03:00 pm"
+             schedule="Every 2 weeks on Friday effective 01. Jan 2025 until 31. Dec 2025 from 02:05 pm to 03:00 pm"
              description="Open hour meeting for Eclipse Tractus-X committers. The goal of the meeting is to discuss and share specific committer tasks/responsibilities."
              contact="[email protected]"
              sessionLink="https://teams.microsoft.com/l/meetup-join/19%3ameeting_ZjlmNTc5MjMtN2Y2YS00YjliLTg3NTItNWE1MmMzMWUzNmYw%40thread.v2/0?context=%7b%22Tid%22%3a%221ad22c6d-2f08-4f05-a0ba-e17f6ce88380%22%2c%22Oid%22%3a%22a8b7a5ee-66ff-4695-afa2-08f893d8aaf6%22%7d"
@@ -93,6 +93,19 @@ All the times are shown in:
              }
 />
 
+<MeetingInfo title="Semantic Model Modelling - Open Meeting"
+             schedule="Every Monday effective 20. January 2025 from 15:30 am to 16:30 am CET"
+             description="Coordination of the development and alignment of aspect models (sldt-semantic-models) as well as ontologies (sldt-ontology-model)."
+             contact="[email protected]"
+             sessionLink="https://teams.microsoft.com/l/meetup-join/19%3ameeting_N2I5MjM1NzUtZmFmZS00MTI2LTgyMmEtOGZiMDMxNmRlYTA4%40thread.v2/0?context=%7b%22Tid%22%3a%221ad22c6d-2f08-4f05-a0ba-e17f6ce88380%22%2c%22Oid%22%3a%22bf6c04e8-bde4-4ca1-ac15-0f85f440ab48%22%7d"
+             additionalLinks={
+                [
+                    {title: 'SLDT Semantic Models Repository', url: 'https://github.com/eclipse-tractusx/sldt-semantic-models'},
+                    {title: 'SLDT Ontology Models Repository', url: 'https://github.com/eclipse-tractusx/sldt-ontology-model'}
+                ]
+             }
+/>
+
 ## One-time meetings
 
 <MeetingInfo title="Refinement Phase - Release 25.06"

community/sigs/05_sig_architecture.md

@@ -0,0 +1,18 @@
+---
+title: "SIG Architecture"
+---
+
+__Focus:__ Document the overall architecture from Tractus-X and document Datataspace Usage Patterns. A place were Tractus-X Architects can align and document the different design decisions that affect the Tractus-X Product as a whole.
+
+## Objectives
+
+- Define architecture guidelines for Eclipse Tractus-X products
+- Document the architecture and the relationships between the products
+- Document the design decisions of the project itself, regarding other dataspaces and organizations
+- Enable a fluid and synchronized integration of the Eclipse Tractus-X dataspace, having a big picture how it comes together.
+- Easy the understanding for external technical viewers who want to learn how Eclipse Tractus-X has been built from architectural point of view.
+- Document dataspace usage patterns to increase performance, reduce complexity and ease the adoption of the dataspace.
+
+__Repository:__ [eclipse-tractusx/sig-architecture](https://github.com/eclipse-tractusx/sig-architecture)
+
+__Project:__ [Tractus-X Architecture](https://github.com/orgs/eclipse-tractusx/projects/78)

docs-kits/kits/Industry Core Kit/Software Development View/page_digital-twins.mdx

@@ -117,7 +117,7 @@ The following conventions for specific asset IDs apply to all digital twins:
 
 | Key            | Availability | Description                                                                                  | Type   |
 | :------------- | :----------- | :------------------------------------------------------------------------------------------- | :----- |
-| partInstanceId | Mandatory    | The serial number of the part from the manufacturer.                                         | String |
+| partInstanceId | Mandatory    | The serial number of a part, as specified by the manufacturer, is the number that is applied to the part (e.g., as a barcode or DMC). The recipient (e.g., a customer) of the part will use this serial number information to look up the digital twin of the part in the manufacturer's Digital Twin Registry.<br/>A manufacturer might create more than one serial number for a part. For example, if customers require the serial number to have a customer-specific format, the manufacturer might create two serial numbers for every part: an internal one with a standard format for ease of use in the manufacturer's internal systems, and a customer-specific one that is actually applied to the part. In this case, the customer-specific serial number should be used as partInstanceId. | String |
 | intrinsicId    | Mandatory    | This the unified technical key for searching a digital twin of a part. In this case the<br/> partInstanceId is used as the intrinsicId.                                         | String |
 | van            | Optional     | **Only for vehicles:** The pseudonymized vehicle identification number (VIN) of the vehicle. | String |
 
@@ -142,9 +142,6 @@ The following conventions for specific asset IDs apply to all digital twins:
 > In order to provide a standardised way to look-up digital twins, the specificAssetIDs are extended by a unified technical key, the intrinsicId. This ensures a correct semantic filling of all other existing attributes in the specificAssetIDs, as the partInstanceId was previously used as an overarching search field, which resulted in the partInstanceId being filled with a batch number for a batch, for example.
 Nevertheless, a search for digital twins can still be used via the corresponding the primary fields from a business point of view, such as partInstanceId or batchId.
 
-standardised identification of a digital twin based on technical key attributes
-Correct semantic filling of all existing fields in the specificAssetIDs (e.g. filling of the partInstanceIDs attribute for JisParts)
-
 #### Submodel Descriptors
 
 To enforce a strict need-to-know (and prevent data from being exposed to non-authorized parties), the visibility of entries in the attribute `specificAssetIds` must be protected, i.e.,their visibility must be restricted to authorized parties only. For that, the attribute `externalSubjectId` must be used. Detailed information about this can be found in the [Digital Twin KIT](../../../../kits/Digital%20Twin%20Kit/Software%20Development%20View/API%20AAS%20Discovery/get-all-asset-links-by-id).

docs-kits_versioned_docs/version-24.08/kits/knowledge-agents/development-view/modules.md

@@ -245,7 +245,7 @@ standard.
 
 Actually, this KIT is caring about two bridges, one which bridges AAS information that is described in Catena-X aspect schemas
 into the Catena-X domain ontologies (the AAS-KA Bridge). And one bridge which is able to emulate
-shells and submodels out of a given (federated) virtual graph.
+shells and submodels out of a given (federated) virtual graph (the SPARQL-AAS Bridge).
 
 [![AAS Bridge(s)](/img/knowledge-agents/aas_bridge_small.png)](/img/knowledge-agents/aas_bridge.png)
 
@@ -268,20 +268,20 @@ There are two main components whose interplay implements the AAS-KA bridge:
 * A flexible SQL/JSON engine, such as Dremio or in parts also Postgresql which is able to mount raw data in various
 formats from remote filesystems and APIs. This engine is used to build flat relational views onto a hierarchical
 json structure that may originate in the value-only-serialization of the AAS. Typically there will be one table/view
-per json-schema/submodel template. As an example, see these [scripts](https://github.com/catenax-ng/product-knowledge/tree/main/infrastructure/resources/dremio)
-* A graph engine (such as [ontop](https://ontop-vkg.org/guide/) ) that is able to bind/translate SPARQL queries into SQL. As an example, see these [bindings](https://github.com/catenax-ng/product-knowledge/tree/main/infrastructure/oem/resources/trace.obda)
+per json-schema/submodel template. As an example, see these [scripts](https://github.com/big-data-spaces/knowledge-agent-deployment/tree/main/infrastructure/resources/dremio)
+* A graph engine (such as [ontop](https://ontop-vkg.org/guide/) ) that is able to bind/translate SPARQL queries into SQL. As an example, see these [bindings](https://github.com/big-data-spaces/knowledge-agent-deployment/tree/main/infrastructure/oem/resources/trace.obda)
 
 Of course, if the data is available in a native SQL-schema, the SQL/JSON-engine can be omitted. Likewise, even the graph engine
 can be left out if a sparql-capable database holds its data in conformance to the CX-ontologies.
 
-#### KA->AAS Bridge
+#### SPARQL->AAS Bridge
 
 In order to form a twin-based, highly-standarized access to any graphTo allow for a more strict
 In order to form a graph-based, flexible access to AAS backend components, we
 employ a bridge virtualization module which denormalizes/caches the information
 inside Shells and Submodels.
 
-Exposing substructures of the distributed knowledge graph via the AAS APIs is possible by deploying the [KA-AAS-Bridge](https://github.com/eclipse-tractusx/knowledge-agents-aas-bridge). This generic tool can be used to expose the graphs structures as AAS by configuring a set of mappings. Each consists of two components
+Exposing substructures of the distributed knowledge graph via the AAS APIs is possible by deploying the [KA-AAS-Bridge](https://github.com/eclipse-tractusx/knowledge-agents-aas-bridge) and its [KA-AAS Deployment](../operation-view/bridge). This generic tool can be used to expose the graphs structures as AAS by configuring a set of mappings. Each consists of two components
 
 * a SPARQL query extracting "flat" information out of the virtual graph
 * a mapping configuration providing the basic structure of the target AAS