View table: SemCons
Jump to navigation
Jump to search
Table structure:
- Element - String
- Id - String
- Status - String
- Proposal - String
- Approval - String
- Deprication - String
- Content - Text
This table has 48 rows altogether.
| Page | Element | Id | Status | Proposal | Approval | Deprication | Content |
|---|---|---|---|---|---|---|---|
| CO:phase | [[CO:phase]] | TT:001 | approved | 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. | |
| IS:mileageChange | [[IS:mileageChange]] | IS:006 | proposed | 2019-06-19 | – | *Define attributes [[#absPosIn|<tt>'''@absPosIn'''</tt>]] and [[#absPos|<tt>'''@absPos'''</tt>]] for "real" mileage changes *Define attribute [[#absPosIn|<tt>'''@absPosIn'''</tt>]] alone in case of an ending mileage *Define attribute [[#absPos|<tt>'''@absPos'''</tt>]] alone in case of a starting mileage *For starting mileages and "real" mileage changes, the [[#absDir|<tt>'''@absDir'''</tt>]] has to be fiven to define the ongoing orientation of the mileage | |
| IS:ocp | [[IS:ocp]] | IS:005 | approved | 2019-06-19 | 2022-07-14 | An <tt><[[IS:ocp_|ocp]]></tt> that refers to a parent <tt><[[IS:ocp_|ocp]]></tt> via an [[#parentOcpRef|<tt>'''@parentOcpRef'''</tt>]] overwrites the attributes and elements of the parent <tt><[[IS:ocp_|ocp]]></tt> if explicitely defined. If an element is specified on an <tt><[[IS:ocp_|ocp]]></tt> that uses a [[#parentOcpRef|<tt>'''@parentOcpRef'''</tt>]] any information provided with that element on a higher layer of the <tt><[[IS:ocp_|ocp]]></tt>-tree is overwritten. There is no merging of element-information from different levels. The same applies for attributes of <tt><[[IS:ocp_|ocp]]></tt>. For further information see example below. | |
| IS:ocp | [[IS:ocp]] | IS:015 | proposed | 2022-07-14 | – | When specifying [[#parentOcpRef|<tt>'''@parentOcpRef'''</tt>]] for an <tt><[[IS:ocp_|ocp]]></tt> circles are not allowed. That means that when following the chain of [[#parentOcpRef|<tt>'''@parentOcpRef'''</tt>]] no <tt><[[IS:ocp_|ocp]]></tt> shall be visited twice. | |
| IS:propOperational | [[IS:propOperational]] | IS:007 | proposed | 2020-02-25 | – | Not all combinations of <tt>'''<span id=operationalType>operationalType</span>'''</tt> and <tt>'''<span id=trafficType>trafficType</span>'''</tt> make sense. E. g. a stopping point with traffic type <tt>'''<span id=shunting>shunting</span>'''</tt> is not plausible. Therefore, the following constraints apply: * if value of <tt>'''<span id=operationalType>operationalType</span>'''</tt> in (<tt>'''<span id=crossover>crossover</span>'''</tt>, <tt>'''<span id=junction>junction</span>'''</tt>, <tt>'''<span id=blockPost>blockPost</span>'''</tt>, <tt>'''<span id=blockSignal>blockSignal</span>'''</tt>) ==> <tt>'''<span id=trafficType>trafficType</span>'''</tt> not set * if value of <tt>'''<span id=trafficType>trafficType</span>'''</tt> == <tt>'''<span id=shunting>shunting</span>'''</tt> ==> <tt>'''<span id=operationalType>operationalType</span>'''</tt> not equal to <tt>'''<span id=stoppingPoint>stoppingPoint</span>'''</tt> | |
| IS:speedChange | [[IS:speedChange]] | IS:001 | proposed | 2019-04-11 | – | <tt>'''<span id=trainRelation>trainRelation</span>'''</tt>: Allways define this attribute! | |
| IS:speedChange | [[IS:speedChange]] | IS:011 | proposed | 2022-03-14 | – | <br> *Every <tt><[[IS:track_|track]]></tt> has to have at least one <tt><[[IS:speedChange_|speedChange]]></tt> at the track begin with parameters [[#pos|<tt>'''@pos'''</tt>]]="0" and [[#dir|<tt>'''@dir'''</tt>]]="up". *Every <tt><[[IS:track_|track]]></tt> has to have at least one <tt><[[IS:speedChange_|speedChange]]></tt> at the track end with parameters [[#pos|<tt>'''@pos'''</tt>]]="{value equal to trackEnd@pos}" and [[#dir|<tt>'''@dir'''</tt>]]="down". | |
| IS:speedProfile | [[IS:speedProfile]] | IS:012 | proposed | 2022-03-14 | – | [[#basicSpeedProfile|<tt>'''@basicSpeedProfile'''</tt>]] is always linked with [[#influence|<tt>'''@influence'''</tt>]]=<tt>'''<span id=increasing>increasing</span>'''</tt> | |
| IS:speedProfile | [[IS:speedProfile]] | IS:013 | proposed | 2022-03-14 | – | <br> *[[#influence|<tt>'''@influence'''</tt>]]=<tt>'''<span id=increasing>increasing</span>'''</tt>: The <tt><[[IS:speedProfile_|speedProfile]]></tt> increases the permitted speed. If multiple "increasing" speed profiles are applicable, select the one with the highest [[#vMax|<tt>'''@vMax'''</tt>]] value. *[[#influence|<tt>'''@influence'''</tt>]]=<tt>'''<span id=decreasing>decreasing</span>'''</tt>: The <tt><[[IS:speedProfile_|speedProfile]]></tt> decreases the permitted speed. If multiple "decreasing" speed profiles are applicable, select the one with the lowest [[#vMax|<tt>'''@vMax'''</tt>]] value. If this value is lower than the speed of an "increasing" speed profile, it overrides that speed. | |
| IS:state | [[IS:state]] | TT:001 | approved | 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. | |
| IS:state (with length) | [[IS:state (with length)]] | TT:001 | approved | 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. | |
| IS:track | [[IS:track]] | IS:004 | proposed | 2019-06-17 | – | Single track railway lines shall have main driving direction [[#mainDir|<tt>'''@mainDir'''</tt>]]="none" if they are used in both directions | |
| IS:trackBegin | [[IS:trackBegin]] | IS:003 | proposed | 2019-06-17 | – | *The value of [[#pos|<tt>'''@pos'''</tt>]] in <tt><[[IS:trackBegin_%23pos|trackBegin]]></tt> is always "0". *The value of [[#pos|<tt>'''@pos'''</tt>]] in <tt><[[IS:trackEnd_%23pos|trackEnd]]></tt> is identical with the length of the track. *If [[#absPos|<tt>'''@absPos'''</tt>]] is used in <tt><[[IS:trackBegin_%23absPos|trackBegin]]></tt>, it has to be given in <tt><[[IS:trackEnd_%23absPos|trackEnd]]></tt>, too. *If two <tt><[[IS:track_|track]]></tt>s are connected, the [[#absPos|<tt>'''@absPos'''</tt>]] values of the connected <tt><[[IS:trackBegin_%23absPos|trackBegin]]></tt> and <tt><[[IS:trackEnd_%23absPos|trackEnd]]></tt> must be identical '''if''' **both are provided and **no <tt><[[IS:mileageChange_|mileageChange]]></tt> is defined at this point and **both <tt><[[IS:track_|track]]></tt>s belong to the same mileage system. | |
| IS:trackEnd | [[IS:trackEnd]] | IS:002 | proposed | 2019-06-17 | – | *The value of [[#pos|<tt>'''@pos'''</tt>]] in <tt><[[IS:trackBegin_%23pos|trackBegin]]></tt> is allways "0". *The value of [[#pos|<tt>'''@pos'''</tt>]] in <tt><[[IS:trackEnd_%23pos|trackEnd]]></tt> is identical with the length of the track. *If [[#absPos|<tt>'''@absPos'''</tt>]] is used in <tt><[[IS:trackBegin_%23absPos|trackBegin]]></tt>, it has to be given in <tt><[[IS:trackEnd_%23absPos|trackEnd]]></tt>, too. *If two <tt><[[IS:track_|track]]></tt>s are connected, the [[#absPos|<tt>'''@absPos'''</tt>]] values of the connected <tt><[[IS:trackBegin_%23absPos|trackBegin]]></tt> and <tt><[[IS:trackEnd_%23absPos|trackEnd]]></tt> must be identical '''if''' **both are provided and **no <tt><[[IS:mileageChange_|mileageChange]]></tt> is defined at this point and **both <tt><[[IS:track_|track]]></tt>s belong to the same mileage system. | |
| IS:tunnel | [[IS:tunnel]] | IS:014 | proposed | 2022-03-14 | – | Define the tunnel resistance factor [[IS:tunnel#resistanceFactorPassenger|<tt>'''@resistanceFactorPassenger'''</tt>]] resp. [[IS:tunnel#resistanceFactorFreight|<tt>'''@resistanceFactorFreight'''</tt>]] only if [[#kind|<tt>'''@kind'''</tt>]] and [[#crossSection|<tt>'''@crossSection'''</tt>]] are not known. | |
| IS:uptime | [[IS:uptime]] | IS:008 | proposed | 2020-02-28 | – | An <tt><[[IS:ocp_%23operationalType|ocp]]></tt> with <tt><[[IS:propOperational_%23operationalType|propOperational]]>@operationalType</tt>=''blockSignal'' shall not have [[#mode|<tt>'''@mode'''</tt>]]=''manned'' (as a manned ''blockSignal'' shall be modelled in railML<sup><small>®</small></sup> 2.x as a ''blockPost''). | |
| IS:uptime | [[IS:uptime]] | IS:009 | proposed | 2020-02-28 | – | An <tt><[[IS:ocp_|ocp]]></tt> with attribute <tt><[[IS:propOperational_%23operationalType|propOperational]]>@operationalType</tt>=''stoppingPoint'' shall not have [[#mode|<tt>'''@mode'''</tt>]]=''manned'' (as a ''stoppingPoint'' has no operational usage and therefore no operational staff by the IM). | |
| IS:uptime | [[IS:uptime]] | IS:010 | proposed | 2020-02-28 | – | An enumeration of several time periods by [[#from|<tt>'''@from'''</tt>]] and [[#until|<tt>'''@until'''</tt>]] for one <tt><[[IS:ocp_|ocp]]></tt> shall not overlap so that for every time there shall be a unique status of <tt><[[IS:uptime_|uptime]]></tt>. | |
| RS:operator | [[RS:operator]] | TT:001 | approved | 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. | |
| RS:owner | [[RS:owner]] | TT:001 | approved | 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. | |
| RS:state | [[RS:state]] | TT:001 | approved | 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. | |
| Template:LangSemcon | [[LangSemcon]] | {{{id}}} | proposed | 2019-07-09 | – | The language identifier shall be used in combination with attributes [[#name|<tt>'''@name'''</tt>]] and [[#description|<tt>'''@description'''</tt>]]. | |
| Template:Semcon | [[Semcon]] | AA:nnn | approved | 2019-06-04 | 2019-06-05 | People who live in glass houses shouldn't throw stones.<br><span style="color:#0000FF">Wer im Glashaus sitzt, soll nicht mit Steinen werfen.</span> | |
| Template:Semcon | [[Semcon]] | AA:nnn | deprecated | 2019-02-12 | 2019-03-18 | Never put off until tomorrow what you can do today. | |
| Template:Semcon | [[Semcon]] | AA:nnn | proposed | 1980-10-16 | – | All work and no play makes Jack a dull boy. | |
| Template:SemconProposal | [[SemconProposal]] | {{{id}}} | proposed | 2018-12-10 | – | Never put off until tomorrow what you can do today. | |
| Template:StartEndCon | [[StartEndCon]] | TT:001 | approved | 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:blockPart | [[TT:blockPart]] | TT:001 | approved | 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:blockPart | [[TT:blockPart]] | TT:003 | approved | 2019-06-13 | 2019-07-18 | By means of a <tt><[[TT:blockPart_|blockPart]]></tt> it is possible to model both journeys with and without reference to a <tt><[[TT:trainPart_|trainPart]]></tt> within a roster, as well as services without change of location (without reference to a <tt><[[TT:trainPart_|trainPart]]></tt>). These 3 basic types are distinguished by the attribute <tt>'''<span id=mission>mission</span>'''</tt>. The following table presents the semantic constraints: <span style="color:#0000FF">Mit Hilfe eines <tt><[[TT:blockPart_|blockPart]]></tt> können innerhalb eines Umlaufplans sowohl Fahrten mit und ohne Referenz auf einen <tt><[[TT:trainPart_|trainPart]]></tt> abgebildet werden, als auch Dienste ohne Ortsveränderung (ohne Referenz auf einen <tt><[[TT:trainPart_|trainPart]]></tt>). Unterschieden werden diese 3 Grundtypen anhand des Attributs <tt>'''<span id=mission>mission</span>'''</tt>. In der folgenden folgende Tabelle werden die semantischen Abhängigkeiten gegenüber gestellt:</span> {| class="wikitable" ! rowspan="2" style="background-color:#efefef;" | ! colspan="5" style="text-align: center; background-color:#efefef;" | attributes of <blockPart> |- | style="text-align: center; font-weight:bold; background-color:#efefef;" | mission | style="text-align: center; font-weight:bold; background-color:#efefef;" | trainPartRef | style="text-align: center; font-weight:bold; background-color:#efefef;" | startOcpRef / endOcpRef | style="text-align: center; font-weight:bold; background-color:#efefef;" | begin / end, beginDay / endDay | style="text-align: center; font-weight:bold; background-color:#efefef;" | runLength |- | style="font-weight:bold; background-color:#efefef;" | trip with reference to a <trainPart> | style="text-align: center;" | timetable | style="text-align: center;" | mandatory | colspan="3" style="text-align: center;" | redundant to referenced <trainPart>, must be empty or without contradiction to referenced <trainPart> |- | style="font-weight:bold; background-color:#efefef;" | trip without reference to a <trainPart> | style="text-align: center;" | fullRun, emptyRun | style="text-align: center;" | shall not be used | style="text-align: center;" | mandatory | style="text-align: center;" | mandatory | style="text-align: center;" | optional |- | style="font-weight:bold; background-color:#efefef;" | service | style="text-align: center;" | all other values | style="text-align: center;" | shall not be used | style="text-align: center;" | mandatory, startOcpRef = endOcpRef | style="text-align: center;" | mandatory | style="text-align: center;" | optional |} | |
| TT:blockPart | [[TT:blockPart]] | TT:004 | approved | 2019-06-20 | 2019-07-18 | <tt>'''<span id=vehicleRef>vehicleRef</span>'''</tt> and <tt>'''<span id=formationRef>formationRef</span>'''</tt> shall not be used within the same blockPart, since a blockPart is either one for a certain vehicle or one for a whole formation.<br><span style="color:#0000FF">Es ist nur entweder <tt>'''<span id=vehicleRef>vehicleRef</span>'''</tt> oder <tt>'''<span id=formationRef>formationRef</span>'''</tt> anzugeben (nicht jedoch beide gleichzeitig), da es sich entweder um einen Blockpart eines Einzelfahrzeugs oder einer Fahrzeuggruppe handelt.</span> | |
| TT:circulation | [[TT:circulation]] | TT:001 | approved | 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:ocpTT | [[TT:ocpTT]] | TT:002 | approved | 2018-10-25 | 2019-06-20 | The attribute sequence is shall be increasing according to the train path.<br/> <span style="color:#0000FF">Das Attribut sequence muss ansteigend entsprechend dem Zuglauf sein.</span> | |
| TT:operatingDay | [[TT:operatingDay]] | TT:001 | approved | 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:operatingPeriod | [[TT:operatingPeriod]] | TT:001 | approved | 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:operatingPeriodRef trainPart | [[TT:operatingPeriodRef trainPart]] | TT:001 | approved | 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:rostering | [[TT:rostering]] | TT:005 | approved | 2019-05-22 | 2019-06-25 | <tt>'''<span id=vehicleRef>vehicleRef</span>'''</tt> and <tt>'''<span id=formationRef>formationRef</span>'''</tt> are to be used exceptional since the circulation plan is either one for a certain vehicle or one for a whole formation.<br><span style="color:#0000FF">Es ist nur entweder <tt>'''<span id=vehicleRef>vehicleRef</span>'''</tt> oder <tt>'''<span id=formationRef>formationRef</span>'''</tt> anzugeben (nicht jedoch beide gleichzeitig), da es sich entweder um einen Umlauf eines Einzelfahrzeugs oder einer Fahrzeuggruppe handelt.</span> | |
| TT:specialService operatingPeriod | [[TT:specialService operatingPeriod]] | TT:001 | approved | 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 operatingPeriodRef | [[TT:specialService operatingPeriodRef]] | TT:001 | approved | 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:stopDescription | [[TT:stopDescription]] | TT:006 | approved | 2018-09-03 | 2019-06-20 | The following table summarises the semantical constraints between the attributes <tt><[[TT:ocpTT_|ocpTT]]></tt>.<tt>'''<span id=ocpType>ocpType</span>'''</tt>, <tt><[[TT:stopDescription_|stopDescription]]></tt>.<tt>'''<span id=guaranteedPass>guaranteedPass</span>'''</tt>, .<tt>'''<span id=commercial>commercial</span>'''</tt>, .<tt>'''<span id=onOff>onOff</span>'''</tt>, .<tt>'''<span id=stopOnRequest>stopOnRequest</span>'''</tt> and .<tt>'''<span id=operationalStopOrdered>operationalStopOrdered</span>'''</tt>:<br> [[File:RailML_2_stopDescription_constraints.png]]<br> * Green cells are default values. * <tt>'''<span id=ocpType>ocpType</span>'''</tt>='begin','end' are deprecated from railML 2.2. * If no <tt><[[TT:stopDescription_|stopDescription]]></tt> is given, it is either a non-guaranteed pass (1.2) or a stop with undefined properties, depending on the attribute <tt>'''<span id=ocpType>ocpType</span>'''</tt>. * ''The term "commercial" of the attribute in railML traditionally refers to the contractual relationship between RU and end-customer, not to the contractual relationship between IM and RU.'' * ''The term "ordered" in the attribute <tt>'''<span id=operationalStopOrdered>operationalStopOrdered</span>'''</tt> refers to the contractual relationship between IM and RU.'' | |
| TT:times | [[TT:times]] | TT:010 | approved | 2019-06-19 | 2020-10-15 | [[#scope|<tt>'''@scope'''</tt>]]='earliest' and 'latest' are ''not'' intended to encode supplement times, as this is redundant to <ocpTT>.<sectionTT>.<runTimes>@operationalReserve, @additionalReserve, @minimalTime. <br/> <span style="color:#0000FF">[[#scope|<tt>'''@scope'''</tt>]]='earliest' und 'latest' sind ''nicht'' zur Abbildung von Fahrzeitzuschlägen zu verwenden, da dies redundant zu <ocpTT>.<sectionTT>.<runTimes>@operationalReserve, @additionalReserve, @minimalTime ist.</span> | |
| TT:times | [[TT:times]] | TT:012 | approved | 2019-06-19 | 2022-06-02 | When [[#scope|<tt>'''@scope'''</tt>]]='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. <br/> <span style="color:#0000FF">Wenn [[#scope|<tt>'''@scope'''</tt>]]= 'actual' verwendet wird, bezieht sich die operating period und/oder timetable period des train(part) auf nur einen einzelnen Betriebstag. Es muss so festgelegt werden, auf welchen Betriebstag sich die erfassten Ist-Zeiten beziehen.</span> | |
| TT:times | [[TT:times]] | TT:014 | approved | 2019-06-19 | 2022-06-02 | [[#arrival|<tt>'''@arrival'''</tt>]] is not to be specified if the attribute <tt>'''<span id=ocpType>ocpType</span>'''</tt> of the parent <tt><[[TT:ocpTT_|ocpTT]]></tt> has the value ''pass'' - use <tt>'''<span id=departure>departure</span>'''</tt> for run-through (passing) times; This is in line with the definition of [[#arrival|<tt>'''@arrival'''</tt>]] as the moment at which the train ends its movement and gets to a halt at the parent <tt><[[TT:ocpTT_|ocpTT]]></tt>. | |
| TT:times | [[TT:times]] | TT:015 | approved | 2019-06-19 | 2022-06-02 | At the first <tt><[[TT:ocpTT_|ocpTT]]></tt> of a <tt><[[TT:trainPart_|trainPart]]></tt> that is not the first one of the <tt><[[TT:trainPartSequence_|trainPartSequence]]></tt>, the attribute [[#arrival|<tt>'''@arrival'''</tt>]] is optional. If it is set anyway, then, for consistency reasons, the value of [[#arrival|<tt>'''@arrival'''</tt>]] of the regarding <tt><[[TT:ocpTT_|ocpTT]]></tt> must be identical for both this <tt><[[TT:trainPart_|trainPart]]></tt> and the preceding one. | |
| TT:times | [[TT:times]] | TT:016 | approved | 2020-10-09 | 2022-06-02 | At the last <tt><[[TT:ocpTT_|ocpTT]]></tt> of a <tt><[[TT:trainPart_|trainPart]]></tt> that is not the last one of the <tt><[[TT:trainPartSequence_|trainPartSequence]]></tt>, the attribute [[#departure|<tt>'''@departure'''</tt>]] is optional. If it is set anyway, then, for consistency reasons, the value of [[#departure|<tt>'''@departure'''</tt>]] of the regarding <tt><[[TT:ocpTT_|ocpTT]]></tt> must be identical for both this <tt><[[TT:trainPart_|trainPart]]></tt> and the subsequent one. | |
| TT:timetablePeriod | [[TT:timetablePeriod]] | TT:001 | approved | 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. | |
| User:Ferri Leberl/IS:tunnel | [[Ferri Leberl/IS:tunnel]] | IS:014 | proposed | 2022-03-14 | – | Define the tunnel resistance factor [[IS:tunnel#resistanceFactorPassenger|<tt>'''@resistanceFactorPassenger'''</tt>]] resp. [[IS:tunnel#resistanceFactorFreight|<tt>'''@resistanceFactorFreight'''</tt>]] only if [[#kind|<tt>'''@kind'''</tt>]] and [[#crossSection|<tt>'''@crossSection'''</tt>]] are not known. | |
| User:Ferri Leberl/TT:ocpTT | [[Ferri Leberl/TT:ocpTT]] | TT:002 | approved | 2018-10-25 | 2019-06-20 | The attribute sequence is shall be increasing according to the train path.<br/> <span style="color:#0000FF">Das Attribut sequence muss ansteigend entsprechend dem Zuglauf sein.</span> | |
| User:Ferri Leberl/TT:stopDescription | [[Ferri Leberl/TT:stopDescription]] | TT:006 | approved | 2018-09-03 | 2019-06-20 | The following table summarises the semantical constraints between the attributes <tt><[[TT:ocpTT_|ocpTT]]></tt>.<tt>'''<span id=ocpType>ocpType</span>'''</tt>, <tt><[[TT:stopDescription_|stopDescription]]></tt>.<tt>'''<span id=guaranteedPass>guaranteedPass</span>'''</tt>, .<tt>'''<span id=commercial>commercial</span>'''</tt>, .<tt>'''<span id=onOff>onOff</span>'''</tt>, .<tt>'''<span id=stopOnRequest>stopOnRequest</span>'''</tt> and .<tt>'''<span id=operationalStopOrdered>operationalStopOrdered</span>'''</tt>:<br> [[File:RailML_2_stopDescription_constraints.png]]<br> * Green cells are default values. * <tt>'''<span id=ocpType>ocpType</span>'''</tt>='begin','end' are deprecated from railML 2.2. * If no <tt><[[TT:stopDescription_|stopDescription]]></tt> is given, it is either a non-guaranteed pass (1.2) or a stop with undefined properties, depending on the attribute <tt>'''<span id=ocpType>ocpType</span>'''</tt>. * ''The term "commercial" of the attribute in railML traditionally refers to the contractual relationship between RU and end-customer, not to the contractual relationship between IM and RU.'' * ''The term "ordered" in the attribute <tt>'''<span id=operationalStopOrdered>operationalStopOrdered</span>'''</tt> refers to the contractual relationship between IM and RU.'' |