| [railML3.2]: AssetsForInterlocking [message #2468] |
Thu, 25 June 2020 07:31 |
Joerg von Lingen
Messages: 148
Registered: May 2011
|
Senior Member |
|
|
Dear all,
in the beta of railML3.1 interlocking there was a superior container for
assetsForInterlocking. However, this was removed as there was the opinion never
having more than one list of assets in one railML file.
There is one aspect which we did not consider - having more than one
infrastructure manager related to the area the file is covering. The
infrastructure managers shall be named in the common part and referred to from
the definition of specifics of that infrastructure manager, i.e. in
<specificInfrastructureManager>. The latter element has a child for reference to
valid lists of assets. So if we have more than one infrastructure manager to
consider for the area of that railML file then we need to have more than one
list of assets in that file. The split of listed assets will allow clear
relation between an asset and its manager.
The need of more than one infrastructure manager applicable arise in case of a
border station like "Brenner".
--
Best regards,
Joerg v. Lingen - Rollingstock Coordinator
|
|
|
|
Members
Search
Help
Login
Home
