| Re: Sequence of ocpTT elements [message #807 is a reply to message #805] |
Mon, 04 June 2012 17:58   |
Joachim Rubröder railML
Messages: 0
Registered: November 2019
|
|
|
|
Hello everybody,
> The index would have to be mandatory, and that's why I would not
> implement it as a metering index because possibly one would have to
> write fictuous data if the metering is unknown. Moreover, in theory
> (maybe someone uses railML for model trains?) there could be two ocptts
> with same meter...
> It seems as if this was a breaking change, so I would prefer leaving it
> for 3.0.
In order to avoid breaking changes, what do you think about introducing an
optional attribute "sequence" for the ocpTT in version 2.2 and declare
that it will become required for 3.0?
Kind regards,
Joachim
--
----== posted via PHP Headliner ==----
|
|
|
|
Members
Search
Help
Login
Home
