| Re: Defining data group "leadingVehicle" [message #1197 is a reply to message #1196] |
Tue, 28 September 2010 10:11   |
Carsten Weber
Messages: 27
Registered: November 2011
|
Junior Member |
|
|
"Joerg von Lingen" <joergvon_lingendd(at)t-onlinede> schrieb im Newsbeitrag
news:i6i65j$5qi$1(at)sifaivifhgde...
> 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.
>
I think there is a missunderstanding. The data group "leadingVehicle" should
include all the data which is relevant when the vehicle is used as a leading
vehicle. It is of course not possible to define in the vehilce data, that
this vehicle is a leading vehicle in the current formation of the train.
This is not the intention to define the "leadingVehicle" data group.
Best regards.
Carsten
|
|
|
|
Members
Search
Help
Login
Home
