User Information |
Login: Dirk Bräuer |
Registered on Tue, 05 August 2008 |
Message Count 313 |
Subject |
Forum: |
Date Posted |
Re: Where to place a "comment" value? |
railml.common |
Thu, 18 May 2017 15:32 |
Re: what about compressed RailML files? |
railml.common |
Thu, 18 May 2017 15:23 |
Re: Extension rolling stock for capacity planning |
railml.rollingstock |
Thu, 18 May 2017 15:16 |
Re: Timetable data elements for railVIVID |
railml.timetable |
Thu, 18 May 2017 12:59 |
Re: Referenzierung von ausgefallenen Zügen / Referencing of canceled trains |
railml.timetable |
Thu, 18 May 2017 12:35 |
Re: Haltezwecke / Stop descriptions |
railml.timetable |
Thu, 18 May 2017 12:28 |
Re: [railML3] Time Dimension requirements from TT view |
railml.timetable |
Fri, 17 February 2017 13:07 |
Addendum: [railML3] Time Dimension requirements from TT view |
railml.timetable |
Sat, 21 January 2017 13:42 |
Re: [railML3] Time Dimension requirements from TT view |
railml.timetable |
Fri, 20 January 2017 16:53 |
Re: Schnittstelle railML zu VDV452 |
railml.timetable |
Thu, 19 January 2017 20:21 |
Re: railML 2.3 infrastructure extension proposal tunnel resistance factor |
railML.infrastructure |
Thu, 19 January 2017 19:50 |
Re: railML 2.3 infrastructure extension proposal line sections |
railML.infrastructure |
Thu, 19 January 2017 19:28 |
Re: [railML3] Linear coordinates |
railML.infrastructure |
Tue, 11 October 2016 10:38 |
Re: [railML3] Strategy of documentation at wiki.railML.org |
railml.common |
Thu, 15 September 2016 13:17 |
Re: InfraAttributes and InfraAttrGroups |
railML.infrastructure |
Thu, 01 September 2016 08:41 |
Re: Wiki pages set to "outdated" |
railml.timetable |
Wed, 06 July 2016 15:57 |
Re: Wiki pages set to "outdated" |
railml.timetable |
Thu, 30 June 2016 14:52 |
Wiki pages set to "outdated" |
railml.timetable |
Wed, 29 June 2016 15:05 |
Re: non-timetable blockParts with track occupancy and train coupling |
railml.timetable |
Wed, 15 June 2016 11:45 |
Minutes on railML meeting, 2nd of June, 2016 |
railml.timetable |
Wed, 15 June 2016 11:45 |
Re: Request for a new optional attribute for train coupling and sharing |
railml.timetable |
Fri, 26 February 2016 10:02 |
Re: Infrastructure train number |
railml.timetable |
Thu, 21 January 2016 16:06 |
Request for a new optional attribute for train coupling and sharing |
railml.timetable |
Thu, 21 January 2016 16:02 |
Re: railML 2.3: Formation attributes shall have values > 0 |
railml.rollingstock |
Wed, 21 October 2015 15:08 |
Explizite Kennzeichnung von gelöschten Zügen und Zugausfällen, Tickets #188 und #247 |
railml.timetable |
Fri, 18 September 2015 10:14 |
Re: Line category according to EN 15528 |
railML.infrastructure |
Wed, 16 September 2015 12:19 |
Re: stopTimes - no reference to the times element |
railml.timetable |
Mon, 17 August 2015 16:16 |
Re: Minimal content of a timetable file |
railml.timetable |
Mon, 17 August 2015 15:46 |
Re: Line category according to EN 15528 |
railML.infrastructure |
Fri, 24 July 2015 18:02 |
Re: Unclear wiki description of attribute operationalStopOrdered |
railml.timetable |
Fri, 24 July 2015 16:57 |
Re: train protection systems |
railML.infrastructure |
Fri, 08 May 2015 19:22 |
Re: Wiki Discussion |
railml.timetable |
Tue, 16 December 2014 16:20 |
Re: odometry, pos and absPos |
railML.infrastructure |
Tue, 09 December 2014 00:44 |
Re: addendum: separation of <ocpTT> from <trainPart> - meeting 11.11. |
railml.timetable |
Mon, 08 December 2014 13:09 |
Change from xml:id to UUID in future? |
railml.common |
Mon, 08 December 2014 10:40 |
To use or not to use? - default values in XSDs |
railml.common |
Mon, 08 December 2014 10:40 |
addendum: separation of <ocpTT> from <trainPart> - meeting 11.11. |
railml.timetable |
Tue, 19 November 2013 19:45 |
Re: new attribute on the vehicle element |
railml.rollingstock |
Tue, 19 November 2013 18:53 |
Re: Blockparts: emptyRuns, depotRuns |
railml.timetable |
Tue, 19 November 2013 16:33 |
Re: planned passenger capacities |
railml.timetable |
Tue, 19 November 2013 13:28 |