User:Ferri Leberl/Spielwiese

From railML 2 Wiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Element Id Status Proposal Approval Deprication Content
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. - Ferri Leberl/IS:tunnel IS:014 proposed 2022-03-14 Define the tunnel resistance factor <tt>@resistanceFactorPassenger</tt> resp. <tt>@resistanceFactorFreight</tt> only if <tt>@kind</tt> and <tt>@crossSection</tt> are not known. - 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> - Ferri Leberl/TT:stopDescription TT:006 approved 2018-09-03 2019-06-20 The following table summarises the semantical constraints between the attributes <tt><ocpTT></tt>.<tt><span id=ocpType>ocpType</span></tt>, <tt><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>

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><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.
- IS:mileageChange IS:006 proposed 2019-06-19 *Define attributes <tt>@absPosIn</tt> and <tt>@absPos</tt> for "real" mileage changes
  • Define attribute <tt>@absPosIn</tt> alone in case of an ending mileage
  • Define attribute <tt>@absPos</tt> alone in case of a starting mileage
  • For starting mileages and "real" mileage changes, the <tt>@absDir</tt> has to be fiven to define the ongoing orientation of the mileage
- IS:ocp IS:005 approved 2019-06-19 2022-07-14 An <tt><ocp></tt> that refers to a parent <tt><ocp></tt> via an <tt>@parentOcpRef</tt> overwrites the attributes and elements of the parent <tt><ocp></tt> if explicitely defined. If an element is specified on an <tt><ocp></tt> that uses a <tt>@parentOcpRef</tt> any information provided with that element on a higher layer of the <tt><ocp></tt>-tree is overwritten. There is no merging of element-information from different levels. The same applies for attributes of <tt><ocp></tt>. For further information see example below. - IS:ocp IS:015 proposed 2022-07-14 When specifying <tt>@parentOcpRef</tt> for an <tt><ocp></tt> circles are not allowed. That means that when following the chain of <tt>@parentOcpRef</tt> no <tt><ocp></tt> shall be visited twice. - 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:001 proposed 2019-04-11 <tt><span id=trainRelation>trainRelation</span></tt>: Allways define this attribute! - IS:speedChange IS:011 proposed 2022-03-14 <br> - IS:speedProfile IS:012 proposed 2022-03-14 <tt>@basicSpeedProfile</tt> is always linked with <tt>@influence</tt>=<tt><span id=increasing>increasing</span></tt> - IS:speedProfile IS:013 proposed 2022-03-14 <br>
  • <tt>@influence</tt>=<tt><span id=increasing>increasing</span></tt>: The <tt><speedProfile></tt> increases the permitted speed. If multiple "increasing" speed profiles are applicable, select the one with the highest <tt>@vMax</tt> value.
  • <tt>@influence</tt>=<tt><span id=decreasing>decreasing</span></tt>: The <tt><speedProfile></tt> decreases the permitted speed. If multiple "decreasing" speed profiles are applicable, select the one with the lowest <tt>@vMax</tt> value. If this value is lower than the speed of an "increasing" speed profile, it overrides that speed.
- 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: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:trackBegin IS:003 proposed 2019-06-17 *The value of <tt>@pos</tt> in <tt><trackBegin></tt> is allways "0". - IS:trackEnd IS:002 proposed 2019-06-17 *The value of <tt>@pos</tt> in <tt><trackBegin></tt> is allways "0". - IS:track IS:004 proposed 2019-06-17 Single track railway lines shall have main driving direction <tt>@mainDir</tt>&#61;"none" if they are used in both directions - IS:tunnel IS:014 proposed 2022-03-14 Define the tunnel resistance factor <tt>@resistanceFactorPassenger</tt> resp. <tt>@resistanceFactorFreight</tt> only if <tt>@kind</tt> and <tt>@crossSection</tt> are not known. - IS:uptime IS:008 proposed 2020-02-28 An <tt><ocp></tt> with <tt><propOperational>@operationalType</tt>=blockSignal shall not have

<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:009 proposed 2020-02-28 An <tt><ocp></tt> with attribute <tt><propOperational>@operationalType</tt>=stoppingPoint shall not have <tt>@mode</tt>=manned (as a stoppingPoint has no operational usage and therefore no operational staff by the IM). - IS:uptime IS:010 proposed 2020-02-28 An enumeration of several time periods by <tt>@from</tt> and <tt>@until</tt> for one <tt><ocp></tt> shall not overlap so that for every time there shall be a unique status of <tt><uptime></tt>. - LangSemcon {{{id}}} proposed 2019-07-09 The language identifier shall be used in combination with attributes <tt>@name</tt> and <tt>@description</tt>. - 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 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 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. - SemconProposal {{{id}}} proposed 2018-12-10 Never put off until tomorrow what you can do today. - 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> - Semcon AA:nnn deprecated 2019-02-12 2019-03-18 Never put off until tomorrow what you can do today. - Semcon AA:nnn proposed 1980-10-16 All work and no play makes Jack a dull boy. - 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: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:003 approved 2019-06-13 2019-07-18 By means of a <tt><blockPart></tt> it is possible to model both journeys with and without reference to a <tt><trainPart></tt> within a roster, as well as services without change of location (without reference to a <tt><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><blockPart></tt> können innerhalb eines Umlaufplans sowohl Fahrten mit und ohne Referenz auf einen <tt><trainPart></tt> abgebildet werden, als auch Dienste ohne Ortsveränderung (ohne Referenz auf einen <tt><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>

attributes of <blockPart>
mission trainPartRef startOcpRef / endOcpRef begin / end, beginDay / endDay runLength
trip with reference to a <trainPart> timetable mandatory redundant to referenced <trainPart>, must be empty or without contradiction to referenced <trainPart>
trip without reference to a <trainPart> fullRun, emptyRun shall not be used mandatory mandatory optional
service all other values shall not be used mandatory, startOcpRef = endOcpRef mandatory optional
- 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: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: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: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: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: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: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 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: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:stopDescription TT:006 approved 2018-09-03 2019-06-20 The following table summarises the semantical constraints between the attributes <tt><ocpTT></tt>.<tt><span id=ocpType>ocpType</span></tt>, <tt><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>

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><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:010 approved 2019-06-19 2020-10-15 <tt>@scope</tt>&#61;'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"><tt>@scope</tt>&#61;'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:012 approved 2019-06-19 2022-06-02 When <tt>@scope</tt>&#61;'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 <tt>@scope</tt>&#61; '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:014 approved 2019-06-19 2022-06-02 <tt>@arrival</tt> is not to be specified if the attribute <tt><span id=ocpType>ocpType</span></tt> of the parent <tt><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 <tt>@arrival</tt> as the moment at which the train ends its movement and gets to a halt at the parent <tt><ocpTT></tt>. - TT:times TT:015 approved 2019-06-19 2022-06-02 At the first <tt><ocpTT></tt> of a <tt><trainPart></tt> that is not the first one of the <tt><trainPartSequence></tt>, the attribute <tt>@arrival</tt> is optional. If it is set anyway, then, for consistency reasons, the value of <tt>@arrival</tt> of the regarding <tt><ocpTT></tt> must be identical for both this <tt><trainPart></tt> and the preceding one. - TT:times TT:016 approved 2020-10-09 2022-06-02 At the last <tt><ocpTT></tt> of a <tt><trainPart></tt> that is not the last one of the <tt><trainPartSequence></tt>, the attribute <tt>@departure</tt> is optional. If it is set anyway, then, for consistency reasons, the value of <tt>@departure</tt> of the regarding <tt><ocpTT></tt> must be identical for both this <tt><trainPart></tt> and the subsequent one. - 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. {{{7}}}