The translation industry is characterized by a plurality of tools, programs and services. To find a "common language" between the various software and tools used in a project, a third party capable of establishing communication is essential. To this end, an API (Application Programming Interface) is used - software interfaces that provide integration for various software.

However, there is a problem, the urgency of which is constantly growing. Every system is using its own API, and therefore each actor has to build a separate connector to various systems, each specific to their API. Thus, the multitude of API specifications causes cross-connectivity development costs to skyrocket. In a world where efficiency plays a key role, and competition is incredibly high (you snooze, you lose!), this approach can no longer be considered viable. It is necessary to have a single, universal solution capable of ensuring compatibility between all the various instruments used in the field of translation.

Logrus Global and several other TAPICC project advocates have set themselves an ambitious goal in solving this difficult but strategically important task. The project TAPICC (Translation API Classes and Cases) has started to achieve real interoperability in an already very zoo-like world of different APIs. Within its framework, a universal API standard is being developed that will "connect" all participants of the translation services market. Such universal standard will ensure the interoperability of existing services and programs without having to implement their specific proprietary interfaces.

Such a problem of universal compatibility can only be solved with close and fruitful industry cooperation. Continued collaboration is difficult to sustain without organizational support. The new API standard is developed under the aegis and on the platform of GALA (Globalization and Localization Association), which ensures organizational and PR support, with many powerhouses such as TAUS, LT-Innovate, Microsoft, SAP, Google, Mozilla, and others having already backed the initiative.

At the GALA conference in Amsterdam there was a separate session dedicated to TAPICC (video can be viewed here). It aroused the sincere interest of a wide audience, with the project itself receiving detailed elaboration regarding both its phased implementation and its popularization. The professional community greeted the idea of a unified API standard with enthusiasm, giving the project a new impetus. The Logrus Global R&D team will have their hands full with this very engaging and demanding work.

Pre-project work began with extensive market research: all previously developed API standards were studied, their pros and contras were analyzed, and the priorities and needs of the participants in the translation industry were determined. A process of careful phased planning followed.

Serious progress has already been made and impressive results have been achieved: a design document for the project has been drawn up, a project steering committee has been organized, project implementation stages have been coordinated with partners from different countries, regulatory documents have been composed, data on various translation formats has been compiled, and much more.

Of course, there is much that still needs to be accomplished in the near future. After the "brainstorming" session held at the conference in Amsterdam, the creation of the first data model, the cataloging of formats, and the preparation of the first prototype will follow. The project committee comprising both research and industry representatives, has determined key strategic development and application goals which we will now steer to in a structured manner, with wider engagement of the industry players.

The project is broken down into 4 large work packages:

1. The Business Metadata work package will define wrapper-mapped metadata, canonical names and values, will define workflow relevance and work on harmonization with other standards and compatibility with other systems;
2. The Payload specification work package will take care of defining various types of payload, define payload-level metadata, canonical names and values, and work on harmonization with other standards and compatibility with other systems;
3. The XLIFF extraction work package will take care of ITS “decoration”, will define extraction reference guides, and also define XLIFF extraction / mergers and OM representation e.g. JLIFF;
4. The API Specification work package will take care of protocols, transfer mechanisms (pull/push), define classes, will create code samples/snippets and eventually develop full API specification.

The TAPICC project is not just the development of an API that will simplify the interaction of participants in the translation sphere. It is a call to unite the professional community in a joint effort to develop and advance the standards of our industry.

Everyone can take part in the project – to do so, it is necessary to join the GALA Connect group dedicated to TAPICC: https://www.gala-global.org/tapicc-translation-api-class-and-cases-initiative

Attend the webinar this Thursday: https://www.gala-global.org/ondemand/toward-common-specifications-translation-apis

This webinar will describe the first working groups and planned deliverables (business metadata, payload specification, API specification), and explain how your company can get involved. Don't miss this opportunity to contribute to a community-driven initiative that has such potential to advance our industry.

Join the online community discussion on TAPICC here: https://www.gala-global.org/tapicc-translation-api-class-and-cases-initiative

Welcome!