Ok. The clients problem is not the version but that different versions are imported at different places and both are declaring targetNamespace=" http://www.w3.org/1999/xlink";. We can change to either schemas/xlink/1.0.0/xlinks.xsd (xlinks.xsd v3.0b2 2001-07) or schemas/gml/2.1.2/xlinks.xsd (xlinks.xsd v2.1.2 2002-07) and the client is happy. The difference between these versions is only that the "use" attribute is added on attribute-nodes. So, the problem is not the version but the mix of versions.
The OGC-link says that http://www.w3.org/1999/xlink.xsd should be used and that differs from the versions above. I'd like to change the import reference in schemas/gml/2.1.2/geometry.xsd to target the xlinks.xsd in the same folder. I can provide a PR if it would likely be accepted. The question of complying to OGC is another issue. On Fri, Aug 21, 2015 at 2:00 PM, Jody Garnett <[email protected]> wrote: > I think the OGC changed some of this stuff, and I am not sure which one > geoserver uses. > > Have a look at http://www.opengeospatial.org/blog/1597and let me know if > it agrees with your experience. It could be either your client or geoserver > needs to transition to official w3c xlink 1.1 Schema. > On Fri, Aug 21, 2015 at 6:56 AM Olle Markljung <[email protected]> > wrote: > >> Hello >> >> >> >> We're experiencing problems with XSD validation from a WFS-client when it >> is trying to use the info from DescribeFeatureType. >> >> I.e. >> http://localhost:8080/geoserver/topp/wfs?service=WFS&version=1.0.0&request=DescribeFeatureType&typeName=topp%3Astates >> >> >> >> The problem seems to be different includes of xlinks.xsd. >> >> http://localhost:8080/geoserver/schemas/gml/2.1.2/feature.xsd imports >> xlinks from the same catalog >> http://localhost:8080/geoserver/schemas/gml/2.1.2/xlinks.xsd. >> >> It also includes geometry.xsd ( >> http://localhost:8080/geoserver/schemas/gml/2.1.2/geometry.xsd) >> >> This file imports xlinks from "../../xlink/1.0.0/xlinks.xsd" ( >> http://localhost:8080/geoserver/schemas/xlink/1.0.0/xlinks.xsd) >> >> >> >> These two separate imports makes the WFS-client go bananas. >> >> Likely due to the fact that they are of different versions. >> >> >> >> If we alter geometry.xsd ( >> https://github.com/geoserver/geoserver/blob/master/src/main/src/main/resources/schemas/gml/2.1.2/geometry.xsd#L10) >> >> >> to import xlinks.xsd from the same catalog as in feature.xsd everything >> is peachy. >> >> >> >> Does anyone know why two different versions are imported? >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Geoserver-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > -- > -- > Jody Garnett >
------------------------------------------------------------------------------
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
