Home » railML newsgroups » railML.infrastructure » [railML3] Designator for NetElements (The designator element shall be added to NetElements.)
[railML3] Designator for NetElements [message #2879] Mon, 17 January 2022 14:16 Go to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 439
Registered: January 2016
Senior Member
Dear all,

within the ETCS use case working group we discussed about adding a designator child element for the topology base element <netElement> (see [1]). So far, a <designator> is only available for all elements within <functionalInfrastructure>, e.g. balises, levelCrossings etc.

The requirement has already been filed in railML development Git system [2].

Please communicate your additional requirements and needs for a <designator> child element in <netElement> here in the forum.

[1] https:// www.railml.org/en/event-reader/railml-is-etcs-telco-2021-10- 18.html
[2] https://development.railml.org/railml/version3/-/issues/476

Thank you very much and best regards
Christian


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: [railML3] Designator for NetElements [message #2918 is a reply to message #2879] Mon, 21 February 2022 14:43 Go to previous messageGo to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 439
Registered: January 2016
Senior Member
Dear all,

after discussion among the railML coordinators, we moved the issue from railML 3 to RTM [1]. However, the central question remains: how shall the <designator> be used? Where do the values come from?

[1] https://development.railml.org/railml/railtopomodel/-/issues/1

Best regards
Christian


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: [railML3] Designator for NetElements [message #2960 is a reply to message #2918] Wed, 16 March 2022 13:04 Go to previous messageGo to next message
Karl-Friedemann Jerosch is currently offline  Karl-Friedemann Jerosch
Messages: 11
Registered: May 2020
Junior Member
Similar to the application of the designator in "functionalInfrastructure" or "assetsForInterlocking", we would like to introduce the <designator> also for the RTM <netElement>.

a) If a railML-file is available as input to a tool chain of independent systems, this could provide a common reference for the tools.

Example:
<netElement id="ne_206" length="7889">
  <designator register="_tool_01" entry="STC-T101_T201_T301" description="common edge name in all tools"/>
  ...
</netElement>

b) On the other hand, if railML files from different tools needs to be combined and no input-reference is available, then it is helpful to have an information of the element's name in each tool.

Example:
<netElement id="ne_206" length="7889">
  <designator register="_tool_01" entry="STC-T101_T201_T301" description="edge name in tool_01"/>
  <designator register="_tool_02" entry="STC-P01_Track1_P03" description="edge name in tool_02"/>
  ...
</netElement> 
Re: [railML3] Designator for NetElements [message #2993 is a reply to message #2960] Mon, 04 April 2022 18:01 Go to previous message
Milan Wölke is currently offline  Milan Wölke
Messages: 142
Registered: April 2007
Senior Member
Hi Karl-Friedemann,

Im really not sure if this approach is going in the right direction. After all the netElement layerof the infrastructure forms an abstract graph on which to place the real world elements, which already include designators. Im not sure if names of elements of this abstract graph should be exchanged as part of the standard. Shouldnt an edge in this graph be defined by its neighboring elements of the functional infrastructure? Otherwise why to split an edge?
Additionally Im not convinced that the designator is really the right tool for this. After all the idea for the designator was to specify a register that is commonly known. The underscore register was intended as an exception, as far as I know. Modelling a designator here would invert this understanding.

My 3 cents.

Best regards, Milan


Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: [railML 3.2] How to handle different granularity in node-edge-models at the level="micro"?
Next Topic: [railML3] Signalled braking distance of a line (de: Regelbremsweg einer Strecke)
Goto Forum:
  


Current Time: Fri Jun 21 00:42:24 CEST 2024