TBX Dialects

TBX-Default

TBX-Default is the designation commonly used when referring to the full set of structural options, data categories, and data category instances accommodated by the TBX standard. The original standard possesses the power to express either complex data entries, such as those found in national termbanks, or the simplest binary term-equivalent pairs, so long as term entries comply with the one concept/one entry principle underlying the TBX structure. It was designed to meet the needs of many different kinds of termbases, which means that taken as a whole, TBX-Default is more powerful and more complex than any one termbase by itself is likely to be. Therefore, it was anticipated in the standard that most users of TBX would adopt a particular subset of TBX-Default that includes the structural and data category options needed for their terminology work, excluding any aspects that are irrelevant for them. As a consequence, so-called dialects of TBX have been created in order to simplify import, export, and validation procedures within a particular working environment. All dialects of TBX should be subsets of TBX-Default. This means that any TBX instance that complies with a particular dialect also complies with TBX-Default. When a software application claims TBX support, it must indicate which dialect of TBX is supported, unless it completely supports TBX-Default in all its complexity.

TBX-Basic

TBX-Basic was designed to efficiently store a large quantity of terminology glossaries in a straightforward XML format.  It can be used to handle monolingual, bilingual, or multilingual glossaries.  For information regarding this format, including starter packages and utilities (e.g. schemas, validators, converters), feel free to visit the following sites:
www.terminorgs.net/TBX-Basic.html (most up to date),
www.ttt.org/tbx,
www.ttt.org/oscarstandards/tbx/,
http://www.tbxinfo.net/tbx-convert/

TBX-Min

TBX-Min is a dialect of TBX designed for simple and straightforward storage of bilingual or monolingual glossaries. The primary use case for TBX-Min is to transmit a glossary to a translator, but TBX-Min can also be used by translators to submit glossaries they have created. It was designed to be easily converted to and from its cousin TBX-Basic, as well as other well known glossary storage formats such as UTX. A number of tools have been made for the purpose of validating and converting TBX-Min files.

  View More TBX-Min Tools and Resources

TBX-Min is ideal for converting existing spreadsheet based glossaries into TBX format (see our tutorial and sample spreadsheets). It can also be viewed or edited using the online TBX-Min Manager. One of the most useful features of TBX-Min that will soon be available is the ability to pull TBX-Min files out of a TBX-Basic file, edit them, and then put them back in to the TBX-Basic file. This would be useful for a Project Manager to send only the necessary glossary to a specialized translator to work with. The translator could make changes to their copy of the TBX-Min file and send it back to the Project Manager when their work is complete. The TBX-Min glossary could then be read back in to the TBX-Basic master glossary to update the changes made by the translator.

Back to Home

 

Last updated: February 9, 2017 at 16:18 pm