| Obligational stop (was: More detailed 'speed change' definitions) [message #444 is a reply to message #322] |
Mon, 12 November 2012 13:17   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Dirk Bräuer <dirkbraeuer(at)irfpde> writes:
>> ** How to define an "obligational stop" where all or only certain trains
>> have to stop prior going on with the same speed aspect as before?
>> ** Could this be an attribute of the speedChange element?
>
> That is an issue I would like to see solved with RailML 2.2. I would
> prefer either such an attribute (obligational stop of head/end of
> train). The other, possible “cleaner” but also more complex solution
> would be to define an infrastructure element “obligationalStop”
> (independently from speed changes).
>
> I think the attribute at a speedChange will be ok.
This issue is implemented with the following commit:
http://trac.assembla.com/railML/changeset/456
The following attributes are added to the 'speedChange' element.
<xs:attribute name="mandatoryStop" type="xs:boolean">
<xs:annotation>
<xs:documentation>specifying the speedChange as a mandatory stop point, e.g. in front of a level crossing</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="mandatoryBraking" type="xs:boolean">
<xs:annotation>
<xs:documentation>specifying the speedChange as a mandatory braking point, e.g. in front of a descending slope</xs:documentation>
</xs:annotation>
</xs:attribute>
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
