<term>

<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 — 3 Elements Available in All TEI Documents
Attributes att.declaring (@decls) att.typed (@type, @subtype) att.canonical (@key, @ref)
targetidentifies the associated gloss element by an absolute or relative URI reference
Status Optional
Datatype

<rng:ref name="data.pointer"/>
data.pointer
Values should be a valid URI reference that resolves to a gloss element
cRefidentifies the associated gloss element using a canonical reference from a scheme defined in a refsDecl element in the TEI header
Status Optional
Datatype

<rng:ref name="data.pointer"/>
data.pointer
Values the result of applying the algorithm for the resolution of canonical references (described in section 16.2.5 Canonical References) should be a valid URI reference that resolves to a gloss element
Note
The refsDecl to use may be indicated with the decls attribute.
sortKeysupplies the sort key for this term in an index.
Status Optional
Datatype

<rng:ref name="data.word"/>
data.word
Values any string of Unicode characters.
David's other principal backer,
Josiah ha-Kohen <index indexName="NAMES">
 <term sortKey="Azarya_Josiah_Kohen">Josiah ha-Kohen b. Azarya</term>
</index> b. Azarya, son of one of the last gaons of Sura was David's own first
cousin.
Note
The sort key is used to determine the sequence and grouping of entries in an index; if this attribute is not supplied, the textual content of the element is used for this purpose.
Used by
May contain
Declaration

<rng:element name="term">
<rng:ref name="att.global.attributes"/>
<rng:ref name="att.declaring.attributes"/>
<rng:ref name="att.typed.attributes"/>
<rng:ref name="att.canonical.attributes"/>
<rng:choice>
 <rng:optional>
  <rng:attribute name="target">
   <rng:ref name="data.pointer"/>
  </rng:attribute>
 </rng:optional>
 <rng:optional>
  <rng:attribute name="cRef">
   <rng:ref name="data.pointer"/>
  </rng:attribute>
 </rng:optional>
</rng:choice>
<rng:optional>
 <rng:attribute name="sortKey">
  <rng:ref name="data.word"/>
 </rng:attribute>
</rng:optional>
<rng:ref name="macro.phraseSeq"/>
</rng:element>
element term
{
   att.global.attributes,
   att.declaring.attributes,
   att.typed.attributes,
   att.canonical.attributes,
   ( attribute target { data.pointer }? | attribute cRef { data.pointer }? ),
   attribute sortKey { data.word }?,
   macro.phraseSeq
}
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="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 fiction.</gloss>
Note
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.