| reference from timetable's <stopDescription> to infrastructure's <stopPost> [message #896] |
Sat, 24 November 2012 11:06  |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Dear Joachim and railML users,
during the last railML.org meeting in Zurich I started wondering if we
really need a reference from the timetable's <stopDescription> to the
infrastructure's <platformEdge> or <serviceSection> (cp. [1], [2]).
For me, it seems to be sufficient to only have a reference to a
<stopPost> element and since the <stopPost> includes the boolean
parameter "virtual", it can be placed everywhere a train or locomotive
can stop (cp. [3]). Further, a stop post refers to its corresponding
platform edge via the parameter "platformEdgeRef", which might be
formulated in a more generic way to include the service sections as
well. Thus, a direct reference from the <stopDescription> to the
<platformEdge> or <serviceSection> would not be necessary anymore, would it?
Any comments appreciated...
[1] https://trac.assembla.com/railML/ticket/195
[2] https://trac.assembla.com/railML/ticket/208
[3] https://trac.assembla.com/railML/ticket/167
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
