[OSGeo-Discuss] OGC compliance of WMS client

2013-04-22 Thread Marco Lechner - FOSSGIS e.V.
Hi,

is a WMS-Client using REQUEST=getcapabilities instead of
REQUEST=GetCapabilities still in compliance with OGC standard
(VERSION1.1.1 as well as 1.3.0)? I don't think so, but I'm unsure.

Marco

-- 
+
FOSSGIS 2013, Die Konferenz für Open Source GIS mit OpenData und OpenStreetMap 
erstmals in der Schweiz!
12.-14. Juni, HSR, Rapperswil, http://www.fossgis.de/konferenz/2013/
+
FOSSGIS e.V.

die unabhängige Hilfe bei freier GIS-Software und freien Geodaten
http://www.fossgis.de
+

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] OGC compliance of WMS client

2013-04-22 Thread Sebastian Goerke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Marco,

it should be. There is a requirement within the WMS specification that
defines REQUEST=GetCapabilities to be supported by a WMS Server. But
it is not forbidden to have support for REQUEST=getcapabilities on
the server side, too. For WMS clients, this means, requests shall use
REQUEST=GetCapabilities because this is the only typing defined
within the specification.

Regards

Sebastian

- -- 
l a t / l o n  GmbH
Aennchenstrasse 19   53177 Bonn, Germany
phone ++49 +228 18496-0  fax ++49 +228 18496-29
http://www.lat-lon.dehttp://www.deegree.org


Am 22.04.2013 11:04, schrieb Marco Lechner - FOSSGIS e.V.:
 Hi,
 
 is a WMS-Client using REQUEST=getcapabilities instead of 
 REQUEST=GetCapabilities still in compliance with OGC standard 
 (VERSION1.1.1 as well as 1.3.0)? I don't think so, but I'm unsure.
 
 Marco
 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlF0/hIACgkQq1hDh4aJykIovACgzJ2X2cEm1tSMhzIAOv1/Vhvl
SokAnjpnEhjRB7x2/DaEITMdfXI2NWUr
=8t+v
-END PGP SIGNATURE-
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] OGC compliance of WMS client

2013-04-22 Thread Bart van den Eijnden
The WMS client should use GetCapabilities, parameter values are case-sensitive. 

Parameter names are not case-sensitive.

Best regards,
Bart

-- 
Bart van den Eijnden
OSGIS - http://osgis.nl

On Apr 22, 2013, at 11:04 AM, Marco Lechner - FOSSGIS e.V. 
marco.lech...@fossgis.de wrote:

 Hi,
 
 is a WMS-Client using REQUEST=getcapabilities instead of
 REQUEST=GetCapabilities still in compliance with OGC standard
 (VERSION1.1.1 as well as 1.3.0)? I don't think so, but I'm unsure.
 
 Marco
 
 -- 
 +
 FOSSGIS 2013, Die Konferenz für Open Source GIS mit OpenData und 
 OpenStreetMap erstmals in der Schweiz!
 12.-14. Juni, HSR, Rapperswil, http://www.fossgis.de/konferenz/2013/
 +
 FOSSGIS e.V.
 
 die unabhängige Hilfe bei freier GIS-Software und freien Geodaten
 http://www.fossgis.de
 +
 
 ___
 Discuss mailing list
 Discuss@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/discuss

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] OGC compliance of WMS client

2013-04-22 Thread Sebastian Goerke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

yes Andrea, but in my opinion it is not forbidden to have additional
support for the other alternative. You have to implement the case
sensitive KVP but it is not forbidden to implement the other additionally.

Regards

Sebastian

- -- 
l a t / l o n  GmbH
Aennchenstrasse 19   53177 Bonn, Germany
phone ++49 +228 18496-0  fax ++49 +228 18496-29
http://www.lat-lon.dehttp://www.deegree.org


Am 22.04.2013 11:25, schrieb Andrea Aime:
 2013/4/22 Marco Lechner - FOSSGIS e.V. marco.lech...@fossgis.de
 
 Hi,
 
 is a WMS-Client using REQUEST=getcapabilities instead of 
 REQUEST=GetCapabilities still in compliance with OGC standard 
 (VERSION1.1.1 as well as 1.3.0)? I don't think so, but I'm
 unsure.
 
 
 My understanding is that it's not. All OGC KVP protocols are based
 on the following (stated in the common ows spec): the key is case
 insensitive, the value is case sensitive
 
 So, something like ReQueSt=GetCapabilities is valid, but 
 request=getcapabilities is not
 
 Cheers Andrea -- == GeoServer training in Milan, 6th  7th June
 2013!  Visit http://geoserver.geo-solutions.it for more
 information. ==
 
 Ing. Andrea Aime @geowolf Technical Lead
 
 GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054  Massarosa
 (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39
 339 8844549
 
 http://www.geo-solutions.it http://twitter.com/geosolutions_it
 
 ---
 
 
 
 ___ Discuss mailing
 list Discuss@lists.osgeo.org 
 http://lists.osgeo.org/mailman/listinfo/discuss
 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlF1BFAACgkQq1hDh4aJykL7NACgo9QVxQUqlHe8p+SgGZC2QAVL
cAwAoIDemfjwpKnXaAiyaf7OQSda8CN2
=s/wV
-END PGP SIGNATURE-
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] OGC compliance of WMS client

2013-04-22 Thread Andrea Aime
On Mon, Apr 22, 2013 at 11:35 AM, Sebastian Goerke goe...@lat-lon.dewrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi,

 yes Andrea, but in my opinion it is not forbidden to have additional
 support for the other alternative. You have to implement the case
 sensitive KVP but it is not forbidden to implement the other additionally.


That's a grey area in the spec indeed. There are CITE tests checking that
the key
is treated as case insensitive, but I don't remember one checking for case
sensitive
values.

It would be interesting to see if there is anything in the WMS client CITE
test suite?
Was it made public, by the way?

Cheers
Andrea

-- 
==
GeoServer training in Milan, 6th  7th June 2013!  Visit
http://geoserver.geo-solutions.it for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

---
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] OGC compliance of WMS client

2013-04-22 Thread Marco Lechner - FOSSGIS e.V.

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

all those posts confirm my understanding. @sebastian, of course its not
a problem to make a server more tolerant (as many wms-servers are) to
make it working with non-compliant clients, but the client has to use
the correct request to stay in compliance. No dissent here.

Marco

Am 22.04.2013 11:35, schrieb Sebastian Goerke:
 Hi,

 yes Andrea, but in my opinion it is not forbidden to have additional
 support for the other alternative. You have to implement the case
 sensitive KVP but it is not forbidden to implement the other additionally.

 Regards

 Sebastian

 ___
 Discuss mailing list
 Discuss@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/discuss

- -- 
+
FOSSGIS 2013, Die Konferenz für Open Source GIS mit OpenData und
OpenStreetMap erstmals in der Schweiz!
12.-14. Juni, HSR, Rapperswil, http://www.fossgis.de/konferenz/2013/
+
FOSSGIS e.V.

die unabhängige Hilfe bei freier GIS-Software und freien Geodaten
http://www.fossgis.de
+

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlF1BvsACgkQq90xqWow83PQ1ACg4rY/VJR66H4c+pAxKFVS/pHg
gnIAoLvC+Vs2pem+zMhHYQ4yY7+2KBTZ
=6k+e
-END PGP SIGNATURE-

___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss


Re: [OSGeo-Discuss] OGC compliance of WMS client

2013-04-22 Thread Sebastian Goerke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hey,

CITE WMS Client test suite is available through the current Beta
release of TEAM Engine:

http://cite.opengeospatial.org/te2/

I think, the WMS Client test suite covers this.

Regards

Sebastian

Am 22.04.2013 11:43, schrieb Andrea Aime:
 On Mon, Apr 22, 2013 at 11:35 AM, Sebastian Goerke
 goe...@lat-lon.dewrote:
 
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
 
 Hi,
 
 yes Andrea, but in my opinion it is not forbidden to have
 additional support for the other alternative. You have to
 implement the case sensitive KVP but it is not forbidden to
 implement the other additionally.
 
 
 That's a grey area in the spec indeed. There are CITE tests
 checking that the key is treated as case insensitive, but I don't
 remember one checking for case sensitive values.
 
 It would be interesting to see if there is anything in the WMS
 client CITE test suite? Was it made public, by the way?
 
 Cheers Andrea
 

- -- 
l a t / l o n  GmbH
Aennchenstrasse 19   53177 Bonn, Germany
phone ++49 +228 18496-0  fax ++49 +228 18496-29
http://www.lat-lon.dehttp://www.deegree.org

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlF1CEIACgkQq1hDh4aJykJAMQCggxQ1s/T2I4bzDgWMAtNUMiNF
WFEAn3Ssn83AhyaY0j5pzCCXkxUCfACU
=nYw4
-END PGP SIGNATURE-
___
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss