| Re: [railML3] Suggested extension for RBC [message #2442 is a reply to message #2438] |
Tue, 19 May 2020 09:29   |
Jörg von Lingen
Messages: 87
Registered: March 2016
|
Member |
|
|
Hi,
I would see the suggested new element <radioBlockCentre> in the interlocking
part of railML as it is a more functional item of train control which has not a
representation at a particular track.
If derived from class "SystemAsset" it would inherit @id for any railML internal
referencing (not NID_RBC), <designator> and <assetName>. The latter one can be
used to store the real name even in different languages. In that way it would be
in parallel to the elements of <controllers> (HMI, TMS) and <signalboxes>
(interlocking module).
The proposed additional attributes (NID_C, NID_RBC, NID_RADIO, NID_MN) can be
attached to the <radioBlockCentre> element. However, the naming should be more
reflect their function than the ETCS variable name. In XML they would be of type
NonNegativeInteger but the limitations as coming from ETCS spec is not that
straight forward. Are there any suggestions as to how model this?
The proposed element <radioBlockCentreBorder> I would see as a new entry in the
list <assetsForInterlocking>. Although there is the issue of defining a position
on a netElement for it. If placed only in IS part the referencing between IS and
IL elements might become a little bit weird, refer post "[railML3]: Referencing
between IS and IL".
Best regards,
Joerg v. Lingen - Interlocking Coordinator
Am 14.05.2020 um 15:11 schrieb Henrik Roslund:
> Hello,
>
> Very good inputs, Karl.
>
> I agree with your suggestions, but I would like to have an
> optional attribute connected to "NID_RBC", "RBC Name", and
> there is the real name of the RBC written, e.g. "Gotthard".
>
> Unfortunately doesn't the link work for me.
>
> Kind regards,
>
> Henrik Roslund
> Senior Consultant ETCS, MIRSE
> TÜV SÜD Schweiz AG
>
> Member of the Workgroup «ETCS Track NET»
|
|
|
|
Members
Search
Help
Login
Home
