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.
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.
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.
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.
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.
I’d like to backport the change to 2.7.x if that’s OK with you guys.
If so, I’ll fix a new PR.
I started to look at the swap to xlink 1.1 and it seems that Justin already started abit (https://github.com/geoserver/geoserver/commit/ec437677677deadb3501f16dbf6e2309ff77a9f9).
The new xsd was avaliable in gs-main but not used by any other xsd what I could see.
I was able to swap everywhere but got held up by WFS-tests failing.
I guess geotools needs to swap at the same time to match but I didn’t get much further due to not beeing able to build geotools (an artefactory seems to be down).
Has there been work/thoughts on this swap before?
I’m also curious why there are three ways to import xlink throughout the code base.
I guess referring to it locally will make it possible to build and use without internet but perhaps the same xlink.xsd could be referenced?
If so, shouldn’t all references be local?
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.
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.
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.
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.
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.
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.