element TrainInformation
diagram taf_cat_complete_sector_p576.png
namespace http://taf-jsg.info/schemes
properties
content complex
children RouteSection Route
used by
elements UpdateLinkMessage/Operation PathCoordinationMessage PathRequestMessage ObjectInfoMessage/TrainInformationExtended
attributes
Name  Type  Use  Default  Fixed  Annotation
RouteInfoVersion  xs:positiveInteger  optional      
documentation
Each time one of the SectionVersions is changed the RouteInfoversion is incremented
annotation
documentation
Contains global routing information and calenders of the different routes a train operates during the time table year.
source <xs:element name="TrainInformation">
 
<xs:annotation>
   
<xs:documentation>Contains global routing information and calenders of the different routes a train operates during the time table year.</xs:documentation>
 
</xs:annotation>
 
<xs:complexType>
   
<xs:sequence>
     
<xs:element name="RouteSection" maxOccurs="unbounded">
       
<xs:complexType>
         
<xs:sequence>
           
<xs:element ref="SectionID">
             
<xs:annotation>
               
<xs:documentation>New ObjectTyp = 'RS' . Use Variant to differentiate section within die set of sections of a train.
                                        Only ObjectType and Variant part of the identifier must be different from the components of Train-ID. StartDate is only needed in train runs.
</xs:documentation>
             
</xs:annotation>
           
</xs:element>
           
<xs:element ref="PlannedJourneyLocation" minOccurs="2" maxOccurs="2">
             
<xs:annotation>
               
<xs:documentation>The first location is the departure of a section. The last the arrival station.
                                        The offset in the TimeAtLocation of arrival station is relativ to the departure day. The offset of arrival location must be zero.
                                        Only LocationIdent and TimingAtLocation structure is filled in this structure.
</xs:documentation>
             
</xs:annotation>
           
</xs:element>
           
<xs:element ref="PlannedCalendar" minOccurs="0">
             
<xs:annotation>
               
<xs:documentation>The calendar of a section must only be defined in the construction start section. The calendar of the other section can be computed from it.</xs:documentation>
             
</xs:annotation>
           
</xs:element>
           
<xs:element name="Successors" minOccurs="0">
             
<xs:complexType>
               
<xs:sequence maxOccurs="unbounded">
                 
<xs:annotation>
                   
<xs:documentation>References to successor sections</xs:documentation>
                 
</xs:annotation>
                 
<xs:element ref="SectionID"/>
               
</xs:sequence>
             
</xs:complexType>
           
</xs:element>
         
</xs:sequence>
         
<xs:attribute name="SectionVersion" type="xs:positiveInteger" use="optional">
           
<xs:annotation>
             
<xs:documentation>When a section changed this version is incremented.</xs:documentation>
           
</xs:annotation>
         
</xs:attribute>
         
<xs:attribute name="HasReferenceCalender" type="xs:boolean" use="optional" default="false">
           
<xs:annotation>
             
<xs:documentation>Calendars of other sections can be computed starting from this section.</xs:documentation>
           
</xs:annotation>
         
</xs:attribute>
       
</xs:complexType>
     
</xs:element>
     
<xs:element name="Route" minOccurs="0" maxOccurs="unbounded">
       
<xs:annotation>
         
<xs:documentation>Optional because all routes can be computed from the route sections</xs:documentation>
       
</xs:annotation>
       
<xs:complexType>
         
<xs:sequence>
           
<xs:element ref="PlannedCalendar">
             
<xs:annotation>
               
<xs:documentation>The calendar of the route defines the days at which train runs of the route start</xs:documentation>
             
</xs:annotation>
           
</xs:element>
           
<xs:sequence minOccurs="2" maxOccurs="unbounded">
             
<xs:element ref="PlannedJourneyLocation">
               
<xs:annotation>
                 
<xs:documentation>Origin, Handover and Destination. Offsets in TimeAtLocation are relativ to the departure day of origin of the route.
                                            Only LocationIdent and TimingAtLocation structure is filled.
</xs:documentation>
               
</xs:annotation>
             
</xs:element>
           
</xs:sequence>
         
</xs:sequence>
         
<xs:attribute name="key">
           
<xs:annotation>
             
<xs:documentation>section variant ids of the route joined with '-'

                                    Only used for convenience.
</xs:documentation>
           
</xs:annotation>
         
</xs:attribute>
       
</xs:complexType>
     
</xs:element>
   
</xs:sequence>
   
<xs:attribute name="RouteInfoVersion" type="xs:positiveInteger" use="optional">
     
<xs:annotation>
       
<xs:documentation>Each time one of the SectionVersions is changed the RouteInfoversion is incremented</xs:documentation>
     
</xs:annotation>
   
</xs:attribute>
 
</xs:complexType>
</xs:element>

attribute TrainInformation/@RouteInfoVersion
type xs:positiveInteger
properties
use optional
annotation
documentation
Each time one of the SectionVersions is changed the RouteInfoversion is incremented
source <xs:attribute name="RouteInfoVersion" type="xs:positiveInteger" use="optional">
 
<xs:annotation>
   
<xs:documentation>Each time one of the SectionVersions is changed the RouteInfoversion is incremented</xs:documentation>
 
</xs:annotation>
</xs:attribute>

element TrainInformation/RouteSection
diagram taf_cat_complete_sector_p577.png
namespace http://taf-jsg.info/schemes
properties
minOcc 1
maxOcc unbounded
content complex
children SectionID PlannedJourneyLocation PlannedCalendar Successors
attributes
Name  Type  Use  Default  Fixed  Annotation
SectionVersion  xs:positiveInteger  optional      
documentation
When a section changed this version is incremented.
HasReferenceCalender  xs:boolean  optional  false    
documentation
Calendars of other sections can be computed starting from this section.
source <xs:element name="RouteSection" maxOccurs="unbounded">
 
<xs:complexType>
   
<xs:sequence>
     
<xs:element ref="SectionID">
       
<xs:annotation>
         
<xs:documentation>New ObjectTyp = 'RS' . Use Variant to differentiate section within die set of sections of a train.
                                        Only ObjectType and Variant part of the identifier must be different from the components of Train-ID. StartDate is only needed in train runs.
</xs:documentation>
       
</xs:annotation>
     
</xs:element>
     
<xs:element ref="PlannedJourneyLocation" minOccurs="2" maxOccurs="2">
       
<xs:annotation>
         
<xs:documentation>The first location is the departure of a section. The last the arrival station.
                                        The offset in the TimeAtLocation of arrival station is relativ to the departure day. The offset of arrival location must be zero.
                                        Only LocationIdent and TimingAtLocation structure is filled in this structure.
</xs:documentation>
       
</xs:annotation>
     
</xs:element>
     
<xs:element ref="PlannedCalendar" minOccurs="0">
       
<xs:annotation>
         
<xs:documentation>The calendar of a section must only be defined in the construction start section. The calendar of the other section can be computed from it.</xs:documentation>
       
</xs:annotation>
     
</xs:element>
     
<xs:element name="Successors" minOccurs="0">
       
<xs:complexType>
         
<xs:sequence maxOccurs="unbounded">
           
<xs:annotation>
             
<xs:documentation>References to successor sections</xs:documentation>
           
</xs:annotation>
           
<xs:element ref="SectionID"/>
         
</xs:sequence>
       
</xs:complexType>
     
</xs:element>
   
</xs:sequence>
   
<xs:attribute name="SectionVersion" type="xs:positiveInteger" use="optional">
     
<xs:annotation>
       
<xs:documentation>When a section changed this version is incremented.</xs:documentation>
     
</xs:annotation>
   
</xs:attribute>
   
<xs:attribute name="HasReferenceCalender" type="xs:boolean" use="optional" default="false">
     
<xs:annotation>
       
<xs:documentation>Calendars of other sections can be computed starting from this section.</xs:documentation>
     
</xs:annotation>
   
</xs:attribute>
 
</xs:complexType>
</xs:element>

attribute TrainInformation/RouteSection/@SectionVersion
type xs:positiveInteger
properties
use optional
annotation
documentation
When a section changed this version is incremented.
source <xs:attribute name="SectionVersion" type="xs:positiveInteger" use="optional">
 
<xs:annotation>
   
<xs:documentation>When a section changed this version is incremented.</xs:documentation>
 
</xs:annotation>
</xs:attribute>

attribute TrainInformation/RouteSection/@HasReferenceCalender
type xs:boolean
properties
use optional
default false
annotation
documentation
Calendars of other sections can be computed starting from this section.
source <xs:attribute name="HasReferenceCalender" type="xs:boolean" use="optional" default="false">
 
<xs:annotation>
   
<xs:documentation>Calendars of other sections can be computed starting from this section.</xs:documentation>
 
</xs:annotation>
</xs:attribute>

element TrainInformation/RouteSection/Successors
diagram taf_cat_complete_sector_p578.png
namespace http://taf-jsg.info/schemes
properties
minOcc 0
maxOcc 1
content complex
children SectionID
source <xs:element name="Successors" minOccurs="0">
 
<xs:complexType>
   
<xs:sequence maxOccurs="unbounded">
     
<xs:annotation>
       
<xs:documentation>References to successor sections</xs:documentation>
     
</xs:annotation>
     
<xs:element ref="SectionID"/>
   
</xs:sequence>
 
</xs:complexType>
</xs:element>

element TrainInformation/Route
diagram taf_cat_complete_sector_p579.png
namespace http://taf-jsg.info/schemes
properties
minOcc 0
maxOcc unbounded
content complex
children PlannedCalendar PlannedJourneyLocation
attributes
Name  Type  Use  Default  Fixed  Annotation
key          
documentation
section variant ids of the route joined with '-'

                                    Only used for convenience.
annotation
documentation
Optional because all routes can be computed from the route sections
source <xs:element name="Route" minOccurs="0" maxOccurs="unbounded">
 
<xs:annotation>
   
<xs:documentation>Optional because all routes can be computed from the route sections</xs:documentation>
 
</xs:annotation>
 
<xs:complexType>
   
<xs:sequence>
     
<xs:element ref="PlannedCalendar">
       
<xs:annotation>
         
<xs:documentation>The calendar of the route defines the days at which train runs of the route start</xs:documentation>
       
</xs:annotation>
     
</xs:element>
     
<xs:sequence minOccurs="2" maxOccurs="unbounded">
       
<xs:element ref="PlannedJourneyLocation">
         
<xs:annotation>
           
<xs:documentation>Origin, Handover and Destination. Offsets in TimeAtLocation are relativ to the departure day of origin of the route.
                                            Only LocationIdent and TimingAtLocation structure is filled.
</xs:documentation>
         
</xs:annotation>
       
</xs:element>
     
</xs:sequence>
   
</xs:sequence>
   
<xs:attribute name="key">
     
<xs:annotation>
       
<xs:documentation>section variant ids of the route joined with '-'

                                    Only used for convenience.
</xs:documentation>
     
</xs:annotation>
   
</xs:attribute>
 
</xs:complexType>
</xs:element>

attribute TrainInformation/Route/@key
annotation
documentation
section variant ids of the route joined with '-'

                                    Only used for convenience.
source <xs:attribute name="key">
 
<xs:annotation>
   
<xs:documentation>section variant ids of the route joined with '-'

                                    Only used for convenience.
</xs:documentation>
 
</xs:annotation>
</xs:attribute>


XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy