`<expan>` | (expansion) contains the expansion of an abbreviation.
Attributes: |
`abbr` | (abbreviation) gives the abbreviation in its unexpanded form.
| Datatype: CDATA
| Values: any string of characters
| Default: #IMPLIED
| Example:
     The address is Southmoor <expan abbr='Rd'>Road</expan>.
`resp` | (responsibility) signifies the editor or transcriber responsible for supplying the expansion of the abbreviation held as the content of the `<expan>` element.
| Datatype: IDREF
| Values: must be 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 or encoding (see chapter 17 ).
| Default: %INHERITED
| Example:
     The address is Southmoor <expan abbrev='Rd' resp=LB>Road</>.
`cert` | (certainty) signifies the degree of certainty ascribed to the expansion of the abbreviation.
| Datatype: CDATA
| Default: #IMPLIED
| Example:
`type` | allows the encoder to classify the abbreviation according to some convenient typology.
| Datatype: CDATA
| Values: any useful classification name, e.g. ``suspension'', ``contraction'', ``brevigraph'', ``title'', ``organization'', ``geographic'', etc.
| Default: #IMPLIED
| Example:
Note | The `type` attribute is provided for the sake of those who wish to classify abbreviations at their point of occurrence; this may be useful in some circumstances, though usually the same abbreviation will have the same type in all occurrences. As the sample values make clear, abbreviations may be classified by the method used to construct them, the method of writing them, or the referent of the term abbreviated; the typology used is up to the encoder and should be carefully planned to meet the needs of the expected use.

Example

Note

This tag is the mirror image of the `<abbr>` tag; both allow the encoder to transcribe both an abbreviation and its expansion. In `<abbr>` , however, the original is transcribed as the content of the element and the expansion as an attribute value; `<expan>` reverses this. The choice between the two is up to the user.

The `<expan>` tag is not required; if appropriate, the encoder may expand abbreviations in the source text silently, without tagging them. If this is done, the TEI header should so indicate.

Tagset additional tag set for common core features
Class data [and indirectly also:] phrase
Filename `teicore2`
Content: May contain character data and phrase-level elements.
Parents ab abbr activity actor add addName addrLine admin affiliation author authority bibl biblScope birth bloc byline camera caption case castItem catDesc cell channel cl classCode closer colloc constitution corr country creation damage dataDesc date dateRange def del derivation desc descrip distance distinct distributor docAuthor docDate docEdition docImprint domain edition editor education emph equiv etym expan extent fDescr factuality figDesc firstLang foreign forename form fsDescr funder fw gen genName gloss gram gramGrp head headItem headLabel hi hyph imprimatur interaction item itype l label lang langKnown language lbl lem locale measure meeting mentioned mood name nameLink note num number occasion occupation opener orgDivn orgName orgTitle orgType orig orth otherForm p per persName phr placeName pos preparedness principal pron pubPlace publisher purpose q quote rdg re ref reg region rendition residence resp restore role roleDesc roleName rs s salute seg sense set settlement sic signed soCalled socecStatus sound speaker sponsor stage street stress subc supplied surname syll symbol tagUsage tech term time timeRange title titlePart tns tr trailer trans u unclear usg valDesc view wit witDetail witness writing xr xref
Children#PCDATA abbr add address app att c caesura cl corr damage date dateRange dateStruct del distinct emph expan foreign formula fw geogName gi gloss handShift hi lang link m measure mentioned name num oRef oVar orgName orig pRef pVar persName phr placeName ptr ref reg restore rs s seg sic soCalled space supplied tag term time timeRange timeStruct title unclear val w xptr xref
Declaration

    <!ELEMENT expan         - -  (%phrase.seq;)                     >
    <!ATTLIST expan              %a.global
              abbr               CDATA               #IMPLIED
              resp               IDREF               %INHERITED

              cert               CDATA               #IMPLIED
              type               CDATA               #IMPLIED       >

See 6.4.5

Back to index