Compliance Testing of Open Source Software for Web Processing Services
0 likes1,166 views
The document summarizes compliance testing of open source web processing services against the OGC Web Processing Service (WPS) specification. It describes testing various WPS implementations and client software for compliance with the WPS standard. The results found that while the server implementations claimed compliance, they often did not fully implement all aspects of the specification, especially around input/output descriptions and asynchronous processing support. It concludes that compliance testing is important for open source software to work properly across implementations, and that a standardized test suite would help with validation.
![Thanks for your attention! swsl.uni-muenster.de Dr. Theodor Foerster [email_address]](https://image.slidesharecdn.com/foss4g2010compliancereduced-100911063618-phpapp02/85/Compliance-Testing-of-Open-Source-Software-for-Web-Processing-Services-32-320.jpg)
Compliance Testing of Open Source Software for Web Processing Services
- 1. Compliance Testing of Open Source Software for Web Processing Services Theodor Foerster Institute for Geoinformatics (ifgi) Foss4G 2010 9th September 2010
- 2. No Shootout!
- 3. Compliance!
- 4. History Class WPS 0.4.0 Candidate (09/2005) WPS 1.0.0 (06/2007) Deegree WPS (deegree 2.2) (12/08) Deegree WPS (deegree 2.3) (04/10) 2005 2007 PyWPS 1.0.0 (11/06) PyWPS 2.0.0 (09/07) 52N WPS 0.x (05/06) PyWPS 3.0.0 (09/08) PyWPS 3.1.0 (01/09) 52N WPS 2.0 (01/09) 52N WPS 1.0 (12/07) 2008 2009 2010 It‘s time for compliance!
- 5. Compliance is crucial Open Source products Transparency Flexibility for the users Supports the community! THE argument over proprietary standards
- 7. WPS 101 Data Information HTTP / XML GetCapabilities DescribeProcess Execute WPS Process 1 Process 2 Process n
- 8. Interoperability OGC WPS Compliance Compliant WPS responses Full support of the specification Store, asynchronous, synchronous Product interoperability Real-world problem
- 9. SETUP
- 10. Test environment Intel Dual core CPU @ 1.66 GHz on a Dell laptop Ubuntu 10.4 Tomcat 6.0.26/Apache2 Java 6
- 12. Service facts Environment Java/Tomcat Python/Apache Java/tomcat C/Apache Tested version 2.0.0 rc 5 3.2 rc: 3.0 1.0 Stated compliance Full Full – with limitations Full Full Installation successful yes yes yes - Requires tomcat 6 Internal Server error: cannot find libjavaplugin_jni.so Remote endpoint yes yes yes yes
- 13. Remote endpoints http://deegree3-testing.deegree.org/deegree-wps-demo/services http://apps.esdi-humboldt.cz/cgi-bin/wps/wps http://giv-wps.uni-muenster.de:8080/wps/WebProcessingService http://zoo-project.org/zoosoo/
- 15. Candidate Clients Version Results XML Clients n/a yes uDig 1.3 yes 52N OpenLayers 1.0 yes QGIS 1.5.0 no gvSIG 1.10 no JUMP 1.3.2 w/ 2.0 rc1 yes
- 16. Client Test procedure Server Login Process selection Process Execution Buffer Applied data LineString Features from WFS (Tasmanian roads) No raster data
- 17. OGC Compliance Validated with XMLSpy GetCapabilities (HTTP-GET) DescribeProcess (HTTP-GET) Execute (HTTP-POST) Store Synchronous Asynchronous
- 19. XML Clients
- 20. XML Clients - results Deegree Client 52°North test client
- 21. uDig Input/Output not supported Metadata not compliant Metadata not compliant
- 22. OpenLayers ProcessID not found Dummy/literal data process work No processes found
- 23. JUMP Input/Output not supported Metadata not compliant Metadata not compliant
- 25. GetCapabilities HTTP-GET Query REQUEST=GetCapabilities&SERVICE=WPS&version=1.0.0 processVersion="1.0.0“ missing <ows:Metadata xlink:Test="Demo"/> invalid
- 26. DescribeProcess HTTP-GET Query REQUEST=DescribeProcess&Service=WPS&version=1.0.0&identifier= XXX Example process buffer MimeType wrong namespace wrong element dataType in Format
- 27. Execute HTTP-POST Example process buffer Sync Store async
- 28. CONCLUSION
- 29. Conclusion Compliance a prerequisite for successful Open Source software Compliance between products pair-wise Client-Server Spec compliance Results are not OGC certified! Standardized test suite required Output/Input problem Validate your schemas!
- 30. Conclusion (contd.) OGC Compliance Caps Desc store sync async Client-Server interoperability XML uDig OL
- 31. Invitation… Compliance testing with volunteers Stand up with demo servers Join the team Mailing list Wiki
- 32. Thanks for your attention! swsl.uni-muenster.de Dr. Theodor Foerster [email_address]