Home » railML newsgroups » railML.infrastructure » Mapping of availability periods of the infrastructure by TT:operatingPeriod
Re: Meanings of "disabled" (Re: Mapping of availability periods of the infrastructure by TT:operatingPeriod) [message #1843 is a reply to message #1802] Mon, 18 June 2018 09:35 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Christian and Tobias,

Am 23.05.2018 um 09:10 schrieb Christian Rößiger:
> [...]
> 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.

I had a look at the implementation in railML 2.3 and my understanding of
the topic is the following one:

* The attribue <state>@disabled is used to mark an infrastructure
element not being available for operation (no matter for which reason)
* In practical usage, we assume that modelled infrastructure is
available for operation --> "default value" of <state>@disabled would be
"false".
* The attribute <state>@disabled is used to explicitly mark
infrastructure elements not being available (@disabled="true").

For railML 2.x I suggest to keep this implementation except there are
users who urgently need to have some changes implemented related to the
<state>.

My proposal for railML 3.x would be to change the <state> modelling:
Instead of the boolean parameter @disabled I prefer having an
enumeration value with different types of states. For example,
infrastructure element can be
* planned
* underConstruction
* inOperation
* removed
* disabled

Do you have any further states in mind?

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
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: etcsTrainCategory
Next Topic: Signal characteristics (de: Signaleigenschaften)
Goto Forum:
  


Current Time: Wed May 01 17:59:20 CEST 2024