| new attribute on the vehicle element [message #539] |
Mon, 16 September 2013 17:28  |
horst.naujoks
Messages: 5
Registered: December 2012
|
Junior Member |
|
|
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
--
----== posted via PHP Headliner ==----
|
|
|
|
| Re: new attribute on the vehicle element [message #542 is a reply to message #539] |
Wed, 18 September 2013 00:46  |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
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
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
