[OSGeo-Standards] [RESTful-Policy.SWG] [OAB] Encodings and REST

[xavier lhomme]

Hi
I meant that because geoservices is already implemented in esri product
like arcgis server, and esri api for javascript or silverligth,
There is also many web applications on www.argis.com.

Then reviewing the specification could also be done by experimenting it :
what could we do with a map service or a feature service?  Or what is the
difference between  wfs and feature service? About encoding,  filtering....
 Le 22 oct. 2012 21:40, "Andrea Aime" <andrea.aime at geo-solutions.it> a
écrit :

> On Mon, Oct 22, 2012 at 9:35 PM, xavier lhomme <lhomme.xavier at gmail.com>wrote:
>
>> Sure reviewing Geoservices specification takes time but you could also
>> experimenting it !
>>
>
> Not sure I got what you mean? Maybe build prototypes of the specification
> to see
> how difficult it actually is to create and use it?
>
> That's something I'd really like to see, have some rough software
> development done in parallel
> to the spec development so that the spec leaders can get some feedback
> from the trenches
> about what actually works, and what does not.
> It's something that I've heard quite a bit in OSGeo circles, in particular
> that having to develop
> a reference implementation after the spec is basically cast in stone does
> very little
> in terms of improving the spec itself.
>
> Cheers
> Andrea
>
> --
> ==
> Our support, Your Success! Visit http://opensdi.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
>
> -------------------------------------------------------
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/standards/attachments/20121022/a6b8e449/attachment.html>