TT:commercialTrainSection/3.3

From railML 3 Wiki
Jump to navigation Jump to search

Automatic Schemaexport for Element commercialTrainSection



Autoexport from the XML-Schema for element TT:commercialTrainSection of railML® version 3.3
    
Documentation The commercial train sections of a commercial train variant provide info about a part of the trains path.
Subschema timetable
Parents*

commercialTrainVariant

Children

additionalStopInfos (0..1), categoryRefs (0..1), freightFacilities (0..1), isCancelled (0..1), isOnRequest (0..1), passengerFacilities (0..1), range (0..1), transportServiceRef (0..1)

Attributes:
  • ordererRef: Reference to the organizational unit that ordered the train (optional; xs:IDREF),

  • sequenceNumber: Used to explicitly specify the order of sections within the enclosing commercialTrainVariant by providing ascending sequence numbers. (obligatory; xs:unsignedInt),

  • isEmpty: Trains marked with this flag are running empty and thus can be treated differently when rescheduling and dispatching. (optional; xs:boolean),

  • isPublic: Unless specified otherwise, all trains are considered public.
    Non-public trains, their schedules and other details must not be communicated to the open public. (optional; xs:boolean),

  • trainType: Allows classification of trains using an extendable enumeration. Mainly used to distinguish between passenger and freight trains. (optional; xs:string; patterns: other:\w{2,}; consider Dev:UsingAny too.)
Possible values:
  • EngineRun: Indicates that the train consists of a locomotive only
  • Goods: Indicates that the train is a freight train
  • Passenger: Indicates that the train is a passenger train,

  • id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory; xs:ID); compare: Dev:Identities
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this Wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.