Issue No. 05 - Sept.-Oct. (2013 vol. 17)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MIC.2013.4
Cristian Mateos , Argentinian National Council for Scientific and Technical Research
Marco Crasso , Argentinian National Council for Scientific and Technical Research
Alejandro Zunino , Argentinian National Council for Scientific and Technical Research
Jose Luis Ordiales Coscia , Universidad Nacional del Centro de la Provincia de Buenos Aires
In a previous article, the authors demonstrated that effectively discovering Web services helps developers avoid several common design errors in Web Service Description Language (WSDL) documents. Their proposed guidelines are unfortunately applicable only when publishers follow the top-down, or contract-first, method of building services, which isn't very popular due to its inherent costs. Here, they present an approach for preventing such errors when using a counterpart method--namely, bottom-up or code-first--and measure the approach's impact on service discovery. The rationale behind the study is that because code-first service interfaces are automatically generated by tools that--given a service implementation--deterministically map programming language constructs onto WSDL elements, the measurable properties of service implementations could influence resulting service interfaces.
Publishing, Web services, Data models, Information analysis, Documentation, Ports (Computers), Web Services Description Language, Electronic publishing
C. Mateos, M. Crasso, A. Zunino and J. L. Ordiales Coscia, "Revising WSDL Documents: Why and How, Part 2," in IEEE Internet Computing, vol. 17, no. 5, pp. 46-53, 2013.