The WFS 2.0 specification has been released:
http://www.opengeospatial.org/standards/wfs
--
Ben Caradoc-Davies
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
-
I wouldn't care about 1.0 until we have a very solid 1.1, and even then
I'm not sure. Would rather let WFS 1.0 fade out as 1.1 should be the
bare minimum these days and 2.0 is getting closer.
Other than that, sounds like a plan to me.
Gabriel
On Thu, 2010-11-04 at 21:53 +0100, Roy Braam wrote:
>
Ok these are the steps (very global) that i think is the best way to success:
- Copy the WFS to a WFS-NG unsupported module (free to do some good refactor)
- Let wfs 1.1 work with super ContentDataStore
- Rebuild the wfs 1.0 version (according the wfs 1.1)
Hmmm, a bit to global
Roy
Hi all,
Chris Holmes schrieb:
> Wow, it'd be awesome to have a group of people taking this on.
>
> After things get going there's one improvement you should definitely
> consider, and there's a chance we may get some funding to have Gabriel
> put some time in to this. Namely caching WFS. IMHO
svg factory does not support expressions that contain properties
Key: GEOT-3307
URL: http://jira.codehaus.org/browse/GEOT-3307
Project: GeoTools
Issue Type: Bug
Compo
Gabriel,
Yep, i mean with 'learn from the past': 'copy - paste the wfs1.1 version :)
Then walk through it and make some nice other versions'
Roy
_
From: Gabriel Roldán [mailto:grol...@opengeo.org]
To: Roy Braam [mailto:roybr...@b3partners.nl]
Cc: Andrea Aime [mailto:andrea.a...@geo-sol
Note I never really meant "from scratch", despite I generally share the
excitement of starting something new and the "but done well" sentiment,
yet the devil is in the details and I'd rather get what's wfs 1.1 out of
the current module as the basis for the new one.
Making WFS_1_1_DataStore extend f
