“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.