Home » railML newsgroups » railML.infrastructure » infrastructure "state"
Re: infrastructure "state" [message #2010 is a reply to message #2009] Thu, 08 November 2018 11:50 Go to previous messageGo to previous message
Christian Rößiger is currently offline  Christian Rößiger
Messages: 62
Registered: March 2015
Member
Dear all,

As I read in https://trac.railml.org/ticket/339, the attribute
"disabled" could not be set to deprecated because it is mandatory.
Therefore it must be kept in railML 2.4 and always be set. To keep the
consistency between both attributes, I would only add the following
dependencies to the wiki instead of my previous suggestion:

status = conceptual|planned|disabled|closed -> disabled=true
status = operational -> disabled=false

Are there any objections / improvements?

Kind regards
Christian Rößiger

Am 08.11.2018 um 09:19 schrieb Christian Rößiger:
> Dear all,
>
> Unfortunately I have only now noticed during the review of the wiki
> pages for the <state> element that there is a new "state" attribute in
> railML2.4 that de facto replaces or extends the previous "disabled"
> attribute. The question for me is how to deal with the old "disabled"
> attribute. It's certainly too late to declare it "deprecated with
> version 2.4" now. Therefore, I would suggest at least to document in the
> wiki that "disabled" and "state" must not have any contradictions. If
> possible, only one of the two attributes should be used at a time.
>
> 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
 
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 22:30:42 CEST 2024