[Pywps-dev] Change Format class according to WPS 1.0 Format data structure

[Jachym Cepicky]

Hi Calin,

If you feel, something should be done in better way, please feel free to do
so. PyWPS-4 is still in very early development phase, any improvements in
the basic codes is welcomed

More to the topic: your note seems to be right. We should use Format and
extend it with the other attributes

And yes -> I started to work i inout.py some time ago and wanted to replace
the implementation, available in app.py with it (it's more complex)

if you get rid of the code from app.js and replace it with the on efrom
inout.py, it would be nice ;-)



Thanks

jachym



po 2. 3. 2015 v 14:17 odesílatel Calin Ciociu <calin.ciociu at gmail.com>
napsal:

Hello everyone,
>
> I have been looking at the Format class in app.py which seemed quite
> simple.
> ComplexOutput class in app.py is actually containing the mime type,
> encoding and schema and also a list with Format objects.
>
> So I've been wondering if it wouldn't be better to take the mime type,
> encoding and schema and put those inside Format class.
> According to Table 23 of WPS 1.0 the Format data structure is containing
> these 3 parameters.
>
> Something else I am not sure about is the FormatBase class in inout.py.
> Was this written so Format class would inherit from FormatBase?
> I could move the whole getter and setter of these parameters to
> FormatBase instead then.
>
>
> Best regards,
>
> Calin
> _______________________________________________
> pywps-dev mailing list
> pywps-dev at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pywps-dev/attachments/20150303/3110eae0/attachment.html>