On 23/04/12 14:39, Andrea Aime wrote: >> On Mon, Apr 23, 2012 at 3:41 AM, Ben >> Caradoc-Davies<[email protected]<mailto:[email protected]>> >> wrote: >>> On 20/04/12 20:44, Justin Deoliveira wrote: >>> Ideally we can do this in a way that doesn't fail when users (and oh there >>> will be a lot of them) reference the old xlink schema. >> >> Apparently OGC plan to take down the old schema. > > So what? Every well designed software around has its own copies of the OGC > schemas, only a fool would > assume the OGC schemas site is always up and always accessible (think running > in a restricted enviroment > for example, or just having a bad network connection day in an app that > regardless serves mostly > the internal network). > Plus lots of sofware is hard-coded to follow the old schemas. > This means we'll have to support both the new and the old
gt-xsd-core Configuration assumes that namespaces uniquely identify schemas. hashCode and equals are defined in terms of the namespace URI, which are the same ( http://www.w3.org/1999/xlink ) for the OGC and W3C XLink schemas. As soon as someone tries to combine schemas that use both the old and new XLink, and they will, Bad Things Will Happen. -- 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
