= ZOO Project WPS implementation testing = ZOO-PSC would like to report results of tests conducted on ZOO-Kernel WPS implementation. Comparison of some current WPS implementation was reported in presentation entitled "COMPLIANCE TESTING OF OPEN SOURCE SOFTWARE FOR WEB PROCESSING SERVICES" [http://www.slideshare.net/TheodorFoerster/compliance-testing-of-open-source-software-for-web-processing-services link]. Our testing results are presented in more details below. The test with ZOO WPS are contrary to the presentation mentioned above [http://www.slideshare.net/TheodorFoerster/compliance-testing-of-open-source-software-for-web-processing-services link]. We call upon the authors of the presentation referred above to make appropriate corrections in their presentation in light of our test results outlined below. We hope that a more well planned and coordinated implementation testing can be done in the future. Gérald Fenoy (Chair ZOO PSC) = ZOO Project WPS testing details = In the FOSS4G2010 presentation [http://www.slideshare.net/TheodorFoerster/compliance-testing-of-open-source-software-for-web-processing-services link], some unusual behavior of the ZOO Kernel was pointed out. Hence, the ZOO PSC decided to conduct our own tests with ZOO WPS implementation using the same method reported in the FOSS4G2010 presentation. First note about this response that we are currently preparing, we weren't able to use XMLSpy 2007 Professional version as no more Evaluation version is available, so we used the XMLSpy 2011 Professional one as we can use it for an evaluation period of 30 days. All the following requests give documents which are valid (using XMLSpy 2011 Professional) against the used schemas. == !GetCapabilities request == In the FOSS4G2010 presentation [http://www.slideshare.net/TheodorFoerster/compliance-testing-of-open-source-software-for-web-processing-services link], an error was pointed out about some unexpected metadata : namely Test attribute to the Metadata node getting the "Demo" value. This was due to wrong ZCFG files of the first Services we made in the beginning of the 2009 year. The provided URL to run this test is wrong, one would use this one : http://zoo-project.org/cgi-bin-new/zoo_loader.cgi?REQUEST=GetCapabilities&SERVICE=WPS&version=1.0.0 {{{ #!html }}} So, for the !GetCapabilities request, the Capabilities document output by the ZOO Kernel is '''Valid'''. == !DescribeProcess request == It was also reported in the presentation that ZOO Kernel can't handle the !DescribeProcess request and output a valid !ProcessDescriptions Document. Indeed the first versions of ZOO Kernel was wrong in that, but hopefully the last one, included in OSGeoLiveDVD 4.0 returns already the valid !ProcessDescriptions document. http://zoo-project.org/cgi-bin-new/zoo_loader.cgi?REQUEST=DescribeProcess&SERVICE=WPS&version=1.0.0&Identifier=Buffer Using the url above we can confirm that ZOO Kernel provide '''Valid''' response for the !DescribeProcess request. Note that this request is '''Valid''' also : http://zoo-project.org/cgi-bin-new/zoo_loader.cgi?REQUEST=DescribeProcess&SERVICE=WPS&version=1.0.0&Identifier=Buffer,Boundary,Centroid,ConvexHull,Simplify,Union,Intersection,Difference,SymDifference == Execute request == ZOO WPS provides valid response for Execute as XML POST requests, as it is the mandatory method. To use the XML POST requests, please copy/paste from this page, please follow this [http://zoo-project.org/test_services.html link] to paste in the HTML form. === Synchronous call using asReference === {{{ #!xml Buffer InputPolygon Playground area BufferDistance Distance which people will walk to get to a playground. 10 Result }}} === Synchronous call with data included === {{{ #!xml Buffer InputPolygon Playground area BufferDistance Distance which people will walk to get to a playground. 10 Result }}} === Asynchronous call with data asReference === {{{ #!xml Buffer InputPolygon Playground area BufferDistance Distance which people will walk to get to a playground. 10 Result }}} Here both statusLocation file and response are '''Valid'''. === Asynchronous call with full data included === You can also use the storeExecuteReponse="true" for !ResponseDocument with the asReference attribute for the Output settled to true as in the following request : {{{ #!xml Buffer InputPolygon Playground area BufferDistance Distance which people will walk to get to a playground. 10 Result }}} The resulting document and the statusLocation document are both '''Valid'''. === !RawDataOutput test === {{{ #!xml Buffer InputPolygon Playground area BufferDistance Distance which people will walk to get to a playground. 10 Result }}} The result is valid in the sens that it is a JSON string representing the resulting polygon.