On Mon, Oct 3, 2011 at 7:45 PM, Justin Deoliveira <[email protected]>wrote:
>
>> Hope what I wrote makes some sense ;-)
>>
> Yeah it does. I think it is really hard to make a decision either way
> without an actual use case. However, I would vote (and this is obviously
> biased) to keep the them separated for now since all the work to add the new
> classes, implement the xml encoding and parsing bindings, update the factory
> and filter visitor interfaces and implementations have all been done. But if
> people feel strongly that is not the way to go i am happy to rework stuff.
>
Nah, I'm not feeling strongly either way and feel for all the work that
already went into the
current direction. It seems to me the semantics of the two are quite on the
"splitting hairs" side
and the time of the WFS 2.0 spec group would have been better spent with
other
topics (like, getting the bounds without getting the features, or providing
a way to extract
unique values, and so on).
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
