Better namespace encoding for app-schema GML 3.2 WFS responses
--------------------------------------------------------------
Key: GEOS-4535
URL: http://jira.codehaus.org/browse/GEOS-4535
Project: GeoServer
Issue Type: Improvement
Components: Application schema
Affects Versions: 2.1.x
Reporter: Ben Caradoc-Davies
Assignee: Ben Caradoc-Davies
Fix For: 2.1.x
Improve namespace encoding by adjusting the effect ChangeNumberOfFeature.xslt has on an encoded response.
-------- Original Message --------
Subject: Re: [Geoserver-users] GML 3.2 Support (GSIP 50)
Date: Thu, 05 May 2011 10:16:39 +0800
From: Ben Caradoc-Davies
To: arif.shaon
CC: andrea.aime, geoserver-users@lists.sourceforge.net <geoserver-users@lists.sourceforge.net>
Aha! I saw this too, but it is not as bad as you might think at first. 
If you look further down in your response, you should see that each
wfs:member element redefines xmlns:gml and xmlns:wfs; this is perfectly
legal if not moral! XML namespaces are lexically scoped, and can be
redefined on any element. The result I see in my unit test
(app-schema-test Gsml30WfsTest.testGetFeatureValid) is is schema-valid
against GeoSciML 3.0rc1, a GML 3.2.1 application schema.
This unexpected (but valid) namespace behaviour is the result of our use
of a shared XML transformation that supports both WFS 1.1 and WFS 2.0
FeatureCollection. I would like to change this in the future, on the
principle of least surprise.
Kind regards,
Ben.
On 05/05/11 00:06, arif.shaon wrote:
Hi Ben,
I have tried this against very simple profile of GML 3.2 and it seems to work. However, I have noticed that the namespace uri for GML in the WFS response document still appears to be the one for GML3.1/2 rather than GML3.2.
Cheers
Arif-----Original Message-----
From: Ben Caradoc-Davies
Sent: 29 April 2011 08:15
To: Shaon, Arif (STFC,RAL,ESC)
Cc: andrea.aime geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] GML 3.2 Support (GSIP 50)Arif,
today I committed support for GML 3.2 in app-schema to trunk. It should
be available in the next nightly build. Note that this is very new and
you may be the first one to try to use it.To access a GML 3.2 app-schema instance, you need to select the "gml32"
OutputFormat in a WFS 1.1 request, for example, by appending
outputformat=gml32 to a GET URL. DescribeFeatureType requests are just
plain WFS 1.1.We would be very interested to know how well it works for you.
Kind regards,
Ben.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira