Home » railML newsgroups » railml.timetable » RFE for connection, DE:Anschluss
Re: RFE for connection, DE:Anschluss [message #873 is a reply to message #870] Fri, 09 November 2012 16:11 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 313
Registered: August 2008
Senior Member
Dear Susanne,

> It changes its running direction in Eschwege, that means "it reverses".

please do not mix the "trainReverse" attribute with the
"orientationReversed" attribute.

- "trainReverse" is an attribute of <ocpTT>,
- "orientationReversed" is an attribute of <formationTT>.

If only the train reverses but not the formation, there is currently no
need to separate two <trainParts>.

In the example of Eschwege with one MU, only the train reverses but not
the formation. So until today: No need for two <trainParts>.

---
With your suggestion to _enforce_ two train parts if a train reverses
(which I would welcome as mentioned in the previous post), the situation
changes:

We could now declare "trainReverse" being obsolete since we could always
use "orientationReversed" (also for single MUs by definition) because we
always will have to have a new <trainPart>.

So: If your suggestion will be accepted (by Joachim and others), I
herewith plead for declaring "trainReverse" obsolete to reduce redundancy.

Best regards,
Dirk.
 
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: Sun Nov 03 21:05:09 CET 2024