| joining and splitting of trains [message #701] |
Mon, 04 October 2010 12:34  |
Christoph.Jobmann
Messages: 12
Registered: October 2010
|
Junior Member |
|
|
Greetings,
lately I was asked if and how it was possible to express the planned
spliting and / or joining of trains in railML2.0. After having a few
closer looks at the html documentation and the wiki the element
TT:connection looked nice.
What confuses me at this point is the observation that it expects a
mandatory trainRef as attribute. I can understand this is required for the
conOperation values 'isExpectedBy' and 'isWaitingFor', but for the values
'join' and 'split' it would seem more straightforward to apply a
trainPartRef as attribute, wouldn't it?
Using a trainRef at this point makes it - at least in my eyes - neccessary
to add a backward connection from the train that the connection is to be
established to since it would not always be obvious which parts of the
trains should be connected to each other.
Even with this trick there still seems to be a flaw about multiple trains
joining and splitting which seems to require evaluating additional
information like positions of trainPartRefs in trains and direction
changes.
Am I missing something? Or would an additional (optional) Attribute
trainPartRef for the element TT:Connection be useful?
Best regards
Christoph Jobmann
--
----== posted via PHP Headliner ==----
|
|
|
|
Members
Search
Help
Login
Home
