Home » railML newsgroups » railml.timetable » TrainpartRefs
Re: TrainpartRefs [message #751 is a reply to message #748] Fri, 09 September 2011 10:32 Go to previous messageGo to previous message
Carsten Weber is currently offline  Carsten Weber
Messages: 27
Registered: November 2011
Junior Member
"Susanne Wunsch" <coord(at)commonrailmlde> schrieb im Newsbeitrag
news:bb262l4ihinfsf(at)remiheepsaxde...
> Hello,
>
> If it would be appreciated, we could separate the "ocpsTT" element for
> referencing it from each train part. But I think that there are some
> cases where some deep attributes of ocpTT differ between the coupled
> train parts. Yes, it's a very seldom use case that should be covered,
> too.
>
In my view maybe we can reduce the contents of ocpsTT (I'm not sure) but we
can not remove it.
For example by running night trains there are train parts which are combined
in an operational train but you are not allowed to board or leave one of the
train parts at each stop. You might look at train D 61458 and CNL 458 at the
current timetable period. Both train parts run from Praha to Erfurt. But you
are not allowed to leave CNL 458 between Praha and Erfurt in opposition to D
61458.
So there will be (up to now) no other chance to bring this information into
RailML as to write some information about ocpTT to the train parts.

> railML 2.1 is even just released, so I'm not very happy in changing
> some core syntax. On the other hand, if that change would bring even
> more users to railML, it would be worth.
>
> Let's go on with this topic in this thread. Maybe it's good for the
> next major release.

Life means change. ;) But we should make sure that these changes are really
needed.

Best regards.

Carsten Weber
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Frage zu TT:category
Next Topic: deprecated attribute "trainLine" for element "trainPart"
Goto Forum:
  


Current Time: Thu May 16 00:43:35 CEST 2024