Each item in a termlist must have a @n attribute An introductory component of the title is expected A main component of the title is expected No respStmt has been provided, giving SC/TC committee numbers an idno of type serialNumber is expected an idno of type stage is expected A Foreword clause in the front matter is mandatory A Scope clause in the body is mandatory a clause must contain at least two subclauses The application subset must be expressed in plainText. The business unit subset must be expressed in plainText. The concept origin must be expressed in plainText. The customer subset must be expressed in plainText. The type of data base must be expressed in plainText. The domain expert must be expressed in plain text. The element working status must be starterElement, workingElement, consolidatedElement, archiveElement, importedElement, or exportedElement. The source of the entry must be expressed in plainText. The environment subset must be expressed in plainText. The index heading must be expressed in plain text. The keyword must be expressed in plain text. The name of the originating person must be expressed in plainText. The name of the originating database must be expressed in plainText. The name of the originating institution must be expressed in plainText. The product subset must be expressed in plainText. The project subset must be expressed in plainText. The security subset must be public or confidential. The search term must be expressed in plain text. The source identifier must be expressed in plainText. The sort key must be expressed in plainText. The name of the subset owner must be expressed in plainText. Antonym concepts should occur at the entry (concept) level. The antonym-concept in this element must be expressed in basicText. Associated concepts should occur at the termEntry or the langSet level. The term in this element must be expressed in basicText. The content of this element must be plain text. It can occur at the concept (termEntry) level, the langSet level or the term (tig or ntig) level. Generic broader concepts should occur at the termEntry level or the langSet level. The term in this element must be expressed in basicText. Partitive broader concepts should occur at the termEntry level or the langSet level. The term in this element must be expressed in basicText. A characteristic should only occur at the term (tig or ntig) level. The content of this element must be plain text. The content of this element must be plainText. Information about a concept position should occur at the termEntry level or the langSet level, and it must be expressed in plainText. Generic coordinate concepts should occur at the termEntry level or the langSet level. The term in this element must be expressed in basicText. Partitive coordinate concepts should occur at the termEntry level or the langSet level. The term in this element must be expressed in basicText. A context sentence can only occur at the term (tig) level. A definition must occur at the termEntry level, the langSet level, or the term (tig) level. An example must occur at the termEntry level, the langSet level, or the term (tig) level. An explanation must occur at the termEntry level, the langSet level, or the term (tig) level. The content of this element must be plain text. The content of this element must be plain text. A quantity should occur at the term (tig or ntig) level. The content of this element must be plain text. A range should occur at the term (tig or ntig) level. The content of this element must be plainText. Related concepts should occur at the termEntry level or the langSet level. The content of this element must be expressed in basicText. Broader related concepts should occur at the termEntry level or the langSet level. The content of this element must be expressed in basicText. Narrower related concepts should occur at the termEntry level or the langSet level. The content of this element must be expressed in basicText. A reliability code can be a value from 1 (least reliable) to 10 (most reliable). A sample sentence can only occur at the term (tig) level. Sequentially related concepts should occur at the termEntry level or the langSet level. The content of this element must be expressed in basicText. Spatially related concepts should occur at the termEntry level or the langSet level. The content of the element must be expressed in basicText. A subject field must be a plainText value. Subject fields usually occur at the termEntry level. Generic subordinate concepts should occur at the termEntry level or the langSet level. The content of the element must be expressed in basicText. Partitive subordinate concepts should occur at the termEntry level or the langSet level. The content of the element must be expressed in basicText. Generic superordinate concepts should occur at the termEntry level or the langSet level. The content of the element must be expressed in basicText. Partitive superordinate concepts should occur at the termEntry level or the langSet level. The content of the element must be expressed in basicText. The content of this element must be plain text. Temporally related concepts should occur at the termEntry level or the langSet level. The content of the element must be expressed in basicText. Thesaurus descriptors should occur at the termEntry level. The content of this element must be plain text. Units should occur at the term (tig or ntig) level. Units must be expressed in plainText. The content of this element must be in plain text. Contexts can only be of one of the following types: definingContext, explanatoryContext, associativeContext, linguisticContext, metalinguisticContext or translatedContext. Definitions can only be of one of the following types: intensionalDefinition, extensionalDefinition, partitiveDefinition, or translatedDefinition. The value of the abbreviated form in this element must be expressed in basicText. The administrative status must be standardizedTerm-admn-sts, preferredTerm-admn-sts, admittedTerm-admn-sts, deprecatedTerm-admn-sts, supersededTerm-admn-sts, legalTerm-admn-sts, or regulatedTerm-admn-sts. Antonym terms should occur at the term (tig or ntig) level. The antonym term in this element must be expressed in basicText. The directionality must be monodirectional, bidirectional, or incommensurate. Information about the etymology of a term must be expressed in noteText. Etymology information should occur at the tig level or at the termCompGrp level. The false friend must be expressed in basicText. The frequency must be commonlyUsed, infrequentlyUsed, or rarelyUsed. The geographical usage must be expressed in plainText. The gender must be masculine, feminine, neuter, or otherGender. Gender should be specified at the term level (tig or ntig) or at the termCompGrp level. The grammatical number must be single, plural, dual, mass, or otherNumber. The grammatical number should be specified at the term level (tig or ntig) or at the termCompGrp level. The grammatical valency must be expressed in plainText. The homograph must be expressed in basicText. The language planning qualifier must be recommendedTerm, nonstandardizedTerm, proposedTerm, or newTerm. The hotkey must be expressed in plainText. The normative authorization must be standardizedTerm, preferredTerm, admittedTerm, deprecatedTerm, supersededTerm, legalTerm, regulatedTerm . The part of speech must be a plainText value. It should be specified only at the term (tig or ntig) level or at the termCompGrp level. The process status must be unprocessed, provisionallyProcessed, or finalized. The pronunciation must be expressed in basicText. It should be specified at the term (tig or ntig) level or at the termCompGrp level. The proprietary restriction must be trademark, serviceMark, or tradeName. The register must be colloquialRegister, neutralRegister, technicalRegister, in-houseRegister, bench-levelRegister, slangRegister, or vulgarRegister . The value of the short form in this element must be expressed in basicText. The temporal qualifier must be archaicTerm, outdatedTerm, or obsoleteTerm. The termLocation must be a plainText value. It should be specified only at the term (tig or ntig) level. The term provenance must be transdisciplinaryBorrowing, translingualBorrowing, loanTranslation, or neologism. The type of term can only be one of the following values: abbreviation, initialism, acronym, clippedTerm, entryTerm, synonym, internationalScientificTerm, fullForm, transcribedForm, symbol, formula, equation, logicalExpression, commonName, variant, shortForm, transliteratedForm, sku, partNumber, phraseologicalUnit, synonymousPhrase, standardText, string, internationalism, shortcut. The term structure must be expressed in plain text. The time restriction must be expressed in plainText.