Search results

Jump to navigation Jump to search

  • CO:designator (redirect from CO:designator vehicleOperator)
    <operationalUndertaking>, <project>, <railwayUndertaking>, <vehicleManufacturer>, <vehicleOperator>, <vehicleOwner> Children: None [0..∞] FIXME(introduced with version
    480 bytes (277 words) - 13:54, 14 May 2024
  • TT:trainPart (section Declaring vehicles as 'closed' (not accessable for public))
    element. operator (deprecated with version 2.3): This is the train operator. It is recommended to use <organizationalUnitBinding> instead of operator. cancellation
    12 KB (1,930 words) - 15:44, 13 May 2024
  • CO:vehicleOperator (section Position of vehicleOperator in the XML-Tree / Position von vehicleOperator im XML-Baum)
    optional The Element <vehicleOperator> may occur several times. None. This element should only be used, if the vehicle operator differs from the <railwayUndertaking>
    2 KB (525 words) - 19:49, 5 January 2024
  • RS:classification
    <manufacturer vehicleManufacturerRef='vm_3' manufacturer-Type='ME26'/> <operator vehicleOperatorRef='vop_1' operatorClass='Di6'/> <operator vehicleOperatorRef='vop_2'
    1 KB (146 words) - 18:24, 3 April 2022
  • RS:operator (section Position of operator in the XML-Tree / Position von operator im XML-Baum)
    <manufacturer vehicleManufacturerRef='vm_3' manufacturer-Type='ME26'/> <operator vehicleOperatorRef='vop_1' operatorClass='Di6'/> <operator vehicleOperatorRef='vop_2'
    3 KB (336 words) - 13:37, 14 May 2024
  • TT:vehicleOperator
    Element <vehicleOperator>, child of <organizationalUnitBinding trainPart> Element <vehicleOperator>, child of <organizationalUnitBinding trainNumber> Element
    230 bytes (18 words) - 09:22, 6 June 2017
  • CO:additionalName vehicleOperator
    additionalName   Parent: <vehicleOperator> Children: None [0..∞] The element <additionalName> provides additional names with descriptions in other languages
    144 bytes (240 words) - 14:52, 16 January 2014
  • RS:manufacturer
    <manufacturer vehicleManufacturerRef='vm_3' manufacturer-Type='ME26'/> <operator vehicleOperatorRef='vop_1' operatorClass='Di6'/> <operator vehicleOperatorRef='vop_2'
    2 KB (222 words) - 06:54, 26 November 2020
  • Dev:Semantic Constraints
    if both are given. Must not overlap with other <operator> validity periods of the same enclosing <vehicle>/<classification>. <RS:owner> (introduced with
    10 bytes (579 words) - 15:58, 18 May 2020
  • RS:vehicle (section Position of vehicle in the XML-Tree / Position von vehicle im XML-Baum)
    only one vehicle of "type 75". Vehicle class vs. specific vehicle In case a single (specific) vehicle shall be described there are two <vehicle> elements
    10 KB (1,797 words) - 13:09, 24 January 2022
  • CO:organizationalUnits
    Parent: <metadata> Children: <infrastructureManager>, <vehicleManufacturer>, <vehicleOperator>, <vehicleOwner> (introduced with version 2.5), <customer>, <railwayUndertaking>
    2 KB (192 words) - 14:04, 12 December 2022
  • Dev:XMLtree
    serialNumber, vehicleManufacturerRef <owner> endDate, ownerClass, startDate, vehicleOwnerRef <operator> endDate, operatorClass, operatorName, startDate
    112 KB (4,754 words) - 18:02, 3 April 2022
  • TT:organizationalUnitBinding trainPart
    <organizationalUnitBinding>   Parent: <trainPart>, <patternTrainPart> Children: <vehicleOperator>, <customer>, <railwayUndertaking>, <operationalUndertaking>, <concessionaire>
    967 bytes (68 words) - 19:21, 9 February 2022
  • TT:organizationalUnitBinding trainNumber
    TT:organizationalUnitBinding trainNumber   Parent: <trainNumber> Children: <vehicleOperator>, <customer>, <railwayUndertaking>, <operationalUndertaking>, <concessionaire>
    776 bytes (60 words) - 09:51, 11 May 2023
  • RS:vehicleIdentification (section Position of vehicleIdentification in the XML-Tree / Position von vehicleIdentification im XML-Baum)
    vehicleIdentification   Parent: <operator> Children: Not yet described. / Noch nicht beschrieben. [0..1] The element <vehicleIdentification> (introduced
    2 KB (211 words) - 21:02, 25 November 2018
  • TT:vehicleOperator organizationalUnitBinding trainPart (section Position of vehicleOperator in the XML-Tree / Position von vehicleOperator im XML-Baum)
    vehicleOperator   Parent: <organizationalUnitBinding> Children: None [0..1] The element <vehicleOperator> allows for referencing a <vehicleOperator> within
    741 bytes (82 words) - 13:28, 10 August 2020
  • TT:vehicleOperator organizationalUnitBinding trainNumber (section Position of vehicleOperator in the XML-Tree / Position von vehicleOperator im XML-Baum)
    vehicleOperator   Parent: <organizationalUnitBinding> Children: None [0..1] This element allows for referencing a <vehicleOperator> within the <metadata>
    534 bytes (69 words) - 09:53, 11 May 2023
  • Dev:changes/2.3 (section Mark trainPart/@operator as deprecated)
    New attribute(s): /rollingstock/vehicles/vehicle/wagon/passenger/places/@tapTsiType9039Code /rollingstock/vehicles/vehicle/wagon/passenger/service/@tapTsiType7161Code
    20 KB (238 words) - 18:57, 22 January 2024
  • CO:additionalName
    CO:additionalName revision CO:additionalName vehicleManufacturer CO:additionalName vehicleOperator CO:additionalName vehicleOwner
    16 bytes (32 words) - 17:23, 21 March 2022
  • Dev:changes/2.3/diff
    <validFor> - <vehicleSystem>Indusi54</vehicleSystem> - <vehicleSystem>Indusi60</vehicleSystem> - <vehicleSystem>Indusi60R</vehicleSystem> - <vehicleSystem>PZ80</vehicleSystem>
    108 KB (9,484 words) - 10:56, 8 October 2021
  • Dev:changes/2.2/diff
    <validFor> + <vehicleSystem>Indusi54</vehicleSystem> + <vehicleSystem>Indusi60</vehicleSystem> + <vehicleSystem>Indusi60R</vehicleSystem> + <vehicleSystem>PZ80</vehicleSystem>
    331 KB (27,016 words) - 10:56, 8 October 2021
  • Dev:XMLtree/2.3
    manufacturerType, serialNumber, vehicleManufacturerRef <operator> endDate, operatorClass, operatorName, startDate, vehicleOperatorRef <vehicleIdentification> countryCode
    65 KB (2,931 words) - 12:19, 8 October 2021
  • TT:additionalName
    trainGroup TT:additionalName trainPart TT:additionalName vehicleManufacturer TT:additionalName vehicleOperator
    16 bytes (48 words) - 17:24, 21 March 2022
  • Dev:XMLtree/2.4
    manufacturerType, serialNumber, vehicleManufacturerRef <operator> endDate, operatorClass, operatorName, startDate, vehicleOperatorRef <vehicleIdentification> countryCode
    72 KB (3,235 words) - 11:59, 11 October 2021
  • TT:additionalName vehicleOperator
    additionalName   Parent: <vehicleOperator> Children: None [0..∞] The element <additionalName> provides additional names with descriptions in other languages
    144 bytes (240 words) - 16:41, 16 January 2014
  • Dev:changes/2.1/diff
    name="vehicle-vehicleFamilyRefKey" refer="rail:vehicleKey"> + <xs:selector xpath=".//rail:vehicles/rail:vehicle" /> + <xs:field xpath="@vehicleFamilyRef"
    531 KB (37,474 words) - 10:55, 8 October 2021
  • Dev:changes/2.4 (section New attribute <crossSection>@ocpCenterSide to indicate the direction in which the train driver has to look to see the (virtual) operator)
    Fact: Change <vehicleBrakeOperation> to optional [0..*] to maintain backwards compatibility Updated Elements: <vehicleBrakes> <vehicleBrakeOperations>
    23 KB (104 words) - 11:10, 3 May 2022
  • Dev:Coding XML Components
    <xs:element name="vehicles" type="rail:eVehicles" minOccurs="0"> <xs:annotation> <xs:documentation>container for single vehicle data or vehicle family data</xs:documentation>
    9 KB (1,033 words) - 17:59, 19 January 2024
  • Dev:Registers
    <operationalUndertaking> <project>. <railwayUndertaking> <vehicleManufacturer> <vehicleOperator> <vehicleOwner> In railML® 3, the designator can be added to any
    10 bytes (721 words) - 21:27, 23 January 2020
  • Dev:changes/2.5/diff
    + <!-- vehicleOperator reference in timetable subschema --> + <xs:keyref name="vehicleOperator-vehicleOperatorKeyref" refer="rail:vehicleOperatorKey"> +
    398 KB (34,006 words) - 10:54, 8 October 2021
  • Dev:changes/2.2 (section operator)
    infrastructureManager-lineKeyref vehicleManufacturerKey vehicleManufacturer-manufacturerKeyref vehicleOperatorKey vehicleOperator-operatorKeyref customerKey customer-customerKeyref
    36 KB (103 words) - 13:54, 21 February 2022
  • UC:TT:ATimetableForACompetition
    not recommended. <vehicle>s and <formation>s If the supply of vehicles is component of the competition, often there are neither vehicles nor formations given
    10 bytes (1,903 words) - 16:12, 3 February 2020
  • UC:TT:FGIInTrain
    <rostering>.formationRef to <formation>.id (optional) from <rostering>.vehicleRef to <vehicle>.id (optional) daily sometimes possibly several times on a day (short-term
    10 bytes (677 words) - 16:12, 3 February 2020
  • UC:RS:OperationalSimulation
    (orderNumber, vehicleRef, vehicleCount) vehicle (ID, name, length, speed, bruttoWeight, tareWeight/nettoWeight, bruttoAdhesion), engine (propulsion-ID, rotationMassFactor
    10 bytes (146 words) - 16:12, 3 February 2020
  • UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings (section vehicle working and rostering data)
    Concatenation of vehicle workings to multi-day sequences of trains served by the same (abstract) vehicle depot runs vehicle standbys vehicle accounting for
    10 bytes (355 words) - 16:12, 3 February 2020
  • UC:RS:TractionPowerSupplySimulation
    elements for motored vehicles: propulsion (voltage, frequency, power, tractiveCurrent[valueTable], totalTractEfficiency/tractiveVehicleEfficiency[valueTable]
    10 bytes (236 words) - 16:12, 3 February 2020
  • Dev:changes/2.5 (section <organizationalUnits> has been extended with child <vehicleOwner>)
    <infrastructureManager>, <operationalUndertaking>, <railwayUndertaking>, <vehicleManufacturer>, <vehicleOperator>
    29 KB (97 words) - 19:00, 22 January 2024
  • Dev:changes/2.4/diff
    <xs:complexContent> <xs:extension base="rail:tOperator"> <xs:sequence> - <xs:element name="vehicleIdentification" type="rail:tVehicleIdentification" minOccurs="0" maxOccurs="1">
    104 KB (9,170 words) - 10:56, 8 October 2021
  • UC:TT:LongTermStrategicTimetabling
    system-> consumers of study information (i.e. authorities) VLTP system-> VLTP vehicle rostering The frequency of this data flow is not defined by any process
    10 bytes (523 words) - 16:12, 3 February 2020
  • TT:UC:Ausschreibungsfahrplan
    not recommended. <vehicle>s and <formation>s If the supply of vehicles is component of the competition, often there are neither vehicles nor formations given
    16 KB (2,372 words) - 16:07, 12 November 2021
  • railML 2 Wiki:Missing elements/2.5
    CO:designator vehicleOwner CO:vehicleOperator CO:additionalName vehicleOperator CO:designator vehicleOperator CO:customer CO:additionalName customer CO:designator
    58 KB (3,897 words) - 17:57, 3 April 2022
  • User:RailML Coord Documentation/TT:trainPart (section Declaring vehicles as 'closed' (not accessable for public))
    element. operator (deprecated with version 2.3): This is the train operator. It is recommended to use <organizationalUnitBinding> instead of operator. cancellation
    9 bytes (1,930 words) - 14:49, 16 January 2023
  • User:RailML Coord Documentation/RS:vehicle (section Position of vehicle in the XML-Tree / Position von vehicle im XML-Baum)
    only one vehicle of "type 75". Vehicle class vs. specific vehicle In case a single (specific) vehicle shall be described there are two <vehicle> elements
    28 bytes (1,797 words) - 14:49, 16 January 2023
  • User:Dirk Bräuer
    not recommended. <vehicle>s and <formation>s If the supply of vehicles is component of the competition, often there are neither vehicles nor formations given
    17 KB (1,966 words) - 01:42, 15 March 2015
  • Template:Table/Dev:Semantic Constraints
    if both are given. Must not overlap with other <operator> validity periods of the same enclosing <vehicle>/<classification>. <RS:owner> (introduced with
    18 KB (3 words) - 14:06, 14 May 2024
Retrieved from "https://wiki2.railml.org/wiki/Special:Search"