| Re: [railML3] Extension of OPEquipment [message #2216 is a reply to message #2196] |
Fri, 05 July 2019 14:02   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Heidrun,
Am 29.05.2019 um 19:28 schrieb Heidrun Jost:
> [...]
> in railML 3's infrastructure there are defined elements in the complex
> type „OPEquipment“.
>
> Thales needs future extensions of switches and derailers: That means an
> element “ownsSwitch” and “ownsDerailer”.
> [...]
The child elements of <opEquipment> are all named <owns*> and they shall
be used to link the operational point with the infrastructure components
that are available there. Extending the concept with <ownsSwitch> and
<ownsDerailer> is not a big problem if there is a need for doing so.
The alternative solution would be to define a generic child element
<ownsInfrastructureElement>, which can be used to refer to any
(functional) infrastructure element.
@all: Which solution do you prefer? Thank you for your feedback!
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
|
|
|
|
Members
Search
Help
Login
Home
