Home » railML newsgroups » railML.infrastructure » [railML3] Designator for NetElements (The designator element shall be added to NetElements.)
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: 141
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

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
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:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri May 17 09:53:52 CEST 2024