Dear all
railML.org would be grateful if you could tell:
(1) is there a need to extend railML 3.3 by a new element <trainProtectionElementGroup> (with reference attribute) or a new attribute @belongsToParent of an existing element <trainProtectionElement>?
(2) did you find a way to group <trainProtectionElement>-s by existing (railML 3.2) elements?
Currently, the need occurs when transforming the Simple example of railML from 2.5 to 3.2: <trainProtectionElementGroup> of railML 2.5 (see source code below) is lost because of missing correspondent element and attribute in railML3.
<trainProtectionElements>
<trainProtectionElement id="tr03_tpe01" pos="3800" absPos="4300" dir="up" medium="magnetic" trainProtectionSystem="Indusi"/>
<trainProtectionElementGroup id="tr03_tpeg01">
<trainProtectionElementRef ref="tr03_tpe01"/>
</trainProtectionElementGroup>
</trainProtectionElements>
As "Simple example" is just a learning material, railML.org wonders whether <trainProtectionElementGroup> is needed in practice.
Thanks in advance.
Sincerely,