feat: prepare DT Kit for CX R3.2 #314
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arnoweiss
changed the title
|
LGTM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The DT Kit should contain examples for use-cases and subsequent Kits how Digital Twin Submodels and Registries can be registered at the EDC. Having proper and harmonized registration across use-cases and business-domains is key for successful discovery of DTs.
This Draft PR shall serve as discussion forum to agree on a preliminary consensus for R3.2 applicable to tractus-edc v0.5.0. Since standardization of CX-0002 is already done, this structure is not standardized. The examples to agree on in the Kit are explicitly not normative. They are working examples that may one day become standards.
So, please: Discuss!
Replacement for #294 that was reverted by #308
ToDos: