| Re: Some small changes, wishes and recommendations for RailML2 timetableschemes [message #811 is a reply to message #703] |
Mon, 17 September 2012 15:35   |
Joachim Rubröder railML
Messages: 0
Registered: November 2019
|
|
|
|
Hi Dirk,
>
> 9c) timetableTypes.aCirculation added:
> <xs:attribute name="vehicleIdx" type="xs:nonNegativeInteger"/>
> <xs:attribute name="groupIdx" type="xs:nonNegativeInteger"/>
> (group and vehicle number of a run or job inside of the circulation)
>
> Reason: This attribute is completely redundant because the information can
be >recreated by counting links (nextBlockâ¦) which link to earlier days
(vehicleIdx) or to >lower vehicles number (groupIdx). Nevertheless, we have
been asked by other users >to provide these values to get the data easier and
to avoid misunderstandings (skipping >of vehicles during standstill).
>
There is an open Ticket http://trac.assembla.com/railML/ticket/75 for this
issue, that could be implemented for version 2.2.
But we discussed the naming conventions internally and are not willing in
introducing new types of "Idx"-elements. We would prefer instead:
<xs:attribute name="vehiclNumber" type="xs:string"/>
<xs:attribute name="vehicleGroupNumber" type="xs:string"/>
Would this be OK for your purpose?
Kind regards...
Joachim
--
Joachim Rubröder
Schema Coordinator: railML.timetable
--
----== posted via PHP Headliner ==----
|
|
|
|
Members
Search
Help
Login
Home
