|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| James Pasley, "Avoid XML Schema Wildcards For Web Service Interfaces," IEEE Internet Computing, vol. 10, no. 3, pp. 72-79, May/June, 2006. | |||
| BibTex | x | ||
| @article{ 10.1109/MIC.2006.45, author = {James Pasley}, title = {Avoid XML Schema Wildcards For Web Service Interfaces}, journal ={IEEE Internet Computing}, volume = {10}, number = {3}, issn = {1089-7801}, year = {2006}, pages = {72-79}, doi = {http://doi.ieeecomputersociety.org/10.1109/MIC.2006.45}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Internet Computing TI - Avoid XML Schema Wildcards For Web Service Interfaces IS - 3 SN - 1089-7801 SP72 EP79 EPD - 72-79 A1 - James Pasley, PY - 2006 KW - XML KW - XML schema KW - HTML KW - Web services KW - validation VL - 10 JA - IEEE Internet Computing ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MIC.2006.45
Developers risk negative side effects when they attempt to make Web services interfaces extensible without understanding the context in which various mechanisms are applied. Given the overuse and misapplication of the HTML example,developers often litter their interfaces with XML Schema wildcards. This increases complexity and results in ambiguous interface definitions. A more appropriate versioning strategy for Web services development can help developers avoid these problems.
Index Terms:
XML, XML schema, HTML, Web services, validation
Citation:
James Pasley, "Avoid XML Schema Wildcards For Web Service Interfaces," IEEE Internet Computing, vol. 10, no. 3, pp. 72-79, May-June 2006, doi:10.1109/MIC.2006.45
Usage of this product signifies your acceptance of the Terms of Use.

