On 24 Nov 2008, at 14:07, Frederik Ramm wrote:
Hi, Stefan de Konink wrote:Frederik Ramm wrote:Alternatively, we could switch from 0.5 to 0.5.1 tomorrow, with the only change being newly introduced version numbers in the XML. That would probably make the saved changes 0.6 compatible then. It might break a few applications if we do this but only those who don't do proper XML parsing and people who write them are asking for trouble anyway. *What about introducing an API server that is able to proxy 0.6 using 0.5request? Thus having a compatibility layer?My suggested Perl script is already on the fringe; a compatibility APIwould be asking for trouble. I can think of a number of scenarios whereit would break in a really non-helpful way. It would also send out the (wrong) message that you can painlessly continue not caring for 0.6...
osmosis already has a --migrate task that may partially work, however as it doesn't fetch the version numbers, so probably shouldn't be used for an uploads.
Shaun
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
