Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Common industry API for translation services presented by TAUS at FEISGILTT


Published on

For additional information, please visit

Published in: Technology
  • Be the first to comment

Common industry API for translation services presented by TAUS at FEISGILTT

  1. 1. TAUS Translation Services APIA TAUS Industry-Shared ServiceProf. Dr. Klemens Waldhör, TAUSRahzeb Choudhury, TAUSFEISGILTT16 October 2012Seattle, USA
  2. 2. From Think Tank to Industry-Shared ServicesThink Tank (since 2005) Industry-Shared Serviceso Reports, Best Practices 1. Promoting MT (since 2006)o Research, Directories 2. Sharing Translation Data (since 2008)o Events, User Forums 3. Interoperability Watchdog (since 2011)o Workshops 4. Dynamic Quality Framework (since 2011)Pushing the industry agenda Reducing costs and driving innovation andand sharing knowledge efficiency for members This slide may not be used or copied without permission from TAUS
  3. 3. Interoperability themes at TAUS Events in 2011 Executive Forum, Barcelona, June  TAUS Response  Sixty decision makers from major buy and  July - XLIFF survey in coordination with TC supply –side stakeholders (434 responses) Conclusions  August – Buyer consultation  Many pragmatic solutions already  XLIFF Symposium – propose implemented in the market. Little core/modules, suggest prioritization, offer business case to revisit legacy to check variances  XLIFF important. Specification process needs to be faster to stay relevant  Need ‘Program Management Office’ to look linkages and consult widely with market to prioritize. Rapidly emergent issues requiring attention
  4. 4. Interoperability themes at TAUS Events in 2011 User Conference, Santa Clara, Oct More info  Hundred decision makers from  Barcelona Summary - major buy and supply–side stakeholders  XLIFF Symposium Presentation –  Open space debate Conclusions  Santa Clara Videos –  Need for common APIs  Registry of implementations  Full TAUS Interoperability Timeline –  Client side pressure
  5. 5. Why a TAUS Translation Services APINow NewLengthy definition processes and Rapid definition, add complexitycomplex standards, with little step by step based on process,compliance checking resulting user/usage and best low adoption rates.Goals/Benefits Ensure most common use scenarios are covered quickly Make it easy to adopt and check compliance Share best practices quickly and gather feedback widely Tackle interoperability issues as they emerge
  6. 6. Massive growth in business use of APIs business-its-social-and-its-happening-quickly/
  7. 7. Relationship to other approaches Linport / Interoperabilty Now -  TAUS API in contrast TIPP  Provides service specification  Defines a container for localization related  Easy to implement workflow  Not a document exchange  No specs how the related services are specification implemented  No requirements on document format to be translated ITS 2.0  Currently only plain text is target,  Related to HTML / XML; provides metadata but more complex translation for the benefit of localization, language objects can be handled too through technologies, and internationalization its JSON based exchange mechanism  ITS marks up documents, but does not provide provide service specifications XLIFF  XML based Document representation format  TAUS API: Xliff usage for providing translatable text (?)  Problem of size, …
  8. 8. A Common Translation Services API  Co-authors  Klemens Waldhör, TAUS Labs  Brian McConnell, Worldwide Lexicon  Reviewed by  Rahzeb Choudhury, TAUS  Vladimir Weinstein, Google  Gustavo Lucardi, Trusted Translations  Grant Straker, Straker Translations  Hans Timmerman, AVB Vertalingen  Marco Trombetti,  Chase Tingley, Spartan Consulting
  9. 9. Goals … API … for software developers who have little or no knowledge about translation services, ... So what do software developers need most?  A simple way to request and get translations from a service in the “cloud”, in effect a command that means “translate this text into French, call me back at when you’re done. thanks.”
  10. 10. Best Practices Usage of Web Services  Simple URLS JSON as exchange format  Accepted standard  Cross (programming) language neutral Standard Return Codes  HTTP Codes TRANSLATION/GET Request  Ask for a translation TRANSLATION/SUBMIT Request  Provide a translation
  11. 11. Best PracticesTypical Translation Tasks Request a translation for a text Submit a translation to the user, or to a cloud translation memory Request review or score for a translation Check the status of a request Cancel a request Accept or reject a completed translation/task Request a list of pending requests/tasks
  12. 12. Example request
  13. 13. The calls/comment/get get comments about a translation/comment/submit submit comment about a translation/im/start start a real-time translation session, reserve translators/im/translate translate a short message in real-time/im/stop end a real-time translation session, release translators/score/get request score for a translation/score/submit submit a score for a translation/request/status check the status of a request, or of all pending requests/request/cancel cancel a task(s)/request/view view a list of pending requests/request/reject reject a task(s)/request/accept accept a task(s)/request/confirm legally confirm a task(s) to be done by party (“official order”)/translation/get request a translation/translation/submitsubmit a translation
  14. 14. Where to get the API specification API definition is coded in an xml document  Simple Extendibility Get it from -
  15. 15. Validation Service  Test API implementations at nteroperability  Dev. sponsored by
  16. 16. Example Workflow implemented by TrustedTranslations
  17. 17. Demonstrating the API with www. lingo24.com Video:
  18. 18. Companies supporting the API We thank the following companies for supporting, implementing and testing our API: Thanks for your API support!
  19. 19. Plans for rollout – next steps Gather feedback from early adopters Integration into (open source) CMS Expand to cover common MT API requirements
  20. 20. For more information,