Term Entry (Concept Entry)
Container for TBX encoding of one entry in a terminological database.
For usage information and contents, see the documentation for ISO TBX at https://www.iso.org/schema/nisosts/v0.2/doc/tbx/index.html. The TBX vocabulary is derived and extended from ISO 30042
Tagging Terms and Definitions in NISO STS: There are two very different strategies for tagging terms and definitions. Both structures occur optionally inside a Term Section (<term-sec>) in NISO STS standards or adoption document: one is TBX and the other is a simpler, less powerful TBX-alternative.
- TBX: TBX is a concept-oriented encoding of terminological data. The TBX element <tbx:termEntry> models a term using the TBX-namespaced vocabulary and ontology for terms, which can record information about any number of synonymous terms in multiple languages. For usage information and contents, see the documentation for ISO TBX at https://www.iso.org/schema/nisosts/v0.2/doc/tbx/index.html. The TBX vocabulary is derived and extended from ISO 30042.
- Term Display: The NISO STS element <term-display> uses natural language to describe terms, and may OR MAY NOT incorporate semantic term elements such as definition (<def> and part of speech <part-of-speech>). Semantic tagging is encouraged, but nothing is enforced.
An organization can choose to use one or the other or, the two encodings may appear side-by-side as equivalents. Processes that deal with NISO STS documents should be prepared to see either (or both) forms of a term entry and to use one or the other (or both) as appropriate.
Term Display: The <term-display> element is a more appearance-oriented encoding of terminological data that may be used when:
- By a standards organization that chooses not to employ TBX,
- When is difficult to generate the desired formatted display from a TBX entry, or
- For backfile conversion, in cases where it is difficult to create a useful TBX term entry from an appearance-oriented input document.
The looser term display description of a term and its definition (potentially containing nothing but undifferentiated text) was designed to:
- Enable tagging term and definition content in the sequence in which that content appears in the standards document;
- Enable, but not require, tagging of the principle semantic components of term and definition sections (such as the term, the definition, related elements, part of speech, etc.);
- Enable tagging that will allow extraction of terms and definitions for use in glossaries containing terms and definitions from many standards; and
- Make tagging existing terms and definitions easier (in some senses) than using the more structured TBX tagging.
TBX Usage Documentation: Documentation for the profile of TBX (TermBase eXchange) used by NISO STS can be found at: https://www.iso.org/schema/nisosts/v0.2/doc/tbx/index.html.
This element may be contained in:
... <body> ... <term-sec id="sec_2.2.5"> <label>2.2.5</label> <tbx:termEntry xmlns:tbx="urn:iso:std:iso:30042:ed-1" id="term_2.2.5"> <tbx:langSet xml:lang="nl"> <tbx:definition>hefplatform bestaande uit een werkplatform en een hydraulische hefinrichting gemonteerd op een zelfaangedreven chassis</tbx:definition> <tbx:note>Zie <std><std-ref>EN 1777</std-ref></std>.</tbx:note> <tbx:tig> <tbx:term>hoogwerker</tbx:term> <tbx:partOfSpeech value="noun"/> <tbx:normativeAuthorization value="preferredTerm"/> </tbx:tig> <tbx:tig>...</tbx:tig> </tbx:langSet> </tbx:termEntry> <term-display>...</term-display> </term-sec> </body> ...