Home » railML newsgroups » railML.infrastructure » infrastructure "state"
Re: infrastructure "state" [message #2049 is a reply to message #2028] Wed, 19 December 2018 15:33 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Thomas,

Am 03.12.2018 um 16:36 schrieb Thomas Nygreen:
> [...]
> I strongly disagree with constraining
> @status=conceptual|planned to @disabled=true. [...]
>
> It seems to me that there are different use cases requiring
> different values for @disabled when
> @status=conceptual|planned, depending on the relevant time
> frame.
>
> For @status=operational|disabled|closed it seems more
> feasible to restrict the value for @disabled.

let me briefly summarize your proposal:

@status="conceptual" --> @disabled="true/false"
@status="planned" --> @disabled="true/false"
@status="operational" --> @disabled="false"
@status="disabled" --> @disabled="true"
@status="closed" --> @disabled="true"

In case that there won't be any conflicting reactions on this proposal
until the end of year, I am going to bring it into the forum as semantic
rule for state.

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
Previous Topic: Use of <bufferStop>
Next Topic: <track>@mainDir
Goto Forum:
  


Current Time: Mon May 06 23:05:38 CEST 2024