Home » railML newsgroups » railml.rollingstock » EU vehicle identification
EU vehicle identification [message #1207] Sat, 05 February 2011 14:18 Go to next message
Joerg von Lingen is currently offline  Joerg von Lingen
Messages: 59
Registered: May 2011
Member
Hello users,

it was suggested to add additional elements at <classification> for the vehicle
identification described by EU paper DV51EN01 annex P or UIC 438. A sample would
like the following:
....
<classification>
<vehicleIdentifications>
<vehicleIdentification typeOfVehicle="00" registeredCountry="00"
technicalCharacteristics="0000" serialNumber="000" checkDigit"0"
countryCode="xxx" vehicleKeeperMarking="xxxxx">
</vehicleIdentification>
<vehicleIdentification typeOfVehicle="00" registeredCountry="00"
technicalCharacteristics="0000" serialNumber="000" checkDigit"0"
countryCode="xxx" vehicleKeeperMarking="xxxxx">
</vehicleIdentification>
</vehicleIdentifications>
</classification>
....
As the identification with a particular serial is limited to one vehicle the
element may occur several times within the description of vehicle class.

The alternative proposal would be to add only the element
<vehicleIdentification> at <operator> as there is some operator dependent
information encoded.

It is also questionable, whether the splitting of national block (5.-11. digit)
into technical charcteristics (4 digits) and serial (3 digits) is always used
that way?

--
Mit freundlichen Grüßen/Best regards,
-------------------------------------
Jörg von Lingen
Re: EU vehicle identification [message #1208 is a reply to message #1207] Thu, 24 February 2011 12:48 Go to previous message
Carsten Weber is currently offline  Carsten Weber
Messages: 26
Registered: November 2011
Junior Member
Dear Jrg,

thanks for your suggestion to define a detailed vehicle identification.

> it was suggested to add additional elements at <classification> for the
> vehicle
> identification described by EU paper DV51EN01 annex P or UIC 438. A sample
> would
> like the following:

We just have to make sure that this systems works also outside of TSI for
which the named paper is defined.

> ...
> <classification>
> <vehicleIdentifications>
> <vehicleIdentification
typeOfVehicle="00"
-> This attribute should be taken out of a single vehicle identification.
The type of vehicle is defined an it is independent from each data set.

registeredCountry="00"

-> This attribute should get a name including UIC-number or something like
that. There is alsready something defined at the infrastructure data.

> technicalCharacteristics="0000"
-> As it is named in the UIC 438. Maybe it should be explained as "series"
inside of the documentation. Basetype for the attribute should be a non
negative integer. The limitation up to four digit is only done for
EU-vehicle identification.

> serialNumber="000"
-> In addition to the number it should also be possible to give the vehicle
a name as an unlimited string like "Saxonia".
-> It would also be helpful to define a serialBegin and serialEnd to be able
to summarise several vehicles in one entry of vehicle identification. So
there should be a constrain which says either (serialNumber or vehicleName)
or (serialBegin) and a second one which says serialBegin requires an
serialEnd-attribute.

> checkDigit"0"
-> It's ok. ;)

> countryCode="xxx"
-> A link in the documentation to the defined countryCodes would be helpful.

> vehicleKeeperMarking="xxxxx">
-> A vehicleOperator would also be useful.

So the operator-dataset includes only the information of a begin and end
date of this vehicle data set at this operator. Maybe this information could
also be moved to the vehicle Identification.

> As the identification with a particular serial is limited to one vehicle
> the
> element may occur several times within the description of vehicle class.

As written above my/our suggestion would be two additional attributes
seriesBegin and seriesEnd to define more than vehicle inside of the vehicle
identification.
>
> The alternative proposal would be to add only the element
> <vehicleIdentification> at <operator> as there is some operator dependent
> information encoded.
>
My suggestion is to kepp it outside of operator and mark operator as
out-of-date to be taken away in version 3.0.

> It is also questionable, whether the splitting of national block (5.-11.
> digit)
> into technical charcteristics (4 digits) and serial (3 digits) is always
> used
> that way?

So they should be defined as none negative integer.
Users have to take care whether they will read a TSI-vehicle-identification
or any other way of defining vehicle identification.

Best regards.

Carsten
Previous Topic: Tilting attributes - roll compensation
Next Topic: Extension of "auxiliaryBrakes"
Goto Forum:
  


Current Time: Mon Aug 21 10:27:16 CEST 2017