You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a reader of the Digital Twin KIT I assume that all mentioned reference implementations are End2End tested in Catena-X/Tractus-X.
This understanding was communicated to TC4M but is a misunderstanding.
The table "Deployment" mentions reference implementations for Submodel Server: FAAST, Basyx and AASX Server. However, Tractus-X does not make End2End Tests with these servers to ensure that the tool chain is working.
Proposal:
Add note stating that no End2End testing for these implementations is done and that usage and testing of these implementations is in the scope of the solution developer.
Change header of column "Reference Implementation" to "(Reference) Implementation"
Acceptance Criteria
Documentation updated
The text was updated successfully, but these errors were encountered:
Description
https://eclipse-tractusx.github.io/docs-kits/kits/Digital%20Twin%20Kit/Operation%20View%20Digital%20Twin%20Kit
As a reader of the Digital Twin KIT I assume that all mentioned reference implementations are End2End tested in Catena-X/Tractus-X.
This understanding was communicated to TC4M but is a misunderstanding.
The table "Deployment" mentions reference implementations for Submodel Server: FAAST, Basyx and AASX Server. However, Tractus-X does not make End2End Tests with these servers to ensure that the tool chain is working.
Proposal:
Add note stating that no End2End testing for these implementations is done and that usage and testing of these implementations is in the scope of the solution developer.
Change header of column "Reference Implementation" to "(Reference) Implementation"
Acceptance Criteria
The text was updated successfully, but these errors were encountered: