User Information |
Login: Joerg von Lingen |
Registered on Tue, 17 May 2011 |
Message Count 148 |
Subject |
Forum: |
Date Posted |
Re: Restricted Areas: limitedBy vs. elements inside |
railml.interlocking |
Sat, 26 January 2019 05:03 |
Re: switchType IS vs. IL |
railml.interlocking |
Sat, 26 January 2019 05:01 |
Re: switchType IS vs. IL |
railML.infrastructure |
Sat, 26 January 2019 05:01 |
Re: [railml3.1] Redundant references in TVD sections and restricted areas |
railml.interlocking |
Sat, 26 January 2019 05:00 |
Re: [railml3.1] Redundant references in TVD sections and restricted areas |
railml.interlocking |
Thu, 17 January 2019 05:35 |
Re: [railml3.1] Redundant references in TVD sections and restricted areas |
railml.interlocking |
Wed, 16 January 2019 12:35 |
Restricted Areas: limitedBy vs. elements inside |
railml.interlocking |
Sun, 13 January 2019 04:37 |
Re: [railml3.1] cleanup of unused types |
railml.common |
Fri, 04 January 2019 05:36 |
Re: [railml3.1] Change "v" to "speed" in attribute names |
railml.common |
Sun, 30 December 2018 05:32 |
Re: Using type EntityILref for references to the infrastructure domain |
railml.interlocking |
Sun, 30 December 2018 05:31 |
Re: What is the rationale for multiple <assetsForIL>s? |
railml.interlocking |
Sun, 30 December 2018 05:26 |
Re: Time vs. Timer in element and attribute names |
railml.interlocking |
Sun, 30 December 2018 05:21 |
Re: railML 3.x: Data Modelling Patterns |
railml.common |
Sat, 29 December 2018 05:08 |
Re: railML 3.x: Data Modelling Patterns |
railml.common |
Wed, 12 December 2018 06:02 |
Re: railMLv3: TVD Section demarcatingTrainDetection |
railml.interlocking |
Thu, 06 December 2018 14:33 |
Re: Partial Route |
railml.interlocking |
Mon, 26 November 2018 06:14 |
Re: Rollingstock - modelling patterns |
railml.rollingstock |
Thu, 22 November 2018 13:30 |
Rollingstock - modelling patterns |
railml.rollingstock |
Tue, 20 November 2018 04:54 |
Re: railML 3.x: Data Modelling Patterns |
railml.common |
Mon, 19 November 2018 05:25 |
Re: Partial Route |
railml.interlocking |
Sat, 17 November 2018 06:23 |
Overlapping or gapping track section borders |
railml.interlocking |
Sat, 17 November 2018 05:48 |
Re: Partial Route |
railml.interlocking |
Wed, 07 November 2018 05:17 |
Re: NetElements vs. Tracks vs. TrainDetectionElements vs. TvdSections |
railML.infrastructure |
Mon, 05 November 2018 15:14 |
Re: [railML3.1] TrainDetectionElement and TrainDetectionElementSection |
railML.infrastructure |
Sat, 20 October 2018 05:41 |
Re: Consolidated Use Cases List |
railml.common |
Sun, 16 September 2018 14:37 |
Re: need for new element stopingActivity time |
railml.rollingstock |
Sun, 16 September 2018 14:26 |
Re: new values for places and service |
railml.rollingstock |
Sun, 16 September 2018 14:23 |
Re: need for new element stopingActivity time |
railml.rollingstock |
Sun, 16 September 2018 14:14 |
Re: @code as element name |
railml.interlocking |
Sun, 26 August 2018 09:00 |
Re: [railML 3.1] border types |
railML.infrastructure |
Sun, 26 August 2018 08:57 |
Re: railML 2.3 infrastructure extension proposal route information at signal |
railML.infrastructure |
Fri, 24 August 2018 10:57 |
@code as element name |
railml.interlocking |
Wed, 15 August 2018 09:34 |
Re: Extension suggestion for track sections |
railML.infrastructure |
Wed, 15 August 2018 09:20 |
Re: new values for places and service |
railml.rollingstock |
Tue, 07 August 2018 08:30 |
Re: speedProfile and rolling stock |
railml.rollingstock |
Tue, 07 August 2018 08:15 |
Re: missing minOccurs="0" for <trainBrakeOperation> |
railml.rollingstock |
Fri, 03 August 2018 05:29 |
Re: Suggestion towards new attributes and sub element for <doors> |
railml.rollingstock |
Fri, 03 August 2018 05:28 |
Re: speedProfile and rolling stock |
railml.rollingstock |
Fri, 03 August 2018 05:21 |
Re: [railML 3.1] border types |
railML.infrastructure |
Sat, 02 June 2018 17:21 |
Re: SI units in railML 3.x |
railml.common |
Tue, 29 May 2018 16:39 |