| Re: infrastructure "state" [message #1933 is a reply to message #1858] |
Thu, 30 August 2018 08:50   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear all,
in a first step of re-newing the data structure for modelling the
infrastructure state, the existing solution from OCP and from
infrastructure element shall be harmonized with upcoming railML 2.4.
OCP status is modelled:
<ocp ...>
<propOther @status="planned">
</ocp>
Further enumeration values are:
* operational
* disabled
* closed
The railML infrastructure element (e.g. levelCrossing) has a different
way of modelling states:
<levelCrossing ...>
<states>
<state disabled="true" operatingPeriodRef="..."/>
</states>
</levelCrossing>
Bringing both concepts together would strengthen the state modelling in
infrastructure. I therefore filed a ticket [1] for this issue that can
be realized quite quickly.
Any comments are appreciated...
[1] https://trac.railml.org/ticket/339
Best regards
Christian
--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
