| Suggested extension for operating rules [message #2283] |
Wed, 04 December 2019 16:13  |
Torben Brand
Messages: 157
Registered: March 2016
|
Senior Member |
|
|
Many objects mapped by railML2.4 have special operating rules. The norwegian sector suggests a new trunk element <operatingRules> which will group and map those special rules. Only special rules that differ from the generic rule book and apply for specific physical objects are mapped. The generic rule book shall not be mapped here!
As the same rule can apply for multiple objects, we form a list of rules that can be referred to from individual elements (objects).
The usage of the <operatingRules> element is optional.
For UC example see current rule book exemption for Hamar station in Norway:
https://orv.banenor.no/sjn/doku.php?id=saerbestemmelser_omra der:trafikk_ost:ost:3.6_dovrebanen_eidsvoll_-_dombas#hamar_s tasjon
We will implement the element as an <nor:> extension in railML2.4, but will deprecate its use if implemented in railML2.5/3.X
Attributes of the element
The sub element <nor:operatingRule> to the container element <nor:operatingRules> contains the standard common attributes without position (@id,@code, @name, @description)
All elements can use the extended optional attribute @ruleRef, with reference to the rule that applies for it.
Code example
<nor:operatingRules>
<nor:operatingRule id="id62" code="HMR1" name="old signal bulb" description="Signal shows orange instead of white aspect"/>
</nor:operatingRules>
...
<signal id="si52" ruleRef="id62"/>
Question: Reference to only one rule enough? Work-around to bunde multiple rules in one rule. Or do we need to make a sub element (if possible on all elements?)
What does the community think?
|
|
|
|
Members
Search
Help
Login
Home
