| Re: Defining data group "leadingVehicle" [message #1196 is a reply to message #1195] |
Sun, 12 September 2010 16:12   |
Joerg von Lingen
Messages: 148
Registered: May 2011
|
Senior Member |
|
|
On 03.09.2010 14:29, Carsten Weber wrote:
> Dear RailML-Users,
>
> to define vehicles some informations need to be filled in only for leading
> vehicles.
> So at the moment some data is grouped in monitoring as a child of engine
> data.
> It would be useful to create a new element "leadingVehicle" at the same
> level like wagon, engine and classification.
> So the information of driversCab, etcs, nationalSystem, trainRadio,
> otherEquipment and the accousticSignaller could be arranged there.
>
There are quite some situations taking advantage of the proposed new
substructure "leadingVehicle". However, it violates the principles of data
hierarchy used in rolling stock data.
It is the intention to provide a data structure for the technical data and
characteristics of any rolling stock independent of the particular use case of a
train running in the network. "leadingVehicle" is an expression of such a
particular use case as a vehicle becomes a leading one only on a particular
train configuration.
The original idea of "engine" was put in all data of the active parts
(propulsion etc) one would find in any loco. The child "monitoring" is, however,
morphodite being in locos and non-driven cars with drivers cab.
The "wagon" shall take all data related to the interior and its equipment, which
is not related to the propulsion.
The question is whether such a radical structure change is really useful?
--
Mit freundlichen Grüßen/Best regards,
-------------------------------------
Jörg von Lingen
|
|
|
|
Members
Search
Help
Login
Home
