Home » railML newsgroups » railml.timetable » RFE for connection, DE:Anschluss
Re: RFE for connection, DE:Anschluss [message #902 is a reply to message #897] Tue, 27 November 2012 16:48 Go to previous messageGo to previous message
Joachim Rubröder railML is currently offline  Joachim Rubröder railML
Messages: 0
Registered: November 2019
Hello all,

> So we still wait for the decision of the scheme coordinator... ;-)
If you both agree, there are no objections from my side.

Susanne mentioned, that the railML semantics should be covered by all
systems.:
> That would mean, that already today a timetabling information
> system has to split train parts if the formation changes, nevertheless
> it does not know the formation type at all.

This would mean to use case a) as a restriction of case b).

> a) Reversing trains _must_ be splitted into several <trainParts>; the
> attribute 'trainReverse' is only allowed at fist <ocpTT>s.

If the attribute 'trainReverse' occurs, it occours at the first <ocpTT>
indicating the symbol <-> for FIS purposes. This can't be checked within
the xsd.

The order of the vehicles could be reverted by 'orientationReversed' but
with no relation to the attribute 'trainReversed'.

Best regards,
Joachim

--
Joachim Rubröder
Schema Coordinator: railML.timetable


--
----== posted via PHP Headliner ==----
 
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
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: stop probability
Next Topic: wiki: missing attribute description for additionalTrainNumber at <train>
Goto Forum:
  


Current Time: Mon May 06 05:32:12 CEST 2024