-
Notifications
You must be signed in to change notification settings - Fork 27
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
resolve #432 remove AASd-120: idShort also allowed for elements #458
Conversation
within a SubmodelElementLis
see admin-shell-io/aas-specs-api#334 for impact on API: not yet resolved For "MySubmodelElementCollection.MySubSubmodelElementList2[0][0]" "MySubmodelElementCollection.MySubSubmodelElementList2[myFirstElement][anotherFirstElement]" |
of an idShortPath notation to be returned in an JSON array. | ||
For SubmodelElementLists the elements can be identified via its index or via its idShort. | ||
For identification via idShort the submodel element's idShort | ||
is separated by "." (dot) from top level down to child level. |
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.
there needs to be a final decision on handling with "." notation or via brackets
see #432 (comment). Also References need to be considered |
# Conflicts: # documentation/IDTA-01001/modules/ROOT/pages/changelog.adoc # documentation/IDTA-01001/modules/ROOT/pages/includes/constraints.adoc # documentation/IDTA-01001/modules/ROOT/pages/mappings/encodings/idshortpath.adoc # documentation/IDTA-01001/modules/ROOT/pages/spec-metamodel/constraints.adoc
use no idShort in IdShortPath for SML #501 instead |
#432 remove AASd-120: idShort also allowed for elements within a SubmodelElementList