TT:PreliminaryDocumentation: Difference between revisions
Jump to navigation
Jump to search
[unchecked revision] | [checked revision] |
(Task structure added) |
(Added semantic constraints for commercialScheduling (by Christian Rößiger / iRFP Dresden)) |
||
Line 5: | Line 5: | ||
{{note|Please note, that this page is made for saving ideas, concepts and descriptions for the upcoming {{rml|3.2}} [[Timetable]] scheme. This page shall be replaced by the official documentation inside this wiki and must not be used for development or certification pourposes.|error}} | {{note|Please note, that this page is made for saving ideas, concepts and descriptions for the upcoming {{rml|3.2}} [[Timetable]] scheme. This page shall be replaced by the official documentation inside this wiki and must not be used for development or certification pourposes.|error}} | ||
= | = <commercialScheduling> = | ||
== | == Semantic constraints == | ||
# all <operationalTrainSectionPart> elements referenced by one <commercialScheduling> element must belong to the same <operationalTrainSection> element | |||
# a <commercialScheduling> links one <commercialTrainSection> and one <operationalTrainSection> (indirectly via reference to one or more <operationalTrainSectionPart> elements). Both must reference the same <itinerary> with an identical offset | |||
# if more than one <commercialScheduling> elements reference the same <commercialTrainSection>, they must not overlap each other locally | |||
# if more than one <commercialScheduling> elements reference the same <operationalTrainSection> (indirectly via reference to <operationalTrainSectionPart>), they must not overlap each other locally | |||
= Task 2 = | = Task 2 = | ||
== Task 2.1 == | == Task 2.1 == | ||
== Task 2.2 == | |||
= Task 3 = | |||
== Task 3.1 == | |||
== Task 3.2 == | |||
== Task 3.3 == |
Latest revision as of 07:08, 13 June 2020
This is the page for the preliminary documentation of railML® 3.2 Timetable scheme concepts.
|
|
<commercialScheduling>
Semantic constraints
- all <operationalTrainSectionPart> elements referenced by one <commercialScheduling> element must belong to the same <operationalTrainSection> element
- a <commercialScheduling> links one <commercialTrainSection> and one <operationalTrainSection> (indirectly via reference to one or more <operationalTrainSectionPart> elements). Both must reference the same <itinerary> with an identical offset
- if more than one <commercialScheduling> elements reference the same <commercialTrainSection>, they must not overlap each other locally
- if more than one <commercialScheduling> elements reference the same <operationalTrainSection> (indirectly via reference to <operationalTrainSectionPart>), they must not overlap each other locally