Search results
Jump to navigation
Jump to search
- <trainPartRef ref='tp_1.1' position='1'/> <trainPartRef ref='tp_3.1' position='2'/> <trainPartRef ref='tp_2.1' position='3'/> <trainPartRef ref='tp_4.1'12 KB (2,023 words) - 20:58, 22 January 2024
- <lineVis> ref <trackVis> ref <trackElementVis> ref <position> x, y <ocpVis> ref <position> x, y <size> height, width <objectVis> ref <position> x, y <size>112 KB (4,754 words) - 18:02, 3 April 2022
- <trainPartRef ref='tp_1.1' position='1'/> <trainPartRef ref='tp_3.1' position='2'/> <trainPartRef ref='tp_2.1' position='3'/> <trainPartRef ref='tp_4.1'24 KB (3,449 words) - 18:37, 22 January 2024
- <connection id="c12" ref="c21"/> </trackBegin> <trackEnd id="tE1"> ... </trackEnd> <connections> <switch id="s1" pos="0"> <connection id="c13" ref="c31" orientation="incoming"45 KB (5,550 words) - 18:04, 19 January 2024
- <propService passenger="true" service="true"/> <propEquipment> <trackRef ref="tr01"/> <trackRef ref="tr02"/> </propEquipment> <propOther status="operational"/>9 KB (1,420 words) - 10:23, 1 February 2024
- </xs:sequence> <xs:attributeGroup ref="rail:aOperatingCode" /> <xs:attributeGroup ref="rail:aTimePeriod" /> + <xs:attributeGroup ref="rail:anyAttribute" /> </xs:complexType>108 KB (9,484 words) - 10:56, 8 October 2021
- <xs:element ref="rail:infrastructure" minOccurs="0" /> - <xs:element ref="rail:infrastructureVisualizations" - minOccurs="0" /> - <xs:element ref="rail:rollingstock"531 KB (37,474 words) - 10:55, 8 October 2021
- sequence="1" ocpRef="A"> <sectionTT> <trackRef ref="tr3"> <trackRef ref="tr6"> <trackRef ref="tr8"> <trackRef ref="tr10"> <trackRef ref="tr9"> </sectionTT>3 KB (441 words) - 16:13, 12 September 2022
- <visualization id="vis0" infrastructureRef="inf0" version="2.4"> <lineVis ref="l1"> <trackVis ref="tr1"> <trackElementVis ref="tr1_b"> <!-- reference to the beginning10 KB (1,182 words) - 19:33, 22 January 2024
- <operationControlPoints> <ocp id="ocp01"> ... <propEquipment> <trackRef ref="tr02"/> <trackRef ref="tr03"/> </propEquipment> ... </ocp> </operationControlPoints>15 KB (1,768 words) - 18:26, 19 January 2024
- <trainPartSequence sequence="1"> <trainPartRef ref="train-part-1"/> </trainPartSequence> <replacements> <replacementOf> <operatingPeriodRef ref="operating-period-KW47-MoFr-18"3 KB (332 words) - 22:40, 25 November 2018
- TT:trainPartRef (section Position of trainPartRef in the XML-Tree / Position von trainPartRef im XML-Baum)Element <trainPartRef> wird genutzt, um einen einzelnen zum Zug gehörenden trainPart (Teilzuglauf, bzw. Zugteil) zu referenzieren. ref: This refers to the2 KB (238 words) - 23:05, 25 November 2018
- name='Dresden Hbf Wiener Strasse' parentOcpRef='ocp02'> <propEquipment> <summary hasSwitches='false' signalBox='none'/> <trackRef ref='track01'/> </propEquipment> <designator18 KB (2,618 words) - 16:53, 19 March 2024
- element, by name the values of minOccurs and maxOccurs. For example, in <ocpRef> (railML® 2) the multiplicity is depicted with [2..2], which means, that1 KB (133 words) - 07:14, 15 November 2022
- 4) (deprecated with version 2.1 and 2.5) ref: reference is required because it's the purpose of the element ref: xs:IDREF; required Not yet described. /813 bytes (125 words) - 14:19, 22 November 2022
- TT:platformEdgeRef (section Position of platformEdgeRef in the XML-Tree / Position von platformEdgeRef im XML-Baum)unterschiedlicher Höhe, kann auch mehr als eine Haltekante befahren werden. ref: This refers to the id attribute of the associated platformEdge element. xs:anyAttribute:1 KB (160 words) - 20:37, 22 January 2024
- org/wiki/IS:baliseGroupRef" /> + </xs:annotation> + </xs:element> + </xs:sequence> <xs:attributeGroup ref="rail:aSignal" /> <xs:attributeGroup ref="rail:aOcpRef" /> </xs:extension>331 KB (27,016 words) - 10:56, 8 October 2021
- name="trainGroup B" parentRef="trg_2"> <trainRef ref="..." sequence="1" /> <trainRef ref="..." sequence="2" /> <trainRef ref="..." sequence="3" /> </trainGroup>9 KB (1,534 words) - 21:00, 22 January 2024
- system WGS84, because it is valid worldwide — see https://spatialreference.org/ref/epsg/wgs-84 (external link). The semantics for the list contents of the coord12 KB (1,472 words) - 19:28, 22 January 2024
- shuntingTime <platformEdgeRef> ref <serviceSectionRef> ref <annotationRef> operatingPeriodRef, ref <organizationalUnitBinding> <vehicleOperator> ref, xsi:type <customer>65 KB (2,931 words) - 12:19, 8 October 2021
- TRACK_COURSE: straight REF_SW: cte2 SW_COURSE: right REF2: csw1 REF3: ctb1 With the "Norwegian definition" we get REF1: cte2 TRACK_COURSE: right REF_SW: cte3 SW_COURSE:5 KB (1,094 words) - 19:21, 22 January 2024
- <vehicleOperator> ref, xsi:type <customer> ref, xsi:type <railwayUndertaking> ref, xsi:type <operationalUndertaking> ref, xsi:type <concessionaire> ref, xsi:type72 KB (3,235 words) - 11:59, 11 October 2021
- G::4326"/> <speed kind="announcement" switchable="false"/> <speedChangeRef ref="sc26301"/> </signal> <signal id="ssig263013" dir="up" pos="15613" absPos="106663"15 KB (2,400 words) - 19:48, 22 January 2024
- TT:operatingPeriodRef trainPart (section Position of operatingPeriodRef in the XML-Tree / Position von operatingPeriodRef im XML-Baum)Element <operatingPeriodRef> referenziert die zum trainPart gehörige Verkehrsperiode. Please, be aware of the semantic constraint(s)! ref: This refers to the2 KB (230 words) - 12:47, 14 May 2024
- replaces <ocpVis>.(introduced with version 2.5) ref: reference is required because it's the purpose of the element ref: xs:IDREF; required please refer to <IS959 bytes (106 words) - 19:40, 22 January 2024
- TT:annotationRef connection (section Position of annotationRef in the XML-Tree / Position von annotationRef im XML-Baum)operatingPeriodRef xs:IDREF, optional ref xs:IDREF, mandatory target: xs:string; either station or train priority: xs:integer operatingPeriodRef: tGenericRef (xs:IDREF);282 bytes (244 words) - 16:01, 28 March 2022
- values). down This goes opposite to up (decreasing relative position values). ref: This refers to the id attribute of the associated <track> element. xs:anyAttribute:995 bytes (166 words) - 12:08, 8 February 2024
- TT:serviceSectionRef (section Position of serviceSectionRef in the XML-Tree / Position von serviceSectionRef im XML-Baum)Haltekanten (platformEdges) auch mehrere solche Abschnitte referenziert werden. ref: This refers to the id attribute of the associated serviceSection element1 KB (154 words) - 20:41, 22 January 2024
- IS:trainProtectionElementGroupRef (section Position of IS:trainProtectionElementGroupRef in the XML-Tree / Position von IS:trainProtectionElementGroupRef im XML-Baum)connected to the signal's aspect None ref: reference is required because it's the purpose of the element ref: tGenericRef The following example (taken from2 KB (168 words) - 14:02, 13 March 2023
- <train> <trainPartSequence> <trainPartRef ref=’TP1.1’ position=’1’> <trainPartRef ref=’TP2.1’ position=’2’> <trainPartRef ref=’TP3.1’ position=’3’> </trainPartSequence>7 KB (948 words) - 18:45, 19 January 2024
- </xs:annotation> </xs:attribute> - <xs:attributeGroup ref="rail:anyAttribute" /> + <xs:attribute ref="xml:lang" /> </xs:complexType> <xs:complexType nam398 KB (34,006 words) - 10:54, 8 October 2021
- kind="execution" trainRelation="headOfTrain" switchable="false"> <speedChangeRef ref="tr03_sc02"/> </speed> </signal> The referenced <speedChange> element is4 KB (487 words) - 17:19, 19 January 2024
- RS:speedProfileRef (section Position of speedProfileRef in the XML-Tree / Position von speedProfileRef im XML-Baum)> in another file. ref xs:IDREF, optional name xs:string, optional Not yet described. / Noch nicht beschrieben. The attributes ref and name shall be used871 bytes (107 words) - 20:25, 25 November 2018
- IS:infraAttrGroupRef (section Position of IS:infraAttrGroupRef in the XML-Tree / Position von IS:infraAttrGroupRef im XML-Baum)IS:infraAttrGroupRef Parent: <infraAttrGroupRefs> Children: None [0..∞] Sub-element for a reference to instances of <infraAttributes>. ref: reference is399 bytes (47 words) - 18:53, 25 November 2018
- once leaving it.(introduced with version 2.5) ref: Reference a <genericArea>, comp. #473 ref: tGenericRef (xs:IDREF); required Not yet described. / Noch686 bytes (109 words) - 12:35, 24 March 2022
- IS:trackRef propEquipment (section Position of trackRef in the XML-Tree / Position von trackRef im XML-Baum)<trackRef>. sequence: This allows for sorting the referenced tracks. ref: This refers to the id attribute of the associated track element. xs:anyAttribute: This316 bytes (162 words) - 19:20, 25 November 2018
- consisting of letters, digits, points (.), dashes (-) or underscores (_) ref: tGenericRef (xs:IDREF); required Must point to the id of another <connection> Please211 bytes (148 words) - 16:28, 20 July 2022
- consisting of letters, digits, points (.), dashes (-) or underscores (_) ref: tGenericRef (xs:IDREF); required Must point to the id of another <connection> Please215 bytes (148 words) - 11:12, 22 January 2013
- IS:ocpRef Parent: <path> Children: None [2..2] This refers to the id attribute of the associated <ocp> element. ref: reference is required because it's428 bytes (52 words) - 14:07, 25 October 2022
- name="singleDate" type="xs:date" /> - <xs:attributeGroup ref="rail:aTimePeriod" /> - <xs:attributeGroup ref="rail:aPeriodTimeSpan" /> + <xs:attribute name="startDate"104 KB (9,170 words) - 10:56, 8 October 2021
- than in the running text. Footnotes can be generated with <ref> tags. A documentation of <ref> tags can be found at mediawiki.org (external link). As to10 bytes (1,478 words) - 18:13, 5 March 2021
- TT:annotationRef trainPart (section Position of annotationRef in the XML-Tree / Position von annotationRef im XML-Baum)operatingPeriodRef xs:IDREF, optional ref xs:IDREF, mandatory target: xs:string; either station or train priority: xs:integer operatingPeriodRef: tGenericRef (xs:IDREF);252 bytes (234 words) - 16:04, 28 March 2022
- TT:annotationRef stopDescription (section Position of annotationRef in the XML-Tree / Position von annotationRef im XML-Baum)operatingPeriodRef xs:IDREF, optional ref xs:IDREF, mandatory target: xs:string; either station or train priority: xs:integer operatingPeriodRef: tGenericRef (xs:IDREF);264 bytes (234 words) - 16:04, 28 March 2022
- version 2.4) (deprecated with version 2.1) ref: reference is required because it's the purpose of the element ref: xs:IDREF; required please refer to <IS795 bytes (109 words) - 13:07, 10 May 2023
- referenced trains. This "counter" defines the chronological order during a day. ref: This refers to the id attribute of the associated train element. xs:anyAttribute:1 KB (146 words) - 18:13, 1 December 2021
- IS:speedChangeRef (section Position of IS:speedChangeRef in the XML-Tree / Position von IS:speedChangeRef im XML-Baum)IS:speedChangeRef Parent: <speed_signal> Children: None [0..∞] Reference to a speed change. ref: reference is required because it's the purpose of the349 bytes (44 words) - 23:28, 25 November 2018
- <xs:element name="metadata" type="dc:elementContainer" minOccurs="0" /> <xs:element ref="rail:infrastructure" minOccurs="0" /> example: <xs:attributeGroup name="aPlaces">5 KB (331 words) - 10:51, 14 November 2023
- RS:categoryRef (section Position of categoryRef in the XML-Tree / Position von categoryRef im XML-Baum)non-railML® attributes in a foreign namespace. How to use it? ref xs:IDREF, mandatory The element <categoryRef> may be used several times. Not yet described. / Noch1 KB (154 words) - 15:58, 15 November 2021
- IS:baliseGroupRef (section Position of IS:baliseGroupRef in the XML-Tree / Position von IS:baliseGroupRef im XML-Baum)IS:baliseGroupRef Parent: IS:signal Children: None [0..∞] Sub-element for a reference to a baliseGroup, which is connected to the signal's aspect ref: reference386 bytes (52 words) - 23:28, 2 July 2021
- the signal to be switchable or fixed (panel) ref: reference to a line switchable: xs:boolean ref: tGenericRef Not yet described. / Noch nicht beschrieben383 bytes (54 words) - 23:23, 25 November 2018
- IS:trainProtectionElementRef (section Position of IS:trainProtectionElementRef in the XML-Tree / Position von IS:trainProtectionElementRef im XML-Baum)<trainProtectionElementRef> addresses the trainProtectionElements belonging to the group. ref: reference is required because it's the purpose of the element ref: xs:IDREF595 bytes (66 words) - 13:29, 25 October 2022
- IS:ocpRef controller (section Position of IS:ocpRef in the XML-Tree / Position von IS:ocpRef im XML-Baum)referenced from more than one controller. ref: reference is required because it's the purpose of the element sequence: ref: xs:IDREF sequence: xs:positiveInteger509 bytes (68 words) - 10:51, 11 December 2018
- with version 2.5) {{{attributes}}} ref: Reference is required because it's the purpose of the element. ref: tGenericRef (xs:IDREF); required Not yet described133 bytes (54 words) - 10:53, 15 April 2024
- version 2.4) (deprecated with version 2.1) ref: reference is required because it's the purpose of the element ref: xs:IDREF; required Not yet described. /473 bytes (81 words) - 19:05, 13 December 2021
- TT:speedProfileRef (section Position of speedProfileRef in the XML-Tree / Position von speedProfileRef im XML-Baum)wird. Im Ausnahmefall, kann auch mehr als ein Geschwindigkeitsprofil gelten. ref: This refers to the id attribute of the associated speedProfile element. xs:anyAttribute:978 bytes (128 words) - 20:44, 22 January 2024
- IS:trackRef locallyControlledArea (section Position of trackRef in the XML-Tree / Position von trackRef im XML-Baum)referenced using <trackRef>. sequence: This allows for sorting the referenced tracks. ref: This refers to the id attribute of the associated track element. xs:anyAttribute:332 bytes (162 words) - 19:04, 25 November 2018
- IS:signalRef stopPost (section Position of signalRef in the XML-Tree / Position von signalRef im XML-Baum)sequence: This allows for sorting the referenced signals. ref: This refers to the id attribute of the associated signal element. xs:anyAttribute: This provides286 bytes (162 words) - 23:32, 25 November 2018
- IS:signalRef signalGroup (section Position of signalRef in the XML-Tree / Position von signalRef im XML-Baum)sequence: This allows for sorting the referenced signals. ref: This refers to the id attribute of the associated signal element. xs:anyAttribute: This289 bytes (162 words) - 19:40, 25 November 2018
- Bahnübergangs. ref: reference to a level crossing switchable: xs:boolean, optional type: enumeration (xs:string), optional ref: tGenericRef, optional Not2 KB (255 words) - 17:39, 1 August 2023
- version 2.4) (deprecated with version 2.1) ref: reference is required because it's the purpose of the element ref: xs:IDREF; required please refer to <IS1 KB (157 words) - 17:44, 19 January 2024
- IS:controllerRef locallyControlledArea (section Position of <controllerRef> in the XML-Tree / Position von <controllerRef> im XML-Baum)with version 2.4) sequence: ref: reference is required because it's the purpose of the element sequence: xs:positiveInteger ref: xs:IDREF Not yet described515 bytes (58 words) - 19:04, 25 November 2018
- with version 2.5) {{{attributes}}} ref: Reference is required because it's the purpose of the element. ref: tGenericRef (xs:IDREF); required Not yet described126 bytes (54 words) - 22:19, 29 November 2021
- with version 2.5) {{{attributes}}} ref: Reference is required because it's the purpose of the element. ref: tGenericRef (xs:IDREF); required Not yet described89 bytes (50 words) - 22:57, 29 November 2021
- with version 2.5) {{{attributes}}} ref: Reference is required because it's the purpose of the element. ref: tGenericRef (xs:IDREF); required Not yet described141 bytes (55 words) - 22:13, 29 November 2021
- TT:blockPartRef (section Position of blockPartRef in the XML-Tree / Position von blockPartRef im XML-Baum)dem Element <blockPartRef> werden blockParts referenziert, um sie als Einzelaufgaben zu einem "Dienst" zu gruppieren. ref: This refers to the id attribute626 bytes (85 words) - 22:05, 25 November 2018
- IS:controllerRef ocp (section Position of <controllerRef> in the XML-Tree / Position von <controllerRef> im XML-Baum)means master controller. ref: reference is required because it's the purpose of the element sequence: xs:positiveInteger ref: xs:IDREF Not yet described516 bytes (68 words) - 12:51, 3 February 2023
- sequence="1"> <trainPartRef ref="tp2_1"/> </trainPartSequence> <!-- From Bf_C to Bf_D --> <trainPartSequence sequence="2"> <trainPartRef ref="tp2_2" position="1"/>8 KB (1,098 words) - 18:21, 19 January 2024
- sequence: This allows for sorting the referenced balises. ref: This refers to the id attribute of the associated balise element. sequence xs:positiveInteger1 KB (144 words) - 23:12, 25 November 2018
- same constraint should be deployed for the tracks in the opposite direction. ref: This refers to the id attribute of the associated track element. xs:anyAttribute:585 bytes (208 words) - 08:14, 31 May 2023
- TT:operatingPeriodRef replacementOf (section Position of <operatingPeriodRef> in the XML-Tree / Position von <operatingPeriodRef> im XML-Baum)(introduced with version 2.4) Spezifiziert die Betriebstage eines Ersatzes ref: This refers to the id attribute of the associated <operatingPeriod> element978 bytes (162 words) - 14:11, 10 August 2020
- from the area to an element bounding this area.(introduced with version 2.5) ref: Reference is required because it's the purpose of the element. xs:anyAttribute:559 bytes (89 words) - 14:05, 25 October 2022
- <trackRef ref="tr01"/> <trackRef ref="tr02"/> <trackRef ref="tr03"/> <trackRef ref="tr04"/> <trackRef ref="tr05"/> <trackRef ref="tr06"/> <trackRef ref="tr07"/>20 KB (1,833 words) - 15:44, 10 October 2023
- consisting of letters, digits, points (.), dashes (-) or underscores (_) ref: tGenericRef (xs:IDREF); required Must point to the id of another <connection> orientation:2 KB (699 words) - 19:20, 22 January 2024
- <trackRef ref="yardTrack01" sequence="1"/> <trackRef ref="segmentTrack01" sequence="2"/> <trackRef ref="yardTrack04" sequence="3"/> <trackRef ref="yardTrack05"7 KB (470 words) - 14:51, 25 September 2023
- <operatingPeriodRef ref='opp_1'/> <ocpsTT> <ocpTT ocpRef='ocp_DNKW_A' ocpType='pass'> <times scope='scheduled' departure='23:55:35'/> </ocpTT> <ocpTT ocpRef='ocp_DNKO'19 KB (2,347 words) - 18:40, 19 January 2024
- <ocpTT ocpRef="_OAR" trackRef="_tr"> <times scope="scheduled" arrival="10:59:00" departure="11:04:00"/> <stopDescription> <platformEdgeRef ref="_pe" />12 KB (1,414 words) - 18:28, 19 January 2024
- sequence="1"> <!-- Berlin to Hannover --> <trainPartRef position="1" ref="CNL_242_1"/> <trainPartRef position="2" ref="CNL_1242_1"/> </trainPartSequence> <trainPartSequence7 KB (964 words) - 21:04, 22 January 2024
- IS:trackRef trackLocation (section Position of IS:trackRef trackLocation in the XML-Tree / Position von IS:trackRef trackLocation im XML-Baum)referenced using <trackRef>.(introduced with version 2.5) sequence: This allows for sorting the referenced tracks. ref: This refers to the id attribute of the113 bytes (168 words) - 11:48, 24 October 2022
- <xs:field xpath="@id" /> </xs:key> Keyrefs have to be defined for all ref and *Ref attributes. They should all refer to a certain element's id attribute9 KB (1,033 words) - 17:59, 19 January 2024
- TT:announcementRef connection (section Position of announcementRef in the XML-Tree / Position von announcementRef im XML-Baum)is determined by the priority (highest priority first). ref xs:IDREF, mandatory operatingPeriodRef xs:IDREF, optional target: xs:string; either station or2 KB (306 words) - 16:41, 24 February 2022
- TT:announcementRef trainPart (section Position of announcementRef in the XML-Tree / Position von announcementRef im XML-Baum)is determined by the priority (highest priority first). ref xs:IDREF, mandatory operatingPeriodRef xs:IDREF, optional target: xs:string; either station or2 KB (286 words) - 16:26, 24 February 2022
- of xs:string, tOtherEnumerationValue); arrival/departure); optional ref: tGenericRef (xs:IDREF); required Not yet described. / Noch nicht beschrieben. Not187 bytes (59 words) - 19:42, 3 April 2022
- revision. (introduced with version 2.5) ref: This refers to the id attribute of the associated element. ref: tGenericRef (xs:IDREF); required Not yet described277 bytes (54 words) - 17:36, 3 April 2022
- ref: Reference is required because it's the purpose of the element. ref: xs:IDREF, required Not yet described. / Noch nicht beschrieben. Not yet described361 bytes (52 words) - 15:48, 8 October 2021
- TT:patternTrainPartRef (section Position of patternTrainPartRef in the XML-Tree / Position von patternTrainPartRef im XML-Baum)(introduced with version 2.5) ref: reference is required because it's the purpose of the element position: ref: tGenericRef (xs:IDREF); required position:693 bytes (82 words) - 17:45, 12 September 2022
- IS:trackSectionRef (section Position of IS:trackSectionRef in the XML-Tree / Position von IS:trackSectionRef im XML-Baum)track sections included in the <releaseGroup>.(introduced with version 2.5) ref The reference to the track section within this group. flankProtection Set600 bytes (86 words) - 10:23, 28 March 2023
- 2022-12-15 2022-12-15 If the trainPartRef attribute is given, then there must also be a trainRef attribute, and the trainPartRef attribute must point to a train10 bytes (579 words) - 15:58, 18 May 2020
- re-used across the sub-schemas, e.g. "geoCoord", "valueTable", "efficiency", "*Ref". This section does not cover these re-used elements. See next section. If15 KB (1,952 words) - 18:11, 15 April 2024
- point for non-railML® attributes in a foreign namespace. How to use it? ref: tGenericRef (xs:IDREF); required hasKeyByDefault: xs:boolean; optional any: xs:any;481 bytes (80 words) - 15:28, 23 May 2022
- this train part. However, it is possible to follow the attribute <trainPartRef>.ref from any train to find out which one (or more) refers to the current train12 KB (1,930 words) - 15:44, 13 May 2024
- id="tr01_te"> <connection ref="tr03_c03" id="tr01_c01"/> </trackEnd> <crossSections> <crossSection id="tr01_cs01" name="Gleis 1" xml:lang="de" ocpRef="ocp01" pos="3002 KB (159 words) - 14:55, 10 October 2023
- id="tr01_te"> <connection ref="tr03_c03" id="tr01_c01"/> </trackEnd> <crossSections> <crossSection id="tr01_cs01" name="Gleis 1" xml:lang="de" ocpRef="ocp01" pos="3002 KB (159 words) - 14:33, 10 October 2023
- TT:announcementRef stopDescription (section Position of announcementRef in the XML-Tree / Position von announcementRef im XML-Baum)is determined by the priority (highest priority first). ref xs:IDREF, mandatory operatingPeriodRef xs:IDREF, optional target: xs:string; either station or2 KB (286 words) - 16:35, 24 February 2022
- id="tr01_te"> <connection ref="tr03_c03" id="tr01_c01"/> </trackEnd> <crossSections> <crossSection id="tr01_cs01" name="Gleis 1" xml:lang="de" ocpRef="ocp01" pos="3002 KB (170 words) - 14:54, 25 September 2023
- id="tr01_te"> <connection ref="tr03_c03" id="tr01_c01"/> </trackEnd> <crossSections> <crossSection id="tr01_cs01" name="Gleis 1" xml:lang="de" ocpRef="ocp01" pos="3002 KB (175 words) - 14:32, 10 October 2023
- sequence="1"> <trainPartRef ref="trainPart1001"/> </trainPartSequence> <replacements> <replacementOf> <operatingPeriodRef ref="operating-period-KW47-MoFr-18"23 KB (104 words) - 11:10, 3 May 2022
- categoryRef="cat_11"> <!-- empty run to stable --> <trainPartRef ref="tp_3" position="1"/> </trainPartSequence> </train> The attribute categoryRef at <train>15 KB (1,905 words) - 11:46, 23 March 2023
- code="5600" infrastructureManagerRef="ima01" name="Bahnstrecke München Ost Pbf – Simbach (Inn) (DB-Grenze)"> <trackRef ref="tr01"/> </line> <line id="lin02"6 KB (516 words) - 11:57, 26 April 2024
- wird genutzt um einen <railwayUndertaking> der <metadata> zu referenzieren. ref: This refers to the id attribute of the associated railwayUndertaking element759 bytes (82 words) - 13:28, 10 August 2020
- element allows for referencing a <railwayUndertaking> within the <metadata>. ref: This refers to the id attribute of the associated customer element. xs:anyAttribute:589 bytes (69 words) - 09:56, 11 May 2023