Closed JoergNeidig closed 9 months ago
maybe Section 5.3.10.4 Constraints is relevant
For referencing a Submodel from an AAS, you indeed just need one key. However, if referring to a SubmodelElement from a ReferenceElement, you need to concatenate more keys to the unique id to construct the path to the desired SubmodelElement. See example
A bunch of the examples online are wrong unfortunately and the whole referencing mechanism in the AAS is at best clumsy.
@JoergNeidig 2024-01-15 is ist sill relevant, or can it be merged with #103
Topic is still relevant, but should be merged with #103, because good examples could answer both questions.
Goes into #103
What does it mean, if a ModelReference has multiple keys? Is there one "main" key? If so, is it the first one in the list? Usually keys/ids are used to identify an element. Does it even make sense to have more than one (sometimes it might make sense if the reference stores semantic information and no IDs)?