Talk:TT:operationalTrainSection: Difference between revisions
Jump to navigation
Jump to search
David Lichti (talk | contribs) (→Semantic Constraints Proposals: Proposals for semantic constraits TT:004 and TT:005) |
David Lichti (talk | contribs) mNo edit summary |
||
| Line 16: | Line 16: | ||
== Itinerary Coverage == | == Itinerary Coverage == | ||
:The itinerary sections defined by the '''operationalTrainSection'''s and their respective '''range'''s must cover the entire '''itinerary''' referenced by the parent '''operationalTrainVariant''''s '''itineraryRef'''. | :The union of all itinerary sections defined by the '''operationalTrainSection'''s and their respective '''range'''s must cover the entire '''itinerary''' referenced by the parent '''operationalTrainVariant''''s '''itineraryRef'''. | ||
[[User:David Lichti|David Lichti]] ([[User talk:David Lichti|talk]]) 15:09, 17 January 2023 (CET) | [[User:David Lichti|David Lichti]] ([[User talk:David Lichti|talk]]) 15:09, 17 January 2023 (CET) | ||
Revision as of 16:15, 17 January 2023
Semantic Constraints Proposals
Well-Defined Ranges
- If the operationalTrainSection has a range element, the baseItineraryPoints referenced therein must belong to the itinerary referenced by the parent operationalTrainVariant's itineraryRef.
I made this one up. It may be better suitable on the range page. David Lichti (talk) 15:09, 17 January 2023 (CET)
Disjoint Sections
- The itinerary sections of an operationalTrainVariant, defined by the operationalTrainSections and their respective ranges, must be pairwise disjoint except for their first/last baseItineraryPoints.
David Lichti (talk) 15:09, 17 January 2023 (CET)
Itinerary Coverage
- The union of all itinerary sections defined by the operationalTrainSections and their respective ranges must cover the entire itinerary referenced by the parent operationalTrainVariant's itineraryRef.
David Lichti (talk) 15:09, 17 January 2023 (CET)