Home » railML newsgroups » railML.infrastructure » [railML3] Grouping IS:trainProtectionElement-s (missing mechanism to group IS:trainProtectionElement-s)
Re: [railML3] Grouping IS:trainProtectionElement-s [message #3278 is a reply to message #3152] Mon, 19 August 2024 10:42 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 465
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

Report message to a moderator

[Message index]
 
Read Message
Read Message
Previous Topic: [railML3] Modelling location of <overCrossing>, <underCrossing> in the network
Next Topic: [railML3] Road traffic signals
Goto Forum:
  

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

Current Time: Wed Oct 02 15:11:35 CEST 2024