ISO 30042:2019 pdf download – Management of terminology resources – TermBase eXchange (TBX)
4 Fundamental principles and concepts
TBX refers to a framework consisting of two interacting components: a core structure and a formalism for defining data category modules. The core structure is expressed in a schema definition language such as RelaxNG (RNG). (The core is also represented by its own data category module.) This component-based approach supports the varying types of terminological data, or data categories, that are included in different terminological data collections. The approach mirrors the terminological markup framework (TMF) in that the core structure shall reflect the abstract data model of TMF in accordance with ISO 16642. In addition, it facilitates an explicit description of what any two dialects within the TBX framework have in common (the core structure) and how they differ (expressed in their respective data category modules). The combination of these two components defines a particular dialect. “TBX” without a dialect indicator is not a file format, it is not a terminology markup language, and it is not itself a dialect. The TBX framework assumes that, because terminological data collections vary significantly, no one dialect would satisfy all user requirements. All dialects within the TBX framework adhere to the core structure, which is described in Clause 8. A RelaxNG schema for the core structure is referenced in Annex C, and the elements and attributes are described in Annex A. Dialects can differ with respect to which data categories are allowed, and at what levels of a concept entry these data categories may occur. These constraints on the core structure are formally represented in one or more data category modules.
A data category module, or simply module, is a list of permissible data categories and constraints on them that are used in the design of a TBX-compliant dialect. Constraints are the permissible content of a data category (including subsets of a standard picklist value domain) and the levels of the concept entry where the data category may occur (see Clause 8). NOTE Sample data category modules are available on the TBX Info website [15] . It is recommended that implementers of TBX adhere to ISO standards and industry guidelines governing the principles and methodologies of terminology management and the content and quality of terminological data collections, such as those described in Clause 2 and the Bibliography. The information represented in a TBX document instance should be concept-oriented. The terms in a single entry are assumed to be synonymous unless otherwise noted. Furthermore, if two systems both fully support a given TBX dialect, then information in that dialect can be preserved when terminological data is exported from one and imported into the other. In the context of TBX, interoperability implies this preservation of data. When different dialects of TBX are used by two systems, interoperability is reduced, and loss of data categories and their content can occur. Thus, claiming compliance to TBX without indicating the dialect does not guarantee any degree of interoperability.