TT:connection: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(clarified usage for connecting trains with multiple stops at the same ocp)
(added documentation for minConnTime provided by David Lichti (Hacon) after discussion in TT Telco)
Line 19: Line 19:
}}
}}
{{missing information|user=[[User:Coordination|Coordination]] 16:02, 21 January 2020 (CEST)|topic=the semantics of ''maxConnTime''}}
{{missing information|user=[[User:Coordination|Coordination]] 16:02, 21 January 2020 (CEST)|topic=the semantics of ''maxConnTime''}}
* {{Attr|minConnTime}}: This is the minimal connection duration needed for this connection operation. This means that a connector will have to wait at least this long after the arrival of the feeder for the passengers to transfer.
* {{Attr|minConnTime}}: Specifies the minimal time between the feeder's arrival and the connector's departure that is considered necessary to realise the connection. The parameters of this estimate are unspecified and need to be agreed upon by the communicating parties. The minimal connection time is an '''estimate''' that '''should''' cover all relevant transfer profiles. It is up to the interface users to agree on what profiles (f.ex. high/limited mobility) and parameters (f.ex. peak hours, temporary elevator disruption) are relevant. The minimal connection time does not affect the arrival or departure times of the participating trains in the railML file. A timetable may contain connections that cannot be realised according to the minimal connection time estimate. It is up to the receiver to accept or refuse such a timetable, and initiate the appropriate error handling.


* {{Attr|maxConnTime}}: This is the maximal connection duration planned for this connection operation.
* {{Attr|maxConnTime}}: This is the maximal connection duration planned for this connection operation.

Revision as of 10:14, 10 October 2022


connection
 


Scheme description / Schemenbeschreibung

Position of connection in the XML-Tree / Position von connection im XML-Baum

Multiplicity / Anzahl

[0..∞]

Semantics / Bedeutung

The Element connection describes any connection between this train and another one.

Das Element connection beschreibt Anschlussbeziehungen zwischen diesem und einem anderen Zug. Flügelungen und Umlaufübergänge werden aber dabei nicht betrachtet.

Attributes of connection / Attribute von connection

  • trainRef: This refers to the id attribute of the associated train element.

Missinginformation.png In this article there is information missing with respect to the semantics of maxConnTime. Please help improving the railML® wiki by filling the gaps. Possibly, you will find further details on the discussion pageCoordination 16:02, 21 January 2020 (CEST)
  • minConnTime: Specifies the minimal time between the feeder's arrival and the connector's departure that is considered necessary to realise the connection. The parameters of this estimate are unspecified and need to be agreed upon by the communicating parties. The minimal connection time is an estimate that should cover all relevant transfer profiles. It is up to the interface users to agree on what profiles (f.ex. high/limited mobility) and parameters (f.ex. peak hours, temporary elevator disruption) are relevant. The minimal connection time does not affect the arrival or departure times of the participating trains in the railML file. A timetable may contain connections that cannot be realised according to the minimal connection time estimate. It is up to the receiver to accept or refuse such a timetable, and initiate the appropriate error handling.
  • maxConnTime: This is the maximal connection duration planned for this connection operation.
  • connType: (introduced with version 2.2) This is the connection type. Possible values are:

Missinginformation.png In this article there is information missing with respect to the semantics of the enumeration items. Please help improving the railML® wiki by filling the gaps. Possibly, you will find further details on the discussion pageFerri Leberl (talk) 16:11, 25 April 2018 (CEST)
  • commercial
  • operational
  • connOperation: This is the connection operation. Possible values are:
  • none There is an unspecific connection to another train.
  • meet The train meets another train. Passengers may change trains in both directions.
  • IsWaitingFor The train is waiting for another train. The considered train may be receiving passengers from the referenced connection train. Anschluss auf einen Zubringer-Zug.
  • IsExpectedBy The train is expected by another train. The referenced connection train may be receiving passengers from the considered train. Anschluss auf einen Abbringer-Zug.
  • join The train will be coupled together with another train.
    (deprecated with version 2.1) The element connection should not be used for splitting and joining of trains, use trains with 'type="commercial"' instead.
  • split This part of the train will go on as another train.
    (deprecated with version 2.1) The element connection should not be used for splitting and joining of trains, use trains with 'type="commercial"' instead.
  • turnaround The train will go on as another train.
    (deprecated with version 2.1) The element connection should not be used for splitting and joining of trains, use trains with 'type="commercial"' instead.
  • other:anything: Any value that does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed. Please, apply Dev:usingAny accordingly.
  • ocpRef: This refers to the id attribute of the associated <ocp> element.
    (introduced with version 2.2) This reference could be used in the case that the passenger changes to a different nearby ocp.
  • trainPartRef: This refers to the id attribute of the associated <trainPart> element.
    (introduced with version 2.2) This reference could be used if the change is to a certain trainPart of the related train.
  • operatingPeriodRef: This refers to the id attribute of the associated <operatingPeriod> element.
    (introduced with version 2.3) References a reduction of the operating days of the connection compared to the operating days of the train part
  • notGuaranteed (introduced with version 2.3): This indicates if the connection could not be guaranteed.
  • nonConnection (introduced with version 2.3): This indicates that no such connection should be generated or communicated, in order to lead passengers to the appropriate connection.
  • samePlatform (introduced with version 2.3): This indicates if the connection is on the same platform.
  • xs:anyAttribute(introduced with version 2.2) This provides an extension point for non-railML® attributes in a foreign namespace. How to use it?

Syntactic Constraints / Syntaktische Beschränkungen

  • trainRef: xs:IDREF, optional (was mandatory until version 2.2)
  • minConnTime: xs:duration, optional
  • connType: union of (restriction of xs:string, tOtherEnumerationValue); tOtherEnumerationValue is an arbitrary string starting with 'other:' followed by at minimum two characters, white space not allowed for extending railML® enumeration lists, optional
  • connOperation: union of (restriction of xs:string, tOtherEnumerationValue); tOtherEnumerationValue is an arbitrary string starting with 'other:' followed by at minimum two characters, white space not allowed for extending railML® enumeration lists, optional

Best practice & Examples / Empfohlene Anwendung & Beispiele

Not yet described. / Noch nicht beschrieben.

Notes / Anmerkungen

If a connecting train is passing an ocp multiple times, the described connection may seem ambiguous to ready systems. If the connecting train is part of the encoding railML the attribute @trainPartRef shall be used to clarify which ocpTT of connecting train is meant. If the connecting train is not part of the encoding railML the timeframe shall be used to identify the correct stop of the connecting train.
Wenn ein verbundener Zug einen Halt mehrfach anfährt, kann es zu einer Zweideutigkeit kommen. Ist der verbundene Zug Teil des railML, so ist das Attribut @trainPartRef zu verwenden diese Zweideutigkeit aufzulösen. Ist der Zug nicht Teil des railML, so soll die Ankunfts- und Abfahrtszeit des verbundenen Zuges genutzt werden um den entsprechenden Halt für den Anschluss zu identifizieren.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.