Home » railML newsgroups » railML.infrastructure » [railMl2] Proposal for new attribute @switchable in <baliseGroup> and wiki refinement
Re: [railMl2] Proposal for new attribute @switchable in <baliseGroup> and wiki refinement [message #2719 is a reply to message #2697] Thu, 20 May 2021 12:34 Go to previous messageGo to previous message
Torben Brand is currently offline  Torben Brand
Messages: 158
Registered: March 2016
Senior Member
If @switchable should be on the <balise> or on the <baliseGroup> depends if the attribute is meant to be physical (on the balise) or on the logical level forming a variable message (on the baliseGroup).

We think it should describe both, so we suggest placing it on the balise. This is in line with @switchable being on the signal and not on the signal's aspect/route. Also, the reference/use of a <balise> is mandatory so the placement on the <balise> would not force the use of a <balise> if you need to indicate @switchable for a <baliseGroup>. Further this would give the additional information which of the individual balises are switchable. Usually in a balise group with variable messages only the first balise is switchable (relaying the signal aspect).

Bane NOR agrees also to this with the argument that the same information is also on the balise and not on the baliseGroup in railML3.2. The terms for the attribute and its values are different, but the placement is the same: railML2.5 balise@switchable="yes/no" = railML3.2 balise@type="controlled/fixed"

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3]: operationalPoint of operationalType="block"
Next Topic: Suggested definition of <ocpVis>
Goto Forum:
  

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

Current Time: Thu May 09 09:53:35 CEST 2024