TT:trackInfo stopDescription ocpTT ocpsTT trainPart: Difference between revisions
[checked revision] | [checked revision] |
(Provided information concerning semantics, attributes and notes, removed "missing semantics" block) |
No edit summary |
||
(11 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
{{elementDocu | {{elementDocu | ||
|elementName={{TT:Tag|trackInfo}} | |intro=2.4 | ||
|parent={{TT:Tag|stopDescription}} | |elementName={{TT:Tag|trackInfo|stopDescription ocpTT ocpsTT trainPart}} | ||
|parent={{TT:Tag|stopDescription|ocpTT ocpsTT trainPart}} | |||
|childs=''None'' | |childs=''None'' | ||
|semantics= | |minocc=0 | ||
|maxocc=∞ | |||
|semantics= | |||
This element allows the specification of several different track and platform designations for one {{TT:Tag|ocpTT}} of the {{TT:Tag|train}} run differentiated by operating days without having to create different {{TT:Tag|trainPart}}s or {{TT:Tag|train}}s. This mapping option can be used if only the designations of the used station tracks and platforms are relevant, but not the referencing of {{IS:Tag|infrastructure}} elements via the {{Attr|trackRef}} attribute or the {{TT:Tag|platformEdgeRef}} element of the parent {{TT:Tag|ocpTT}}. | This element allows the specification of several different track and platform designations for one {{TT:Tag|ocpTT}} of the {{TT:Tag|train}} run differentiated by operating days without having to create different {{TT:Tag|trainPart}}s or {{TT:Tag|train}}s. This mapping option can be used if only the designations of the used station tracks and platforms are relevant, but not the referencing of {{IS:Tag|infrastructure}} elements via the {{Attr|trackRef}} attribute or the {{TT:Tag|platformEdgeRef}} element of the parent {{TT:Tag|ocpTT}}. | ||
Line 40: | Line 42: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| | |semcon = {{TT:008}}{{TT:009}} | ||
}} | }} |
Latest revision as of 18:20, 24 September 2023
Scheme description / Schemenbeschreibung
Position of <trackInfo> in the XML-Tree / Position von <trackInfo> im XML-Baum
- Parent: <stopDescription>
- Children: None
Multiplicity / Anzahl
Semantics / Bedeutung
This element allows the specification of several different track and platform designations for one <ocpTT> of the <train> run differentiated by operating days without having to create different <trainPart>s or <train>s. This mapping option can be used if only the designations of the used station tracks and platforms are relevant, but not the referencing of <infrastructure> elements via the trackRef attribute or the <platformEdgeRef> element of the parent <ocpTT>.
Dieses Element ermöglicht die Angabe mehrerer unterschiedlicher Gleis- und Bahnsteigkanten-Bezeichnungen für eine <ocpTT> des Zuglaufs, separiert nach Verkehrstagen ohne hierfür unterschiedliche <trainPart>s oder <train>s anlegen zu müssen. Diese Abbildungsmöglichkeit kann nur verwendet werden, wenn lediglich die Bezeichnungen der genutzten Bahnhofsgleise und Bahnsteigkanten relevant sind, nicht jedoch die Referenzierung von <infrastructure>-Elementen über das trackRef-Attribut oder das <platformEdgeRef>-Element der übergeordneten <ocpTT>.(introduced with version 2.4)
Please, be aware of the semantic constraint(s)!
Attributes of <trackInfo> / Attribute von <trackInfo>
- operatingPeriodRef: Operating days on which the station track / the platform edge is used. Verkehrstage, an denen das Bahnhofsgleis / die Bahnsteigkante genutzt wird.
- track: Designation of the track. Bezeichnung des Bahnhofsgleises.
- platform: Designation of the platform edge. Bezeichnung der Bahnsteigkante.
- xs:anyAttribute: This provides an extension point for non-railML® attributes in a foreign namespace. How to use it?
Syntactic Constraints / Syntaktische Beschränkungen
- operatingPeriodRef: xs:IDREF, optional
- track: xs:string, optional
- platform: xs:string, optional
- xs:anyAttribute: This provides an extension point for non-railML® attributes in a foreign namespace. How to use it?
Semantic Constraints / Semantische Beschränkungen
|
|
Best practice & Examples / Empfohlene Anwendung & Beispiele
<trainPart id="..." > <operatingPeriodRef ref="op_Daily" /> <ocpsTT> ... <ocpTT sequence="23" ocpRef="ocp_FF" ocpType="stop"> <times scope="scheduled" arrival="12:23:36" departure="12:25:48"/> <stopDescription commercial="true"> <trackInfo operatingPeriodRef="op_Monday-Friday" track="Track 4" /> <trackInfo operatingPeriodRef="op_Saturday+Sunday_in_Winter" track="Track 7" platform="7A" /> <trackInfo operatingPeriodRef="op_Saturday+Sunday_in_Summer" track="Track 5" platform="5.1" /> </stopDescription> </ocpTT> ... </ocpsTT> </trainPart>
Notes / Anmerkungen
Not yet described. / Noch nicht beschrieben.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.