-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(trace): traceability kit release for 23.09 (3.2.0) #322
docs(trace): traceability kit release for 23.09 (3.2.0) #322
Conversation
Update the Traceability KIT because of the EDC asset structure rework for Release 3.2
docs(trace): updated KIT with changes because of AAS v3.0
…et structure to give data provides more flexibility in how to create EDC assets for submodels of digital twins
…port and how to invoke it
… 0.4.x With EDC 0.4.x, the asset:prop:* fields no longer exists and are replaced with a DCAT Catalog based approach. Filter criteria as previously defined no longer work. As a quick fix, only the asset id (referenced by id) is allowed in subprotocolBody for release 3.2.
…try-v2 docs(trace): updated KIT to reflect that a decentralized DTR is used
…ew, adoption view
… in Traceability Kit
…rework docs(trace): updated conventions for submodel descriptors and EDC asset structure
docs(trace): update policies for release 3.2
docs-kits/kits/Traceability Kit/Software Development View/page_software-development-view.md
Outdated
Show resolved
Hide resolved
docs-kits/kits/Traceability Kit/Software Development View/page_software-development-view.md
Outdated
Show resolved
Hide resolved
From my point of view just a view minor things, that would not block a merge, but could be considered for further improvement:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall, but cannot provide feedback on the contents, so further approvals should be given
Based on @SebastianBezold comments:
I updated the files accordingly to only mention "release" instead of "Catena-X release" to reduce misunderstandings.
I updated and added some links to the standards. Nevertheless due to the current timeline, it isn't possible to link to the correct standard. As I understand, @danielmiehle will discuss this in the lifecycle process. |
This pull request is still in Draft mode since it waits for internal approval of the traceability use case team as well as a successful quality gate check. If both things are fulfilled, I will change it to be ready for the merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please add the versions of the standards you are referencing to
(e.g. CX - 0004 Semantic Model V 1.0.1)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After IP clearance - PR will be merged.
docs(trace): Removed optional customer attributes from Batch aspect model
docs(trace): updated how to define visibility for digital twins based on the concept
10c7a90
to
48281ed
Compare
Just to let you know, IP clearance has been successful. The branch is updated to the current status of |
This pull request updates the Traceability KIT to be compatible with the Catena-X release 3.2.0.