| railML3: vehicle vs. vehiclePart - needed attributes [message #2520] |
Tue, 25 August 2020 05:32  |
Joerg von Lingen
Messages: 149
Registered: May 2011
|
Senior Member |
|
|
Dear all,
in the previous post I have introduced the definition of a single vehicle which resulted in the need of having
vehicleParts. Now we have to determine which of the attributes (or child elements) formerly used for vehicle shall be
part of the vehiclePart.
It is clear that attributes like "speed" or "loadingGauge" or "trackGauge" will not vary for the individual
vehicleParts. Thus they shall remain at vehicle.
There might be attributes like "length" or "mass" which may be used for vehicleParts and vehicle. Even the numbering
might be used for both levels.
There are attributes like passenger seats which are clearly at vehicleParts only.
Finally we have attributes like "axleLoad" which vary in some cases for the vehicleParts and are needed to be specifyied
per vehiclePart.
So please tell me your needs, which information has to be at vehicle level and which per vehiclePart.
--
Regards,
Jörg von Lingen - Rollingstock Coordinator
|
|
|
|
Members
Search
Help
Login
Home
