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 previous message
Jörgen Strandberg is currently offline  Jörgen Strandberg
Messages: 15
Registered: August 2017
Junior Member
Hi

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:annotation>
<xs:documentation>This balise group transmits at least a UNISIG Packet 90.</xs:documentation>
</xs:annotation>
</xs:enumeration>
<xs:enumeration value="stopIfInStaffResponsible">
<xs:annotation>
<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>
</xs:annotation>
</xs:enumeration>

(This was brought up during ETCS working group meeting.)

Report message to a moderator

[Message index]
 
Read Message
Read Message
Previous Topic: [railML3] Signalled braking distance of a line (de: Regelbremsweg einer Strecke)
Next Topic: Sequence of infrastructure-subelements
Goto Forum:
  

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

Current Time: Mon Apr 29 01:27:50 CEST 2024