Home » railML newsgroups » railml.timetable » Sequence of ocpTT elements
Re: Sequence of ocpTT elements [message #809 is a reply to message #808] Thu, 07 June 2012 16:01 Go to previous messageGo to previous message
Andreas Tanner is currently offline  Andreas Tanner
Messages: 52
Registered: March 2012
Member
Dear everyone,

I would vote for Joachim's proposal to avoid an - even if only formal -
incompatibility between minor versions.

--Andreas.

Am 05.06.2012 17:15, schrieb Dirk Bräuer:
> Dear Joachim and Andreas,
>
>> 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?
>
> I would of course welcome it.
>
> I would also not see any problem in declaring it required from 2.2.
> Anybody who implements 2.2 has to change at least something (the
> namespace location?). It should not be demanded too much to add such a
> simply counting attribute. So if we consider it being required we can -
> from our side - do it from the beginning.
>
> If there would be a "sequence" attribute in 2.2 - whether required or
> not - we would always write it from the first release of 2.2 and also we
> would require it on input. There is no reason to move forward the
> programming effort - it will not become easier.
>

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Datatype for distance in sectionTT
Next Topic: dayOffset vs. arrival/departureDay
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri May 17 09:14:07 CEST 2024