User Information |
Login: christian.rahmig |
Registered on Fri, 15 January 2016 |
Message Count 474 |
Subject |
Forum: |
Date Posted |
Re: Include track length information in topology |
railML.infrastructure |
Fri, 18 January 2019 16:18 |
Re: Include track length information in topology |
railML.infrastructure |
Fri, 18 January 2019 15:28 |
Re: Use the concept of layer for splitting the data |
railML.infrastructure |
Fri, 18 January 2019 15:10 |
Re: [railml3.1] Change "v" to "speed" in attribute names |
railml.common |
Fri, 18 January 2019 11:27 |
Re: railML 3.x: Data Modelling Patterns |
railml.common |
Wed, 16 January 2019 10:26 |
Re: Multiple train protection systems |
railML.infrastructure |
Mon, 14 January 2019 16:23 |
Re: How to model ETCS BL2 speed restrictions and gradients, in railML v2.x |
railML.infrastructure |
Fri, 11 January 2019 11:22 |
Re: How to model ETCS BL2 speed restrictions and gradients, in railML v2.x |
railML.infrastructure |
Tue, 08 January 2019 21:00 |
Re: scheme location to be adressed via HTTPS instead of HTTP |
railml.common |
Mon, 07 January 2019 15:08 |
Re: <track>@mainDir |
railML.infrastructure |
Wed, 19 December 2018 15:49 |
Re: infrastructure "state" |
railML.infrastructure |
Wed, 19 December 2018 15:33 |
Re: railML 3.x: Data Modelling Patterns |
railml.common |
Tue, 18 December 2018 22:17 |
Re: Define requirements for processContent strictly than lax |
railml.common |
Tue, 18 December 2018 22:04 |
Re: infrastructure "state" |
railML.infrastructure |
Mon, 26 November 2018 16:28 |
Re: <railMLv3> Infra Geometry Terminology |
railML.infrastructure |
Mon, 26 November 2018 16:24 |
Re: NetElements vs. Tracks vs. TrainDetectionElements vs. TvdSections |
railML.infrastructure |
Fri, 02 November 2018 16:31 |
Re: Platform element location: is it really necessary? |
railML.infrastructure |
Fri, 02 November 2018 16:09 |
Re: Infrastructure Visualization |
railML.infrastructure |
Fri, 02 November 2018 15:55 |
Re: Infrastructure Visualization |
railML.infrastructure |
Thu, 25 October 2018 13:52 |
Re: [railML3.1] TrainDetectionElement and TrainDetectionElementSection |
railML.infrastructure |
Mon, 22 October 2018 19:14 |
Re: the use of @dir in railML. |
railML.infrastructure |
Fri, 19 October 2018 16:42 |
Re: [railML3.1] TrainDetectionElement and TrainDetectionElementSection |
railML.infrastructure |
Mon, 15 October 2018 12:56 |
Re: @minOccurs, @maxOccurs and @use |
railml.common |
Thu, 04 October 2018 16:56 |
Re: <track>@mainDir |
railML.infrastructure |
Tue, 02 October 2018 14:33 |
Re: Representation of operational stations |
railML.infrastructure |
Tue, 02 October 2018 14:14 |
Re: missing minOccurs="0" for <trainBrakeOperation> |
railml.rollingstock |
Tue, 02 October 2018 13:25 |
@minOccurs, @maxOccurs and @use |
railml.common |
Tue, 02 October 2018 13:18 |
@minOccurs, @maxOccurs and @use |
railml.rollingstock |
Tue, 02 October 2018 13:18 |
Re: infrastructure "state" |
railML.infrastructure |
Tue, 02 October 2018 12:55 |
Re: Marking @frontier and @chargeFrontier as DEPRECATED? |
railML.infrastructure |
Tue, 02 October 2018 11:07 |
Re: Modelling of gaps and overlaps in mileage |
RailTopoModel |
Mon, 24 September 2018 14:55 |
Re: Proposal for incorporating length information in RTM NetElement |
RailTopoModel |
Mon, 17 September 2018 14:02 |
Re: Harmonize rolenames for association between *Location and *AssociatedNetElement |
RailTopoModel |
Mon, 17 September 2018 13:41 |
Re: Network location |
RailTopoModel |
Mon, 17 September 2018 13:37 |
Re: Reference to PositioningSystem |
RailTopoModel |
Mon, 17 September 2018 13:19 |
Re: Lateral location of elements |
RailTopoModel |
Mon, 17 September 2018 12:29 |
Values of attribute @dir |
railML.infrastructure |
Mon, 17 September 2018 12:15 |
directions in railML 3 |
railML.infrastructure |
Mon, 17 September 2018 12:01 |
Re: Marking @frontier and @chargeFrontier as DEPRECATED? |
railML.infrastructure |
Fri, 31 August 2018 11:34 |
Re: railML 2.3 infrastructure extension proposal operational properties of an OCP |
railML.infrastructure |
Fri, 31 August 2018 10:53 |