<term> contains a single-word, multi-word, or symbolic designation which is regarded as a technical term. [3.3.4 Terms, Glosses, Equivalents, and Descriptions]
Modulecore — Elements Available in All TEI Documents
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @style, @rendition, @xml:base, @xml:space) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) att.declaring (@decls) att.pointing (@targetLang, @target, @evaluate) att.typed (@type, @subtype) att.canonical (@key, @ref) att.sortable (@sortKey) att.cReferencing (@cRef)
Member of
Contained by
analysis: cl phr s span
figures: cell figDesc
iso-fs: fDescr fsDescr
linking: ab seg
spoken: u writing
tagdocs: eg valDesc
verse: metSym rhyme
May contain
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.
We may define <term xml:id="TDPVrend="sc">discoursal point of view</term> as
<gloss target="#TDPV">the relationship, expressed
through discourse structure, between the implied author or some other addresser, and the

This element is used to supply the form under which an index entry is to be made for the location of a parent index element.

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.