<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
Module core — 3 Elements Available in All TEI Documents
In addition to global attributes att.placement (@place)
type describes the type of note.
Status Optional
Datatype

<rng:ref name="data.enumerated"/>
data.enumerated
Values Values can be taken from any convenient typology of annotation suitable to the work in hand; e.g. annotation, gloss, citation, digression, preliminary, temporary
Note
For specialized types of editorial annotation (e.g. for marking corrections, normalizations, cruxes, etc.), see chapter 12 Critical Apparatus.
resp (responsible party) indicates who is responsible for the annotation: author, editor, translator, etc.
Status Recommended when applicable
Datatype

<rng:ref name="data.pointer"/>
data.pointer
Values a pointer to one of the identifiers declared in the document header, associated with a person asserted as responsible for some aspect of the text's creation, transcription, editing, encoding, or annotation
anchored indicates 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.
target indicates the point (or points) of attachment for a note, or the beginning of the span to which the note is attached.
Status Recommended when applicable
Datatype 1–∞ occurrences of 

<rng:ref name="data.pointer"/>
data.pointer
separated by whitespace
Values reference to the xml:ids of element(s) which begin at the location in question (e.g. the xml:id of an anchor element).
Values Référence à le(s) xml:ids de(s) élément(s) qui commence(nt) à l'endroit en question (par exemple, l'xml:id d'un élémentanchor ).
Note
If target and targetEnd are to be used to indicate where notes attach to the text, then elements at the appropriate locations (anchor elements if necessary) must be given xml:id values to be pointed at.
targetEnd points 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(pointer1, pointer2).
Used by
May contain
Declaration

<rng:element name="note">
 <rng:ref name="att.global.attributes"/>
 <rng:ref name="att.placement.attributes"/>
 <rng:optional>
  <rng:attribute name="type">
   <rng:ref name="data.enumerated"/>
  </rng:attribute>
 </rng:optional>
 <rng:optional>
  <rng:attribute name="resp">
   <rng:ref name="data.pointer"/>
  </rng:attribute>
 </rng:optional>
 <rng:optional>
  <rng:attribute name="anchored" a:defaultValue="true">
   <rng:ref name="data.truthValue"/>
  </rng:attribute>
 </rng:optional>
 <rng:optional>
  <rng:attribute name="target">
   <rng:list>
    <rng:oneOrMore>
     <rng:ref name="data.pointer"/>
    </rng:oneOrMore>
   </rng:list>
  </rng:attribute>
 </rng:optional>
 <rng:optional>
  <rng:attribute name="targetEnd">
   <rng:list>
    <rng:oneOrMore>
     <rng:ref name="data.pointer"/>
    </rng:oneOrMore>
   </rng:list>
  </rng:attribute>
 </rng:optional>
 <rng:ref name="macro.specialPara"/>
</rng:element>
element note
{
   att.global.attributes,
   att.placement.attributes,
   attribute type { data.enumerated }?,
   attribute resp { data.pointer }?,
   attribute anchored { data.truthValue }?,
   attribute target { list { data.pointer+ } }?,
   attribute targetEnd { list { 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="foot" 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.