Search results
Jump to navigation
Jump to search
- TT:customer organizationalUnitBinding trainPart (section Position of customer in the XML-Tree / Position von customer im XML-Baum)customer Parent: <organizationalUnitBinding> Children: None [0..1] The element <customer> allows for referencing a <customer> within the <metadata>.699 bytes (82 words) - 13:28, 10 August 2020
- TT:customer organizationalUnitBinding trainNumber (section Position of <customer> in the XML-Tree / Position von <customer> im XML-Baum)<customer> Parent: <organizationalUnitBinding> Children: ’’None’’ [0..1] This element allows for referencing a <customer> within the <metadata>. ref:569 bytes (69 words) - 09:55, 11 May 2023
- Element <customer>, child of <organizationalUnitBinding trainPart> Element <customer>, child of <organizationalUnitBinding trainNumber> Element <customer>, child209 bytes (18 words) - 09:21, 6 June 2017
- TT:organizationalUnitBinding trainPart (section Position of <organizationalUnitBinding> in the XML-Tree / Position von <organizationalUnitBinding> im XML-Baum)1] (introduced with version 2.2) The element organizationalUnitBinding describes what organizational units are responsible for this trainPart. (introduced967 bytes (68 words) - 19:21, 9 February 2022
- TT:organizationalUnitBinding trainNumber (section Position of TT:organizationalUnitBinding trainNumber in the XML-Tree / Position von TT:organizationalUnitBinding trainNumber im XML-Baum)TT:organizationalUnitBinding trainNumber Parent: <trainNumber> Children: <vehicleOperator>, <customer>, <railwayUndertaking>, <operationalUndertaking>776 bytes (60 words) - 09:51, 11 May 2023
- zusammengefasst werden können. organizationalUnitRef: (introduced with version 2.5) Reference to any organization below <organizationalUnits> (<infrastructureManager>12 KB (1,737 words) - 11:19, 18 March 2024
- "extensions":["persist"]} <railml> version, xsi:schemaLocation <metadata> <organizationalUnits> <infrastructureManager> code, description, id, name, rail:lang <additionalName>112 KB (4,754 words) - 18:02, 3 April 2022
- <concessionaire> Parent: <organizationalUnitBinding> Children: ’’None’’ [0..1] This element allows for referencing a <concessionaire> within the <metadata>581 bytes (69 words) - 09:58, 11 May 2023
- <contractor> Parent: <organizationalUnitBinding> Children: ’’None’’ [0..1] This element allows for referencing a <contractor> within the <metadata>.573 bytes (69 words) - 09:59, 11 May 2023
- <railwayUndertaking> Parent: <organizationalUnitBinding> Children: ’’None’’ [0..1] This element allows for referencing a <railwayUndertaking> within589 bytes (69 words) - 09:56, 11 May 2023
- <operationalUndertaking> Parent: <organizationalUnitBinding> Children: ’’None’’ [0..1] This element allows for referencing an <operationalUndertaking>598 bytes (69 words) - 09:57, 11 May 2023
- attribute @organizationalUnitRef was added in order to differentiate between categories of the same name that are related to different organizationalUnits and29 KB (97 words) - 19:00, 22 January 2024
- name="customerKey"> - <xs:selector xpath=".//rail:organizationalUnits/rail:customer" /> + <xs:selector xpath="./rail:metadata/rail:organizationalUnits/rail:customer"398 KB (34,006 words) - 10:54, 8 October 2021
- </xs:annotation> + <xs:sequence> + <xs:element name="organizationalUnits" type="rail:tOrganizationalUnits" minOccurs="0"> + <xs:annotation> + <xs:documentation>Container331 KB (27,016 words) - 10:56, 8 October 2021
- "openlevels":2} <railml> version, xsi:schemaLocation <metadata> <organizationalUnits> <infrastructureManager> code, description, id, name, rail:lang <additionalName>65 KB (2,931 words) - 12:19, 8 October 2021
- "openlevels":2} <railml> version, xsi:schemaLocation <metadata> <organizationalUnits> <infrastructureManager> code, description, id, name, rail:lang <additionalName>72 KB (3,235 words) - 11:59, 11 October 2021
- Dev:changes/2.2 (section organizationalUnits)Fact: <organizationalUnits> and its children have been introduced. Related Development Tickets:36 KB (103 words) - 13:54, 21 February 2022
- UC:TT:TrafficManagementPlan (category Use case (TT))<trainPart> <formationTT> <operatingPeriodRef> <ocpsTT> <sectionTT> <runTimes> <connections> <stopDescription> <stopTimes> <organizationalUnitBinding> <category>10 bytes (1,739 words) - 16:12, 3 February 2020
- patternTrainPart TT:formationTT TT:ocpsTT TT:ocpTT TT:times TT:sectionTT TT:trackRef sectionTT_ocpTT TT:runTimes sectionTT_ocpTT TT:alternativeSectionsTT TT:alternativeSectionTT58 KB (3,897 words) - 17:57, 3 April 2022