Section E.4 shows syntax for a path that can go down the subcomponent hierarchy to assign a value to an EMV2 element. It uses @ as separator of the core part from the EMV2 part. Users can also specify the element within its own subclause by just specifying the qualified name (element with optional type) within the subclause.
In AADLV2 we introduced the concept of data set to associate property values with AADL models. This would allow us to avoid contained property associations - a goal for AADL V3.
Also, the path starting with the core model has not been implemented and sofar noone has complained.
Section E.4 shows syntax for a path that can go down the subcomponent hierarchy to assign a value to an EMV2 element. It uses @ as separator of the core part from the EMV2 part. Users can also specify the element within its own subclause by just specifying the qualified name (element with optional type) within the subclause. In AADLV2 we introduced the concept of data set to associate property values with AADL models. This would allow us to avoid contained property associations - a goal for AADL V3. Also, the path starting with the core model has not been implemented and sofar noone has complained.