Re-introducing @ruleCode

Description

Background

In railML 2.x a signal can be linked with a rule book identifier using attribute @ruleCode. In railML 3.x the @ruleCode attribute is (so far) not modelled.

Links

• Forum discussion:
  • Torben Brand, 25.02.2020: https://www.railml.org/forum/index.php?t=msg&th=712&start=0&
  • Torben Brand, 18.03.2022: https://www.railml.org/forum/index.php?t=msg&th=712&goto=2967&#msg_2967
• Trac tickets
  • #443 (closed)
• Wiki documentation
  • IS:signalIS: https://wiki3.railml.org/wiki/IS:signalIS

Solution proposal railML 3.2

Option 1: implement missing attribute @ruleCode for signals (and other signalling related elements)

Option 2: A new "designator-like" element is introduced with attributes @rulebook and @entry. This could be called <typeDesignator>

Option 3: use already available child element <designator> to specify a rule code.

Update 18.03.2022: Option 2 has been marked as preferred solution. The <typeDesignator> shall be available for all functional infrastructure elements.

• Version changed from 3.2 to 3.2b1_ETCS

as agreed in coordinators telco on March 2nd, 2021

changed the description

changed milestone to %3.2

removed 3.2 3.2b1_ETCS labels

changed the description

changed the description

changed the description

added Docu M Documentation labels and removed task label

solution option 2 has been implemented with railML 3.2 beta3

changed the description

closed

reopened

Documentation missing

added before knew how to link EA to GitLab

closed