| scope and additionalTrainNumber / compatibility to "DB: Ergänzungsfahrpläne" [message #776 is a reply to message #775] |
Mon, 16 April 2012 16:23  |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear all,
this 'post' is mainly to bring the discussion to an intermediate
agreement. (It is always confusing to have 'open' tasks for years without
knowing the opinion of the others.)
> Das ist mit dem Attribut "additionalTrainNumber" möglich.
Yes. We have cleared that "additionalTrainNumber" has to be used for
"Nummer des Ergänzungsfahrplans" in case of such DB(-compatible)
timetables.
Summary:
- In RailML 2.x we only have so far the possibility to 'group' trains
using attributes but not with structures.
- The attributes "scope" and "additionalTrainNumber" shall be used to
group trains sharing the same train number.
- For cases with compatibility to the DB's terminology of
"Ergänzungsfahrpläne", the following rules apply:
DB: "Stammfahrplan" = RailML: scope=primary
DB: "Startflügel" = RailML: scope=secondaryStart
DB: "Zielflügel" = RailML: scope=secondaryEnd
DB: "Doppelfahrplan" = RailML: sscope=econdaryInner
DB: "Nummer des Ergänzungsfahrplans" = RailML: additionalTrainNumber
> Für die nächste große Version habe ich die Gruppierung der Züge mit
> gleicher Zugnummer in einem Element <trainGroup> im Trac-Ticket #146
> vorgeschlagen. [1]
We would then have the redundancy of grouping this trains with attributes
and with the structure <trainGroup> as well. However, I appreciate this
solution for clearness. We should have done it years ago as Simon
recommended.
Best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
