<profileDesc>

<profileDesc> (text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting. [2.4 The Profile Description 2.1.1 The TEI Header and its Components]
Moduleheader — 2 The TEI Header
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))
Used by
model.teiHeaderPart
Contained by
header: teiHeader
May contain
corpus: particDesc settingDesc textDesc
header: calendarDesc creation langUsage textClass
transcr: handNotes listTranspose
Declaration

<rng:element name="profileDesc">
 <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.global.change.attributes"/>
 <rng:group>
  <rng:zeroOrMore>
   <rng:ref name="model.profileDescPart"/>
  </rng:zeroOrMore>
 </rng:group>
</rng:element>
element profileDesc
{
   att.global.attributes,
   att.global.linking.attributes,
   att.global.analytic.attributes,
   att.global.facs.attributes,
   att.global.change.attributes,
   ( model.profileDescPart* )
}
Example
<profileDesc>
 <langUsage>
  <language ident="fr">French</language>
 </langUsage>
 <textDesc n="novel">
  <channel mode="w">print; part issues</channel>
  <constitution type="single"/>
  <derivation type="original"/>
  <domain type="art"/>
  <factuality type="fiction"/>
  <interaction type="none"/>
  <preparedness type="prepared"/>
  <purpose type="entertain" degree="high"/>
  <purpose type="inform" degree="medium"/>
 </textDesc>
 <settingDesc>
  <setting>
   <name>Paris, France</name>
   <time>Late 19th century</time>
  </setting>
 </settingDesc>
</profileDesc>
Note
Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of profileDesc.
In earlier versions of these Guidelines, it was required that the creation element appear first.