Transcription where a vacat is evident or suspected

xml version || id: vacat|| traditional typographic representation | regular expression test | epidoc appearance with standard xslt | notes | questions and issues | responsibility for this section | cvs information || post a comment || test this page

Release or development version: r-5

Implementation of the guidance in this section is required for leiden conformance.

for divset 1: editionitemcount != typographicitemcount

The element <space/> should be used where a blank space on the stone is considered significant.

Traditional typographic representation

EpiDoc Encoding

  1. Imperator <space dim="horizontal" extent="3" unit="character" /> Caesar
  2. Valeria <space id="space1" dim="horizontal" extent="3" unit="character" /> <certainty target="space1" locus="#gi" degree="low" /> Atticilla
  3. senatus <space id="space2" dim="horizontal" extent="3" unit="character" precision="circa" /> populusque
  4. dona <space id="space3" dim="horizontal" extent="5" unit="character" precision="circa" /> <certainty target="space3" locus="#gi" degree="low" /> nobis pacem

EpiDoc appearance with standard XSLT

  1. Imperator (vac. 3) Caesar
  2. Valeria (vac. 3) Atticilla
  3. senatus (vac.? 3) populusque
  4. dona (vac.? 5) nobis pacem

Notes

  1. The use of the <certainty> element in these examples conforms to the consensus reached in a protacted discussion on the Markup list under the rubrics "REQ COMMENT: lacuna/vacat and uncertainty" and "Certainty etc." ( 1-10 June 2002).
  2. <certainty target="extent"/> has, however, been replaced by precision attribute on <space/> as of Spring 2007.

Questions and issues

  1. GB (2006-07-19): This section also impinges on the "whitespace" discussion. Ideally, all space on stone should be marked up the same way in the XML (using <space/>), with contextual stylesheets rendering some as (vac.) and others with whitespace—dependent of course on the desires of the project: USEP want more whitespace; InsAph want more ( vv.).

Responsibility for this section

CVS Information

Revision number: $Revision: 1.14 $

Revision name (if any): $Name: r-5 $

Revision date: $Date: 2007/06/06 16:22:17 $

Revision committed by: $Author: gabrielbodard $