Common industry API for translation services presented by TAUS at FEISGILTT
Download as PPTX, PDF•2 likes•1,623 views
The document outlines the TAUS Translation Services API, which aims to simplify translation requests for software developers without prior translation service knowledge. It emphasizes the need for interoperability and effective integration of translation processes through a JSON-based exchange mechanism. Future steps include gathering feedback from users and expanding the API's capabilities to meet market demands.
Common industry API for translation services presented by TAUS at FEISGILTT
- 1. TAUS Translation Services API A TAUS Industry-Shared Service Prof. Dr. Klemens Waldhör, TAUS Rahzeb Choudhury, TAUS FEISGILTT 16 October 2012 Seattle, USA
- 2. From Think Tank to Industry-Shared Services Think Tank (since 2005) Industry-Shared Services o 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 and and sharing knowledge efficiency for members This slide may not be used or copied without permission from TAUS
- 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. 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 http://tinyurl.com/d938xlf stakeholders XLIFF Symposium Presentation – Open space debate http://tinyurl.com/6yhroqa Conclusions Santa Clara Videos – Need for common APIs http://tinyurl.com/9h3j9hr Registry of implementations Full TAUS Interoperability Timeline –http://tinyurl.com/dy4ta66 Client side pressure
- 5. Why a TAUS Translation Services API Now New Lengthy definition processes and Rapid definition, add complexity complex standards, with little step by step based on process, compliance checking resulting user/usage and best practices. in 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. Massive growth in business use of APIs http://blog.programmableweb.com/2012/05/22/6000-apis-its- business-its-social-and-its-happening-quickly/
- 8. 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, …
- 9. 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, Translated.net Chase Tingley, Spartan Consulting
- 10. 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 www.foo.com/submit when you’re done. thanks.”
- 11. 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
- 12. Best Practices Typical 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
- 14. Example request
- 15. 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
- 16. Where to get the API specification API definition is coded in an xml document Simple Extendibility Get it from - http://tinyurl.com/9btqw3n
- 17. Validation Service Test API implementations at http://www.tauslabs.com/i nteroperability Dev. sponsored by
- 18. Example Workflow implemented by Trusted Translations
- 19. Demonstrating the API with www. lingo24.com http://taus.test.lingo24.com/v1.1 Video: http://www.youtube.com/watch?v=-_h3ZEVIyuU
- 20. Companies supporting the API We thank the following companies for supporting, implementing and testing our API: Thanks for your API support!
- 21. Plans for rollout – next steps Gather feedback from early adopters Integration into (open source) CMS Expand to cover common MT API requirements
- 22. For more information, please contact: [email protected] m