News

OASIS seeks standards for language translation

The Organisation for the Advancement of Structured Information Standards (OASIS) consortium yesterday announced that members have formed a technical committee to develop standards for Web services-based language translation services.

The OASIS Translation Web Services Technical Committee will develop a Web service definition language for interactions between publishers of content who need it translated into different languages and the translation vendors, said OASIS president and chief executive officer Patrick Gannon.

DataPower Technology, IBM, the Localisation Research Centre, Microsoft, Oracle and SAP are collaborating to use Web services for a workflow linking tasks that comprise a complex software localisation process.

"What [the committee wants] is a standard way of interfacing between those who are requesting the service and those who are providing the services," Gannon said. The mechanism for the translation will be a set of standard WSDL packets.

Gannon cited software companies as a potential benefactor, with these companies requiring documentation be translated into multiple languages.

The translation is part of an effort in which various industries each need to agree on a standard set of Web services definitions, Gannon said.

The technical committee will concentrate first on defining service types that are relevant to the software/content localisation industry. The committee's specification will drive development of WSDL documents to be published in a UDDI registry and, potentially, in an ebXML registry.

The committee will co-ordinate efforts with the OASIS XML Localisation Interchange File Format Technical Committee.
Related Topics: Web software, VIEW ALL TOPICS

Email Alerts

Register now to receive ComputerWeekly.com IT-related news, guides and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
 

COMMENTS powered by Disqus  //  Commenting policy