-------- Original Message --------
Subject:        Re: [Qgis-developer] [Qgis-user] LIZMAP ERROR PRINT - HELP!
Date:   Wed, 11 Jun 2014 10:57:34 +0200
From:   Marco Hugentobler <marco.hugentob...@sourcepole.ch>
To:     qgis-develo...@lists.osgeo.org



Hi

I agree that most clients will not be affected by a change in the
GetCapabilities response. However, the release is quite close, therefore
it will be good to not change the capabilities document now.

After release, we might remove the additional elements from
GetCapabilities. When GetProjectSettings has been introduced, we did not
change it immediately to give clients a bit time to catch up.

Speaking about OGC compliancy in general: I heard from developers in
other projects that probably each product needs small tweaks before
passing the compliance tests (and not only the validation of the
capabilities response is tested). So if someone wants to look into that
and provide (constructive) feedback, that will be greatly appreciated.

Regards,
Marco

On 11.06.2014 10:25, Jürgen E. Fischer wrote:
Hi Andreas,

On Wed, 11. Jun 2014 at 08:39:11 +0200, Andreas Neumann wrote:
It is true that in some cases we need to improve to be more standards
compliant. This is a group effort. Everybody can contribute. Removing
GetPrint from GetCapabilities, or implementing in a standard compliant way,
would help. We could still have it listed in GetProjectSettings.
It's disputable if the current way is not compliant.

Changing that might break clients that query the capabilities for the presense
of GetPrint if we'd applied a (less-disputable ;)) compliant prefix (ie.
GetPrint to qgis:GetPrint).

Note that this would only apply to the name of the operation element in
capabilities, the actual request wouldn't need to changed.

So it's unclear to me if there are actually any clients that would break.

At least some already use GetProjectSettings, others might just imply GetPrint
without checking GetCapabilities - both groups wouldn't be affected.

The clients that check capabilities would just need to look for qgis:GetPrint
instead or alternatively of GetPrint - and that should just be a trivial
change, when 2.4 is deployed.

Also there are probably not that many clients around that actually use
GetPrint.


Jürgen



--
Dr. Marco Hugentobler
Sourcepole -  Linux & Open Source Solutions
Weberstrasse 5, CH-8004 Zürich, Switzerland
marco.hugentob...@sourcepole.ch http://www.sourcepole.ch
Technical Advisor QGIS Project Steering Committee



_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user

Reply via email to