Search results

Jump to navigation Jump to search

  • TT:formationInformation
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further
    523 bytes (38 words) - 21:56, 25 April 2022
  • UC:Use cases
    to use cases. CO Use Cases – IL Use Cases – IS Use Cases – RS Use Cases – TT Use Cases View/edit list on the separate source page   If you want to reactivate
    7 KB (287 words) - 15:43, 8 April 2024
  • TT:activityTrainReverse
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further
    523 bytes (38 words) - 21:55, 25 April 2022
  • TT:activityRollingStock
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further
    523 bytes (38 words) - 21:55, 25 April 2022
  • TT:activityLoad
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further
    515 bytes (38 words) - 21:55, 25 April 2022
  • TT:activityOther
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further
    516 bytes (38 words) - 21:55, 25 April 2022
  • TT:operationalTrainSectionPart
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further
    1 KB (91 words) - 10:22, 13 October 2022
  • TT:activityTripDependency
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further
    525 bytes (38 words) - 21:55, 25 April 2022
  • TT:activityCrewDependency
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further
    525 bytes (38 words) - 21:55, 25 April 2022
  • UC:TT:ExchangeOfFormationData (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)
    to define a (potentially different) formation for a train part on each of its operating days. The assigned formation must match the restrictions of the
    6 KB (688 words) - 13:26, 13 March 2023
  • Main Page (section Timetable and Rostering (TT))
    use: Infrastructure (IS) and Interlocking (IL). The Timetable and Rostering (TT) and Rollingstock (RS) subschemas are in active development and can be obtained
    10 KB (1,041 words) - 10:56, 2 May 2024
  • UC:TT:FGIInTrain (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)
    referenced: from <ocpTT>.ocpRef to <ocp>.id (mandatory) Rolling stock is referenced: from <formationTT>.formationRef to <formation>.id (optional) from <rostering>
    9 KB (677 words) - 18:10, 27 June 2022
  • UC:TT:ATimetableForACompetition (category Use case (TT))
    <rollingstock> is referenced from <formationTT>.formationRef to <formation>.id (optional) from <rostering>.formationRef to <formation>.id (optional) from <rostering>
    16 KB (1,903 words) - 13:27, 13 March 2023
  • Dev:Changes/3.2
    stop TT:feeder TT:followupSection TT:followupSections TT:formationInformation TT:identifier TT:identifier:range TT:identifiers TT:isCancelled TT:isCommercial
    3 KB (756 words) - 14:47, 27 June 2022
  • UC:TT:RunTimeCalculationInput (category Use case (TT))
    focused on formations. Such formations are considered to be a sequence of vehicles, at least one vehicle. Typically, vehicles of such formations are not specific
    6 KB (858 words) - 12:09, 25 March 2024
  • UC:TT:SlotOrdering (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)
    Infrastructure <ocpTT> Ordered stops Rolling stock <formationTT> Loco types Weight Length Maximum speed Infrastructure restrictions As a minimum the <ocpTT> elements
    2 KB (273 words) - 13:26, 13 March 2023
  • TT:formationInformation/3.2
    Automatic Schemaexport for Element formationInformation
    2 KB (5 words) - 12:43, 8 February 2024
  • UC:TT:TrafficManagementPlan (category Use case (TT))
    <trainPartSequence> <trainPartRef> <trainPart> <formationTT> <operatingPeriodRef> <ocpsTT> <sectionTT> <runTimes> <connections> <stopDescription> <stopTimes>
    3 KB (270 words) - 15:11, 27 June 2022
  • UC:TT:TimetableInformation (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)
    infrastructure: <operationalPoint>, <platform>, <platformEdge> rolling stock: <formation> (?) interlocking: - This section serves to specify the required data regarding
    5 KB (751 words) - 13:28, 13 March 2023
  • TT:activityTrainReverse/3.2
    Autoexport from the XML-Schema for element TT:activityTrainReverse of railML® version 3.2 UML-visualization of TT Documentation Allows to specify that the
    5 KB (5 words) - 21:55, 25 April 2022
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)
Retrieved from "https://wiki3.railml.org/wiki/Special:Search"