| Re: [railML3] missing @ruleCode? [message #2361 is a reply to message #2358] |
Fri, 28 February 2020 16:12   |
christian.rahmig
Messages: 439
Registered: January 2016
|
Senior Member |
|
|
Dear Torben,
I agree with Jörg: the content of railML 2 attribute @ruleCode seems to be better located in the interlocking domain of the signal since it refers to aspects the signal can show.
From my understanding, the information should be splitted in two aspects: the name/reference of the rule book (e.g. "Ril301" for DB's "Signalbuch") and the rule code of the signal in the referenced rule book (e.g. "SH2"). So, the structure of this information is very similar to the <designator> element, with the difference that a rule book is being referenced instead of an register and the entry is named rule code.
Best regards
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
