TT:identifier:range

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element TT:identifier:range of railML® version 3.3
    
Documentation Specifies the section of the trains path for which the enclosing train number is valid.
Subschema timetable
Parents*

commercialTrainSection, identifier, operationalTrainSection

Children

None

Attributes:
  • end: Reference to the last base itinerary point that is reached with the enclosing train number. (obligatory; xs:IDREF),

  • start: Reference to the first base itinerary point that is left with the enclosing train number. (obligatory; xs:IDREF)
*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.


 

Autoexport from the XML-Schema for element TT:identifier:range of railML® version 3.2
    
Documentation Specifies the section of the trains path for which the enclosing train number is valid.
Subschema timetable
Parents*

commercialTrainSection, identifier, operationalTrainSection

Children

None

Attributes:
  • end: Reference to the last base itinerary point that is reached with the enclosing train number. (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}}),

  • start: Reference to the first base itinerary point that is left with the enclosing train number. (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}})
*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.


 

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 questions.


Changes 3.1→3.2

There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.

Introduced with version 3.2.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues