General container for the different TAF/TAP TSI subareas. Shows the calendar of the different events on those subareas.
Recent Activity
April 20, 2023
March 6, 2023
- 2:09pm[TAF/TAP TSI] [] Mario Toma updated Additional value in the ReasonOfReference code list Monday, March 6Mario Toma updated Additional value in the ReasonOfReference code list Changes to Modify the following element * 1016 = Same capacity need * 1016 = Same capacity need - (Additional information: + (Reference to the Capacity -Reference to the previous train according to which the Capacity Needs +Needs Announcements from the previous year)* -Announcements was created)* * . . .* * . . .* Mario Toma updated Additional value in the ReasonOfReference code list
February 20, 2023
February 17, 2023
February 16, 2023
- 12:10pm[TAF/TAP TSI] [] Nektarios Zacharias updated Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when interruption was first declared, not when train is stopped Thursday, February 16Nektarios Zacharias updated Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when interruption was first declared, not when train is stopped Changes to Problem description So it would me more clear to replace this comment by "*/Date and Time when So it would me more clear to replace this comment by "*/Date and Time when -message was first declared/*"+interruption was first declared/*" Changes to Modify the following element <xs:element name="InterruptionDateTime" type="xs:dateTime"> <xs:element name="InterruptionDateTime" type="xs:dateTime"> <xs:annotation> <xs:annotation> - <xs:documentation>Date and Time when message was first + <xs:documentation>Date and Time when interruption was -declared</xs:documentation>+first declared</xs:documentation> </xs:annotation> </xs:annotation> </xs:element> </xs:element> Nektarios Zacharias updated Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when interruption was first declared, not when train is stopped
February 15, 2023
- 4:32pm[TAF/TAP TSI] [] Nicolas Jasinski updated Clarification of TrainActivity type codes 0044 to 0047 "connecting service" Wednesday, February 15Nicolas Jasinski updated Clarification of TrainActivity type codes 0044 to 0047 "connecting service" Too many differences to list. See Revisions for details.Nicolas Jasinski updated Clarification of TrainActivity type codes 0044 to 0047 "connecting service"
February 3, 2023
- 2:18pm[TAF/TAP TSI] [] Nektarios Zacharias updated Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when interruption was first declared, not when train is stopped Friday, February 3Nektarios Zacharias updated Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when interruption was first declared, not when train is stopped Changes to Title -Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when message was first declared, not when train is stopped+Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when interruption was first declared, not when train is stopped Nektarios Zacharias updated Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when interruption was first declared, not when train is stopped
- 2:04pm[TAF/TAP TSI] [] Nektarios Zacharias updated Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when interruption was first declared, not when train is stopped Friday, February 3Nektarios Zacharias updated Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when interruption was first declared, not when train is stopped Changes to ID +356 Nektarios Zacharias updated Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when interruption was first declared, not when train is stopped
January 27, 2023
December 20, 2022
December 16, 2022
- 2:52pm[TAF/TAP TSI] [] Eric Jourdain created Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when interruption was first declared, not when train is stopped Friday, December 16Eric Jourdain created Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when interruption was first declared, not when train is stopped Eric Jourdain created Change comment on "InterruptionDateTime" parameter in TrainRunningInterruptionMessage to clarify that interruption incident starts when interruption was first declared, not when train is stopped