TT:baseItineraryPoint/3.2

Automatic Schemaexport for Element baseItineraryPoint

Autoexport from the XML-Schema for element TT:baseItineraryPoint of railML® version 3.2 UML-visualization of TT
Documentation	A base itinerary is made up of 1 or more base itinerary points. Instinctively one would assume that at least 2 base itinerary points would be required, however for modeling stabling of trains at a track only a single point is needed and the requirement for a second one would actually be a problem. When describing a movement from one place to another however at least 2 base itinerary points are needed. Each such base itinerary point represents a stop or passthrough at an operational point along the route.
Subschema	timetable
Parents*	baseItinerary
Children	followupSections (0..1), pass (1..1), stop (1..1), times (0..*), trackRef (0..*)
Attributes: locationRef: Provides a reference to an operational point that is defined in the infrastructure. (obligatory; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|\{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}\}), id: unique identifier (obligatory; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|\{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[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. 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.