Search results

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

railML® 2, it is possible to describe and validate that a <train> must reference one or more <trainPart>s, that all <trackElements> must have a position on

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

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

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

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

TT:commercialSchedulings TT:commercialTrain TT:commercialTrainReference TT:commercialTrainSection TT:commercialTrainVariant TT:commercialTrains TT:connectionTransferTime

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

Selected trains: provide the timetable entries for a subset of trains, for further special analysis Macroscopic infrastructure Interval trains / train groups

properties of trains and train parts. Train parts with disjunctive operating days do not have to be mixed with coupled train parts, which apply to train coupling

attribute (code or name) from trainPart to the commercial train referencing trains (via "code" or trainNumber/scope/additionalTrainNumber) referencing categories

This use cases aim is to exchange data with systems that are focused on train runtime calculation. This kind of calculation is carried out in varying levels

elements (e.g. trains) To be specified As a bare minimum the commercial view of a <train> can be reduced to one <trainPart> with a sequence of <ocpTT> elements

Automatic Schemaexport for Element commercialTrain

Automatic Schemaexport for Element operationalTrain

element TT:timetableScenario of railML® version 3.2 UML-visualization of TT Documentation A timetable scenario is an abstract entity used to group validities

activities (blocks) that are carried out by a group of vehicles in a unit of time. Such a vehicle group is a sequence of vehicles, at least a single vehicle

Autoexport from the XML-Schema for element TT:transportServiceRef of railML® version 3.2 UML-visualization of TT Documentation Allows referencing a transport

example does not re-use railML® elements, attributes, attribute groups, types, groups. It is fully based on XML Schema types. (lines 17, 23, 29, 34) The

for element TT:transportService of railML® version 3.2 UML-visualization of TT Documentation A transport service groups a number of trains that provide