Template:Table/Dev:Semantic Constraints: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
(Updated table to include new sem cons of timetable) |
(approved semcon) |
||
| Line 18: | Line 18: | ||
|TT:002 | |TT:002 | ||
|2023-01-12 | |2023-01-12 | ||
| | |2023-04-06 | ||
| | | | ||
|When calculating which {{TT:Tag|operationalTrainVariant}} of an {{TT:Tag|operationalTrain}} is valid on a particular day always a maximum of one active {{TT:Tag|operationalTrainVariant}} shall be the result. If the result is more than one {{TT:Tag|operationalTrainVariant}}, all except one shall be marked as {{TT:Tag|isCancelled}} or {{TT:Tag|isOnRequest}}. | |When calculating which {{TT:Tag|operationalTrainVariant}} of an {{TT:Tag|operationalTrain}} is valid on a particular day always a maximum of one active {{TT:Tag|operationalTrainVariant}} shall be the result. If the result is more than one {{TT:Tag|operationalTrainVariant}}, all except one shall be marked as {{TT:Tag|isCancelled}} or {{TT:Tag|isOnRequest}}. | ||
| Line 25: | Line 25: | ||
|TT:003 | |TT:003 | ||
|2023-01-12 | |2023-01-12 | ||
| | |2023-04-06 | ||
| | | | ||
|When calculating which {{TT:Tag|commercialTrainVariant}} of an {{TT:Tag|commercialTrain}} is valid on a particular day always a maximum of one active {{TT:Tag|commercialTrainVariant}} shall be the result. If the result is more than one {{TT:Tag|commercialTrainVariant}}, all except one shall be marked as {{TT:Tag|isCancelled}} or {{TT:Tag|isOnRequest}}. | |When calculating which {{TT:Tag|commercialTrainVariant}} of an {{TT:Tag|commercialTrain}} is valid on a particular day always a maximum of one active {{TT:Tag|commercialTrainVariant}} shall be the result. If the result is more than one {{TT:Tag|commercialTrainVariant}}, all except one shall be marked as {{TT:Tag|isCancelled}} or {{TT:Tag|isOnRequest}}. | ||
Revision as of 17:38, 2 May 2023
| Element | ID | Proposal date | Date of acception | Date of deprecation | Description |
|---|---|---|---|---|---|
| <TT:operationalTrainSectionPart> | TT:001 | 2022-09-15 | 2022-10-13 | There is always only a single successor and predecessor for an <operationalTrainSectionPart> in the chain of <operationalTrainSectionPart>s that are linked via the attribute @next. | |
| <TT:operationalTrainVariant> | TT:002 | 2023-01-12 | 2023-04-06 | When calculating which <operationalTrainVariant> of an <operationalTrain> is valid on a particular day always a maximum of one active <operationalTrainVariant> shall be the result. If the result is more than one <operationalTrainVariant>, all except one shall be marked as <isCancelled> or <isOnRequest>. | |
| <TT:commercialTrainVariant> | TT:003 | 2023-01-12 | 2023-04-06 | When calculating which <commercialTrainVariant> of an <commercialTrain> is valid on a particular day always a maximum of one active <commercialTrainVariant> shall be the result. If the result is more than one <commercialTrainVariant>, all except one shall be marked as <isCancelled> or <isOnRequest>. | |
| <TT:operationalTrainSection> | TT:004 | 2022-01-12 | 2023-03-09 | The itinerary sections of an <operationalTrainVariant>, defined by the <operationalTrainSection>s and their respective <range>s, that are not <isCancelled> and not marked as <isOnRequest>, must be pairwise disjoint, except for their respective first and last <baseItineraryPoint>s. | |
| <TT:operationalTrainSection> | TT:005 | 2022-01-12 | 2023-03-09 | The first(last) <baseItineraryPoint> of each <operationalTrainSection> within an <operationalTrainVariant> must either be the referenced <itinerary>'s first(last) <baseItineraryPoint>, or coincide with another section's last(first) <baseItineraryPoint>. | |
| <TT:commercialTrainSection> | TT:006 | 2022-01-12 | 2023-03-09 | The itinerary sections of an <commercialTrainVariant>, defined by the <commercialTrainSection>s and their respective <range>s, that are not <isCancelled> and not marked as <isOnRequest>, must be pairwise disjoint, except for their respective first and last <baseItineraryPoint>s. | |
| <TT:commercialTrainSection> | TT:007 | 2022-01-12 | 2023-03-09 | The first(last) <baseItineraryPoint> of each <commercialTrainSection> within an <commercialTrainVariant> must either be the referenced <itinerary>'s first(last) <baseItineraryPoint>, or coincide with another section's last(first) <baseItineraryPoint>. |