Home » railML newsgroups » railML.infrastructure » [railML3] balise group functional type suggestions (Suggested changes to tBaliseGroupFunctionalType in railML v3.2 beta3)
[railML3] balise group functional type suggestions [message #2988] Mon, 04 April 2022 09:53 Go to next message
Jörgen Strandberg is currently offline  Jörgen Strandberg
Messages: 15
Registered: August 2017
Junior Member

For conformity, these enumeration values the 'BaliseGroup'-suffix should be removed, alternatively the suffix should be added to all other enumeration values:

<xs:enumeration value="infillBaliseGroup"/>
<xs:enumeration value="signalBaliseGroup"/>

These enumeration values should be added:

<xs:enumeration value="trackAheadFree">
<xs:documentation>This balise group transmits at least a UNISIG Packet 90.</xs:documentation>
<xs:enumeration value="stopIfInStaffResponsible">
<xs:documentation>This balise group transmits at least a UNISIG Packet 137 including Q_SRSTOP=0 for the mileageDirection valid for this function.</xs:documentation>

(This was brought up during ETCS working group meeting.)
Re: [railML3] balise group functional type suggestions [message #2996 is a reply to message #2988] Thu, 07 April 2022 14:28 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 439
Registered: January 2016
Senior Member
Dear Jorgen,

thank you very much for your feedback. I re-opened the Git issue #366 [1] and updated its description accordingly. The changes will be implemented with railML 3.2 release.

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

Best regards

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: [railML3] Signalled braking distance of a line (de: Regelbremsweg einer Strecke)
Next Topic: Sequence of infrastructure-subelements
Goto Forum:

Current Time: Thu Jun 20 23:48:24 CEST 2024