This element does not appear in railML® 3.2 within the IL subschema. It is available only in railML® 3.1. Do not hesitate to contact railML.org for further questions.
IL:itinerary: Difference between revisions
Jump to navigation
Jump to search
[unchecked revision] | [checked revision] |
(Created page with "{{subst:docBase |element=itinerary |subschema=IL}}") |
No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 13: | Line 13: | ||
=={{Additional Information}}== | =={{Additional Information}}== | ||
==={{Notes}}=== | ==={{Notes}}=== | ||
This element is renamed in 3.2 to {{tag|IL|routeSequence}} to avoid name collision with {{tag|TT|itinerary}} in timetable domain. | |||
==={{Open issues}}=== | ==={{Open issues}}=== |
Latest revision as of 11:57, 21 May 2022
Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IL:itinerary of railML® version 3.1 | |
Documentation | Itinerary is a combination of single routes defining the path from A to B independent of involved signalBoxes (interlockings). |
Subschema | interlocking |
Parents* | itineraries |
Children | any (0..*), comboEntry (1..1), comboExit (1..1), containsRoute (1..*), designator (0..1) |
Attributes:
| |
*Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element. |
Changes 3.1→3.2
Removed with version 3.2.
Semantics
Best Practice / Examples
Additional Information
Notes
This element is renamed in 3.2 to <routeSequence> to avoid name collision with <itinerary> in timetable domain.