Text Encoding Initiative

The XML Version of the TEI Guidelines

<delSpan>


<delSpan> (deleted span of text) marks the beginning of a longer sequence of text deleted, marked as deleted, or otherwise signaled as superfluous or spurious by an author, scribe, annotator, or corrector.
Attributes (In addition to global attributes and those inherited from editIncl)
type classifies the deletion, using any convenient typology.
Datatype: CDATA
Sample values include:
overstrike deletion indicated by line crossing out the text.
erasure deletion indicated by erasure of the text.
bracketed deletion indicated by brackets in the text or margin.
subpunction deletion indicated by dots beneath the letters deleted.
Default: #IMPLIED
Example:

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:

to identifies the endpoint of the deleted passage, by supplying the value of the id attribute of an <anchor> or other empty element placed there.
Datatype: IDREF
Values: any valid identifier.
Default: #REQUIRED
Example:

Note

Both the beginning and the end of the deleted material must be marked; the beginning by the <delSpan> element itself, the end by the to attribute. The element pointed at by to is understood to be included within the deleted passage.

status indicates whether the deletion is faulty, e.g. by including too much or too little text.
Datatype: CDATA
Sample values include:
excess start some text at the beginning of the deletion is marked as deleted even though it clearly should not be deleted.
excess end some text at the end of the deletion is marked as deleted even though it clearly should not be deleted.
short start some text at the beginning of the deletion is not marked as deleted even though it clearly should be.
short end some text at the end of the deletion is not marked as deleted even though it clearly should be.
unremarkable the deletion is not faulty.
Default: unremarkable
Example:

Note

Marking a deletion as faulty is inescapably an interpretive act; the usual test applied in practice is the linguistic acceptability of the text with and without the letters or words in question.

Example
<p>Paragraph partially deleted.  This is the undeleted
portion <delSpan resp="author" to="a23"/>and this the deleted
portion of the paragraph.</p>
<p>Paragraph deleted together with neighboring material.</p>
<p>Second fully deleted paragraph.</p>
<p>Paragraph partially deleted; in the middle of this
paragraph the deletion ends and the anchor point marks
the resumption <anchor id="a23"/> of the text. ...</p>
Note

Both the beginning and ending of the deleted sequence must be marked: the beginning by the <delSpan> element, the ending by the target of the to attribute.

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 <delSpan> 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 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 <delSpan> tag with the <gap>, <damage>, <unclear> and <supplied> elements, 18.2.4 Use of the Gap, Del, Damage, Unclear and Supplied Tags in Combination.

The <delSpan> 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 teitran2; Additional tag set for Physical Transcription: enabled by TEI.transcr
Class editIncl
Data Description May contain character data and phrase-level elements.
May occur within ab abbr activity actor add addName addrLine address admin affiliation analytic app argument author authority back bibl biblFull biblScope biblStruct birth bloc body byline camera caption case castGroup castItem castList cell channel cit cl classCode closer colloc constitution corr country creation damage date dateRange dateStruct dateline def del derivation descrip dictScrap distance distinct distributor div div0 div1 div2 div3 div4 div5 div6 div7 docAuthor docDate docEdition docImprint docTitle domain edition editor education emph entry entryFree epigraph epilogue etym expan extent factuality figDesc figure firstLang foreName foreign form front funder fw gen genName geogName gloss gram gramGrp graph group head headItem headLabel hi hyph imprimatur imprint interaction item itype l label lang langKnown language lbl lem lg lg1 lg2 lg3 lg4 lg5 list listBibl locale m measure meeting mentioned metDecl monogr mood name nameLink note num number occasion occupation offset ofig opener orgDivn orgName orgTitle orgType orig orth otherForm p per performance persName phr placeName pos preparedness principal prologue pron pubPlace publicationStmt publisher purpose q quote rdg rdgGrp re ref reg region rendition residence resp respStmt restore role roleDesc roleName row rs s salute seg sense series set settlement sic signed soCalled socecStatus sound sp speaker sponsor stage street stress subc supplied surname syll symbol table tagUsage tech term termEntry text tig time timeRange timeStruct title titlePage titlePart tns tr trailer trans u unclear usg view w wit witDetail witList witness writing xr xref
Declaration
<!ELEMENT delSpan %om.RO;  EMPTY> 
<!ATTLIST delSpan  
      %a.global;
      type CDATA #IMPLIED
      resp IDREF %INHERITED;
      cert CDATA #IMPLIED
      hand IDREF %INHERITED;
      to IDREF #REQUIRED
      status CDATA "unremarkable">
See further 18.1.4 Additions and Deletions

Up: 35 Elements