Hi Andrea, You bring up some valid points that should be fixed/addressed. Obviously this can be fixed.
However, I would advise to not make a big fuss about this issue and stay pragmatic and focused. Open individual bug reports for each of the non-compliance behavior and back it up with references to the WMS spec. Don't put more than one issues in the bug report but create several reports for each issue. This way it is easier to address and discuss. I can maybe help to understand how the GetPrint command ended up in the GetCapabilities response. When QGIS Web Client was developed there was a print command lacking. Since WMS did not provide a way to point to certain pre-defined layout and specify the necessary parameters we decided to extend the WMS capabilities of QGIS server. The spec (at least in the days of WMS 1.1 when this was added) was not very clear about these extensions. Later, we introduced a request called "GetProjectSettings", which actually is an extended "GetCapabilities" request - here we can now extend according to our requirements without having to violate other standard requests. The GetProjectSettings response contains a lot of "non-standard" information that is used between QGIS server and QGIS web client - things like layout information, widget information, data types, etc. Now that the GetProjectSettings command exists we could actually remove the GetPrint from the GetCapabilities response or we could try to be standard-compliant by using an extension mechanism. It is not true that QGIS people do not care about standards - but it is a lot of effort to make sure everything really complies properly and works interoperable. Even if QGIS would be fully standards compliant it does not necessarily means it is fully interoperable as the specification does not answer everything. You can help to make QGIS server more standards compliant, but you have to properly document this (with links to specifications) and find a developer willing to work on this. I am quite confident that these issues can be resolved. Andreas Am 08.06.2014 12:55, schrieb Jürgen E. Fischer: > Hi Andrea, > > On Sun, 08. Jun 2014 at 13:15:51 +0200, Andrea Peri wrote: >> The last response of Jef in the ticket explain clearly what it the strateguy >> of qgis.The important is tobe compatible with other software GS. Thie mean >> the QGIS-server don't metter for real wms compatibility and interoperability. > > I not the strateguy of qgis. I just speak for myself. So don't mistake > anything I say with what the "qgis group" is up to. > > BTW the other ignorant guy you have apparently been talking to doesn't speak > for the group either. But it would still be nice if you wouldn't attribute his > statements to me. ;) > > Sorry for the noise. I'm not constructive enough to get a fruitful discussion > going, so I'll move on to other tickets. > > > JÃrgen > > _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer