<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 |
| Attributes | Attributes att.global (xml:id, n, xml:lang) (lim.att.global.fragmentable (part)) (att.global.rendition (rendition)) (att.global.source (source)) att.pointing (target) att.typed (type) att.canonical (ref) |
| Member of | |
| Contained by |
core: abbr add author bibl corr date del desc editor emph expan foreign gloss head hi item l label mentioned name note num orig p pubPlace publisher q quote ref reg resp rs sic term time title unclear
corpus: activity
namesdates: addName affiliation birth death faith floruit forename genName langKnown nameLink nationality objectName occupation orgName persName placeName residence roleName settlement sex surname
textstructure: byline dateline docAuthor docDate docEdition docImprint imprimatur salute signed titlePart trailer
|
| May contain |
core: abbr add choice date del ellipsis emph foreign gap gloss graphic hi lb mentioned milestone name note noteGrp num orig pb ptr q quote ref reg rs sic term time title unclear
figures: figure
gaiji: g
header: idno
lim: noteMarker rule
linking: linkGrp
msdescription: locusGrp
namesdates: addName affiliation forename genName geo location nameLink objectName orgName persName placeName roleName settlement surname
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.
|
| Examples |
A computational device that infers structure
from grammatical strings of words is known as a <term>parser</term>, and much of the historyof NLP over the last 20 years has been occupied with the design of parsers.
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>
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>
We discuss Leech's concept of <term ref="myGlossary.xml#TDPV2" rend="sc">discoursal point of view</term> below.
|
| Source | Github
<elementSpec module="core" ident="term"> <gloss>term</gloss> <desc>contains a single-word, multi-word, or symbolic designation which is regarded as a technical term.</desc> <classes> <memberOf key="att.global"/> <memberOf key="model.emphLike"/> <memberOf key="att.pointing"/> <memberOf key="att.typed"/> <memberOf key="att.canonical"/> </classes> <content> <macroRef key="macro.phraseSeq"/> </content> </elementSpec> |