Home » railML newsgroups » railml.timetable » Attribute processStatus to be declared deprecated for <train>, <trainPart> and <trainGroup>
Re: Attribute processStatus to be declared deprecated for <train>, <trainPart> and <trainGroup> [message #2331 is a reply to message #2323] Mon, 17 February 2020 15:53 Go to previous messageGo to previous message
Christian Rößiger is currently offline  Christian Rößiger
Messages: 62
Registered: March 2015
Member
Hello,

we discussed the future of the "processStatus" attribute during the
railML telephone conference, as the documentation in the wiki is
inadequate and none of the participants could provide a plausible way of
using it. All participants of the telephone conference currently using
this attribute use the attribute in a different context, so that a
functioning exchange is unlikely. Furthermore, only a few of the
possible values of the enumeration are used or the value range is
extended by individual "other:xxx" values. For this reason, we have
proposed to declare the attribute as "deprecated".
For mapping different planning states or versions of a train I would
suggest to introduce a new attribute or element to avoid confusion. For
this purpose we would appreciate a modeling suggestion from you. If you
want to keep the existing attribute "processStatus", we would also be
interested in information about which values of the enumeration you use
and what exactly is encoded with them.
I would not try to merge "pathStatus" and "processStatus". With
"pathStatus" different states of a train are described during a train
path allocation process. A train can have several different pathStatus
if it is ordered at several different infrastructure managers. I
understand the "pathStatus" attribute here as additional information of
a train. The new attribute for the planning statuses, on the other hand,
should help to distinguish different instances of <train> elements, so
it becomes part of an external primary key of a train/train part. For
these reasons I would also leave "pathStatus" at <trainPartSequence> and
the new attribute at <trainPart> / <train> / <trainGroup>.

Best 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
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Meaning and usage of @shuntingTime
Next Topic: Extension suggestion for alternativeSectionTT
Goto Forum:
  


Current Time: Sun May 05 09:43:43 CEST 2024