TT:identifiers:identifier

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element TT:identifiers:identifier of railML® version 3.3
    
Documentation Provides information about the identity of the enclosing train.
Subschema timetable
Parents*

identifiers

Children

range (0..1)

Attributes:
  • issuerRef: Reference to organizational unit that represents the issuer of the train number. (optional; xs:IDREF),

  • number: Used to specify the train number itself. (obligatory; xs:string),

  • type: Allows to specify the kind of train number described by the enclosing element. (obligatory; xs:string; patterns: other:w{2,})
Possible values:
  • CommercialTrainNumber: Used to identify a commercial train number. Often this number is communicated to the passengers or customers.
  • OperationalTrainNumber: Operational Train Number. Usualy the number used in the interlocking to track a train. This number is often not communicated to the passenger/customer but used internally.
  • TafTapTsiCaseReferenceId: An identifier used in the context of the TAF/TAP TSI. The TSI refers to this as the CR Object Type.
  • TafTapTsiPathId: An identifier used in the context of the TAF/TAP TSI. The TSI refers to this as the PA Object Type.
  • TafTapTsiPathRequestId: An identifier used in the context of the TAF/TAP TSI. The TSI refers to this as the PR Object Type.
  • TafTapTsiRouteId: An identifier used in the context of the TAF/TAP TSI. The TSI refers to this as the RO Object Type.
  • TafTapTsiTrainId: An identifier used in the context of the TAF/TAP TSI. The TSI refers to this as the TR Object Type.,

  • variant: Specifies the variant of the train with the trainnumber encoded by the enclosing element. Inspired by the variant element of the TAF TAP TSI Object Identifier. (optional; xs:string)
*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.2 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.

This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.


Changes 3.2→3.3

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

Introduced with version 3.3.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues