feat: first updated esds communication KIT. by Andrew96897 · Pull Request #1555 · eclipse-tractusx/eclipse-tractusx.github.io

Andrew96897 · 2026-06-18T08:15:58Z

Description

[ADDED BY MATHIAS]

This is like the kit logo looks like:

From sideways:

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
Copyright and license header are present on all affected files

- Introduced a new category for the eSDScom KIT in sidebarsDocsKits.js with links to its changelog and views. - Added the eSDScom KIT logo as an SVG file along with its licensing information. - Updated the generated kit navigation items to include the eSDScom KIT with its corresponding route.

matbmoser

So I have supported you on finding a logo and setting up the KIT structure correctly.

I did not changed any content from the KIT since this is something that I would expect you to do (Since you know more than me)

However I have provided some feedback as an external adopter, and also added some points which normally other KITs are also doing.

I feel that is missing some "valuable" content description here, like some JSON payloads for example. I see the model is not published so I would recommend you to add it here.

I know it is long, but it would bring value if it is at least organized in sections with each payload being available to be seen in JSON format.

You can use <details> tags to hide the payloads so it is easier to read if the files are too big. I have provided some examples how to do it. You can even include it inside code blocks from Markdown.

matbmoser · 2026-06-18T12:41:15Z

+
+### Core Semantic Models
+
+[io.catenax.esdscom 1.0.0 extended Safety Data Sheet communication](https://github.com/eclipse-tractusx/sldt-semantic-models/tree/main/io.catenax.esdscom/1.0.0)


This link does not exists! There is no published datamodel, and if it would be published this would not be the url.

Since this model is not published feel free to add it here:

<details> <summary><strong>Catena-X Safety Datasheet Model Payload</summary> Add your model here: ... </details>

matbmoser · 2026-06-18T12:42:49Z

+                "leftOperand": "UsagePurpose",
+                "operator": "isAnyOf",
+                "rightOperand": [
+                  "cx.esdscom.base:1"


is this aligned with the Expert Group from data sovereignty? @DanielaWuensch

Not sure if this is how we should reference.

was already checked.

Was aligned with Daniela Wuensch.

Mail von Freitag, 10. April 2026:
"Hallo Dirk, hallo Anita,

Die Änderung in CX-0152 zum eSDScom purpose sind in diesem PR an dieser Stelle:

https://github.com/catenax-eV/product-standardization-prod/pull/597/changes#diff-b809678ec8be329cbfeb3079b29409b6338f87cce75bab0075355a9931e0b6a9R221

bereit für den Review. Darauf könnt ihr euch dann mit dem rightOperand cx.esdscom.base:1 des Usage Purpose beziehen.

Viele Grüße,
Daniela"

matbmoser · 2026-06-18T12:43:06Z

+
+## Tutorials & Resources
+
+Not yet available.


If you dont have tutorials just remove it.

matbmoser · 2026-06-18T12:48:07Z

+### Model Example
+
+Due to the model size, for further information please refer to [esdscom.eu](https://esdscom.eu)
+


We could add an example here if you would like, that would give some quality to the documentation.

feel free to add it like this, so it gets "hidden" in a dropdown:

<details> <summary><strong>XML Safety Datasheet Model</summary> Add your model here: ... </details>

@dirk-qualisys : Could you please add the draft model or the XML here?

matbmoser · 2026-06-18T12:54:31Z

@copilot please find typos

matbmoser · 2026-06-18T12:59:03Z

Please review if the KIT logo is correct and you like it. Added a random color, since this is a different use case than "just sustainability".

Copilot

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

matbmoser · 2026-06-19T06:47:11Z

Policy is correct just confirmed with the DataSov EG. Not sure if we should use Neptune 2026/09/ in the context from json-ld.

matbmoser · 2026-06-19T06:48:01Z

+      "https://w3id.org/catenax/2025/9/policy/odrl.jsonld",
+      "https://w3id.org/catenax/2025/9/policy/context.jsonld"


This is where I meant. @jSchuetz88 is possible to use 2026 here?

hillmer · 2026-06-19T09:24:23Z

@matbmoser : we try to eliminate the errors within the ticket but cannot edit. Can you please advice us, how to fork this repository, so that we can work in it?

matbmoser · 2026-06-22T09:17:23Z

@matbmoser : we try to eliminate the errors within the ticket but cannot edit. Can you please advice us, how to fork this repository, so that we can work in it?

ok normally Andrew could edit its own branch in the fork

matbmoser · 2026-06-22T09:17:58Z

I can apply at least the suggestions I have done.

matbmoser · 2026-06-22T09:21:38Z

@Andrew96897 I have applied the edit to the points I have told. The only thing that is missing is to add the data models. @hillmer adding the data models is something that I cant do. I have requested the KIT master builder to do a check for typos and final quality checks.

Copilot

Pull request overview

Copilot reviewed 7 out of 13 changed files in this pull request and generated 13 comments.

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

matbmoser · 2026-06-25T07:39:23Z

+### Changed
+
+- Nothing yet
+
+### Deprecated
+
+- Nothing yet
+
+### Removed
+
+- Nothing yet
+
+### Fixed
+
+- Nothing yet
+
+### Security
+
+- Nothing yet


This we should remove

matbmoser · 2026-06-25T07:44:09Z

+                "leftOperand": "UsagePurpose",
+                "operator": "isAnyOf",
+                "rightOperand": [
+                  "cx.esdscom.base:1"


was already checked.

matbmoser · 2026-06-25T07:46:45Z

+
+Model: eSDScom
+Version: 1.0.0
+Namespace: urn:samm:io.catenax.eSDScom:1.0.0


@jSchuetz88 could you check here please.

matbmoser · 2026-06-25T07:47:41Z

+#### Standards
+
+Technical standards and protocol compliance are not applicable.
+
+#### Tutorials
+
+Developer quick-start guides and code examples are not yet available.


Suggested change

#### Standards

Technical standards and protocol compliance are not applicable.

#### Tutorials

Developer quick-start guides and code examples are not yet available.

I would take this out, because it does not adds value.

stanfaldin · 2026-06-29T09:09:07Z

Closes #https://github.com/eclipse-tractusx/eclipse-tractusx.github.io/pull/1555#discussion_r3472679137

semantic model part updated

matbmoser · 2026-07-30T07:56:02Z

what is the latest state from this pr

Copilot

Pull request overview

Copilot reviewed 7 out of 13 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (6)

data/kitsData.js:481

The logo SVG contains an explicit “Uploaded to: SVG Repo” marker, but the master data license block doesn’t provide originalSourceUrl (supported by the schema) to reference the original third-party source. For TRG 7.07 third-party attribution, please add originalSourceUrl pointing to the exact SVG Repo asset page (and keep sourceUrl as the repository copy).

      logoLicencse: {
        type: 'CC-BY-4.0',
        authors: '2026 eSDScom Workgroup and contributors; 2026 Catena-X Automotive Network e.V.; 2026 Contributors to the Eclipse Foundation',
        licenseUrl: 'https://github.com/eclipse-tractusx/eclipse-tractusx.github.io/blob/main/static/img/kits/esdscom-kit/esdscom-kit-raw-logo.svg.license',
        sourceUrl: 'https://github.com/eclipse-tractusx/eclipse-tractusx.github.io/blob/main/static/img/kits/esdscom-kit/esdscom-kit-raw-logo.svg'

static/img/kits/esdscom-kit/esdscom-kit-raw-logo.svg.license:6

The .license sidecar is missing the eSDScom Workgroup attribution even though data/kitsData.js lists it in the authors. Also, since the SVG indicates it was sourced from SVG Repo, TRG 7.07 third-party attribution expects the original source URL (and ideally author) to be captured (either here or via originalSourceUrl in master data).

- SPDX-License-Identifier: CC-BY-4.0
- SPDX-FileCopyrightText: 2026 Contributors to the Eclipse Foundation
- SPDX-FileCopyrightText: 2026 Catena-X Automotive Network e.V.
- Source URL: https://github.com/eclipse-tractusx/eclipse-tractusx.github.io/blob/main/static/img/kits/esdscom-kit/esdscom-kit-raw-logo.svg

docs-kits/kits/esdscom-kit/adoption-view/adoption-view.md:9

The copyright header uses Copyright(c) without a space. TRG 7.02 recommends the canonical format Copyright (c) <year> ... for consistency across the repo.

<!--
Copyright(c) 2026 Contributors to the Eclipse Foundation

docs-kits/kits/esdscom-kit/development-view/development-view.md:9

The copyright header uses Copyright(c) without a space. TRG 7.02 recommends the canonical format Copyright (c) <year> ... for consistency across the repo.

<!--
Copyright(c) 2026 Contributors to the Eclipse Foundation

docs-kits/kits/esdscom-kit/changelog.md:9

The copyright header uses Copyright(c) without a space. TRG 7.02 recommends the canonical format Copyright (c) <year> ... for consistency across the repo.

<!--
Copyright(c) 2025 Contributors to the Eclipse Foundation

docs-kits/kits/esdscom-kit/development-view/development-view.md:54

This section still contains a placeholder standard identifier (CX-XXXX). Shipping placeholders in KIT docs is confusing for readers and makes the compliance requirements ambiguous.

To participate in the eSDScom use case, the following single standard MUST be fulfilled only by data providers:

- CX-XXXX eSDScom In the Catena-X technical landscape, the standard assumes the use of CX-0126-IndustryCorePartType.
The architecture follows a pull-based pattern: data is pushed from supplier to consumer (or other way around) but made accessible by the data provider. This standard applies equally to Data Providers and Consumers. All parties involved in the exchange must implement the agreed data structure and access patterns to ensure interoperability within the Catena-X network.

+      type: 'category',
+      label: 'eSDScom KIT',
+      link: { type: 'generated-index' }
+      collapsed: true,


hillmer · 2026-07-30T08:06:13Z

Status: We need support in the github topics for creating this PR. There are several comments which we do not understand, Until now the status is that we wait for the data model release and continue afterwards

…nd consistency

…itsData

matbmoser

I just confirmation from @jSchuetz88 that your standard will be the CX-0162 I will add it here already.

matbmoser · 2026-08-07T10:01:50Z

+
+To participate in the eSDScom use case, the following single standard MUST be fulfilled only by data providers:
+
+- CX-XXXX eSDScom In the Catena-X technical landscape, the standard assumes the use of CX-0126-IndustryCorePartType.


Suggested change

- CX-XXXX eSDScom In the Catena-X technical landscape, the standard assumes the use of CX-0126-IndustryCorePartType.

- CX-0162 eSDScom In the Catena-X technical landscape, the standard assumes the use of CX-0126-IndustryCorePartType.

matbmoser

Ok I just saw two very important things which were wrong with the content. @Andrew96897 @hillmer

matbmoser · 2026-08-07T10:06:20Z

+- CX-XXXX eSDScom In the Catena-X technical landscape, the standard assumes the use of CX-0126-IndustryCorePartType.
+The architecture follows a pull-based pattern: data is pushed from supplier to consumer (or other way around) but made accessible by the data provider. This standard applies equally to Data Providers and Consumers. All parties involved in the exchange must implement the agreed data structure and access patterns to ensure interoperability within the Catena-X network.
+
+1. All Identification and Access Management (IAM) follows the CX-0015 IAM & Access Control Paradigm for users and Clients standard [https://catenax-ev.github.io/docs/standards/CX-0015-IAMandAccessControlParadigmForUsersAndClients] which lays out the principles for both, data providers and data consumers.


Just a quick modification that I have just saw which is wrong:

Suggested change

1. All Identification and Access Management (IAM) follows the CX-0015 IAM & Access Control Paradigm for users and Clients standard [https://catenax-ev.github.io/docs/standards/CX-0015-IAMandAccessControlParadigmForUsersAndClients] which lays out the principles for both, data providers and data consumers.

1. All Data Exchange Requirements follows the CX-0018 Dataspace Connectivity [https://catenax-ev.github.io/docs/standards/CX-0018-DataspaceConnectivity] and which lays out the principles for both, data providers and data consumers. More information can be found in the [Connector KIT](https://eclipse-tractusx.github.io/docs-kits/kits/connector-kit/adoption-view).

The IAM principal works different in Catena-X it is only valid for the portal, not for the data exchange, so we are not authenticating using Keycloak the data exchange, but rather using the CX-0018 standard which is core.

matbmoser · 2026-08-07T10:09:17Z

+1. All Identification and Access Management (IAM) follows the CX-0015 IAM & Access Control Paradigm for users and Clients standard [https://catenax-ev.github.io/docs/standards/CX-0015-IAMandAccessControlParadigmForUsersAndClients] which lays out the principles for both, data providers and data consumers.
+2. Both, the data providers and consumers shall be identified in the Catena-X dataspace following the CX-0010 Business Partner Number Standard [https://catenax-ev.github.io/docs/standards/CX-0010-BusinessPartnerNumber] so that a clear identification of both parties enables automatic data exchange.
+The Onboarding of the parties on the Catena-X Dataspace shall be effectuated following the CX-0006 Registration and initial Onboarding standard [https://catenax-ev.github.io/docs/standards/CX-0006-RegistrationAndInitialOnboarding].
+


Suggested change

3. The data provider party must have a digital twin registry which comply with the [CX-0002](https://catenax-ev.github.io/docs/standards/CX-0002-DigitalTwinsInCatenaX) standard, detailed in the [Digital Twin KIT](https://eclipse-tractusx.github.io/docs-kits/kits/digital-twin-kit/adoption-view). In this way the eSDScom data model can be provided in a AAS Shell Descriptor as a Submodel, more information in the [development view](./development-view/development-view.md).

matbmoser · 2026-08-07T14:01:53Z

After this clarification I can merge.

updated esds

b20d410

github-project-automation Bot added this to Tractus-X Webpage Jun 18, 2026

github-project-automation Bot moved this to Inbox in Tractus-X Webpage Jun 18, 2026

matbmoser self-requested a review as a code owner June 18, 2026 12:39

matbmoser reviewed Jun 18, 2026

View reviewed changes

matbmoser requested a review from Copilot June 18, 2026 12:54

Copilot started reviewing on behalf of matbmoser June 18, 2026 12:55 View session

matbmoser mentioned this pull request Jun 18, 2026

1st version of eSDScom KIT #1551

Closed

2 tasks

matbmoser changed the title ~~first updated esds~~ feat: first updated esds communication KIT. Jun 18, 2026

Copilot AI reviewed Jun 18, 2026

matbmoser reviewed Jun 19, 2026

View reviewed changes

Update docs-kits/kits/esdscom-kit/adoption-view/adoption-view.md

b008ec0

matbmoser added 2 commits June 22, 2026 11:18

Update docs-kits/kits/esdscom-kit/development-view/development-view.md

edbb1d6

Update docs-kits/kits/esdscom-kit/adoption-view/adoption-view.md

54c2dd4

matbmoser requested a review from Copilot June 22, 2026 09:18

Copilot started reviewing on behalf of matbmoser June 22, 2026 09:19 View session

Copilot AI reviewed Jun 22, 2026

View reviewed changes

feat: fixed typos and apply suggestions from code review

5d7bc4f

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

matbmoser reviewed Jun 25, 2026

View reviewed changes

Andrew96897 and others added 3 commits June 25, 2026 10:24

Changes made after attending KIT open office hour

79ec6ad

Fix typo in use case description for eSDScom

8121220

Update sidebarsDocsKits.js

e1f4a6f

stephanbcbauer linked an issue Jun 29, 2026 that may be closed by this pull request

Release of eSDScom KIT eclipse-tractusx/sig-release#1534

Open

Update adoption-view.md

01e4f11

semantic model part updated

matbmoser requested a review from Copilot July 30, 2026 07:56

Copilot started reviewing on behalf of matbmoser July 30, 2026 07:56 View session

Copilot AI reviewed Jul 30, 2026

View reviewed changes

Comment thread sidebarsDocsKits.js

Comment on lines +697 to +700

type: 'category',

label: 'eSDScom KIT',

link: { type: 'generated-index' }

collapsed: true,

matbmoser reviewed Aug 6, 2026

View reviewed changes

Comment thread docs-kits/kits/esdscom-kit/development-view/development-view.md Outdated

Comment thread docs-kits/kits/esdscom-kit/development-view/development-view.md

matbmoser added 3 commits August 6, 2026 09:39

Update docs-kits/kits/esdscom-kit/development-view/development-view.md

397a1c2

Update docs-kits/kits/esdscom-kit/development-view/development-view.md

b30292b

Merge branch 'main' into eSDS

ff386a4

matbmoser reviewed Aug 6, 2026

View reviewed changes

Comment thread docs-kits/kits/esdscom-kit/development-view/development-view.md

Comment thread docs-kits/kits/esdscom-kit/development-view/development-view.md Outdated

matbmoser added 3 commits August 6, 2026 09:48

Update docs-kits/kits/esdscom-kit/development-view/development-view.md

e2d460f

Update docs-kits/kits/esdscom-kit/development-view/development-view.md

360a2d0

Update content hash in auto-generated kitNavItems.js

936c2e9

matbmoser reviewed Aug 6, 2026

View reviewed changes

Comment thread docs-kits/kits/esdscom-kit/resources/REUSE.toml Outdated

Comment thread docs-kits/kits/esdscom-kit/changelog.md

matbmoser added 4 commits August 6, 2026 10:47

Update docs-kits/kits/esdscom-kit/resources/REUSE.toml

ca80597

Update docs-kits/kits/esdscom-kit/changelog.md

4826189

Update adoption-view and development-view documentation for clarity a…

d125198

…nd consistency

Update versioning and release date for eSDScom KIT in changelog and k…

406f04d

…itsData

matbmoser reviewed Aug 7, 2026

View reviewed changes

matbmoser requested changes Aug 7, 2026

View reviewed changes

github-project-automation Bot moved this from Inbox to Todo in Tractus-X Webpage Aug 7, 2026


		### Core Semantic Models

		[io.catenax.esdscom 1.0.0 extended Safety Data Sheet communication](https://github.com/eclipse-tractusx/sldt-semantic-models/tree/main/io.catenax.esdscom/1.0.0)

		### Model Example

		Due to the model size, for further information please refer to [esdscom.eu](https://esdscom.eu)

		"https://w3id.org/catenax/2025/9/policy/odrl.jsonld",
		"https://w3id.org/catenax/2025/9/policy/context.jsonld"


		To participate in the eSDScom use case, the following single standard MUST be fulfilled only by data providers:

		- CX-XXXX eSDScom In the Catena-X technical landscape, the standard assumes the use of CX-0126-IndustryCorePartType.

	- CX-XXXX eSDScom In the Catena-X technical landscape, the standard assumes the use of CX-0126-IndustryCorePartType.
	- CX-0162 eSDScom In the Catena-X technical landscape, the standard assumes the use of CX-0126-IndustryCorePartType.

	1. All Identification and Access Management (IAM) follows the CX-0015 IAM & Access Control Paradigm for users and Clients standard [https://catenax-ev.github.io/docs/standards/CX-0015-IAMandAccessControlParadigmForUsersAndClients] which lays out the principles for both, data providers and data consumers.
	1. All Data Exchange Requirements follows the CX-0018 Dataspace Connectivity [https://catenax-ev.github.io/docs/standards/CX-0018-DataspaceConnectivity] and which lays out the principles for both, data providers and data consumers. More information can be found in the [Connector KIT](https://eclipse-tractusx.github.io/docs-kits/kits/connector-kit/adoption-view).

Uh oh!

Conversation

Andrew96897 commented Jun 18, 2026 • edited by matbmoser Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Pre-review checks

Uh oh!

matbmoser left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

A-KKunert Jun 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

matbmoser commented Jun 18, 2026

Uh oh!

matbmoser commented Jun 18, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

matbmoser commented Jun 19, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

hillmer commented Jun 19, 2026

Uh oh!

matbmoser commented Jun 22, 2026

Uh oh!

matbmoser commented Jun 22, 2026

Uh oh!

matbmoser commented Jun 22, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

stanfaldin commented Jun 29, 2026

Uh oh!

matbmoser commented Jul 30, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Andrew96897 commented Jun 18, 2026 •

edited by matbmoser

Loading

A-KKunert Jun 26, 2026 •

edited

Loading

matbmoser left a comment •

edited

Loading