Forum: railml.timetable » circulations should be optional

Home » railML newsgroups » railml.timetable » circulations should be optional

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

Re: circulations should be optional [message #923 is a reply to message #912]

Tue, 12 February 2013 16:55

Joachim Rubröder railML is currently offline

Joachim Rubröder railML
Messages: 0
Registered: November 2019

Dear Andreas,

there seem to be no objections against this issue. I therefore opened a
ticket:
https://trac.assembla.com/railML/ticket/221

But for an implementation in version 2.2, I definitely prefer the solution
with optional <circulations>. Your suggestion with additional <blocks>
below <timetable> would result in two different possible locations which
is not desirable

Kind regards,
Joachim

-------------------------------------
Joachim RubrÃ¶der
Schema Coordinator: railML.timetable

--
----== posted via PHP Headliner ==----

Report message to a moderator

[Message index]

		circulations should be optional By: Andreas Tanner on Wed, 02 January 2013 10:29
		Re: circulations should be optional By: Joachim Rubröder railML on Tue, 12 February 2013 16:55
		Re: circulations should be optional By: Andreas Tanner on Wed, 13 February 2013 08:37
		Re: circulations should be optional By: Dirk Bräuer on Tue, 12 March 2013 18:25

Previous Topic:	train annotations
Next Topic:	infrastructure train path: where to put path parameters

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue May 14 10:07:56 CEST 2024