Specification of <balise> and <baliseGroup> and their relation
Description
The definition of elements and and their relationship between is not detailed enough and should be sharpened. In particular, it must be clarified how to model balises in a group.
Background
This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future.
railML2.4 defines a and a element. railML2.4nor defines clearer how these are to be modelled in relation to each other. This is done in three different ways:
- The balise group
- The balise group with individual defined functional balises
- Balise groups with individual balises with known locations
Additionally, the element is extended by the attribute “@switchable.”
For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.6.
Links
- Forum discussion:
- Torben Brand, 25.02.2021: [https://www.railml.org/forum/index.php?t=msg&th=798&goto=2673&#msg_2673]
- Trac tickets:
- #431
- Wiki documentation:
- IS:balise: [http://wiki2.railml.org/wiki/IS:balise]
- IS:baliseGroup: [http://wiki2.railml.org/wiki/IS:baliseGroup]
Proposed solution in railML 2.5
The element shall be extended with new attribute @type (values: "fixed" and "controlled") to describe that the balise is switchable. A "controlled" balise is switchable while a "fixed" balise is not switchable and can only submit one fixed dataset.
The enumeration of attribute @type shall be extended to cover specific (national) types of balises. (Attention: enumeration is already extendable)
A best practice example (or three ones) shall be added to the railML2 wiki pages of and .
It is suggested to model the balise/baliseGroup relation in three levels of detail:
- Only the baliseGroup
- One dummy balise is placed (since baliseGroup cannot exist alone) using attributes @id, @dir and @pos
- baliseGroup with individual functional balises
- All balises of baliseGroup are placed with identical locations (describing the location of the very first balise of the baliseGroup) using attributes @id, @name, @dir, @pos
- baliseGroup with individual balises with (real) locations