TT:tafTapTsiTrainID train: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
m (Fixed link to external document)
 
(9 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<!--{{multiple use}}
{{mult line|TT|train|tafTapTsiTrainID}}
{{mult line|TT|replacementOf|tafTapTsiTrainID}}-->
{{ElementDocu|
{{ElementDocu|
elementName = tafTapTsiTrainID
elementName = tafTapTsiTrainID
Line 9: Line 12:
|parent = {{TT:Tag|train}}
|parent = {{TT:Tag|train}}
|childs = None.
|childs = None.
|minocc=0
|maxocc=1
|inheritedAttributes =  
|inheritedAttributes =  
This element does not inherit any attributes.
This element does not inherit any attributes.


|ownAttributes =
|ownAttributes =
* {{Attr|ObjectType}}: Provides a possibility for differentiantion between the objects: Train, Path, Case Reference and Path Request
* {{Attr|objectType}}: Provides a possibility for differentiantion between the objects: Train, Path, Case Reference and Path Request
:* {{Enum|TR}} Train
:* {{Enum|TR}} Train
:* {{Enum|PA}} Path
:* {{Enum|PA}} Path
:* {{Enum|CR}} Case Reference
:* {{Enum|CR}} Case Reference
:* {{Enum|PR}} Path Request
:* {{Enum|PR}} Path Request
* {{Attr|Company}}: Identifies a railway company (RU or IM) by the unique company id (also known as RICS)
* {{Attr|companyCode}}: Identifies a railway company (RU or IM) by the unique company id (also known as RICS). This code is defined in TAP TSI B.8 as well as the UIC IRS/leaflet 920-1:2006
* {{Attr|Core}}: It is the main part of identifier and is determent by the company that creates  it.
* {{Attr|core}}: It is the main part of identifier and is determent by the company that creates  it.
* {{Attr|Variant}}: The variant shows a relationship between two identifiers referring to the same business case (e.g. a request for a train path)
* {{Attr|variant}}: The variant shows a relationship between two identifiers referring to the same business case (e.g. a request for a train path)
* {{Attr|TimetableYear}}: Refers to the timetable period in which the business will be carried out.
* {{Attr|timetableYear}}: Refers to the timetable period in which the business will be carried out.
* {{Attr|StartDate}}: Is only used in the operational phase and refers to the date where the single train will start the train journey.
* {{Attr|startDate}}: Is only used in the operational phase and refers to the date where the single train will start the train journey.


|constraints =
|constraints =
* {{Attr|Company}} mandatory
* {{Attr|objectType}}: {{railMLType|tTapTsiObjectType}}, mandatory
* {{Attr|Core}} mandatory
* {{Attr|companyCode}}: {{railMLType|tCompanyCode}}, mandatory
* {{Attr|Variant}} mandatory
* {{Attr|core}}: {{railMLType|tTapTsiCore}}, mandatory
* {{Attr|TimetableYear}} mandatory
* {{Attr|variant}}: {{railMLType|tTapTsiVariant}}, mandatory
* {{Attr|StartDate}} optional
* {{Attr|timetableYear}}: {{railMLType|tTapTsiTimetableYear}}, mandatory
* {{Attr|startDate}}: {{railMLType|tTapTsiStartDate}}, optional


|example =
|example =
Example text here
Further documentation can be found on the ERA website:
 
* {{external|https://www.era.europa.eu/system/files/2022-11/TAP%20B%2056%20-%20RU_IM%20Communication%20Application%20Guide.pdf|TAP TSI technical document B.56|comment=see 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.
}}
}}

Latest revision as of 08:14, 23 February 2023


tafTapTsiTrainID
 


Scheme description / Schemenbeschreibung

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

  • Parent: <train>
  • Children: None.

Multiplicity / Anzahl

[0..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
  • companyCode: Identifies a railway company (RU or IM) by the unique company id (also known as RICS). This code is defined in TAP TSI B.8 as well as the UIC IRS/leaflet 920-1:2006
  • 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

  • objectType: restriction of xs:string; provides a possibility for differentiantion between the objects: Train, Path, Case Reference and Path Request, mandatory
  • companyCode: restriction of xs:integer; company code according TAP TSI B.8 and UIC IRS/leaflet 920-1:2006, mandatory
  • core: restriction of xs:string; it is the main part of identifier and is determined by the company that creates it, mandatory
  • variant: restriction of xs:string; the variant shows a relationship between two identifiers referring to the same business case, mandatory
  • timetableYear: restriction of xs:integer; refers to the timetable period in which the business will be carried out, mandatory
  • startDate: restriction of xs:date; the start of the date/time in effect, 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.