| Re: Meanings of "disabled" (Re: Mapping of availability periods of the infrastructure by TT:operatingPeriod) [message #1802 is a reply to message #1782] |
Wed, 23 May 2018 09:10   |
Christian Rößiger
Messages: 61
Registered: March 2015
|
Member |
|
|
Dear Tobias,
since the <state> element is located in the <infrastructure> domain of
railML, I assume that it was originally intended to indicate
restrictions due to infrastructure work or not yet / no longer available
infrastructure. I have assumed, however, that the same means can also be
used to map infrastructure elements that are "operationally" closed. For
this reason, periodically recurring periods are also planned for this
element. The gradation of 'disabled' would then have to be derived from
the type of source of the railML data or from the usecase.
However, the purpose of the disabled attribute is also unclear to me. If
you assume that an infrastructure element without <state> element is
always available, you can only define restrictions with the <state>
element, i.e. it only makes sense to use "disabled=true". However, if
the infrastructure is not available by default, only "disabled=false"
may be used. The attribute "disabled" is therefore completely
unnecessary in this form.
I therefore take a very positive view of proposals for a more
comprehensible implementation.
Kind regards
Christian Rößiger
--
iRFP e. K. · Institut für Regional- und Fernverkehrsplanung
Hochschulstr. 45, 01069 Dresden
Tel. +49 351 4706819 · Fax. +49 351 4768190 · www.irfp.de
Registergericht: Amtsgericht Dresden, HRA 9347
|
|
|
|
Members
Search
Help
Login
Home
