| last open points for speedProfiles in railML 2.2 [message #368] |
Sat, 22 September 2012 11:12  |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Dear railML users,
the release of the new version railML 2.2 is approaching...
One big issue of the new schema is the implementation of speed profiles
that will be referenced by the <speedChange> elements. Since speed
instructions depend on a lot of parameters resulting directly from the
train (e.g. braking configuration, load), from the track's geography
(e.g. slope) or from operation (e.g. route of the train), the
<speedProfile> element includes a lot of attributes. The details can be
found in trac ticket [1].
At the end of this trac ticket few open points are listed and I want to
put these open points here into the forum and ask for your comments:
1. What to do with the current "trainCategory" attribute in <speedChange>?
Marking as "deprecated" is an easy way, but there are nevertheless
international train categories for lines, e.g. "NC_Train" of the ETCS
domain. Therefore I suggest to introduce a new attribute
"etcsTrainCategory" and mark the other one as deprecated.
2. What to do with the current "status" attribute in <speedChange>?
It is possible to define a state of validity for a speed restriction
in the sense of 'planned' or 'active' or ... However, I think, it is
better to put this information inside the <speedProfile> instead of the
<speedChange>.
3. How to define the "blocking of a track"?
The speed restriction vMax="0" within a <speedChange> does not imply
a blocking of a track. In particular, it may be possible to order a
train to enter a blocked track with a speed of 25 km/h. Therefore, I
suggest to add another attribute "blocked" of type boolean within the
<speedProfile>.
4. 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?
A maximum speed vMax="0" within a <speedChange> can be interpreted
as a mandatory stop. If we want to qualify the information of vMax="0",
we need to add another attribute to the <speedChange> element, e.g.
"specialPurpose". Its enumeration values like 'mandatoryStop' or
'mandatoryBraking' may cover all cases of obligational stops.
[1] https://trac.assembla.com/railML/ticket/41
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
