Search results

Jump to navigation Jump to search

  • 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
  • UC:Use cases
    cases. While the emphasis of the railML®-wiki lies in documenting single elements in a bottom-up approach, we also try to help users to capture the concepts
    7 KB (287 words) - 15:43, 8 April 2024
  • UC:TT:TAF/TAP TSI (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)
    of a <train> can be reduced to one <trainPart> with a sequence of <ocpTT> elements with commercially relevant stops (<stopDescription> with commercial='true')
    4 KB (592 words) - 18:06, 7 December 2023
  • TT:commercialTrainSection (category Elements)
    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 (38 words) - 16:55, 13 March 2023
  • TT:operationalTrainSection (category Elements)
    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 (38 words) - 16:45, 13 March 2023
  • Dev:Semantic Constraints
    Therefore, their implementation will be checked during certification. Elements with approved semantic constraints are listed in Category:Semantic constraints
    4 KB (579 words) - 16:49, 13 March 2023
  • TT:baseItineraryPoint:stop (category Elements)
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further
    525 bytes (36 words) - 21:54, 25 April 2022
  • TT:previousActivities (category Elements)
    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
    521 bytes (38 words) - 21:55, 25 April 2022
  • TT:additionalStopInfos:additionalStopInfo (category Elements)
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further
    540 bytes (36 words) - 21:55, 25 April 2022
  • TT:baseItineraryPoint (category Elements)
    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
    521 bytes (38 words) - 21:54, 25 April 2022
  • TT:isOnRequest (category Elements)
    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
    514 bytes (38 words) - 21:55, 25 April 2022
  • TT:operationalTrainSectionPart (category Elements)
    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:stop:activities (category Elements)
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further
    517 bytes (36 words) - 21:55, 25 April 2022
  • TT:externalTrainReference (category Elements)
    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:56, 25 April 2022
  • TT:mediaResources (category Elements)
    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
    517 bytes (38 words) - 21:56, 25 April 2022
  • TT:operationalTrainVariant (category Elements)
    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 (85 words) - 17:36, 2 May 2023
  • TT:isCancelled (category Elements)
    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
    514 bytes (38 words) - 21:55, 25 April 2022
  • TT:followupSection (category Elements)
    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
    518 bytes (38 words) - 21:54, 25 April 2022
  • TT:itinerary (category Elements)
    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
    512 bytes (38 words) - 21:55, 25 April 2022
  • TT:commercialTrainVariant (category Elements)
    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 (101 words) - 17:37, 2 May 2023
  • TT:additionalStopInfo:activities (category Elements)
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further
    531 bytes (36 words) - 21:55, 25 April 2022
  • TT:times (category Elements)
    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
    508 bytes (38 words) - 21:54, 25 April 2022
  • TT:commercialTrain (category Elements)
    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
    518 bytes (38 words) - 21:56, 25 April 2022
  • TT:validity (category Elements)
    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
    511 bytes (38 words) - 21:54, 25 April 2022
  • TT:train (category Elements)
    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
    508 bytes (38 words) - 21:56, 25 April 2022
  • TT:operationalTrain (category Elements)
    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
    519 bytes (38 words) - 21:55, 25 April 2022
  • TT:timetable (category Elements)
    transportServices (0..1), validities (0..1) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    512 bytes (4 words) - 18:52, 19 December 2019
  • TT:itineraries (category Elements)
    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
    514 bytes (38 words) - 21:55, 25 April 2022
  • TT:connectionTransferTime (category Elements)
    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:56, 25 April 2022
  • TT:connector (category Elements)
    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
    512 bytes (38 words) - 21:56, 25 April 2022
  • TT:feeder (category Elements)
    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
    509 bytes (38 words) - 21:56, 25 April 2022
  • TT:identifiers (category Elements)
    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
    514 bytes (38 words) - 21:55, 25 April 2022
  • TT:transferRelation (category Elements)
    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
    519 bytes (38 words) - 21:56, 25 April 2022
  • TT:commercialConnections (category Elements)
    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
    524 bytes (38 words) - 21:56, 25 April 2022
  • TT:commercialTrains (category Elements)
    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
    519 bytes (38 words) - 21:56, 25 April 2022
  • TT:baseItineraries (category Elements)
    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
    518 bytes (38 words) - 21:54, 25 April 2022
  • TT:operationalTrains (category Elements)
    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
    520 bytes (38 words) - 21:55, 25 April 2022
  • TT:validities (category Elements)
    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
    513 bytes (38 words) - 21:54, 25 April 2022
  • TT:formationInformation (category Elements)
    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
  • TT:commercialSchedulings (category Elements)
    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
    524 bytes (38 words) - 21:56, 25 April 2022
  • TT:timetableScenario (category Elements)
    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
    520 bytes (38 words) - 21:54, 25 April 2022
  • TT:announcement (category Elements)
    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:57, 25 April 2022
  • TT:transportService (category Elements)
    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
    519 bytes (38 words) - 21:57, 25 April 2022
  • TT:categories (category Elements)
    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
    513 bytes (38 words) - 21:54, 25 April 2022
  • TT:timetableScenarios (category Elements)
    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
    521 bytes (38 words) - 21:54, 25 April 2022
  • TT:connectionTransferTimes (category Elements)
    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
    526 bytes (38 words) - 21:56, 25 April 2022
  • TT:transportServices (category Elements)
    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
    520 bytes (38 words) - 21:57, 25 April 2022
  • TT:reserve (category Elements)
    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
    784 bytes (81 words) - 16:11, 7 March 2024
  • TT:passengerTextInfo (category Elements)
    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
    520 bytes (38 words) - 21:57, 25 April 2022
  • TT:routeRefs (category Elements)
    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
    512 bytes (38 words) - 21:54, 25 April 2022
  • TT:reserves (category Elements)
    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
    511 bytes (38 words) - 21:54, 25 April 2022
  • TT:rule (category Elements)
    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
    507 bytes (38 words) - 21:54, 25 April 2022
  • TT:pass (category Elements)
    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
    507 bytes (38 words) - 21:54, 25 April 2022
  • TT:audioFragments (category Elements)
    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
    517 bytes (38 words) - 21:56, 25 April 2022
  • TT:textFragments (category Elements)
    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:56, 25 April 2022
  • TT:categoryRefs (category Elements)
    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:56, 25 April 2022
  • TT:trackRefs (category Elements)
    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
    512 bytes (38 words) - 21:54, 25 April 2022
  • TT:mediaCategories (category Elements)
    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
    518 bytes (38 words) - 21:57, 25 April 2022
  • TT:commercialConnection (category Elements)
    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
  • TT:trackRef (category Elements)
    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
    511 bytes (38 words) - 21:54, 25 April 2022
  • TT:timetable:announcements (category Elements)
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further
    525 bytes (36 words) - 21:57, 25 April 2022
  • TT:timetable:passengerTextInfos (category Elements)
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further
    530 bytes (36 words) - 21:57, 25 April 2022
  • TT:audioFragment (category Elements)
    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:56, 25 April 2022
  • TT:followupSections (category Elements)
    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
    519 bytes (38 words) - 21:54, 25 April 2022
  • TT:platformEdgeRefs (category Elements)
    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
    519 bytes (38 words) - 21:55, 25 April 2022
  • TT:category (category Elements)
    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
    511 bytes (38 words) - 21:54, 25 April 2022
  • TT:identifier (category Elements)
    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
    513 bytes (38 words) - 21:55, 25 April 2022
  • TT:externalTrainReference:stop (category Elements)
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further
    529 bytes (36 words) - 21:56, 25 April 2022
  • TT:stop:passengerTextInfos (category Elements)
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further
    525 bytes (36 words) - 21:55, 25 April 2022
  • TT:stop:announcements (category Elements)
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further
    520 bytes (36 words) - 21:55, 25 April 2022
  • TT:textToSpeechTemplate (category Elements)
    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
  • TT:operationalTrainSectionPart:additionalStopInfos (category Elements)
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further
    549 bytes (36 words) - 21:56, 25 April 2022
  • TT:timeBasedRule (category Elements)
    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:54, 25 April 2022
  • TT:baseItinerary (category Elements)
    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
    3 KB (335 words) - 10:49, 16 May 2022
  • TT:lineRef (category Elements)
    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
    510 bytes (38 words) - 21:54, 25 April 2022
  • TT:isCommercial (category Elements)
    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:arrival (category Elements)
    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
    510 bytes (38 words) - 21:54, 25 April 2022
  • TT:routeRef (category Elements)
    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
    511 bytes (38 words) - 21:54, 25 April 2022
  • TT:departure (category Elements)
    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
    512 bytes (38 words) - 21:54, 25 April 2022
  • TT:minimalTime (category Elements)
    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
    514 bytes (38 words) - 21:54, 25 April 2022
  • TT:categoryRef (category Elements)
    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
    514 bytes (38 words) - 21:56, 25 April 2022
  • TT:mediaCategory (category Elements)
    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:57, 25 April 2022
  • UC:TT:TimetableInformation (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)
    (e.g. next 10 days only) changes for time window: provide only updated elements for a fixed time window (e.g. next 30 days) LTP: the next yearly timetable
    5 KB (751 words) - 13:28, 13 March 2023
  • TT:externalTrainNumber (category Elements)
    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
    522 bytes (38 words) - 21:56, 25 April 2022
  • TT:tafTapTsiId (category Elements)
    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
    514 bytes (38 words) - 21:56, 25 April 2022
  • TT:operationalRange (category Elements)
    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
    519 bytes (38 words) - 21:56, 25 April 2022
  • TT:origin (category Elements)
    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
    509 bytes (38 words) - 21:56, 25 April 2022
  • TT:destination (category Elements)
    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
    514 bytes (38 words) - 21:56, 25 April 2022
  • Main Page (section Timetable and Rostering (TT))
    and Rostering (TT) and Rollingstock (RS) subschemas are in active development and can be obtained for development and test purposes. Elements that do not
    10 KB (1,041 words) - 10:56, 2 May 2024
  • TT:commercialTrainReference (category Elements)
    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
    527 bytes (38 words) - 21:56, 25 April 2022
  • TT:textFragment (category Elements)
    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:56, 25 April 2022
  • TT:isOperationalIM (category Elements)
    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
    518 bytes (38 words) - 21:55, 25 April 2022
  • TT:isOperationalRU (category Elements)
    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
    518 bytes (38 words) - 21:55, 25 April 2022
  • TT:announcementRef (category Elements)
    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
    518 bytes (38 words) - 21:55, 25 April 2022
  • TT:activityRef (category Elements)
    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
    514 bytes (38 words) - 21:55, 25 April 2022
  • TT:commercialScheduling (category Elements)
    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
  • TT:transportServiceRef (category Elements)
    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
    522 bytes (38 words) - 21:56, 25 April 2022
  • TT:referencePoint (category Elements)
    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
    517 bytes (38 words) - 21:54, 25 April 2022
  • UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)
    Adopt vehicle working scheduling to timetable changes; Umlauf an Jahresfahrplan anpassen The importing system holds timetable and vehicle working data
    2 KB (209 words) - 18:11, 27 June 2022
  • TT:platformEdgeRef (category Elements)
    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
    518 bytes (38 words) - 21:55, 25 April 2022
  • TT:operatingDayValidity (category Elements)
    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:54, 25 April 2022
  • TT:startPoint (category Elements)
    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
    513 bytes (38 words) - 21:56, 25 April 2022
  • TT:activityRollingStock (category Elements)
    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:activityOther (category Elements)
    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:activityTrainReverse (category Elements)
    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:operationalTrainSection:additionalStopInfos (category Elements)
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further
    545 bytes (36 words) - 21:55, 25 April 2022
  • TT:variant (category Elements)
    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
    510 bytes (38 words) - 21:57, 25 April 2022
  • TT:stoppingPlaceRef (category Elements)
    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
    519 bytes (38 words) - 21:55, 25 April 2022
  • TT:transferPoint (category Elements)
    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:57, 25 April 2022
  • TT:activityLoad (category Elements)
    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:passengerTextInfoRef (category Elements)
    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:locationRef (category Elements)
    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
    514 bytes (38 words) - 21:56, 25 April 2022
  • UC:TT:ExchangeOfFormationData (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)
    exactly one sequence of <trainPart> elements. Today it may contain several "parallel" sequences of <trainPart> elements at the same time, which makes it impossible
    6 KB (688 words) - 13:26, 13 March 2023
  • TT:text (category Elements)
    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
    507 bytes (38 words) - 21:57, 25 April 2022
  • UC:TT:TrafficManagementPlan (category Use case (TT)) (section Which specific data do you expect to receive/send (elements)?)
    <trainPartSequence> <trainPartRef> <trainPart> <formationTT> <operatingPeriodRef> <ocpsTT> <sectionTT> <runTimes> <connections> <stopDescription> <stopTimes>
    3 KB (270 words) - 15:11, 27 June 2022
  • UC:TT:FGIInTrain (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)
    complexity can vary. At least this use case needs the following elements: the elements <train> and <trainPart> to supply information about line, direction
    9 KB (677 words) - 18:10, 27 June 2022
  • TT:identifier:range (category Elements)
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further
    518 bytes (36 words) - 21:55, 25 April 2022
  • TT:itinerary:range (category Elements)
    This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further
    517 bytes (36 words) - 21:55, 25 April 2022
  • UC:TT:RunTimeCalculationInput (category Use case (TT))
    to certain elements that limit their use in RTC beyond restrictions The exact list of elements and attributes can be found in the elements requirement
    6 KB (858 words) - 12:09, 25 March 2024
  • TT:activityTripDependency (category Elements)
    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 (category Elements)
    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:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings (category Use case (TT)) (section Which specific data do you expect to receive/send (elements)?)
    manually using a file based interface. Common Infrastructure: the import uses elements from mesoscopic and macroscopic perspective Rolling stock static Template:Complexity
    3 KB (355 words) - 18:11, 27 June 2022
  • UC:TT:LongTermCirculationPlanning (category Use case (TT))
    differently in structural terms. Reference must be made to rolling stock elements in order to describe which vehicle types a rostering refers to. Furthermore
    6 KB (926 words) - 17:00, 4 December 2023
  • UC:TT:ATimetableForACompetition (category Use case (TT)) (section Which specific data do you expect to receive/send (elements)?)
    following data in general: <train> elements with their routes and timings (in associated <trainPart> elements), <ocp> elements to describe the references from
    16 KB (1,903 words) - 13:27, 13 March 2023
  • Dev:Changes/3.2 (section Introduced Elements)
    contain a TT subschema, this list should display all TT emements of railML® 3.2 except <timetable>. TT:activityCrewDependency TT:activityLoad TT:activityOther
    3 KB (756 words) - 14:47, 27 June 2022
  • TT:externalTrainReference:stop/3.2
    Children locationRef (1..1) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    336 bytes (5 words) - 21:56, 25 April 2022
  • TT:timetableScenarios/3.2
    Children timetableScenario (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    360 bytes (5 words) - 21:54, 25 April 2022
  • TT:itineraries/3.2
    timetable Children itinerary (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    329 bytes (5 words) - 21:55, 25 April 2022
  • TT:connectionTransferTimes/3.2
    connectionTransferTime (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    401 bytes (5 words) - 21:56, 25 April 2022
  • TT:platformEdgeRefs/3.2
    Children platformEdgeRef (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    426 bytes (5 words) - 21:55, 25 April 2022
  • TT:commercialTrains/3.2
    Children commercialTrain (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    351 bytes (5 words) - 21:56, 25 April 2022
  • TT:timetable:passengerTextInfos/3.2
    Children passengerTextInfo (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    390 bytes (5 words) - 21:57, 25 April 2022
  • TT:validities/3.2
    timetable Children validity (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    325 bytes (5 words) - 21:54, 25 April 2022
  • TT:timetable:announcements/3.2
    Children announcement (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    375 bytes (5 words) - 21:57, 25 April 2022
  • TT:baseItineraries/3.2
    Children baseItinerary (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    346 bytes (5 words) - 21:54, 25 April 2022
  • TT:isOperationalIM/3.2
    Parents* stop Children None Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    352 bytes (5 words) - 21:55, 25 April 2022
  • TT:reserves/3.2
    followupSection Children reserve (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    399 bytes (5 words) - 21:54, 25 April 2022
  • TT:mediaCategories/3.2
    Children mediaCategory (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    449 bytes (5 words) - 21:57, 25 April 2022
  • TT:commercialSchedulings/3.2
    commercialScheduling (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    423 bytes (5 words) - 21:56, 25 April 2022
  • TT:commercialConnections/3.2
    commercialConnection (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    360 bytes (5 words) - 21:56, 25 April 2022
  • TT:operationalTrains/3.2
    Children operationalTrain (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    355 bytes (5 words) - 21:55, 25 April 2022
  • TT:transportServices/3.2
    Children transportService (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    355 bytes (5 words) - 21:57, 25 April 2022
  • TT:categories/3.2
    timetable Children category (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    325 bytes (5 words) - 21:54, 25 April 2022
  • TT:identifiers/3.2
    Children identifier (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    454 bytes (5 words) - 21:55, 25 April 2022
  • TT:isOperationalRU/3.2
    Parents* stop Children None Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    352 bytes (5 words) - 21:55, 25 April 2022
  • TT:trackRefs/3.2
    followupSection Children trackRef (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    457 bytes (5 words) - 21:54, 25 April 2022
  • TT:textFragments/3.2
    Children textFragment (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    486 bytes (5 words) - 21:56, 25 April 2022
  • TT:stop:activities/3.2
    activityTrainReverse (0..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    721 bytes (5 words) - 21:55, 25 April 2022
  • TT:audioFragments/3.2
    Children audioFragment (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    490 bytes (5 words) - 21:56, 25 April 2022
  • TT:operationalTrainSection:additionalStopInfos/3.2
    Children additionalStopInfo (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    528 bytes (5 words) - 21:55, 25 April 2022
  • TT:rule/3.2
    Children timeBasedRule (0..1) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    428 bytes (5 words) - 21:54, 25 April 2022
  • TT:train/3.2
    (1..1), tafTapTsiId (1..1) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    453 bytes (5 words) - 21:56, 25 April 2022
  • TT:textToSpeechTemplate/3.2
    audioFragment Children None Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    365 bytes (5 words) - 21:56, 25 April 2022
  • TT:operationalTrainSectionPart:additionalStopInfos/3.2
    Children additionalStopInfo (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    607 bytes (5 words) - 21:56, 25 April 2022
  • TT:mediaResources/3.2
    (0..1), textFragments (0..1) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    549 bytes (5 words) - 21:56, 25 April 2022
  • TT:transferRelation/3.2
    (0..1), transferPoint (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    494 bytes (5 words) - 21:56, 25 April 2022
  • TT:categoryRefs/3.2
    Children categoryRef (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    474 bytes (5 words) - 21:56, 25 April 2022
  • TT:additionalStopInfo:activities/3.2
    activityTripDependency (0..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    718 bytes (5 words) - 21:55, 25 April 2022
  • TT:routeRefs/3.2
    followupSection Children routeRef (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    458 bytes (5 words) - 21:54, 25 April 2022
  • TT:externalTrainReference/3.2
    times (1..*), train (1..1) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    670 bytes (5 words) - 21:56, 25 April 2022
  • TT:stop:announcements/3.2
    Children announcementRef (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    760 bytes (5 words) - 21:55, 25 April 2022
  • TT:timeBasedRule/3.2
    `supplementInPercent=12.3`. (optional; xs:float) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    537 bytes (5 words) - 17:41, 15 January 2024
  • TT:previousActivities/3.2
    Children activityRef (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    801 bytes (5 words) - 21:55, 25 April 2022
  • TT:timetable/3.2
    transportServices (0..1), validities (0..1) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 21:54, 25 April 2022
  • TT:feeder/3.2
    externalTrainReference (1..1) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    606 bytes (5 words) - 17:41, 15 January 2024
  • TT:pass/3.2
    train crossing, ...). (optional; xs:boolean) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    621 bytes (5 words) - 21:54, 25 April 2022
  • TT:connector/3.2
    externalTrainReference (1..1) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    624 bytes (5 words) - 17:41, 15 January 2024
  • TT:stop:passengerTextInfos/3.2
    passengerTextInfoRef (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    785 bytes (5 words) - 21:55, 25 April 2022
  • TT:isOnRequest/3.2
    operationalTrainVariant Children None Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    646 bytes (5 words) - 21:55, 25 April 2022
  • TT:variant/3.2
    announcement variant. (optional; xs:anyURI) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    606 bytes (5 words) - 21:57, 25 April 2022
  • TT:arrival/3.2
    encoded by this element. (obligatory; xs:time) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    686 bytes (5 words) - 21:54, 25 April 2022
  • TT:departure/3.2
    encoded by this element. (obligatory; xs:time) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    689 bytes (5 words) - 21:54, 25 April 2022
  • TT:baseItineraryPoint:stop/3.2
    dwell time is needed. (optional; xs:duration) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 21:55, 25 April 2022
  • TT:announcementRef/3.2
    XML-Schema for element TT:announcementRef of railML® version 3.2 UML-visualization of TT Documentation Allows referencing of announcement elements. Subschema timetable
    778 bytes (5 words) - 21:55, 25 April 2022
  • TT:passengerTextInfoRef/3.2
    element TT:passengerTextInfoRef of railML® version 3.2 UML-visualization of TT Documentation Allows referencing of passenger text info elements. Subschema
    810 bytes (5 words) - 21:55, 25 April 2022
  • UC:IS:IntegratedTMS (section Which specific data do you expect to receive/send (elements)?)
    RBC), timetable planning system and (optionally) fleet management system. IL TT tbd tbd tbd tbd
    2 KB (179 words) - 17:27, 13 February 2023
  • TT:routeRef/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    703 bytes (5 words) - 21:54, 25 April 2022
  • TT:minimalTime/3.2
    described section. (obligatory; xs:duration) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    718 bytes (5 words) - 17:41, 15 January 2024
  • TT:lineRef/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    729 bytes (5 words) - 21:54, 25 April 2022
  • TT:audioFragment/3.2
    the audio fragment. (optional; xs:language) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    869 bytes (5 words) - 21:56, 25 April 2022
  • TT:locationRef/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    797 bytes (5 words) - 21:56, 25 April 2022
  • TT:times/3.2
    intended and relevant for RU/IM operations. *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1,004 bytes (5 words) - 21:54, 25 April 2022
  • TT:activityRef/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    764 bytes (5 words) - 21:55, 25 April 2022
  • TT:trackRef/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    752 bytes (5 words) - 21:54, 25 April 2022
  • TT:isCommercial/3.2
    planned as stop on request. (optional; xs:boolean) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    874 bytes (5 words) - 12:43, 8 February 2024
  • TT:categoryRef/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    740 bytes (5 words) - 21:56, 25 April 2022
  • TT:mediaCategory/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    779 bytes (5 words) - 12:43, 8 February 2024
  • TT:followupSections/3.2
    Children followupSection (1..*) Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    818 bytes (5 words) - 17:41, 15 January 2024
  • TT:additionalStopInfos:additionalStopInfo/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 15:55, 8 February 2024
  • TT:baseItinerary/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    880 bytes (5 words) - 21:54, 25 April 2022
  • TT:tafTapTsiId/3.2
    of the TAF TAP TSI Id (obligatory; xs:string) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 12:43, 8 February 2024
  • TT:itinerary/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    924 bytes (5 words) - 21:55, 25 April 2022
  • TT:operationalRange/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    903 bytes (5 words) - 21:56, 25 April 2022
  • TT:validity/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    997 bytes (5 words) - 12:43, 8 February 2024
  • TT:destination/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 21:56, 25 April 2022
  • TT:timetableScenario/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 12:43, 8 February 2024
  • TT:commercialTrain/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 12:43, 8 February 2024
  • TT:origin/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 21:56, 25 April 2022
  • TT:externalTrainNumber/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 12:43, 8 February 2024
  • TT:operationalTrain/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 12:43, 8 February 2024
  • TT:text/3.2
    the resource is provided in full length/size. *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 12:43, 8 February 2024
  • TT:announcement/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 12:43, 8 February 2024
  • TT:transportService/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    993 bytes (5 words) - 12:43, 8 February 2024
  • TT:followupSection/3.2
    priority. (optional; xs:nonNegativeInteger) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 21:54, 25 April 2022
  • UC:IS:Timetabling (section Which specific data do you expect to receive/send (elements)?)
    Timetabling Subschema: Infrastructure   Related subschemas: IL TT RS  Reported by: ProRail For general information on use cases see UC:Use cases
    3 KB (343 words) - 13:44, 13 March 2023
  • TT:platformEdgeRef/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 12:43, 8 February 2024
  • TT:reserve/3.2
    about the type of supplement can be provided. *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 12:43, 8 February 2024
  • TT:textFragment/3.2
    the resource is provided in full length/size. *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 12:43, 8 February 2024
  • UC:RS:OperationalSimulation (section Which specific RS data do you expect to receive/send (elements)?)
    various vehicle types and train formations Technical, Performance Mandatory elements/attributes: formation (ID, name); trainOrder; vehicleRef (orderNumber,
    1 KB (146 words) - 13:29, 13 March 2023
  • TT:identifier:range/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 12:43, 8 February 2024
  • TT:identifier/3.2
    TSI Object Identifier. (optional; xs:string) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 12:43, 8 February 2024
  • TT:connectionTransferTime/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    1 KB (5 words) - 12:43, 8 February 2024
  • TT:formationInformation/3.2
    rolling stock sub schema. (optional; xs:boolean) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 12:43, 8 February 2024
  • TT:transportServiceRef/3.2
    description of the destination. (optional; xs:string) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 12:43, 8 February 2024
  • TT:isCancelled/3.2
    operating and accounting. (optional; xs:string) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 12:43, 8 February 2024
  • TT:passengerTextInfo/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 12:43, 8 February 2024
  • TT:referencePoint/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 12:43, 8 February 2024
  • TT:stoppingPlaceRef/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 12:43, 8 February 2024
  • UC:RS:TractionPowerSupplySimulation (section Which specific RS data do you expect to receive/send (elements)?)
    Technical, Performance Energy Expected elements/attributes in addition to “Operational simulation”: Mandatory elements for motored vehicles: propulsion (voltage
    2 KB (236 words) - 13:43, 13 March 2023
  • TT:baseItineraryPoint/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 17:41, 15 January 2024
  • TT:operatingDayValidity/3.2
    validity applies even if a day is a public holiday. *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 21:54, 25 April 2022
  • TT:category/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 12:43, 8 February 2024
  • TT:commercialConnection/3.2
    timetable subschema apply. (optional; xs:duration) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 12:43, 8 February 2024
  • TT:operationalTrainSection/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 12:43, 8 February 2024
  • TT:commercialTrainSection/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 12:43, 8 February 2024
  • TT:itinerary:range/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 12:43, 8 February 2024
  • TT:startPoint/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 21:57, 25 April 2022
  • TT:timetable/3.1
    Parents* railML Children None Attributes: None *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    267 bytes (5 words) - 18:52, 19 December 2019
  • TT:commercialTrainVariant/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    3 KB (5 words) - 21:56, 25 April 2022
  • TT:transferPoint/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    3 KB (5 words) - 17:41, 15 January 2024
  • TT:commercialTrainReference/3.2
    -fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    2 KB (5 words) - 12:43, 8 February 2024
  • TT:operationalTrainVariant/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    3 KB (5 words) - 17:41, 15 January 2024
  • TT:commercialScheduling/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    3 KB (5 words) - 12:43, 8 February 2024
  • TT:operationalTrainSectionPart/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    3 KB (5 words) - 12:43, 8 February 2024
  • TT:activityTrainReverse/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    5 KB (5 words) - 21:55, 25 April 2022
  • TT:activityOther/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    5 KB (5 words) - 12:43, 8 February 2024
  • TT:activityLoad/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    5 KB (5 words) - 12:43, 8 February 2024
  • TT:activityRollingStock/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    5 KB (5 words) - 21:55, 25 April 2022
  • TT:activityTripDependency/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    6 KB (5 words) - 12:43, 8 February 2024
  • UC:IS:PassengerInformationSystem (section Which specific data do you expect to receive/send (elements)?)
    Information System (PISY) Subschema: Infrastructure   Related subschemas: TT RS  For general information on use cases see UC:Use cases
    1 KB (157 words) - 13:46, 13 March 2023
  • TT:activityCrewDependency/3.2
    [0-9a-fA-F]{12}\}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts
    7 KB (5 words) - 12:43, 8 February 2024
  • UC:IS:ExchangeOfLogicalTrainPositions (section Which specific data do you expect to receive/send (elements)?)
    Logical Train Positions Subschema: Infrastructure   Related subschemas: IL TT RS  Reported by: Siemens Mobility For general information on use cases see
    16 KB (1,407 words) - 11:50, 18 July 2022
  • Dev:UsingAny (section New elements, respectively sub-trees (Use of xs:any))
    xs:any element for optional extensions by own elements, respectively sub-trees. That's the case for all elements with the generic railML® attributes id, code
    23 KB (2,659 words) - 09:51, 1 June 2022
  • UC:IS:DriverAdvisorySystem (section Which specific data do you expect to receive/send (elements)?)
    Driver Advisory System (DASY) Subschema: Infrastructure   Related subschemas: TT RS  Reported by: IS For general information on use cases see UC:Use cases
    3 KB (306 words) - 13:48, 13 March 2023
  • UC:IS:CapacityPlanning (section Which specific IS data do you expect to receive/send (elements)?)
    extended with attributes or link to service concept values and stochastic elements.
    5 KB (687 words) - 13:46, 13 March 2023
  • TT:PreliminaryDocumentation
    <operationalTrainSectionPart> elements). Both must reference the same <itinerary> with an identical offset if more than one <commercialScheduling> elements reference the
    1 KB (97 words) - 07:08, 13 June 2020
  • Dev:TrainProtectionSystems (section Affected Elements)
    TrainProtectionSystems comprises of train protection systems. It provides two container elements for track bound systems and train bound systems respectively. Your railML®
    11 KB (422 words) - 15:50, 16 November 2022
  • Dev:Reversing trains and formations
    Zügen im Timetable-Subschema. In the <timetable> scheme, there are two elements or attributes concerning the running direction of a train formation: <
    7 KB (771 words) - 13:39, 13 March 2023
Retrieved from "https://wiki3.railml.org/wiki/Special:Search"