[Pywps-dev] WPS 2.0

[Tom Kralidis]

+1 agree. An analysis of standard, changes between WPS 1.0 and 2.0,
and impacts on the codebase will help milestone whether it's targeted
for PyWPS 4.2.0 or 5 (breaking changes).

On Mon, Feb 20, 2017 at 5:01 PM, Jáchym Čepický
<jachym.cepicky at gmail.com> wrote:
> Hi Jorge,
>
> the question is IMHO premature, there is no roadmap and we (I) can not make
> any eastimation IMHO.
>
> I'm still (slowly) getting through the standard.
>
> One of new key features would be nested inputs, which would be *good to
> have* - and having support for them back in 1.0.0 response (some unpacked
> version of nested inputs for 2.0.0)
>
> So, what you can basically do, read the standard and prepare the roadmap
> (will help there)
>
> J
>
>
>
> Dne 20.2.2017 v 10:59 Mendes de Jesus, Jorge napsal(a):
>>
>> Hi to all
>>
>>
>> What is the current status of WPS2.0 implementation has someone already
>> implemented ??? 52N, degree???
>>
>>
>> I saw the WPS2.0 issue in github, and I am looking at a possibility for an
>> inkind contribution for the development of WPS2.0  ( no money :( ) in pyWPS.
>> How  much work/days would be necessary to implement WPS2.0  and release
>> pywps4.2 ?
>>
>>
>> Jorge
>>
>> _______________________________________________
>> pywps-dev mailing list
>> pywps-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/pywps-dev
>>
>
> --
> Jachym Cepicky
> e-mail: jachym.cepicky at gmail.com
> twitter: @jachymc
> _______________________________________________
> pywps-dev mailing list
> pywps-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pywps-dev