Validity times [message #1734] |
Tue, 20 March 2018 15:49 |
christian.rahmig
Messages: 436 Registered: January 2016
|
Senior Member |
|
|
Dear all,
the information that a NetElement is valid (for operation) is currently
modelled with the attributes @validFrom and @validTo. A resulting small
example looks like this:
<netElement ... validFrom="2018-01-01" validTo="2018-12-31"/>
This implementation of validity times has two drawbacks:
* It is not possible to model other infrastructure states, e.g. "under
construction"
* It does not allow to model segmented validity times, e.g. before and
after a construction blocking
The second point is really essential. Therefore, I propose to change the
RTM modelling in the following way: instead of attributes @validFrom and
@validTo, use a repeatable child element <valid> with attributes @from
and @to to define the different segments of validity time. The resulting
small example may look like this:
<netElement ...>
<valid from="2018-01-01" to="2018-06-29"/>
<valid from="2018-07-02" to="2018-12-31"/>
</netElement>
Any feedback is highly appreciated...
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
|
|
|