<note>

<note> contains a note or annotation. 3.8.1 Notes and Simple Annotation 2.2.6 The Notes Statement 3.11.2.6 Notes and Other Additional Information 9.3.5.4 Notes within Entries
Modulecore — 3 Elements Available in All TEI Documents
Attributesatt.global (@xml:id, @n, @xml:lang, @rend, @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.placement (@place) att.pointing (@target, @evaluate) att.responsibility (@cert, @resp) att.typed (@type, @subtype)
anchoredindicates whether the copy text shows the exact place of reference for the note.
Status Optional
Datatype 

<rng:ref name="data.truthValue"/>
data.truthValue
Note
In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. ‘page 218, lines 3–4’). The anchored attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. The value true indicates that such an explicit location is indicated in the copy text; the value false indicates that the copy text does not indicate a specific place of attachment for the note. If the specific symbols used in the copy text at the location the note is anchored are to be recorded, use the n attribute.
targetEndpoints to the end of the span to which the note is attached, if the note is not embedded in the text at that point.
Status Recommended when applicable
Datatype 1–∞ occurrences of 

<rng:ref name="data.pointer"/>
data.pointer
separated by whitespace
Values reference to the xml:id(s) of element(s) which end at the location(s) in question, or to an empty element at the point in question.
Note
This attribute is retained for backwards compatibility; it may be removed at a subsequent release of the Guidelines. The recommended way of pointing to a span of elements is by means of the range function of XPointer, as further described in 16.2.4.4 range().
Used by
model.noteLike
Contained by
analysis: cl m phr s span w
core: abbr add addrLine address author bibl biblScope biblStruct cit corr date del distinct editor email emph expan foreign gloss head headItem headLabel hi imprint item l label lg list measure mentioned monogr name note num orig p pubPlace publisher q quote ref reg resp rs said series sic soCalled sp speaker stage street term time title unclear
corpus: activity channel constitution derivation domain factuality interaction locale preparedness purpose
dictionaries: case colloc def dictScrap entry entryFree etym form gen gram gramGrp hom hyph iType lang lbl mood number orth per pos pron re sense stress subc syll tns usg xr
drama: actor camera caption castGroup castItem castList epilogue performance prologue role roleDesc set sound tech view
figures: cell figure table
gaiji: char glyph
header: authority change classCode creation distributor edition extent funder geoDecl handNote language notesStmt principal scriptNote sponsor typeNote
linking: ab seg
msdescription: accMat acquisition additions adminInfo altIdentifier catchwords collation colophon condition custEvent decoNote explicit filiation finalRubric foliation heraldry incipit layout material msItem msItemStruct musicNotation objectType origDate origPlace origin provenance rubric secFol signatures source stamp summary support surrogates textLang watermark
namesdates: addName affiliation age birth bloc climate country death district education event faith floruit forename genName geogName langKnown location nameLink nationality occupation org orgName persName person place placeName population region residence roleName settlement sex socecStatus state surname terrain trait
nets: graph
spoken: u writing
tagdocs: valDesc
textcrit: app lem rdg wit witDetail
textstructure: argument back body byline closer dateline div div1 div2 div3 div4 div5 div6 div7 docAuthor docDate docEdition docImprint docTitle epigraph floatingText front group imprimatur opener postscript salute signed text titlePage titlePart trailer
transcr: damage fw restore supplied surplus
verse: metDecl metSym rhyme
May contain
analysis: c cl interp interpGrp m pc phr s span spanGrp w
certainty: certainty precision respons
core: abbr add address bibl biblStruct binaryObject cb choice cit corr date del desc distinct email emph expan foreign gap gloss graphic hi index l label lb lg list listBibl measure measureGrp mentioned milestone name note num orig p pb ptr q quote ref reg rs said sic soCalled sp stage term time title unclear
dictionaries: lang oRef oVar pRef pVar
drama: camera caption castList move sound tech view
figures: figure formula table
gaiji: g
header: biblFull idno
iso-fs: fLib fs fvLib
linking: ab alt altGrp anchor join joinGrp link linkGrp seg timeline
msdescription: catchwords depth dim dimensions height heraldry locus locusGrp material msDesc objectType origDate origPlace secFol signatures stamp watermark width
namesdates: addName affiliation bloc country district forename genName geo geogFeat geogName listEvent listNym listOrg listPerson listPlace nameLink offset orgName persName placeName region roleName settlement state surname
nets: eTree forest forestGrp graph tree
spoken: incident kinesic pause shift u vocal writing
tagdocs: att classRef classSpec code eg egXML elementRef elementSpec gi ident listRef macroRef macroSpec moduleRef moduleSpec schemaSpec specDesc specGrp specGrpRef specList tag val
textcrit: app listWit witDetail
textstructure: floatingText
transcr: addSpan am damage damageSpan delSpan ex fw gb handShift restore space subst supplied surplus
verse: caesura rhyme
Declaration

<rng:element name="note">
 <rng:ref name="att.global.attributes"/>
 <rng:ref name="att.global.linking.attributes"/>
 <rng:ref name="att.global.analytic.attributes"/>
 <rng:ref name="att.global.facs.attributes"/>
 <rng:ref name="att.placement.attributes"/>
 <rng:ref name="att.pointing.attributes"/>
 <rng:ref name="att.responsibility.attributes"/>
 <rng:ref name="att.typed.attributes"/>
 <rng:optional>
  <rng:attribute name="anchored" a:defaultValue="true">
   <rng:ref name="data.truthValue"/>
  </rng:attribute>
 </rng:optional>
 <rng:optional>
  <rng:attribute name="targetEnd">
   <rng:list>
    <rng:ref name="data.pointer"/>
    <rng:zeroOrMore>
     <rng:ref name="data.pointer"/>
    </rng:zeroOrMore>
   </rng:list>
  </rng:attribute>
 </rng:optional>
 <rng:ref name="macro.specialPara"/>
</rng:element>
element note
{
   att.global.attributes,
   att.global.linking.attributes,
   att.global.analytic.attributes,
   att.global.facs.attributes,
   att.placement.attributes,
   att.pointing.attributes,
   att.responsibility.attributes,
   att.typed.attributes,
   attribute anchored { data.truthValue }?,
   attribute targetEnd { list { data.pointer, data.pointer* } }?,
   macro.specialPara
}
Example
In the following example, the translator has supplied a footnote containing an explanation of the term translated as "painterly":
And yet it is not only
in the great line of Italian renaissance art, but even in the
painterly <note place="bottom" type="gloss" resp="#MDMH">
 <term xml:lang="de">Malerisch</term>. This word has, in the German, two
distinct meanings, one objective, a quality residing in the object,
the other subjective, a mode of apprehension and creation. To avoid
confusion, they have been distinguished in English as
<mentioned>picturesque</mentioned> and
<mentioned>painterly</mentioned> respectively.
</note> style of the
Dutch genre painters of the seventeenth century that drapery has this
psychological significance.

For this example to be valid, the code MDMH must be defined elsewhere, for example by means of a responsibility statement in the associated TEI Header:

<respStmt xml:id="MDMH">
 <resp>translation from German to English</resp>
 <name>Hottinger, Marie Donald Mackie</name>
</respStmt>
Example

The global n attribute may be used to supply the symbol or number used to mark the note's point of attachment in the source text, as in the following example:

Mevorakh b. Saadya's mother, the matriarch of the
family during the second half of the eleventh century, <note n="126" anchored="true"> The
alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to
Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents
published by Jacob Mann.

However, if notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may well be considered unnecessary to record the note numbers.