As fascinating as Web services are, how do they affect the localization Industry? Isn't this a Web developer issue? After all, it isn't as if we will ever need to localize Web services, or use them to help with localization.
This is largely true as far as localizing Web services is concerned. Since Web services are XML-based, they are already potentially 'globalization-friendly', and the translatable content is no different from that of any Web application. The data structures required by Web services, however, may make the task of localization considerably easier.
For example, two defining characteristics of Web-based information are increased traffic and the need to constantly update content. Automation is becoming a key comonent is the localization industry's attempt to manage these issues. Great strides have been made with individual pieces of the puzzle, such as content extraction, translation memory, previewing, and project management, and Web services may provide the glue that binds the pieces together and streamlines the process.
What is also apparent is that any such process could be applicable to content regardless of its source. In this way Web services could provide the future infrastructure for the localization industry. | 
