<del>

| ## Text Encoding Initiative
### The XML Version of the TEI Guidelines # <del>

`<del>` | (deletion) contains a letter, word or passage deleted, marked as deleted, or otherwise indicated as superfluous or spurious in the copy text by an author, scribe, annotator, or corrector.
Attributes | (In addition to global attributes and those inherited from edit)
`type` | classifies the type of deletion using any convenient typology.
| Datatype: CDATA
| Values: any string identifying the class of deletion.
| Default: #IMPLIED
| Example:
Note | No recommendation of any particular typology is made here; note however that the type attribute should not be used to record the manner in which the deletion is signalled in the source. This should be recorded using the global `rend` attribute, with values such as ‘subpunction' (dots below the line indicate matter to be deleted); ‘overstrike' (lines through the text indicated matter to be deleted); ‘erasure' (material to be deleted has been erased, but remains legible enough to transcribe); ‘bracketed' (brackets around the material indicate that it is spurious or superfluous), etc.
`status` | may be used to indicate faulty deletions, e.g. strikeouts which include too much or too little text.
| Datatype: CDATA
| Values: any description of flaws in the marking of a deletion, e.g. ‘excess left', ‘excess right', ‘short left', ‘short right'.
| Default: unremarkable
| Example:
Note | Status information on each deletion is needed rather rarely except in critical editions from authorial manuscripts.
`resp` | (responsible) signifies the editor or transcriber responsible for identifying the hand of the deletion.
| 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 Certainty and Responsibility).
| Default: %INHERITED;
| Example:
`cert` | (certainty) signifies the degree of certainty ascribed to the identification of the hand of the deletion.
| Datatype: CDATA
| Default: #IMPLIED
| Example:
`hand` | signifies the hand of the agent which made the deletion.
| Datatype: IDREF
| Values: must be one of the hand identifiers declared in the document header (see section 18.2.1 Document Hands).
| Default: %INHERITED;
| Example:

Example

    <l>
       <del rend="overtyped">Mein</del> Frisch
    <del rend="overstrike" type="primary">schwebt</del> weht der Wind</l>

Note

Cf. `<gap>`.

Degrees of uncertainty over what can still be read may be indicated by use of the `<certainty>` element (see 17 Certainty and Responsibility).

This element should be used for deletion of shorter sequences of text, typically single words or phrases. The `<delSpan>` element should be used for longer sequences of text, for those containing structural subdivisions, and for those containing overlapping additions and deletions.

The text deleted must be at least partially legible, in order for the encoder to be able to transcribe it. If it is not legible at all, the `<del>` tag should not be used. Rather, the `<gap>` tag should be employed to signal that text cannot be transcribed, with the value of the `reason` attribute giving the cause for the omission from the transcription as deletion. If it is not fully legible, the `<unclear>` element (available when using the additional tagset for transcription of primary sources) should be used to signal the areas of text which cannot be read with confidence. See further sections 18.1.7 Text Omitted from or Supplied in the Transcription and, for the close association of the `<del>` tag with the `<gap>`, `<damage>`, `<unclear>` and `<supplied>` elements (the latter three tags available when using the additional tagset for transcription of primary sources), 18.2.4 Use of the Gap, Del, Damage, Unclear and Supplied Tags in Combination.

The `<del>` tag should not be used for deletions made by editors or encoders. In these cases, either the `<corr>` tag or the `<gap>` tag should be used.

Module Declared in file teicore2; Core tag sets: enabled when any TEI base is enabled
Class edit
Data Description May contain character data and phrase-level elements.
May contain #PCDATA abbr add addSpan address alt altGrp anchor app c caesura cb certainty cl corr damage date dateRange dateStruct del delSpan distinct emph expan fLib foreign formula fs fsLib fvLib fw gap geogName gloss handShift hi index interp interpGrp join joinGrp lang lb link linkGrp m measure mentioned milestone name num oRef oVar orgName orig pRef pVar pb persName phr placeName ptr ref reg respons restore rs s seg sic soCalled space span spanGrp supplied term time timeRange timeStruct timeline title unclear w xptr xref
May occur within 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 date dateRange def del derivation descrip dictScrap distance distinct distributor docAuthor docDate docEdition docImprint domain edition editor education emph entryFree etym expan extent factuality figDesc firstLang foreName foreign form 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 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 view wit witDetail witness writing xr xref
Declaration

    <!ELEMENT del %om.RR;  %phrase.seq;>
    <!ATTLIST del
          %a.global;
          type CDATA #IMPLIED
          status CDATA "unremarkable"
          resp IDREF %INHERITED;
          cert CDATA #IMPLIED
          hand IDREF %INHERITED;>

See further 6.5.3 Additions, Deletions, and Omissions

Up: 35 Elements