12.1.130. <term>

<term> (term) contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.4.1. Terms and Glosses]
Module	core — Specification
Attributes	att.global @xml:id @n @xml:lang @xml:base att.global.analytic @ana att.global.change @change att.global.facs @facs att.global.linking @corresp @synch @sameAs @copyOf @next @prev @exclude @select att.global.rendition @rend @style @rendition att.global.responsibility @cert @resp att.global.source @source att.cReferencing @cRef att.canonical @key @ref att.cmc @generatedBy att.pointing @targetLang @target @evaluate att.sortable @sortKey att.typed @type @subtype
Member of	model.emphLike
Contained by	core: abbr author bibl biblScope citedRange date desc editor email expan gloss head hi item name p pubPlace publisher rb resp rt term corpus: channel domain interaction purpose figures: figDesc header: authority catDesc change edition licence principal rendition tagUsage namesdates: affiliation age education faith floruit forename gender langKnown nationality occupation orgName persName persPronouns placeName residence sex socecStatus surname
May contain	analysis: c pc core: abbr cit date email expan graphic name note quote ref ruby term title dictionaries: lang figures: figure gaiji: g header: idno linking: seg namesdates: affiliation forename orgName persName persPronouns placeName state surname trait tagdocs: ident transcr: metamark character data
Note	When this element appears within an <index> element, it is understood to supply the form under which an index entry is to be made for that location. Elsewhere, it is understood simply to indicate that its content is to be regarded as a technical or specialised term. It may be associated with a <gloss> element by means of its ref attribute; alternatively a <gloss> element may point to a <term> element by means of its target attribute. In formal terminological work, there is frequently discussion over whether terms must be atomic or may include multi-word lexical items, symbolic designations, or phraseological units. The <term> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <term> element to be used by practitioners of any persuasion. As with other members of the att.canonical class, instances of this element occuring in a text may be associated with a canonical definition, either by means of a URI (using the ref attribute), or by means of some system-specific code value (using the key attribute). Because the mutually exclusive target and cRef attributes overlap with the function of the ref attribute, they are deprecated and may be removed at a subsequent release.
Example	`A computational device that infers structure from grammatical strings of words is known as a <term>parser</term>, and much of the history of NLP over the last 20 years has been occupied with the design of parsers.`
Example	`We may define <term xml:id="TDPV1" rend="sc">discoursal point of view</term> as <gloss target="#TDPV1">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>`
Example	`We may define <term ref="#TDPV2" rend="sc">discoursal point of view</term> as <gloss xml:id="TDPV2">the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss>`
Example	`We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2" rend="sc">discoursal point of view</term> below.`
Content model	<content> <macroRef key="macro.phraseSeq"/> </content> ⚓
Schema Declaration	`element term { att.global.attributes, att.cReferencing.attributes, att.canonical.attributes, att.cmc.attributes, att.pointing.attributes, att.sortable.attributes, att.typed.attributes, macro.phraseSeq }`⚓