Template:Table/Dev:Semantic Constraints: Difference between revisions
Jump to navigation
Jump to search
[checked revision] | [checked revision] |
(+descriptions TT) |
m (typo) |
||
(18 intermediate revisions by 4 users not shown) | |||
Line 15: | Line 15: | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other validity periods. | |Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other validity periods. | ||
|- | |- | ||
| | |{{TT:Tag|specialService|wiki=2|ex=1}} | ||
|TT: | |TT:018 | ||
|2018-11-12 | |2018-11-12 | ||
|2019-03-21 | |2019-03-21 | ||
| | | | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other | |Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other {{TT:Tag|specialService}} validity periods of the same enclosing {{TT:Tag|operatingPeriod}}. | ||
|- | |- | ||
|{{TT:Tag|operatingPeriodRef|trainPart|wiki=2|ex=1}} | |{{TT:Tag|operatingPeriodRef|trainPart|wiki=2|ex=1}} | ||
| | |CO:002 | ||
|2018-11-12 | |2018-11-12 | ||
|2019-03-21 | |2019-03-21 | ||
| | | | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given | |Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. | ||
|- | |- | ||
|{{TT:Tag|operatingPeriod|wiki=2|ex=1}} | |{{TT:Tag|operatingPeriod|wiki=2|ex=1}} | ||
| | |CO:002 | ||
|2018-11-12 | |2018-11-12 | ||
|2019-03-21 | |2019-03-21 | ||
| | | | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given | |Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. | ||
|- | |- | ||
|{{TT:Tag|operatingDay|wiki=2|ex=1}} | |{{TT:Tag|operatingDay|wiki=2|ex=1}} | ||
|TT: | |TT:019 | ||
|2018-11-12 | |2018-11-12 | ||
|2019-03-21 | |2019-03-21 | ||
| | | | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other validity periods. | |Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other {{TT:Tag|operatingDay}} validity periods of the same enclosing {{TT:Tag|operatingPeriod}}. | ||
|- | |- | ||
|{{Tag| | |{{TT:Tag|circulation|wiki=2|ex=1}} | ||
| | |CO:002 | ||
|2018-11-12 | |2018-11-12 | ||
|2019-03-21 | |2019-03-21 | ||
| | | | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given | |Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. | ||
|- | |- | ||
|{{TT:Tag| | |{{TT:Tag|blockPart|wiki=2|ex=1}} | ||
| | |CO:002 | ||
|2018- | |2018-11-12 | ||
|2019- | |2019-03-21 | ||
| | | | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. | |||
|- | |- | ||
|{{ | |{{Tag|rs|designator|wiki=2|ex=1}} {{intro|2.5}} | ||
| | |RS:001 | ||
|2018-11-12 | |2018-11-12 | ||
|2019-03-21 | |2019-03-21 | ||
| | | | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with | |Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with the validity periods of other entries of the same {{Attr|register}} of the same enclosing {{RS:Tag|state}}. | ||
|- | |- | ||
|{{ | |{{RS:Tag|operator|wiki=2|ex=1}} | ||
| | |RS:002 | ||
|2018-11-12 | |2018-11-12 | ||
|2019-03-21 | |2019-03-21 | ||
| | | | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other validity periods. | |Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other {{RS:Tag|operator}} validity periods of the same enclosing {{RS:Tag|vehicle}}/{{RS:Tag|classification}}. | ||
|- | |- | ||
|{{ | |{{RS:Tag|owner|wiki=2|ex=1}} {{intro|2.5}} | ||
|RS:003 | |||
| | |||
|2018-11-12 | |2018-11-12 | ||
|2019-03-21 | |2019-03-21 | ||
| | | | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other validity periods. | |Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other {{RS:Tag|owner}} validity periods of the same enclosing {{RS:Tag|vehicle}}/{{RS:Tag|classification}}. | ||
|- | |- | ||
|{{RS | |{{Tag|RS|state|wiki=2|ex=1}} | ||
| | |RS:004 | ||
|2018-11-12 | |2018-11-12 | ||
|2019-03-21 | |2019-03-21 | ||
| | | | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other validity periods. | |Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other {{RS:Tag|state}} validity periods of the same enclosing {{RS:Tag|vehicle}}/{{RS:Tag|states}}. | ||
|- | |- | ||
|{{IS:Tag|state|wiki=2|ex=1}} | |{{IS:Tag|state|wiki=2|ex=1}} | ||
| | |IS:020 | ||
|2018-11-12 | |2018-11-12 | ||
|2019-03-21 | |2019-03-21 | ||
| | | | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other validity periods. | |Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other {{IS:Tag|state}} validity periods of the same enclosing {{IS:Tag|states}} collection. See also {{wiki2|Dev:Defining temporal availability of infrastructure elements and speed profiles}}. | ||
|- | |- | ||
|{{IS:Tag|state (with length)|wiki=2|ex=1}} | |{{IS:Tag|state (with length)|wiki=2|ex=1}} | ||
| | |IS:021 | ||
|2018-11-12 | |2018-11-12 | ||
|2019-03-21 | |2019-03-21 | ||
| | | | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other validity periods. | |Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other {{IS:Tag|state (with length)}} validity periods of the same enclosing {{IS:Tag|states (with length)}} collection. See also {{wiki2|Dev:Defining temporal availability of infrastructure elements and speed profiles}}. | ||
|- | |- | ||
|{{IS:Tag|designator|wiki=2|ex=1}} | |{{IS:Tag|designator|wiki=2|ex=1}} | ||
| | |CO:001 | ||
|2018-11-12 | |||
|2019-03-21 | |||
| | |||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with the validity periods of other entries of the same {{Attr|register}} of the same enclosing element. | |||
|- | |||
|{{Tag|co|designator|wiki=2|ex=1}} {{intro|2.5}} | |||
|CO:001 | |||
|2018-11-12 | |2018-11-12 | ||
|2019-03-21 | |2019-03-21 | ||
| | | | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with | |Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with the validity periods of other entries of the same {{Attr|register}} of the same enclosing element. | ||
|- | |- | ||
|{{Tag|co|phase|wiki=2|ex=1}} {{intro|2.5}} | |{{Tag|co|phase|wiki=2|ex=1}} {{intro|2.5}} | ||
| | |CO:002 | ||
|2018-11-12 | |2018-11-12 | ||
|2019-03-21 | |2019-03-21 | ||
| | | | ||
|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given | |Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. | ||
|- | |- | ||
| | |{{TT:Tag|ocpTT|wiki=2|ex=1}} | ||
| | |TT:002 | ||
| | |2018-10-25 | ||
| | |2019-06-20 | ||
| | | | ||
| | |The attribute sequence is shall be increasing according to the train path. | ||
|- | |- | ||
|{{ | |<s>{{TT:Tag|ocpTT|wiki=2|ex=1}}</s> | ||
| | | | ||
|2018-10-25 | |||
|''discarded'' | |||
| | | | ||
|<s>No {{attr|ocpRef}} is allowed to occur more than one time in the same {{TT:Tag|trainPart}}</s> | |||
|- | |||
|{{TT:Tag|blockPart|wiki=2|ex=1}} | |||
|TT:003 | |||
|2019-07-13 | |||
|2019-07-18 | |||
| | | | ||
|By means of a {{TT:Tag|blockPart}} it is possible to model both journeys with and without reference to a {{TT:Tag|trainPart}} within a roster, as well as services without change of location (without reference to a {{TT:Tag|trainPart}}). These 3 basic types are distinguished by the attribute {{Attr|mission}}. The following table presents the semantic constraints: ''(not included here)'' | |||
|- | |||
|{{TT:Tag|blockPart|wiki=2|ex=1}} | |||
|TT:004 | |||
|2019-07-20 | |||
|2019-07-18 | |||
| | |||
|{{Attr|vehicleRef}} and {{Attr|formationRef}} shall not be used within the same blockPart, since a blockPart is either one for a certain vehicle or one for a whole formation. | |||
|- | |- | ||
|{{TT:Tag|rostering|wiki=2|ex=1}} | |{{TT:Tag|rostering|wiki=2|ex=1}} | ||
Line 164: | Line 155: | ||
|{{Attr|vehicleRef}} and {{Attr|formationRef}} are to be used exceptional since the circulation plan is either one for a certain vehicle or one for a whole formation. | |{{Attr|vehicleRef}} and {{Attr|formationRef}} are to be used exceptional since the circulation plan is either one for a certain vehicle or one for a whole formation. | ||
|- | |- | ||
|{{TT:Tag|stopDescription|wiki=2|ex=1}} | |{{TT:Tag|stopDescription|wiki=2|ex=1}} | ||
|TT:006 | |TT:006 | ||
|2018-09-03 | |2018-09-03 | ||
Line 178: | Line 169: | ||
| | | | ||
|- | |- | ||
|{{TT:Tag|trackInfo|wiki=2|ex=1}} | |{{TT:Tag|trackInfo|wiki=2|ex=1}} | ||
|TT:008 | |TT:008 | ||
|2018-08-21 | |2018-08-21 | ||
Line 185: | Line 176: | ||
|The representation of differentiated track usage must not result in differences in arrival and departure times. In these cases, a separate {{TT:Tag|trainPart}} / {{TT:Tag|train}} with different arrival and departure times must be created. | |The representation of differentiated track usage must not result in differences in arrival and departure times. In these cases, a separate {{TT:Tag|trainPart}} / {{TT:Tag|train}} with different arrival and departure times must be created. | ||
|- | |- | ||
|{{TT:Tag|trackInfo|wiki=2|ex=1}} | |{{TT:Tag|trackInfo|wiki=2|ex=1}} | ||
|TT:009 | |TT:009 | ||
|2018-08-21 | |2018-08-21 | ||
Line 202: | Line 193: | ||
|TT:011 | |TT:011 | ||
|2019-06-19 | |2019-06-19 | ||
| | |[[special:diff/13391/13393|''discarded'']] | ||
| | | | ||
| | | | ||
Line 216: | Line 207: | ||
|TT:013 | |TT:013 | ||
|2019-06-19 | |2019-06-19 | ||
| | |[[special:diff/13361/13362|''discarded'']] | ||
| | | | ||
| | | | ||
Line 247: | Line 238: | ||
| | | | ||
|If the trainPartRef attribute is given, then there must also be a trainRef attribute, and the trainPartRef attribute must point to a train part of the train referenced by the trainRef attribute. | |If the trainPartRef attribute is given, then there must also be a trainRef attribute, and the trainPartRef attribute must point to a train part of the train referenced by the trainRef attribute. | ||
|- | |||
|<s>{{IS:Tag|speedChange|wiki=2|ex=1}}</s> | |||
|IS:001 | |||
|2019-04-11 | |||
|''discarded'' | |||
| | |||
|<s>Always define {{Attr|trainRelation}}</s> | |||
|- | |- | ||
|{{IS:Tag|trackEnd|wiki=2|ex=1}} | |{{IS:Tag|trackEnd|wiki=2|ex=1}} | ||
Line 254: | Line 252: | ||
| | | | ||
| | | | ||
*The value of {{@|pos}} in {{IS:Tag|trackBegin|attr=pos}} is always the lowest value of all specified {{IS:Tag|trackElements}} and {{IS:Tag|ocsElements}}. It is always lower than the value of {{@|pos}} of {{IS:Tag|trackEnd|attr=pos}}. | *The value of {{@|pos}} in {{IS:Tag|trackBegin|attr=pos}} is always the lowest value of all specified {{IS:Tag|trackElements}} and {{IS:Tag|ocsElements}}. It is always lower (or equal if length = 0) than the value of {{@|pos}} of {{IS:Tag|trackEnd|attr=pos}}. | ||
*The value of {{@|pos}} in {{IS:Tag|trackEnd|attr=pos}} is always the highest value of all specified {{IS:Tag|trackElements}} and {{IS:Tag|ocsElements}}. It is always higher than the value of {{@|pos}} of {{IS:Tag|trackBegin|attr=pos}}. | *The value of {{@|pos}} in {{IS:Tag|trackEnd|attr=pos}} is always the highest value of all specified {{IS:Tag|trackElements}} and {{IS:Tag|ocsElements}}. It is always higher (or equal if length = 0) than the value of {{@|pos}} of {{IS:Tag|trackBegin|attr=pos}}. | ||
*Subtracting the value of {{@|pos}} in {{IS:Tag|trackBegin|attr=pos}} from the value of {{@|pos}} in {{IS:Tag|trackEnd|attr=pos}} will result in the length of the enclosing {{IS:Tag|track}}. | *Subtracting the value of {{@|pos}} in {{IS:Tag|trackBegin|attr=pos}} from the value of {{@|pos}} in {{IS:Tag|trackEnd|attr=pos}} will result in the length of the enclosing {{IS:Tag|track}}. | ||
*If two {{IS:Tag|track}}s are connected, the {{@|absPos}} values of the connected {{IS:Tag|trackBegin|attr=absPos}} and {{IS:Tag|trackEnd|attr=absPos}} must be identical '''if''' | *If two {{IS:Tag|track}}s are connected, the {{@|absPos}} values of the connected {{IS:Tag|trackBegin|attr=absPos}} and {{IS:Tag|trackEnd|attr=absPos}} must be identical '''if''' | ||
Line 268: | Line 266: | ||
| | | | ||
| | | | ||
*The value of {{@|pos}} in {{IS:Tag|trackBegin|attr=pos}} is always the lowest value of all specified {{IS:Tag|trackElements}} and {{IS:Tag|ocsElements}}. It is always lower than the value of {{@|pos}} of {{IS:Tag|trackEnd|attr=pos}}. | *The value of {{@|pos}} in {{IS:Tag|trackBegin|attr=pos}} is always the lowest value of all specified {{IS:Tag|trackElements}} and {{IS:Tag|ocsElements}}. It is always lower (or equal if length = 0) than the value of {{@|pos}} of {{IS:Tag|trackEnd|attr=pos}}. | ||
*The value of {{@|pos}} in {{IS:Tag|trackEnd|attr=pos}} is always the highest value of all specified {{IS:Tag|trackElements}} and {{IS:Tag|ocsElements}}. It is always higher than the value of {{@|pos}} of {{IS:Tag|trackBegin|attr=pos}}. | *The value of {{@|pos}} in {{IS:Tag|trackEnd|attr=pos}} is always the highest value of all specified {{IS:Tag|trackElements}} and {{IS:Tag|ocsElements}}. It is always higher (or equal if length = 0) than the value of {{@|pos}} of {{IS:Tag|trackBegin|attr=pos}}. | ||
*Subtracting the value of {{@|pos}} in {{IS:Tag|trackBegin|attr=pos}} from the value of {{@|pos}} in {{IS:Tag|trackEnd|attr=pos}} will result in the length of the enclosing {{IS:Tag|track}}. | *Subtracting the value of {{@|pos}} in {{IS:Tag|trackBegin|attr=pos}} from the value of {{@|pos}} in {{IS:Tag|trackEnd|attr=pos}} will result in the length of the enclosing {{IS:Tag|track}}. | ||
*If two {{IS:Tag|track}}s are connected, the {{@|absPos}} values of the connected {{IS:Tag|trackBegin|attr=absPos}} and {{IS:Tag|trackEnd|attr=absPos}} must be identical '''if''' | *If two {{IS:Tag|track}}s are connected, the {{@|absPos}} values of the connected {{IS:Tag|trackBegin|attr=absPos}} and {{IS:Tag|trackEnd|attr=absPos}} must be identical '''if''' | ||
Line 286: | Line 284: | ||
|IS:005 | |IS:005 | ||
|2019-06-19 | |2019-06-19 | ||
| | |2022-07-14 | ||
| | | | ||
|An {{tag|IS|ocp}} that refers to a parent {{tag|IS|ocp}} via an {{@|parentOcpRef}} overwrites the attributes and elements of the parent {{tag|IS|ocp}} if explicitely defined. If an element is specified on an {{IS:Tag|ocp}} that uses a {{@|parentOcpRef}} any information provided with that element on a higher layer of the {{IS:Tag|ocp}}-tree is overwritten. There is no merging of element-information from different levels. The same applies for attributes of {{IS:Tag|ocp}}. | |An {{tag|IS|ocp}} that refers to a parent {{tag|IS|ocp}} via an {{@|parentOcpRef}} overwrites the attributes and elements of the parent {{tag|IS|ocp}} if explicitely defined. If an element is specified on an {{IS:Tag|ocp}} that uses a {{@|parentOcpRef}} any information provided with that element on a higher layer of the {{IS:Tag|ocp}}-tree is overwritten. There is no merging of element-information from different levels. The same applies for attributes of {{IS:Tag|ocp}}. | ||
Line 304: | Line 302: | ||
|IS:007 | |IS:007 | ||
|2020-02-25 | |2020-02-25 | ||
|discarded | |''discarded'' | ||
| | | | ||
| | | | ||
Line 330: | Line 328: | ||
|An enumeration of several time periods by {{@|from}} and {{@|until}} for one {{Tag|IS|ocp}} shall not overlap so that for every time there shall be a unique status of {{Tag|IS|uptime}}. | |An enumeration of several time periods by {{@|from}} and {{@|until}} for one {{Tag|IS|ocp}} shall not overlap so that for every time there shall be a unique status of {{Tag|IS|uptime}}. | ||
|- | |- | ||
|{{IS:Tag|speedProfile|wiki=2|ex=1|semcon=IS:012}} | |{{IS:Tag|speedChange|wiki=2|ex=1|semcon=IS:011}} | ||
|IS:011 | |||
|2022-03-14 (to be def. more accurately) | |||
|2021-11-10 (40th conference slide 11) | |||
| | |||
| | |||
*Every {{tag|is|track}} has to have at least one {{tag|is|speedChange}} at the track begin with parameters {{@|pos}}="0" and {{@|dir}}="up". | |||
*Every {{tag|is|track}} has to have at least one {{tag|is|speedChange}} at the track end with parameters {{@|pos}}="{value equal to trackEnd@pos}" and {{@|dir}}="down". | |||
|- | |||
|{{IS:Tag|speedProfile|wiki=2|ex=1|semcon=IS:012}} | |||
|IS:012 | |IS:012 | ||
|2022-03-14 | |2022-03-14 | ||
Line 337: | Line 344: | ||
|{{@|basicSpeedProfile}} is always linked with {{@|influence}}={{enum|increasing}} | |{{@|basicSpeedProfile}} is always linked with {{@|influence}}={{enum|increasing}} | ||
|- | |- | ||
|{{IS:Tag|speedProfile|wiki=2|ex=1|semcon=IS:013}} | |{{IS:Tag|speedProfile|wiki=2|ex=1|semcon=IS:013}} | ||
|IS:013 | |IS:013 | ||
|2022-03-14 | |2022-03-14 | ||
Line 356: | Line 363: | ||
|IS:015 | |IS:015 | ||
|2022-07-14 | |2022-07-14 | ||
|2022-08-11 | |||
| | |||
|When specifying {{@|parentOcpRef}} for an {{IS:Tag|ocp}} circles are not allowed. That means that when following the chain of {{@|parentOcpRef}} no {{IS:Tag|ocp}} shall be visited twice. | |||
|- | |||
|{{IS:Tag|axleWeightChange|wiki=2|ex=1|semcon=IS:016}} {{IS:Tag|clearanceGaugeChange}} {{IS:Tag|electrificationChange}} {{IS:Tag|gaugeChange}} {{IS:Tag|ownerChange}} {{IS:Tag|gradientChange}} {{IS:Tag|powerTransmissionChange}} {{IS:Tag|radiusChange}} | |||
|IS:016 | |||
|2021-11-10 | |||
|2021-11-10 | |||
| | |||
|must not have @dir attribute according to {{site|https://www.railml.org/en/event-reader/40th-railml-conference-gothenburg.html|Report from the Infrastructure developers in railML 3.2 and 2.5}} slide 9 and {{ticket|357|2}} | |||
|- | |||
|{{CO:Tag|railml|wiki=2|ex=1|semcon=IS:017}} {{IS:Tag|infrastructure}} | |||
|IS:017 | |||
|2024-03-25 | |||
|2024-03-25 | |||
| | | | ||
|either {{IS:Tag|infrastructure}} or {{CO:Tag|railml}} must have @version attribute | |||
|- | |||
|{{CO:Tag|metadata|wiki=2|ex=1|semcon=IS:018}} @name | |||
|IS:018 | |||
|2024-03-25 | |||
|2024-03-25 | |||
| | | | ||
| | |either {{CO:Tag|metadata}} must have {{CO:Tag|dc:language}} child or every @name attribute accompanied by @xml:lang | ||
|- | |||
|{{IS:Tag|gradientChange|wiki=2|ex=1|semcon=IS:019}} | |||
|IS:019 | |||
|2024-03-25 | |||
|2024-03-25 | |||
| | |||
|there can be no two {{IS:Tag|gradientChange}} belonging to the same track with the same @pos attribute | |||
|} | |} |
Revision as of 20:58, 3 June 2024
Element | ID | Proposal date | Date of acception | Date of deprecation | Description |
---|---|---|---|---|---|
<TT:timetablePeriod> | TT:001 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with other validity periods. | |
<TT:specialService> | TT:018 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with other <specialService> validity periods of the same enclosing <operatingPeriod>. | |
<TT:operatingPeriodRef> | CO:002 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. | |
<TT:operatingPeriod> | CO:002 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. | |
<TT:operatingDay> | TT:019 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with other <operatingDay> validity periods of the same enclosing <operatingPeriod>. | |
<TT:circulation> | CO:002 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. | |
<TT:blockPart> | CO:002 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. | |
<RS:designator> (introduced with version 2.5) | RS:001 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with the validity periods of other entries of the same register of the same enclosing <state>. | |
<RS:operator> | RS:002 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with other <operator> validity periods of the same enclosing <vehicle>/<classification>. | |
<RS:owner> (introduced with version 2.5) | RS:003 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with other <owner> validity periods of the same enclosing <vehicle>/<classification>. | |
<RS:state> | RS:004 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with other <state> validity periods of the same enclosing <vehicle>/<states>. | |
<IS:state> | IS:020 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with other <state> validity periods of the same enclosing <states> collection. See also Dev:Defining temporal availability of infrastructure elements and speed profiles. | |
<IS:state (with length)> | IS:021 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with other <state (with length)> validity periods of the same enclosing <states (with length)> collection. See also Dev:Defining temporal availability of infrastructure elements and speed profiles. | |
<IS:designator> | CO:001 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with the validity periods of other entries of the same register of the same enclosing element. | |
<CO:designator> (introduced with version 2.5) | CO:001 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with the validity periods of other entries of the same register of the same enclosing element. | |
<CO:phase> (introduced with version 2.5) | CO:002 | 2018-11-12 | 2019-03-21 | Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. | |
<TT:ocpTT> | TT:002 | 2018-10-25 | 2019-06-20 | The attribute sequence is shall be increasing according to the train path. | |
2018-10-25 | discarded | ||||
<TT:blockPart> | TT:003 | 2019-07-13 | 2019-07-18 | By means of a <blockPart> it is possible to model both journeys with and without reference to a <trainPart> within a roster, as well as services without change of location (without reference to a <trainPart>). These 3 basic types are distinguished by the attribute mission. The following table presents the semantic constraints: (not included here) | |
<TT:blockPart> | TT:004 | 2019-07-20 | 2019-07-18 | vehicleRef and formationRef shall not be used within the same blockPart, since a blockPart is either one for a certain vehicle or one for a whole formation. | |
<TT:rostering> | TT:005 | 2019-05-22 | 2019-06-25 | vehicleRef and formationRef are to be used exceptional since the circulation plan is either one for a certain vehicle or one for a whole formation. | |
<TT:stopDescription> | TT:006 | 2018-09-03 | 2019-06-20 | Constraints between the attributes <ocpTT>.ocpType, <stopDescription>.guaranteedPass, .commercial, .onOff, .stopOnRequest and .operationalStopOrdered | |
TT:007 | 2019-06-19 | discarded | 2020-04-23 | ||
<TT:trackInfo> | TT:008 | 2018-08-21 | 2019-06-20 | The representation of differentiated track usage must not result in differences in arrival and departure times. In these cases, a separate <trainPart> / <train> with different arrival and departure times must be created. | |
<TT:trackInfo> | TT:009 | 2018-08-21 | 2019-06-20 | The operating days days of the <operatingPeriodRef>s of the individual <trackInfo> entries must be disjoint and must not contain more traffic days than the parent <trainPart>. If fewer traffic days are provided in the <trackInfo> entries than the parent <trainPart> contains, the information (e.g. attribute trackInfo) of the parent <ocpTT> must be evaluated for these operating days. | |
<TT:times> (Correct encoding of run time supplements) | TT:010 | 2019-06-19 | 2020-10-15 | @scope='earliest' and 'latest' are not intended to encode supplement times, as this is redundant to <ocpTT>.<sectionTT>.<runTimes>@operationalReserve, @additionalReserve, @minimalTime. | |
<TT:times> | TT:011 | 2019-06-19 | discarded | ||
<TT:times> | TT:012 | 2019-06-19 | 2022-06-02 | When @scope='actual' is used, then the operating period and/or timetable period specified at the trainpart level shall refer to only one operating day. Like this the operating day to which the actual times refer is defined. | |
<TT:times> | TT:013 | 2019-06-19 | discarded | ||
<TT:times> (Arrival times for passing OCP's) | TT:014 | 2019-06-19 | 2022-06-02 | @arrival is not to be specified if the attribute ocpType of the parent <ocpTT> has the value pass - use departure for run-through (passing) times; This is in line with the definition of @arrival as the moment at which the train ends its movement and gets to a halt at the parent <ocpTT>. | |
<TT:times> (Arrival time at first OCP) | TT:015 | 2019-06-19 | 2022-06-02 | At the first <ocpTT> of a <trainPart> that is not the first one of the <trainPartSequence>, the attribute @arrival is optional. If it is set anyway, then, for consistency reasons, the value of @arrival of the regarding <ocpTT> must be identical for both this <trainPart> and the preceding one. | |
<TT:times> (Departure time at last OCP) | TT:016 | 2020-10-09 | 2022-06-02 | At the last <ocpTT> of a <trainPart> that is not the last one of the <trainPartSequence>, the attribute @departure is optional. If it is set anyway, then, for consistency reasons, the value of @departure of the regarding <ocpTT> must be identical for both this <trainPart> and the subsequent one. | |
<TT:connection> | TT:017 | 2022-12-15 | 2022-12-15 | If the trainPartRef attribute is given, then there must also be a trainRef attribute, and the trainPartRef attribute must point to a train part of the train referenced by the trainRef attribute. | |
IS:001 | 2019-04-11 | discarded | |||
<IS:trackEnd> | IS:002 | 2019-06-17 |
| ||
<IS:trackBegin> | IS:003 | 2019-06-17 |
| ||
<IS:track> | IS:004 | 2019-06-17 | Single track railway lines shall have main driving direction @mainDir="none" if they are used in both directions | ||
<IS:ocp> | IS:005 | 2019-06-19 | 2022-07-14 | An <ocp> that refers to a parent <ocp> via an @parentOcpRef overwrites the attributes and elements of the parent <ocp> if explicitely defined. If an element is specified on an <ocp> that uses a @parentOcpRef any information provided with that element on a higher layer of the <ocp>-tree is overwritten. There is no merging of element-information from different levels. The same applies for attributes of <ocp>. | |
<IS:mileageChange> | IS:006 | 2019-06-19 |
| ||
IS:007 | 2020-02-25 | discarded | |||
<IS:uptime> | IS:008 | 2020-02-28 | An <ocp> with <propOperational>@operationalType=blockSignal shall not have
@mode=manned (as a manned blockSignal shall be modelled in railML® 2.x as a blockPost). | ||
<IS:uptime> | IS:009 | 2020-02-28 | An <ocp> with attribute <propOperational>@operationalType=stoppingPoint shall not have @mode=manned (as a stoppingPoint has no operational usage and therefore no operational staff by the IM). | ||
<IS:uptime> | IS:010 | 2020-02-28 | An enumeration of several time periods by @from and @until for one <ocp> shall not overlap so that for every time there shall be a unique status of <uptime>. | ||
<IS:speedChange> | IS:011 | 2022-03-14 (to be def. more accurately) | 2021-11-10 (40th conference slide 11) |
| |
<IS:speedProfile> | IS:012 | 2022-03-14 | @basicSpeedProfile is always linked with @influence=increasing | ||
<IS:speedProfile> | IS:013 | 2022-03-14 |
| ||
<IS:tunnel> | IS:014 | 2022-03-14 | Define the tunnel resistance factor @resistanceFactorPassenger resp. @resistanceFactorFreight only if @kind and @crossSection are not known. | ||
<IS:ocp> | IS:015 | 2022-07-14 | 2022-08-11 | When specifying @parentOcpRef for an <ocp> circles are not allowed. That means that when following the chain of @parentOcpRef no <ocp> shall be visited twice. | |
<IS:axleWeightChange> <clearanceGaugeChange> <electrificationChange> <gaugeChange> <ownerChange> <gradientChange> <powerTransmissionChange> <radiusChange> | IS:016 | 2021-11-10 | 2021-11-10 | must not have @dir attribute according to Report from the Infrastructure developers in railML 3.2 and 2.5 (link to the railML® website) slide 9 and #357 | |
<railml> <infrastructure> | IS:017 | 2024-03-25 | 2024-03-25 | either <infrastructure> or <railml> must have @version attribute | |
<metadata> @name | IS:018 | 2024-03-25 | 2024-03-25 | either <metadata> must have <dc:language> child or every @name attribute accompanied by @xml:lang | |
<IS:gradientChange> | IS:019 | 2024-03-25 | 2024-03-25 | there can be no two <gradientChange> belonging to the same track with the same @pos attribute |