Template:Table/Dev:Semantic Constraints: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
(Descriptions IS)
Line 62: Line 62:
|2019-06-20
|2019-06-20
|
|
|
|The attribute sequence is shall be increasing according to the train path.
|-
|-
|<s>{{TT:Tag|ocpTT|wiki=2|ex=1}} (second semantic constraint)</s>
|<s>{{TT:Tag|ocpTT|wiki=2|ex=1}} (second semantic constraint)</s>
Line 154: Line 154:
|
|
|
|
*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".
|-
|-
|{{TT:Tag|rostering|wiki=2|ex=1}}
|{{TT:Tag|rostering|wiki=2|ex=1}}
Line 252: Line 254:
|
|
|
|
*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|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}}.
*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'''
**both are provided and
**no {{IS:Tag|mileageChange}} is defined at this point and
**both {{IS:Tag|track}}s belong to the same mileage system.
|-
|-
|{{IS:Tag|trackBegin|wiki=2|ex=1}}
|{{IS:Tag|trackBegin|wiki=2|ex=1}}
Line 259: Line 268:
|
|
|
|
*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|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}}.
*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'''
**both are provided and
**no {{IS:Tag|mileageChange}} is defined at this point and
**both {{IS:Tag|track}}s belong to the same mileage system.
|-
|-
|{{IS:Tag|track|wiki=2|ex=1}}
|{{IS:Tag|track|wiki=2|ex=1}}
Line 265: Line 281:
|
|
|
|
|
|Single track railway lines shall have main driving direction {{@|mainDir}}&#61;"none" if they are used in both directions
|-
|-
|{{IS:Tag|ocp|wiki=2|ex=1}}
|{{IS:Tag|ocp|wiki=2|ex=1}}
Line 272: Line 288:
|
|
|
|
|
|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}}.
|-
|-
|{{IS:Tag|mileageChange|wiki=2|ex=1}}
|{{IS:Tag|mileageChange|wiki=2|ex=1}}
Line 280: Line 296:
|
|
|
|
*Define attributes {{@|absPosIn}} and {{@|absPos}} for "real" mileage changes
*Define attribute {{@|absPosIn}} alone in case of an ending mileage
*Define attribute {{@|absPos}} alone in case of a starting mileage
*For starting mileages and "real" mileage changes, the {{@|absDir}} has to be fiven to define the ongoing orientation of the mileage
|-
|-
|<s>{{IS:Tag|propOperational|wiki=2|ex=1}}</s>
|<s>{{IS:Tag|propOperational|wiki=2|ex=1}}</s>
Line 293: Line 313:
|
|
|
|
|
|An {{Tag|IS|ocp|attr=operationalType}} with {{Tag|IS|propOperational|@=operationalType}}=''blockSignal'' shall not have
{{@|mode}}=''manned'' (as a manned ''blockSignal'' shall be modelled in {{rml|2.x}} as a ''blockPost'').
|-
|-
|{{IS:Tag|uptime|attr=IS:009|wiki=2|ex=1}}
|{{IS:Tag|uptime|attr=IS:009|wiki=2|ex=1}}
Line 300: Line 321:
|
|
|
|
|
|An {{Tag|IS|ocp}} with attribute {{Tag|IS|propOperational|@=operationalType}}=''stoppingPoint'' shall not have {{@|mode}}=''manned'' (as a ''stoppingPoint'' has no operational usage and therefore no operational staff by the IM).
|-
|-
|{{IS:Tag|uptime|attr=IS:010|wiki=2|ex=1}}
|{{IS:Tag|uptime|attr=IS:010|wiki=2|ex=1}}
Line 307: 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}}.
|-
|-
|{{IS:Tag|speedProfile|wiki=2|ex=1|semcon=IS:012}} (first semantic constraint)
|{{IS:Tag|speedProfile|wiki=2|ex=1|semcon=IS:012}} (first semantic constraint)
Line 314: Line 335:
|
|
|
|
|
|{{@|basicSpeedProfile}} is always linked with {{@|influence}}={{enum|increasing}}
|-
|-
|{{IS:Tag|speedProfile|wiki=2|ex=1|semcon=IS:013}} (second semantic constraint)
|{{IS:Tag|speedProfile|wiki=2|ex=1|semcon=IS:013}} (second semantic constraint)
Line 322: Line 343:
|
|
|
|
*{{@|influence}}={{enum|increasing}}: The {{tag|is|speedProfile}} increases the permitted speed. If multiple "increasing" speed profiles are applicable, select the one with the highest {{@|vMax}} value.
*{{@|influence}}={{enum|decreasing}}: The {{tag|is|speedProfile}} decreases the permitted speed. If multiple "decreasing" speed profiles are applicable, select the one with the lowest {{@|vMax}} value. If this value is lower than the speed of an "increasing" speed profile, it overrides that speed.
|-
|-
|{{IS:Tag|tunnel|wiki=2|ex=1|semcon=IS:014}}
|{{IS:Tag|tunnel|wiki=2|ex=1|semcon=IS:014}}
Line 328: Line 351:
|
|
|
|
|
|Define the tunnel resistance factor {{@|resistanceFactorPassenger|IS:tunnel}} resp. {{@|resistanceFactorFreight|IS:tunnel}} only if {{@|kind}} and {{@|crossSection}} are not known.
|-
|-
|{{IS:Tag|ocp|wiki=2|ex=1|semcon=IS:015}}
|{{IS:Tag|ocp|wiki=2|ex=1|semcon=IS:015}}
Line 335: Line 358:
|
|
|
|
|
|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.
|}
|}

Revision as of 17:00, 3 July 2023

Return to article

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:operatingPeriodRef>><TT:specialService> 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:operatingPeriod>><TT:specialService> 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:operatingPeriodRef> 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:operatingPeriod> 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:operatingDay> 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.
<RS:state> 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:ocpTT> (first semantic constraint) TT:002 2018-10-25 2019-06-20 The attribute sequence is shall be increasing according to the train path.
<TT:ocpTT> (second semantic constraint) 2018-10-25 discarded
<TT:circulation> 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:blockPart> (first semantic constraint) 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:blockPart> (second semantic constraint) TT:003 2019-07-13
<TT:blockPart> (third semantic constraint) TT:004 2019-07-20
<RS:operator> 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.
<RS:owner> (introduced with version 2.5) 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.
<IS:state> 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.
<IS:state (with length)> 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.
<IS:designator> 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.
<CO:phase> (introduced with version 2.5) 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.
<IS:speedChange> (first semantic constraint) IS:001 2019-04-11 discarded 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:speedChange> (second semantic constraint) IS:011 2022-03-14
  • Every <track> has to have at least one <speedChange> at the track begin with parameters @pos="0" and @dir="up".
  • Every <track> has to have at least one <speedChange> at the track end with parameters @pos="{value equal to trackEnd@pos}" and @dir="down".
<TT:rostering> TT:005 2019-05-22 2019-06-25
<TT:stopDescription> (first semantic constraint) TT:006 2018-09-03 2019-06-20
<TT:stopDescription> (Stop on request / More than one stop type per OCP) TT:007 2019-06-19 discarded 2020-04-23
<TT:trackInfo> (first semantic constraint) TT:008 2018-08-21 2019-06-20
<TT:trackInfo> (second semantic constraint) TT:009 2018-08-21 2019-06-20
<TT:times> (Correct encoding of run time supplements) TT:010 2019-06-19 2020-10-15
<TT:times> TT:011 2019-06-19
<TT:times> TT:012 2019-06-19 2022-06-02
<TT:times> TT:013 2019-06-19
<TT:times> (Arrival times for passing OCP's) TT:014 2019-06-19 2022-06-02
<TT:times> (Arrival time at first OCP) TT:015 2019-06-19 2022-06-02
<TT:times> (Departure time at last OCP) TT:016 2020-10-09 2022-06-02
<TT:connection> TT:017 2022-12-15 2022-12-15
<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 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
  • Define attributes @absPosIn and @absPos for "real" mileage changes
  • Define attribute @absPosIn alone in case of an ending mileage
  • Define attribute @absPos alone in case of a starting mileage
  • For starting mileages and "real" mileage changes, the @absDir has to be fiven to define the ongoing orientation of the mileage
<IS:propOperational> 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:speedProfile> (first semantic constraint) IS:012 2022-03-14 @basicSpeedProfile is always linked with @influence=increasing
<IS:speedProfile> (second semantic constraint) IS:013 2022-03-14
  • @influence=increasing: The <speedProfile> increases the permitted speed. If multiple "increasing" speed profiles are applicable, select the one with the highest @vMax value.
  • @influence=decreasing: The <speedProfile> decreases the permitted speed. If multiple "decreasing" speed profiles are applicable, select the one with the lowest @vMax value. If this value is lower than the speed of an "increasing" speed profile, it overrides that speed.
<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 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.
Retrieved from "https://wiki2.railml.org/index.php?title=Template:Table/Dev:Semantic_Constraints&oldid=14896"