Home » railML newsgroups » railML.infrastructure » [railML3] missing @ruleCode? (railML3, @ruleCode)
Re: [railML3] missing @ruleCode? [message #2358 is a reply to message #2345] Fri, 28 February 2020 06:33 Go to previous messageGo to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 87
Registered: March 2016
Member
Hi,

from the brief description in wiki I am not sure about the use of @ruleCode. As it seems to be more functional related I
would see it more in SignalIL than SignalIS. In railML2 the attribute is just a plain string. However, the question is,
whether each signal will have its individual code or there is a limited list for an IM to choose from?

Can you explain your using of the attribute a little bit more?

Regards,
Jörg von Lingen - Interlocking Coordinator
Torben Brand wrote on 25.02.2020 11:37:
> It seems that the very practical attribute @ruleCode (in
> railML2) describing the type of signal in a national
> specific unique way is missing in railML3?
>
> The type can be defined in railML2 (by @type and @function)
> and in a more detailed way in railML3 (by the used sub
> elements) in a railML generic way. But the national specific
> way needs also to be modelled. Both from an asset
> perspective (a home signal looks different in Germany than
> in Norway) and in an interlocking perspective. As the rules
> for a home signal can be different.
>
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3] Loading gauge profile
Next Topic: [railML3] Identifiers in Infrastructure
Goto Forum:
  


Current Time: Fri May 03 11:54:14 CEST 2024