| [railML3] Grouping IS:trainProtectionElement-s [message #3152] |
Mon, 30 October 2023 13:15  |
Larissa Zhuchyi
Messages: 49
Registered: November 2022
|
Member |
|
|
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,
Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
| Re: [railML3] Grouping IS:trainProtectionElement-s [message #3278 is a reply to message #3152] |
Mon, 19 August 2024 10:42  |
christian.rahmig
Messages: 474
Registered: January 2016
|
Senior Member |
|
|
Dear Larissa, dear all,
as there has been no feedback on the questions, I assume that the topic is not relevant for current railML 3 use case implementations.
However, let me add some comments to the issue for a potential future implementation:
* railML 3 uses both approaches for grouping elements. Therefore, principally both approaches are possible.
* If there are different features needed for the single train protection element and the train protection element group, let's define a new functional infrastructure element <trainProtectionElementGroup>.
* If there can be several grouping levels of train protection elements, let's use the @belongsToParent approach.
So, dear community, is the topic of grouping train protection elements interesting (and required) for you?
Best regards
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
