| railML 2.3 infrastructure extension proposal - a new "state" [message #1632] |
Thu, 31 August 2017 12:57  |
Torben Brand
Messages: 157
Registered: March 2016
|
Senior Member |
|
|
There is an existing element <state> in railML2.3 that applies to certain selected elements. Jernbanedirektoratet and Bane NOR use case needs to extend the features of the state and make it more flexible. Unfortunately the current <state> element it is not extendable and the structure as an element seems too complex and rigid for our need. We thus suggest to add a new Norwegian extension attribute to our extension railML2.3nor which can be placed on any element and is valid for that element and all sub elements (inheritance) within the element.
Placing the attribute nor:state
The new attribute @nor:state can be placed on any element. It is valid for that element and all sub elements (inheritance) within the element. Inheritance can be broken by defining a new state on an element.
For instance the attribute @nor:state can be placed on <infrastructure id="" name="" nor:state="operational">
For railML files containing multiple planned states with states spanning over more than one ocp area we suggest to first define an <infrastructure with nor:state="operational" and then one or multiple <infrastrucure with nor:state="planned" with their corresponding operatingPeriodRef="id".
For smaller planned changes within an ocp the nor:change attribute can be placed on a planned track within the same infrastructure. Even smaler changes within one track can be placed on the element(s) itself.
The planned tracks must have connections to the operational tracks over the <connection> element.
If no nor:state is not defined the value is by default "operational"
Values of nor:state
We need the values: operational/planned/disabled/closed/historic.
operational: the described infrastructure is operational
planned: the infrastructure is planned in the future.
disabled: the infrastructure is still in place, but operationally disabled.
removed: vital or all elements of the infrastructure is removed but juridical rights are in place
closed: The infrastructure is still in place but juridical rights have been removed
historic: all elements of the infrastructure is removed and juridical rights have been removed.
The timeframe of the defined states are defined in the existing element <timetable/operationalPeriods/operationalPeriode> @startDate and @endDate with an attribute in the infrastructure @operatingPeriodRef refering to it.
|
|
|
|
Members
Search
Help
Login
Home
