TT:tafTapTsiTrainID train: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
(Updated Examples)
Line 32: Line 32:


|example =
|example =
Example text here
Further documentation can be found on the ERA website:
 
* [http://www.era.europa.eu/Document-Register/Documents/ERA_Technical_Document_TAP_B_56_FINAL.pdf TAP TSI technical document B.56 (chapter 9 - Use of identifiers)]
[http://www.era.europa.eu/Document-Register/Documents/ERA_Technical_Document_TAP_B_56_FINAL.pdf TAP TSI technical document B.56 (chapter 9 - Use of identifiers)]


|openissues =
|openissues =
No known open issues yet.
No known open issues yet.
}}
}}

Revision as of 09:08, 26 February 2016


tafTapTsiTrainID
 


Scheme description / Schemenbeschreibung

Position of tafTapTsiTrainID in the XML-Tree / Position von tafTapTsiTrainID im XML-Baum

  • Parent: <train>
  • Children: None.

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

The element tafTapTsiTrainID describes the so called unique TransportID, used for the explicit identification of a train, especially for international train runs. The number will be imlemented during the implementation of the TAF/TAP TSI.

Das Element tafTapTsiTrainID beschreibt die eindeutige Zugnummer, welche für die Identifizierung insbesondere internationaler Zugläufe verwendet werden kann. Diese Nummer wird im Rahmen der europäischen Implementierung der TAF/TAP TSI implementiert.

Attributes of tafTapTsiTrainID / Attribute von tafTapTsiTrainID

This element does not inherit any attributes.

  • ObjectType: Provides a possibility for differentiantion between the objects: Train, Path, Case Reference and Path Request
  • TR Train
  • PA Path
  • CR Case Reference
  • PR Path Request
  • Company: Identifies a railway company (RU or IM) by the unique company id (also known as RICS)
  • Core: It is the main part of identifier and is determent by the company that creates it.
  • Variant: The variant shows a relationship between two identifiers referring to the same business case (e.g. a request for a train path)
  • TimetableYear: Refers to the timetable period in which the business will be carried out.
  • StartDate: Is only used in the operational phase and refers to the date where the single train will start the train journey.

Syntactic Constraints / Syntaktische Beschränkungen

  • Company mandatory
  • Core mandatory
  • Variant mandatory
  • TimetableYear mandatory
  • StartDate optional

Best practice & Examples / Empfohlene Anwendung & Beispiele

Further documentation can be found on the ERA website:

Notes / Anmerkungen

Not yet described. / Noch nicht beschrieben.

Open issues / Offene Punkte/Pendenzen

No known open issues yet.