Terminology is more than a bilingual list
A useful termbase may distinguish a concept from the words used for it, record a domain and identify an approved or discouraged expression. Our practical concern is to preserve those distinctions when information moves between tools.
For example, two departments may use the word “account” for different concepts. A flat list can hide that ambiguity. Before exporting terminology, decide which contextual information the receiving team needs to choose correctly.
An illustrative exchange
An application team maintains a concept for permanent account deletion, with terms in English, Dutch, German, Spanish and Polish. It also records that “sign out” is a separate action.
Our suggested test is to export a small collection and inspect what the destination preserves. Does the concept relationship survive? Are definitions, language variants and usage notes still accessible? Can an editor distinguish preferred wording from an alternative?
This exercise is not an official TBX validation procedure. It demonstrates why an export should be judged against the information the project actually needs.
Versions and dialects
The 2019 ISO document describes TBX-Core; other industry dialects are separate implementation resources. Do not assume that two tools advertising “TBX support” accept the same dialect or preserve the same fields. Consult their stated support and use representative samples. ISO scope.
Connection to LISA
TBX is one of the clearest technical links between LISA's portfolio and later standardization. The archived LISA material includes an earlier TBX reference. That historical document should not be substituted for the 2019 edition when planning a new implementation. LISA portfolio archive.
AI-assisted terminology work
Our recommendation is to separate term extraction from term approval. AI can suggest candidate terms or flag inconsistent usage; an accountable terminology process decides what the entries mean and when they apply.
Supplying a glossary to a model does not guarantee adherence. Keep terminology instructions available to reviewers and check target usage in context. A wrong term can be fluent and still change the product's meaning.
Source record and related reading
ISO 30042, TBX Info and the LISA archive. This guide does not reproduce the paid ISO text or provide complete implementation requirements.