<abstract>

<abstract> contains a summary or formal abstract prefixed to an existing source document by the encoder. [2.4.4. Abstracts]
Moduleheader
Attributesatt.global (@xml:id, @n, @xml:lang, @xml:base, @xml:space) (att.global.rendition (@rend, @style, @rendition)) (att.global.linking (@corresp, @synch, @sameAs, @copyOf, @next, @prev, @exclude, @select)) (att.global.analytic (@ana)) (att.global.facs (@facs)) (att.global.change (@change)) (att.global.responsibility (@cert, @resp)) (att.global.source (@source))
Member of
model.profileDescPart
Contained by
header: profileDesc
May contain
core: list listBibl p
figures: table
linking: ab
namesdates: listEvent listNym listObject listOrg listPerson listPlace listRelation
textcrit: listApp
Note

This element is intended only for cases where no abstract is available in the original source. Any abstract already present in the source document should be encoded as a div within the front, as it should for a born-digital document.

Example
<profileDesc>
 <abstract resp="#LB">
  <p>Good database design involves the acquisition and deployment of
     skills which have a wider relevance to the educational process. From
     a set of more or less instinctive rules of thumb a formal discipline
     or "methodology" of database design has evolved. Applying that
     methodology can be of great benefit to a very wide range of academic
     subjects: it requires fundamental skills of abstraction and
     generalisation and it provides a simple mechanism whereby complex
     ideas and information structures can be represented and manipulated,
     even without the use of a computer. </p>
 </abstract>
</profileDesc>
Content model
<content>
 <alternate minOccurs="1"
  maxOccurs="unbounded">
  <classRef key="model.pLike"/>
  <classRef key="model.listLike"/>
  <elementRef key="listBibl"/>
 </alternate>
</content>
Schema Declaration
element abstract
{
   tei_att.global.attributes,
   ( tei_model.pLike | tei_model.listLike | tei_listBibl )+
}