Forum: railml.timetable » Request for a new optional attribute for train coupling and sharing

Home » railML newsgroups » railml.timetable » Request for a new optional attribute for train coupling and sharing

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Request for a new optional attribute for train coupling and sharing [message #1356 is a reply to message #1348]

Thu, 02 June 2016 12:51

Vasco Paul Kolmorgen
Messages: 55
Registered: November 2004

Member

The problem was explained by Dirk Bräuer and the issue was discussed again in the railML's Timetable developer meeting in Berlin on June 2nd, 2016.

Conclusion: As a solution in a (possibly) upcoming railML 2.x is not urgent as a <any> field was used by the proposer. The issue has to be take into consideration for the refactoring in railML 3.x and -if not solved by the refactoring process- to be discussed again.

Regards,
--
Vasco Paul Kolmorgen
railML.org Coordinator
Dresden; Germany www.railml.org

Report message to a moderator

[Message index]

		Request for a new optional attribute for train coupling and sharing By: Dirk Bräuer on Thu, 21 January 2016 16:02
		Re: Request for a new optional attribute for train coupling and sharing By: Philip Wobst on Thu, 18 February 2016 16:31
		Re: Request for a new optional attribute for train coupling and sharing By: Dirk Bräuer on Fri, 26 February 2016 10:02
		Re: Request for a new optional attribute for train coupling and sharing By: Vasco Paul Kolmorgen on Thu, 02 June 2016 12:51

Previous Topic:	Infrastructure train number
Next Topic:	stopTimes - no reference to the times element

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Apr 30 03:49:04 CEST 2024