Search results

Jump to navigation Jump to search

  • 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
View ( | ) (20 | 50 | 100 | 250 | 500)
Retrieved from "https://wiki2.railml.org/wiki/Special:Search"