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
Registration of a new twin is (at least in Catena-X) equivalent to the creation of a new twin. Thus, a Data Provider
should always ensure that there is no AAS-descriptor created for the respective assetIds yet. If there already is one,
the submodel-descriptor should
be [added to the existing shell-descriptor](#registering-a-new-submodel-at-an-existing-twin).
Aside from the fact, that this could be a single LoC the wording does not make much sense to me.
Suggestion: Registration of a new twin is (at least in Catena-X) equivalent to the creation of a new twin. Thus, a Data Provider should always ensure that an AAS-descriptor for the respective assetIds does not exist yet. If one exists, the submodel-descriptor should be [added to the existing shell-descriptor](#registering-a-new-submodel-at-an-existing-twin).
The text was updated successfully, but these errors were encountered:
eclipse-tractusx.github.io/docs-kits/kits/Digital Twin Kit/Software Development View/page_software-development-view.md
Lines 164 to 167 in ea9e89e
Aside from the fact, that this could be a single LoC the wording does not make much sense to me.
Suggestion:
Registration of a new twin is (at least in Catena-X) equivalent to the creation of a new twin. Thus, a Data Provider should always ensure that an AAS-descriptor for the respective assetIds does not exist yet. If one exists, the submodel-descriptor should be [added to the existing shell-descriptor](#registering-a-new-submodel-at-an-existing-twin).
The text was updated successfully, but these errors were encountered: