Numerous stakeholders (from individual to large company), crossing many technical formats (Software strings, word to text and back). Challenges to vendor adoption in industry. Different objectives

Good examples of complimentary and duplicated features across the standards. SRX allows defining sometimes-complex rules for mixing bi-directional text, or handling to improve leverage. Worth noting they are also very quiet standards.

TBX is designed to facilitate the following use cases:

Interchange, such as that required to support
• the flow of terminological data between technologies and systems
• integration of terminological data from multiple sources
• data conversion necessitated by a change in applications or technologies
Dissemination, including
• querying multiple terminological databases through a single user interface by passing data through a
common intermediate format on a batch or dynamic basis
• placing data on an online site for download by interested parties
• making entries which require some work available for public feedback
• making terminology available dynamically in networked applications through a Web service
Analysis and representation, including
• comparing the contents of various terminological databases
• studying how lossless a conversion between two terminology databases can be
• designing a new terminological database intended to minimize loss during conversion..

Includes terminology, good illustration of the breadth of use cases internationalisation implies.

Lemon heavily used (despite being revised in ontolex). TBX and Multilingual (as opp. Bilingual dicts). Best Practice guidelines from W3C.

Lemon heavily used (despite being revised in ontolex). TBX and Multilingual (as opp. Bilingual dicts). Best Practice guidelines from W3C.

Some of these standards are ageing. LISA is gone, and there are new efforts over things like AR. The idea of separating transportation and processing representations and creating object or serialised formats might be worth expanding on.