Home » railML newsgroups » railml.rollingstock » Re: new attribute on the vehicle element
Re: new attribute on the vehicle element [message #1219 is a reply to message #1218] Mon, 23 September 2013 13:07 Go to previous messageGo to previous message
Joerg von Lingen is currently offline  Joerg von Lingen
Messages: 148
Registered: May 2011
Senior Member
Dear all,

we had already discussed the issue of UIC numbers for vehicles. The major point of discussion was whether the number
will stay with the vehicle during its entire lifetime or changes with the owner/operator. There we couldn't reach
clarification.

This question was of importance as to where storing the UIC-number in the tree. I would prefer to place it under
Classification/Operator because we then have a clear information of the time period the number is assigned to that
vehicle. At the moment the string element <operatorClass> can be used in that sense. However, I woul go for a more
stringent definition which shall be then cover all types of vehicles (wagons and loco).

I will try to provide a proposal on this within the next weeks.

Best Jörg.

Susanne Wunsch wrote the following on 18.09.2013 00:46:
> Hello Horst,
>
> I move the request to the rollingstock group. The 'vehicle' element is
> part of the rollingstock sub-schema. I'm sure, Jörg (RS coordinator)
> will provide some feedback. He already worked on parts of the UIC wagon
> classification.
>
> horstnaujoks(at)qnamiccom (Horst Naujoks) writes:
>
>> Dear all,
>>
>> I'm a developer at Qnamic AG
>> ( http://http://www.railml.org//index.php/entwickler.html?show =35) and
>> we using RailML in different contexts in our products.
>>
>> I'd like to submit the following extension to the railMl
>> infrastructure schema:
>>
>> The element <vehicle> should be completed by an new optional attribute
>> 'uicVehicleNumber'. The whole purpose of this number is documented
>> here: http://en.wikipedia.org/wiki/UIC_wagon_numbers. The new
>> attribute supposed as an explicit supplement to the existing
>> id/code/name attribute facility. It should support a better data
>> exchange in systems which share this number.
>>
>> Today, we already employ this attribute by the usage of a schema
>> extension (as an 'any' attribute) and of course we'd like to replace
>> this construct by an explicitly specified attribute.
>>
>> Kind Regards,
>>
>> Horst Naujoks
>
> Crosspost & Followup-To: railML.rollingstock
>
> Kind regards...
> Susanne
>
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Distinguish vehicles by vehicle category
Next Topic: power attribute in vehicle/engine/propulsion
Goto Forum:
  


Current Time: Sat May 04 06:09:16 CEST 2024