Klaus
Fleischmann
Preventing the Babylonian
API Confusion
Who is Klaus?
• Studied Interpreting and Technical
Communication in Austria and CA
• Founded Kaleidoscope 1996
• Gala Board Member since 2015
• Localization and Technology Geek
Who is Kaleidoscope?
Authoring, Content
• Component-Based AuthoringSCHEMA ST4
• SCHEMA Content Delivery Suite
• Information design
• Authoring through Acrolinx
TranslationServices
• eurocom Translation Services
• Technical translations
• Marketing
• Transcreation
• Localization
• Language Subscription
Translation Software
• SDL
• Trados
• GroupShare
• WorldServer
• Collaboration
• globalReview
• smartQuery
Terms
• SDL MultiTerm
• quickTerm
• Processes and data modeling
• Checking the correctness
Agenda
• The issue
• Initiatives
• dercom COTI
• Sample implementations
• Next steps
The issue
CMS, PIM,
PLM, PDM,
CRM …
„CAT“, project
management
File exchange
Workflow exchange
Information exchange
?
Status
Currently, these integration
are largely project-driven
Status
Which is great…
Status
… for a while.
Status
But technology changes…
And that´s not enough…
• CAT tools want to talk to each others
• MT and CAT want to interact
• More and more is based in the cloud
• Every LSP is offering portals or Web APIs
• …
Status
You get the idea…
Vision
So our vision is:
A standardized API
Agenda
• The issue
• Initiatives
• dercom COTI
• Sample implementations
• Next steps
TAUS Translation API
• Set of intentionallysimple calls to „get a translation“
• Targeted at clientsand LSPs
• Project is currently„resting“ – Gala topick it up?
LTI Cloud
• Language Technology Industry
• LTI cloud is a platform to– Research existing LT
components
– Prototype new components
– Plug and Play componentsinto composite products
• Not pushing a „standard“
Agenda
• The issue
• Initiatives
• dercom COTI
• Sample implementations
• Next steps
Who is „dercom“?
• Founded 2013 by 7 leading German producers
• Goas was a „neutral“ interface for exchangingtranslation projectsbetween CMS and CAT
• COTI: CommonTranslation Interface
(Association of German Producers of
Structured Authoring and Concent
Management Systems)
Why Germany?
• Very mature yetfragmented market forboth CMS and CATsystems
• „German approach“ tochallenges resulted in very early developmentof highly complexsystems
(Association of German Producers of
Structured Authoring and Concent
Management Systems)
3 Levels
• Level 1
– Standardized project
package wrapper
• Level 2
– Automatically
transferring packages
between systems
• Level 3
– Realtime communication
via API between CMS and
CAT systems
• Download the
specification v 1.1:
http://www.dercom.de/
Level 1
• Container file *.COTI
– COTI.xml with project
information
• Translation files,
including settings etc.
• Reference files
• Multilingual
Level 2
• Still package-based, but with automatic fileexchange
• Via watched folders:– Untranslated
– Translated
– Error
– Archive
– Logs
Export from CMS to watched folder
Import to CAT
Translation
Export from CATto watched folder
Import to CMS
Level 3
• Direct interaction via
detailed API (SOAP)
• WS-Security, encryption,
X.509 token etc. for
information security
• Session and project IDs
Level 3
• Supports
– Rejection
– Cancellation
– Update / revision
– Status information
• Detailed, 50 page API
specification
Agenda
• The issue
• Initiatives
• dercom COTI
• Sample implementations
• Next steps
Sample implementations
Type Sample Implementation
COTI Level 1 SDL Trados Studio with COTI Plugin
COTI Level 2 Connecting Content with SDL Trados Studio
COTI Level 2,5 Remote PIM* with SDL Trados Studio and COTI Plugin
COTI Level 3 Remote CMS* with Connecting Content and SDL GroupShare
* Note: „Tester Tools“ will be used
instead of actual remote systems
Agenda
• The issue
• Initiatives
• dercom COTI
• Sample implementations
• Next steps
Today´s Goal
• Raise awareness
• Test the grounds
– Interesting?
– Feedback?
– Not an issue for you?
Next Goals
• Find project sponsors
• Bring together existingplayers
• Gala thinking abouttaking over the„rebirthing“ of the API project
• Good idea?