| Re: SpeedChange : Protection system reference [message #342 is a reply to message #336] |
Thu, 05 July 2012 15:47   |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Pierre and Christian,
we should not try to implement all cables or such which are in practice in
the RailML or at least in Infrastructure scheme of RailML. Rather, we
should as ourselves which function such a cross-reference should provide:
If there is a real and general function, we should implement the link. If
there is no objective or general function, we should leave it as a special
local case for adoption in local sub-schemes of RailML.
We should also consider the actual case as a property of RailML
Interlocking Scheme.
In my opinion, the speed change sign and the <trainProtectionElement> have
independent functions. (Of course they have the same origin or reason why
they are there but: If there would be a speed change without
<trainProtectionElement> or vice versa, each one would have to function
alone.)
Both should be implemented as single elements may be with the same
position (meter). A reading software can possibly expect that there should
be a <trainProtectionElement> at or near the position of a <speedChange>
but there is no _general_ (internationally accepted) necessity for that.
But if you decide to make that cross-reference anyway, as an optional
attribute - what objection should one have?
With best regards,
Dirk.
---
Am 05.07.2012, 06:12 Uhr, schrieb Christian Rahmig
<coord(at)infrastructurerailmlorg>:
> Hello Pierre,
>
>> In the Belgian railway, the speedChanges could be equipped with a
>> protection system (crocodile).
>>
>> We suggest to add a reference from <speedChange> to the
>> <trainProtection>
>> element.
>>
>> [de: Es wird ein Attribut benoetigt, welches vom <speedChange> zum
>> <trainProtectionElement> (BE: 'Krokodil' / DE: Gleismagnet) verweist.]
>
> This reference from a <speedChange> to a <trainProtectionElement> is a
> useful innovation, which may be implemented with railML 2.2, because the
> reference attribute will be optional. However, is it really the
> <speedChange> that needs to refer to the <trainProtectionElement> or is
> it the signal, which is connected to the magnet or the Belgian crocodile?
>
> Any comments appreciated...
>
> Regards
>
> ---
> Christian Rahmig
> railML.infrastructure coordinator
--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/
|
|
|
|
Members
Search
Help
Login
Home
