<div dir="ltr">Hi,<div><br></div><div>yes, immplementation of such process should be straight forward</div></div><br><div class="gmail_quote"><div dir="ltr">pá 20. 5. 2016 v 16:11 odesílatel Peter Schut via WPS-dev <<a href="mailto:wps-dev@lists.opengeospatial.org">wps-dev@lists.opengeospatial.org</a>> napsal:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi Benjamin,<br><br></div>I would be happy to implement part or all of the test suite in my own personal WPS implementation. (It's written in Ruby, and not open-source). I'd also be interested in working on and potentially hosting a publicly-accessible client that could be used to run compliance testing.<br><br></div>Cheers, Peter.<br><br></div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 19, 2016 at 9:53 AM, Benjamin Proß <span dir="ltr"><<a href="mailto:wps-dev@lists.opengeospatial.org" target="_blank">wps-dev@lists.opengeospatial.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Dear WPS implementers,<br>
<br>
A while (well, almost 2 years...) ago we talked about OGC CITE
tests for WPS 1.0.0 and how the execute operation could be tested.<br>
The Abstract Test Suite of the WPS 1.0.0 standard (05-007r7,
see[1]) describes the following tests for execute (see annex A
4.4):<br>
<br>
Test HTTP GET (if advertised/supported by the WPS)<br>
Test HTTP POST<br>
Test execute with output set to raw data (literal-, complex-,
boundingboxdata)<br>
Test execute with output set to response document (literal-,
complex-, boundingboxdata)<br>
Test execute with response storing and status updates (if
advertised/supported by the WPS/process)<br>
Test language selection for execute<br>
<br>
Now the issue here is that we need a process to test the execute
operation. We talked about using a simple echo-process, that takes
one of each data types as input and output.<br>
I attached an example process description. Things like the
identifier, formats, datatypes and supported CRS' need to be
discussed. <br>
But apart from that.. What do you think, would you be able to
provide such a process in your WPS framework?<br>
<br>
Cheers,<br>
<br>
Benjamin<br>
<br>
[1] <a href="http://portal.opengeospatial.org/files/?artifact_id=24151" target="_blank">http://portal.opengeospatial.org/files/?artifact_id=24151</a><br>
</p>
<pre cols="72">--
Benjamin Proß
Software Engineer
52°North Geoprocessing Community
52°North Initiative for Geospatial Open Source Software GmbH
Martin-Luther-King-Weg 24
Fon: <a href="tel:%2B49-%280%29-251%E2%80%93396371-42" value="+4925139637142" target="_blank">+49-(0)-251–396371-42</a>
Fax: <a href="tel:%2B49-%280%29-251%E2%80%93396371-11" value="+4925139637111" target="_blank">+49-(0)-251–396371-11</a>
<a href="mailto:b.pross@52north.org" target="_blank">b.pross@52north.org</a>
<a href="http://52north.org/" target="_blank">http://52north.org/</a>
General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk
Local Court Muenster HRB 10849
</pre>
</div>
<br>_______________________________________________<br>
WPS-dev mailing list<br>
<a href="mailto:WPS-dev@lists.opengeospatial.org" target="_blank">WPS-dev@lists.opengeospatial.org</a><br>
<a href="https://lists.opengeospatial.org/mailman/listinfo/wps-dev" rel="noreferrer" target="_blank">https://lists.opengeospatial.org/mailman/listinfo/wps-dev</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>
WPS-dev mailing list<br>
<a href="mailto:WPS-dev@lists.opengeospatial.org" target="_blank">WPS-dev@lists.opengeospatial.org</a><br>
<a href="https://lists.opengeospatial.org/mailman/listinfo/wps-dev" rel="noreferrer" target="_blank">https://lists.opengeospatial.org/mailman/listinfo/wps-dev</a><br>
</blockquote></div>