On 23/04/12 14:43, Andrea Aime wrote: > Ben, look, if a change is necessary for some reason you have to go and make > revision n+1 of the standard > and deprecate the old standards, not change standards released years ago > under the software feet. > The idea that I can release a software compliant with version X of a spec in > 2005 and have it magically > become incompatible in 2012 is inconceivable, it's a if electrical sockets > could magically change their shape > overnight and all your equipment at home suddenly becomes unusable
I asked Simon Cox and he had this response (republished here with his permission): *** Begin quote of Simon Cox, footnote in [square brackets] is Ben *** Actually OGC has a careful definition of compatibility. It is defined at the XML document instance level. OGC implicitly reserves the right to change schemas as long as previously valid instances are still valid. In this case the argument is that since the xlink:XXX attributes have not changed and ditto the xlink namespace, then there is no real change. The sockets will not change shape overnight. Its more analogous to when the bills started coming from Synergy instead of Western Power [1]. If you carried on sending your cheque to Western Power your electricity would stop being supplied. *** End quote *** [1] In 2006 Western Australia broke up its state-owned electricity provider Western Power; Synergy is the new electricity retailer. Kind regards, -- Ben Caradoc-Davies <[email protected]> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
