railML 3 issueshttps://development.railml.org/railml/version3/-/issues2024-01-11T17:33:39+01:00https://development.railml.org/railml/version3/-/issues/529Create wiki documentation for IS:etcsLevelTransition2024-01-11T17:33:39+01:00TT CoordinationCreate wiki documentation for IS:etcsLevelTransitionThe ETCS working group created a draft documentation for the railML 3 element etcsLevelTransition. It also includes information on the subelement switchToLevel. From this a wiki documentation shall be created.
ETCS Working group documen...The ETCS working group created a draft documentation for the railML 3 element etcsLevelTransition. It also includes information on the subelement switchToLevel. From this a wiki documentation shall be created.
ETCS Working group document: https://cloud.railml.org/f/89860 <br>
Wiki pages: https://wiki3.railml.org/wiki/IS:etcsLevelTransition and https://wiki3.railml.org/wiki/IS:switchToLevel3.3IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/527Add examples from ETCS working group documentation to wiki page CO:speedProfile2024-01-10T17:10:19+01:00TT CoordinationAdd examples from ETCS working group documentation to wiki page CO:speedProfileThe ETCS working group has created a documentation for speedProfiles. Only a small part of this documentation was taken over to the railML 3 wiki. In particular the extensive example was not included in the documentation. This should be ...The ETCS working group has created a documentation for speedProfiles. Only a small part of this documentation was taken over to the railML 3 wiki. In particular the extensive example was not included in the documentation. This should be corrected after a review by the ETCS working group.
Documentation in question: https://cloud.railml.org/f/89853
Wiki page: https://wiki3.railml.org/wiki/CO:speedProfile3.3CO CoordinationCO Coordinationhttps://development.railml.org/railml/version3/-/issues/526Review wiki documentation for IS:speedSection2024-01-10T17:10:40+01:00TT CoordinationReview wiki documentation for IS:speedSectionThe documentation for IS:speedSection was taken over from the documentation provided by Karl-Friedemann Jerosch from Siemens.
However crosschecking the content I noticed that the picture for the first example is missing. Also there is a...The documentation for IS:speedSection was taken over from the documentation provided by Karl-Friedemann Jerosch from Siemens.
However crosschecking the content I noticed that the picture for the first example is missing. Also there is a statement that a speedSection would be required to at least reference one speed profile when actually looking at the xsd that does not seem to be the case.3.3IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/525Propose Semantic Constraint introduced by ETCS group2024-01-10T15:09:56+01:00TT CoordinationPropose Semantic Constraint introduced by ETCS groupThe ETCS working group introduced a semantic constraint for balise groups documented in the provided documentation for the element baliseGroup and balise. The following wording was proposed:
>The element “baliseGroup” shall always use t...The ETCS working group introduced a semantic constraint for balise groups documented in the provided documentation for the element baliseGroup and balise. The following wording was proposed:
>The element “baliseGroup” shall always use the railML option “spotLocation” to define the balise group location on the topology.
Also a justification for the semantic constraint was brought forth:
>According to UNISIG-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 3.4.2.2.1 and UNISIG-040 (versions 2.3.0, 3.3.0 or 3.4.0) section 3.3.1.3, a balise group (represented by the railML element “baliseGroup”) shall be considered as point-shaped element without extension. The reference location of the balise group is the location of the balise with N_PIG=0.
A forum post should be created and if nobody disagrees the semantic constraint should be added to the wiki.3.3IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/524Improve Wiki documentation for IS:levelCrossingIS2024-01-09T16:19:15+01:00TT CoordinationImprove Wiki documentation for IS:levelCrossingISThe ETCS working group has prepared a document that could be used as a basis for an improved wiki documentation.
ETCS WG document: https://cloud.railml.org/f/82657 <br>
Wiki page to be improved: https://wiki3.railml.org/wiki/IS:levelCr...The ETCS working group has prepared a document that could be used as a basis for an improved wiki documentation.
ETCS WG document: https://cloud.railml.org/f/82657 <br>
Wiki page to be improved: https://wiki3.railml.org/wiki/IS:levelCrossingIS3.3IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/369Track length2023-10-05T15:18:48+02:00IS CoordinationTrack length## Description
In railML 3.1, each `<track>` element has to have at least one child element `<length>` for describing the operational or physical length of the track. It is suggested to remove this requirement and to make child element ...## Description
In railML 3.1, each `<track>` element has to have at least one child element `<length>` for describing the operational or physical length of the track. It is suggested to remove this requirement and to make child element `<length>` completely optional, because there are use cases that don't need the length information at all.
### Background
### Links
* Forum discussion:
* Christian Rößiger, 18.07.2019: [https://www.railml.org/forum/index.php?t=msg&th=678&goto=2224&#msg_2224]
* Trac ticket:
* #369
* Wiki documentation:
* (railML 2) IS:track: [https://wiki2.railml.org/index.php?title=IS:track]
* IS:track: [https://wiki3.railml.org/wiki/IS:track]
* IS:length: [https://wiki3.railml.org/wiki/IS:length]
## Proposed solution railML 3.2
Change child element `<track><length>` multiplicity from `1..*` to `0..*`
_For reasons of downwards compatibility, this change will be implemented with version 3.3, but marked obsolete in 3.2 already_3.3IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/329Extension of time reference in <state> (de: Erweiterung des Zeitbezugs in Ele...2022-05-09T17:53:47+02:00IS CoordinationExtension of time reference in <state> (de: Erweiterung des Zeitbezugs in Element <state>)## Description
The current implementation of <track><states><state> is missing a clear time reference. So far, it is only possible to use attribute @operatingPeriodRef to link from a state to an operating period. Main problem: it is not...## Description
The current implementation of <track><states><state> is missing a clear time reference. So far, it is only possible to use attribute @operatingPeriodRef to link from a state to an operating period. Main problem: it is not possible to model exact times for begin and end of a time span.
Task: Find a better solution for implementing explicit time reference in <state>.
### Background
Time aspects linked with <operatingPeriod> have an explicit timetable focus. The intended use in infrastructure domain would require a modification of the existing time concept (extension with hours, minutes and seconds). In order not to mix data model requirements, it is suggested to create a purely IS solution.
### Links
* Forum discussion
* Milan Wölke, 19.03.2018: [https://www.railml.org/forum/index.php?t=msg&th=559&start=0&]
* Trac ticket
* Wiki documentation
* IS:state states track: [https://wiki.railml.org/index.php?title=IS:state_states_track]
## Proposed solution in railML 2.4
Let's have a look at quite a simple example:
```
<track id="trc01" ...>
<states>
<state disabled="true" operatingPeriodRef="opp01" startTime="22:00:00" endTime="06:00:00" endDayOffset="1"/>
</states>
</track>
```
The track "trc01" is blocked from 28.04.2018, 22:00h CEST, until 29.04.2018, 06:00h CET. The state defines the time and the "offset" to correctly calculate the duration of the blocking. The referenced operating period defines the dates (xs:date) for the blocking.
In parallel to the infrastructure scheme extension the operating period concept need to be adapted: **the attributes <operatingPeriod><specialService>@startTime and @endTime shall be marked DEPRECATED** since they cannot be used from practical perspective.
## Proposed solution in railML 3.x
In railML 3.x the implementation shall be adapted: time aspects have to modelled intependently from infrastructure and timetable domain in order to ensure generic usaage.3.3IS CoordinationIS Coordinationhttps://development.railml.org/railml/version3/-/issues/100Mandatory stop at level crossing (de: Zwangshalt am BÜ)2022-05-09T14:47:42+02:00Deleted UserMandatory stop at level crossing (de: Zwangshalt am BÜ)## Description
There are sometimes local requirements to stop a train in front of a level crossing. Train staff has to protect the train run against the individual traffic on the street.
The German words for this szenario are: "Halt mi...## Description
There are sometimes local requirements to stop a train in front of a level crossing. Train staff has to protect the train run against the individual traffic on the street.
The German words for this szenario are: "Halt mit Sicherung durch Zugpersonal".
We can introduce a **stop** attribute in the **levelCrossing** element with a boolean type.
Additionally the timetable may mark this level crossing with a "non-commercial" stop (**ocp**).
### Links
* Forum discussion:
* Susanne Wunsch, November 2012: [https://www.railml.org/forum/index.php?t=msg&th=120&goto=444&#msg_444]
* Trac ticket system:
* Wiki documentation:
* SpeedChange: [http://wiki.railml.org/index.php?title=IS:speedChange]
## Proposed solution for railML 2.4
Mandatory stops shall be modelled using <speedChange>@mandatoryStop="true". Whether the mandatory stop is signalized or not, shall be indicated by using <speedChange>@signalised. Further, a <signal> shall be modelled to reference the <speedChange>:
<signal><speed><speedChangeRef ref=""/>
## Proposed solution for railML 3.x
In order to suit to all different types of use cases it is suggested to have an independent object for a railway vehicle stopping place, which can be referenced by different other elements.3.3IS CoordinationIS Coordination