Home » railML newsgroups » railml.timetable » [Request for railML3] Different station tracks in one <ocpTT> for different <operatingPeriod>s
Re: [Request for railML2.4] Different station tracks in one <ocpTT> for different <operatingPeriod>s [message #1852 is a reply to message #1821] Fri, 22 June 2018 12:10 Go to previous message
Christian Rößiger is currently offline  Christian Rößiger
Messages: 62
Registered: March 2015
Member
Dear all,

After internal discussion, we have decided to update our proposal for
the modeling of seasonal track use in stations. The following points
have been changed:

- Attribute "description" is omitted and replaced by the two attributes
"track" and "platform"
- All attributes of the new element <trackInfo> are now optional

Many Greetings
Christian Rößiger

Am 04.06.2018 um 11:55 schrieb Christian Rößiger:
> Dear all,
>
> contrary to its title, the previous forum post does not refer to a
> request for railML 3, but railML 2.4. Details on the implementation in
> railML can be viewed at
> http://forum.railML.org/userfiles/2018-05-22_irfp_saisoniert e-gleisbelegung-railml24.pdf.
> The implementation of this proposal in version 2.4 was decided on May
> 23. We ask for comments and remarks.

--
iRFP e. K. · Institut für Regional- und Fernverkehrsplanung
Hochschulstr. 45, 01069 Dresden
Tel. +49 351 4706819 · Fax. +49 351 4768190 · www.irfp.de
Registergericht: Amtsgericht Dresden, HRA 9347

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: DepartureDay / ArrivalDay at first <ocpTT> of a train run
Next Topic: stopDescription: New enumeration value 'none' for attribute onOff in railML 2.4
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Mon May 06 02:15:56 CEST 2024