| Re: [railML3] missing @ruleCode? [message #2369 is a reply to message #2363] |
Wed, 04 March 2020 19:35   |
Thomas Nygreen
Messages: 68
Registered: March 2008
|
Member |
|
|
Hi,
@ruleCode originatedas a way to include the national code of a stop post (and then more generally any signal). The given examples seem to me to be more about identifying the exact type of signal (e.g. to be able to look up its physical appearance), rather than its aspects. For boards there is little difference, as they have only one aspect. To provide an example, there are multiple light signal types (in any country) capable of showing the aspects "closed", "proceed" and "limitedProceed". In railML3 we can separate between some of these using <signalConstruction>@type and <signalIL>@function, but there may still be more than one type matching the @type and @function. How do you specify which specific type of signal it is? Another example is boards, where IL does not provide much, but where signalbooks usually have specific codes for each kind of board.
Best regards,
Thomas
Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
