Re: Infrastructure registers [message #1749 is a reply to message #1747] |
Tue, 03 April 2018 10:48 |
christian.rahmig
Messages: 436 Registered: January 2016
|
Senior Member |
|
|
Dear Dirk,
> I do only prefer railML.org to formally ensure that the enumeration values for the attribute "register=" can only be set to registers which are clearly intended to be used at exactly this occurrence of "register", namely at <ocp>s, not for that at <line>s.
Why do you want to have this clear separation?
Will it help to rename the attribute <ocp>@register into
<ocp>@ocpRegister? This may be useful in future if we extend the
designator concept to lines, too, having an attribute
<line>@lineRegister? Both attributes may point to registers listed in
the codelist Registers.xml.
Would this work for you?
Best regards
Christian
--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|