LADaS Annotation Guidelines

Juliette Janes, Sarah Bénière, Lucence Ing, Thibault Clérice

► To cite this version:

Juliette Janes, Sarah Bénière, Lucence Ing, Thibault Clérice. LADaS Annotation Guidelines. 2025. [https://inria.hal.science/hal-05252327v2](https://inria.hal.science/hal-05252327v2)

HAL Id: hal-05252327

https://inria.hal.science/hal-05252327v2

Preprint submitted on 4 Nov 2025

**HAL** is a multi-disciplinary open access
archive for the deposit and dissemination of sci-
entific research documents, whether they are pub-
lished or not. The documents may come from
teaching and research institutions in France or
abroad, or from public or private research centers.

L'archive ouverte pluridisciplinaire HAL, est
destinée au dépôt et à la diffusion de documents
scientifiques de niveau recherche, publiés ou non,
émanant des établissements d'enseignement et de
recherche français ou étrangers, des laboratoires
publics ou privés.

<figure><img src="image_1.png" /></figure>

Distributed under a Creative Commons Attribution 4.0 International License
# LADaS Annotation Guidelines

Juliette Janès, Sarah Bénière, Lucence Ing, Thibault Clérice

ALMAnaCH, Inria, Paris

## Introduction

Automatic Text Recognition (ATR) technologies have enabled the creation of large digital corpora of printed, typewritten, and handwritten texts. However, further text processing is needed in order to make the most of those digitised documents since “[m]isidentifying footnotes, running titles, or marginal text as the main body of the text introduces noise into the character masses” (Clérice et al., 2024). In computer vision, Document Layout Analysis (DLA) covers a set of tasks—among which object detection—to identify and extract visually interesting zones from an image.

LADaS<fnref n="1" /> is both a controlled vocabulary for describing the layout of paginated textual documents and related materials (such as posters, manuscripts, typewritten or printed texts), and a dataset of images annotated using this vocabulary. The LADaS Guidelines present the taxonomy defined to describe these documents by introducing and defining the various elements that make up the vocabulary. The goal is to produce a dataset suitable for training a layout recognition model like YOLO (among others), following the principles DLA. Within a document-image-to-TEI pipeline, the aim is to detect and identify the different zones that make up the text: paragraphs, lines, headings, footnotes, images, etc. The core of the LADaS model is to be able to reconstruct a document image into a TEI file.

This document is addressed to annotators and model users, and presents the LADaS Annotation Guidelines. It describes the vocabulary used both for the annotation labels and their definitions, details the specifications for every label, and features explicit examples. Examples of annotated full pages are available in

the appendix.

40

## Vocabulary

41

### Specifications

42

The specifications presented in the LADaS Annotation Guidelines follow the RFC 2119 norm (Bradner, 1997) on requirement level indication keywords, which are capitalised.

43

44

45

46

## Labels

47

The LADaS annotation labels are structured in two levels<fnref n="2" /> corresponding to established controlled vocabularies:

48

49

50

1. Level 1 comes from SegmOnto. First introduced in 2021, it is used in order to “describe document layout during the segmentation phase of the OCR process” (Gabay et al., 2024). In LADaS, it corresponds to “Zones,” which are clearly defined areas on a page layout (e.g. main zone of text, images, tables, etc.). New zones were added in the current specifications to process more recent types of structures, such as code and forms.

51

52

53

54

55

56

57

58

59

60

61

2. Level 2 provides a more detailed description of the page layout. It focuses on the graphical representation of elements (e.g. headings, paragraphs, etc.). The labels' structuration and names are based on the TEI Guidelines (TEI Consortium, 2025), and definitions rely on both the TEI and the Cambridge Online Dictionary as it is free of charge.

62

63

64

65

66

67

68

69

70

The LADaS syntax uses a hyphen to mark the junction between Level 1 and Level 2. For instance:

71

72

73

<footnote n="1">¹Layout Analysis Dataset with SegmOnto.</footnote>

<footnote n="2">²There will also be a “Level 0,” which is still under consideration regarding its practical implementation.</footnote>
* A heading from the main body of text is labelled: **MainZone-Head**;

* A paragraph in a footnote is labelled: **MarginTextZone-P**;

* A bibliographic entry in a list of references is labelled: **MainZone-PStructured**.

Level-2 labels MUST depend on level-1 labels. Thus, a `-P` label MUST NOT appear alone, and annotators SHOULD use **MainZone-P** or **MarginTextZone-P** depending on the context, for example.

There is a tacit use case if, and only if, the only possible Level-2 label associated to the Level-1 label is an anonymous block (`-Ab`). It is then REQUIRED that the Level-2 part is omitted to the advantage of the Level-1 label only. As a result, instead of **RunningTitleZone-Ab**, annotators MUST use **RunningTitleZone**. However, for zones like the main zone, which accept other Level-2 labels, anonymous blocks MUST be annotated when they appear (e.g. **MainZone-Ab**).

## Tagging Recommendations

### Recommendations for Bounding Boxes

The LADaS annotations consist of rectangular bounding boxes around each object to detect. While written with rectangular bounding boxes in mind, please note that the following recommendations are also valid for annotations using oriented bounding boxes and polygons.

For purposes of annotation consistency, we recommend that annotators leave a space equivalent to the padding of a lower-case “o” between the object and its bounding box. Ideally, the bounding boxes SHOULD NOT overlap. However, overlapping is permitted in cases where it is unavoidable, like text exceeding a field’s boundary in a form, or an image surrounded by a paragraph).

### Special Cases

**Indented Text.** If paragraphs are indented, then the indent MUST be included in the bounding box. This is also the case with single-line paragraphs.

**Captions.** Whenever there is a caption associated to an object (especially for media objects), the caption MUST be annotated with its own bounding box and included in the corresponding broader zone (e.g. **GraphicZone**, Fig. 1).

<figure><img src="image_2.png" /><figcaption>Figure 1. Example of imbrication with an image and its caption (GraphicZone in red and GraphicZone-Head in green)</figcaption></figure>

## Structure of the Annotation Descriptions

Each LADaS annotation description is documented using a consistent format. The title of each entry begins with a brief description of the zone or segment, followed by the corresponding label in brackets. The entry is then organised into standardised components, each clearly defined and explained. Illustrative examples accompany the description, with the relevant zone visually highlighted in red.

The following text defines each component of an entry, with the component name presented in bold, followed by its definition. If a particular component is not applicable to the zone, it is marked as N/A (Non Applicable).
140

**Definition**: A definition written with information coming from SegmOnto, the TEI Guidelines, or the Cambridge Online Dictionary;

141

142

143

*In Level-1 descriptions:*

144

* **MUST be specified by**: Mandatory Level-2 specifications for Level-1 labels;

145

146

* **MAY be specified by**: Optional Level-2 specifications for Level-1 labels;

147

148

*In Level-2 descriptions:*

149

* **MUST specify**: Mandatory Level-1 specification for Level-2 labels;

150

151

* **MAY specify**: Optional Level-1 specifications for Level-2 labels;

152

153

**Special case(s)**: Clarifications on ambiguous situations;

154

155

**Potential post-processing**: Suggestions to enhance content processing beyond basic LADaS zone detection;

156

157

158

**Suggested TEI mapping**: Preferred TEI tag for the zone and its content, as expected in the LADaS pipeline output and the reconstructed TEI file.

159

160

161

162

The LADaS Guidelines suggest the TEI elements without presenting all the possible context. As a result, some elements are subject to TEI-specific constraints. For instance, according to the TEI Guidelines, `<titlePage>` is only allowed when embedded inside a `<front>` or `<back>` element, and not in the `<body>`. This issue will be addressed in the documentation included in the LADaS TEI schema.

163

164

165

166

167

168

169

170
171 Contents

<table><tbody><tr><td>172</td><td>1 SegmOnto Semantic Level</td><td>5</td></tr><tr><td>173</td><td>1.1 Primary Text Zones</td><td>5</td></tr><tr><td>174</td><td>1.1.1 Main Body of Text (MainZone)</td><td>5</td></tr><tr><td>175</td><td>1.1.2 Margin Text (MarginTextZone)</td><td>5</td></tr><tr><td>176</td><td>1.1.3 Title Pages (TitlePageZone)</td><td>6</td></tr><tr><td>177</td><td>1.2 Media</td><td>6</td></tr><tr><td>178</td><td>1.2.1 Images (GraphicZone)</td><td>6</td></tr><tr><td>179</td><td>1.2.2 Figures (FigureZone)</td><td>7</td></tr><tr><td>180</td><td>1.2.3 Tables (TableZone)</td><td>7</td></tr><tr><td>181</td><td>1.2.4 Forms (FormZone)</td><td>8</td></tr><tr><td>182</td><td>1.2.5 Sheet Music (MusicZone)</td><td>8</td></tr><tr><td>183</td><td>1.3 Material Zones</td><td>9</td></tr><tr><td>184</td><td>1.3.1 Digitisation Artefacts (DigitizationArtefactZone)</td><td>9</td></tr><tr><td>185</td><td>1.3.2 Numberings (NumberingZone)</td><td>9</td></tr><tr><td>186</td><td>1.3.3 Running Titles (RunningTitleZone)</td><td>9</td></tr><tr><td>187</td><td>1.3.4 Stamps (StampZone)</td><td>9</td></tr><tr><td>188</td><td>1.3.5 Quire Marks (QuireMarksZone)</td><td>10</td></tr><tr><td>189</td><td>2 TEI Graphic Level</td><td>11</td></tr><tr><td>190</td><td>2.1 Text</td><td>11</td></tr><tr><td>191</td><td>2.1.1 Headings (Head)</td><td>11</td></tr><tr><td>192</td><td>2.1.2 Structured Headings (HeadStructured)</td><td>11</td></tr><tr><td>193</td><td>2.1.3 Paragraphs (P)</td><td>11</td></tr><tr><td>194</td><td>2.1.4 Labelled Paragraphs (PLabelled)</td><td>12</td></tr><tr><td>195</td><td>2.1.5 Structured Paragraphs (PStructured)</td><td>13</td></tr><tr><td>196</td><td>2.1.6 Quoted Paragraphs (PQuoted)</td><td>13</td></tr><tr><td>197</td><td>2.1.7 Styled Paragraphs (PStyled)</td><td>14</td></tr><tr><td>198</td><td>2.1.8 List Items (Item)</td><td>14</td></tr><tr><td>199</td><td>2.1.9 Line Groups (Lg)</td><td>14</td></tr><tr><td>200</td><td>2.1.10 Dateline (Dateline)</td><td>15</td></tr><tr><td>201</td><td>2.1.11 Address (Address)</td><td>15</td></tr><tr><td>202</td><td>2.1.12 Signed (Signed)</td><td>15</td></tr><tr><td>203</td><td>2.1.13 Anonymous Blocks (Ab)</td><td>15</td></tr><tr><td>204</td><td>2.1.14 Continued Section (Continued)</td><td>16</td></tr><tr><td>205</td><td>2.2 Media and Other</td><td>17</td></tr><tr><td>206</td><td>2.2.1 Part (Part)</td><td>17</td></tr><tr><td>207</td><td>2.2.2 Decoration (Decoration)</td><td>17</td></tr><tr><td>208</td><td>2.2.3 Maths (Maths)</td><td>18</td></tr><tr><td>209</td><td>2.2.4 Manuscript Addenda (ManuscriptAddendum)</td><td>18</td></tr><tr><td>210</td><td>2.2.5 Field (Field)</td><td>18</td></tr><tr><td>211</td><td>2.2.6 Drop Capitals (DropCapital)</td><td>18</td></tr><tr><td>212</td><td>3 Full-Page Annotations</td><td>19</td></tr><tr><td>213</td><td>4 Addendum on Line Segmentation</td><td>34</td></tr></tbody></table>
# 1 SegmOnto Semantic Level

## 1.1 Primary Text Zones

The primary text zones are the zones on the page layout where we typically find textual context. There are three primary text zones: the main body of text, text in the margins, and title pages.

### 1.1.1 Main Body of Text (MainZone)

**Definition:** The MainZone is the main area containing the text. It excludes any paratext and can either be a single block or multiple columns. (Fig. 2, 3)

**MUST be specified by:** N/A

**MAY be specified by:** -Head, -P, -PLabelled, -PStructured, -PQuoted, -PStarred, -Item, -Lg, -Address, -Signed, -Ab, -Continued, -Maths, -Dateline

**Special case(s):** N/A

**Potential post-processing:** N/A

**Suggested TEI mapping:** N/A

<figure><img src="image_3.png" /></figure>

<figure><img src="image_4.png" /><figcaption>Figure 3. Example of MainZone with two columns</figcaption></figure>

### 1.1.2 Margin Text (MarginTextZone)

<table><tr><td><strong>Definition:</strong> The MarginTextZone describes any text contained in the margins, no matter their position on the page. They can be upper margins, lower margins, outer margins, but also inner margins (in the case of multiple columns, for example). (Fig. 4)</td><td>234</td></tr><tr><td><strong>MUST be specified by:</strong> N/A</td><td>241</td></tr><tr><td><strong>MAY be specified by:</strong> -P, -PLabelled, -PStructured, -PStarred, -Item, -Lg, -Ab, -ManuscriptAddendum, -Continued</td><td>242<br>243<br>244</td></tr><tr><td><strong>Special case(s):</strong> N/A</td><td>245</td></tr><tr><td><strong>Potential post-processing:</strong> N/A</td><td>246</td></tr><tr><td><strong>Suggested TEI mapping:</strong> &lt;note&gt;</td><td>247</td></tr></table>

<footnote>(*) Jan Gissens, conseiller juridique de la Commission des Communautés européennes, chargé de cours à l'Université d'Anvers. Les opinions exposées au présent article n'engagent que leur auteur.

(1) Dans la terminologie du T.N.P. (art. IX, § 3) « un Etat d'arme nucléaire est un Etat qui a fabriqué et a fait exploser une arme nucléaire ou un autre dispositif du Royaume-Uni, de la France et de la République Populaire de Chine. Depuis l'admission de cette demeure à P.O.N.U., le 26 octobre 1971, les cinq Etats d'armes nucléaires sont les cinq membres permanents du Conseil de Sécurité. Ni la Chine Populaire, ni la France n'ont signé le T.N.P.

Les Etats membres de la Communauté qui ne sont pas dotés d'armes nucléaires sont la Belgique, le République Fédérale d'Allemagne, l'États-Unis, le Luxembourg et les Pay-Bas. Dans le présent article nous les désignerons par l'expression « les cinq Etats membres ».</footnote>
<figure><img src="image_5.png" /><figcaption>Figure 4. MarginTextZone example</figcaption></figure>

<caption>Figure 5. TitlePageZone example</caption>

### 1.1.3 Title Pages (TitlePageZone)

**Definition:** *TitlePageZone* characterises the entire page, rather than a section within a page. The title page is distinct from the other pages, and is traditionally the first page of a document. It provides bibliographic or identifying information like the work's title, publication date, name(s) of the printer(s), publisher(s) and author(s), for example. (Fig. 5)

**MUST be specified by:** -Ab

**MAY be specified by:** N/A

**Special case(s):** N/A

**Potential post-processing:** N/A

**Suggested TEI mapping if the content is manually annotated:** <titlePage> with structured content from the TEI Guidelines

**Suggested TEI mapping if the content is NOT manually annotated:** <div type="titlePage">

## 1.2 Media

### 1.2.1 Images (GraphicZone)

The media section gathers non-textual and mixed zones. Media zones include: images (drawings or photographs), figures featured within a frame with a title and/or caption, tables, forms, and sheet music.

**Disclaimer:** In the absence of specific post-processing, the TEI mapping for media elements is <figure> by default.

**Definition:** *A GraphicZone* contains a piece of non-textual media (e.g. image, map, photograph, video) with its associated caption and possibly descriptive paragraphs. (Fig. 6)

**MUST be specified by:** N/A

**MAY be specified by:** -Head, -Part, -P, -Ab, -Decoration, Maths

**Special case(s):** If a GraphicZone contains several images (possibly with their own subcaptions), then each is annotated as a GraphicZone-Part within the GraphicZone.
288 Potential post-processing: N/A

289 Suggested TEI mapping: <figure>

furent caricaturés par le dessinateur J.Carlos qui opéra également ce changement thématique
contraint à partir de la fin des années 1930, s'engagea dans l'antinazisme et chroniqua les
avancées de la guerre à travers ses dessins.

<figure><img src="image_6.png" /></figure>

106 BULSCHOTZ, Caricatura dos Tempos, São Paulo, Edições Melhoramentos, 1982 (Ière édition : 1948).

<caption>Figure 6. GraphicZone example</caption>

290 1.2.2 Figures (FigureZone)

291 Definition: A FigureZone characterises tex-

292 tual elements featured within a frame, with a

293 title and/or caption. It is separated from the

294 rest of the text, and is identified by a different

295 font and character size. It is mostly used for

296 code snippets. (Fig. 7)

297 MUST be specified by: N/A

298 MAY be specified by: -Head, -Ab

299 Special case(s): N/A

300 Potential post-processing: N/A

301 Suggested TEI mapping: <figure

302 type="code">

<figure><img src="image_7.png" /><figcaption>Figure 7. FigureZone example</figcaption></figure>

1.2.3 Tables (TableZone)

303

**Definition:** A TableZone represents a table of any kind with its associated caption. Tables are characterised as structured arrangements of facts, text, or numbers in columns and rows. There must be at least two corresponding columns. (Fig. 8)

304

305

306

307

308

309

MUST be specified by : N/A

310

MAY be specified by: -Head, -Ab

311

**Special case(s):** Tables of contents that are structured with clearly separated page numbers, and headings ideally on a single line, they are annotated **TableZone** (Fig. 9). In other cases, they SHOULD be annotated **MainZone-PStructured** (see section 2.1.5).

312

313

314

315

316

317

**Potential post-processing:** Use a table extractor and the table's coordinates on the page in order to encode the content of the table. The LADAS annotations do not handle the table's content.

318

319

320

321

322

Suggested TEI mapping if a table extractor is used: <table> with <row> and <cell>

323

324

Suggested TEI mapping if a table extractor is NOT used: <figure type="table">

325

326

<figure><img src="image_8.png" /><figcaption>Figure 8. TableZone example</figcaption></figure>
<figure><img src="image_9.png" /><figcaption>Figure 9. Table of contents annotated as TableZone</figcaption></figure>

<table><thead><tr><th></th><th></th></tr></thead><tbody><tr><td>327</td><td><strong>1.2.4 Forms (FormZone)</strong></td></tr><tr><td>328</td><td><strong>Definition:</strong> Forms are documents with fields to fill in. The FormZone encompasses the form as a whole. (Fig. 10)</td></tr><tr><td>329</td><td><strong>MUST be specified by:</strong> N/A</td></tr><tr><td>330</td><td><strong>MAY be specified by:</strong> -Part, -Head, -Field</td></tr><tr><td>331</td><td><strong>Special case(s):</strong> N/A</td></tr><tr><td>332</td><td><strong>Potential post-processing:</strong> See the <span style="color:blue;">Field</span> (Field) section.</td></tr><tr><td>333</td><td><strong>Suggested TEI mapping:</strong> &lt;figure type="form"&gt;</td></tr><tr><td>334</td><td><strong>Special case(s):</strong> N/A</td></tr><tr><td>335</td><td><strong>Potential post-processing:</strong> See the <span style="color:blue;">Field</span> (Field) section.</td></tr><tr><td>336</td><td><strong>Suggested TEI mapping:</strong> &lt;figure type="form"&gt;</td></tr><tr><td>337</td><td><strong>Special case(s):</strong> N/A</td></tr></tbody></table>

<figure><img src="image_10.png" /><figcaption>Figure 10. FormZone example</figcaption></figure>

### 1.2.5 Sheet Music (MusicZone) 338

**Definition:** MusicZone is used to annotate sheet music, that is either printed or handwritten. (Fig. 11)

**MUST be specified by:** N/A 342

**MAY be specified by:** -Ab 343

**Special case(s):** N/A 344

**Potential post-processing:** N/A 345

**Suggested TEI mapping:** &lt;notatedMusic&gt; 346

<figure><img src="image_11.png" /><figcaption>Figure 11. MusicZone example</figcaption></figure>
## 1.3 Material Zones

Material zones are textual contents originated from the materiality of the document which are not principal textual contents. They encompass: digitisation artefacts, numberings, running titles, stamps, and quire marks.

**Reminder :** *Material Zones do not take a second level annotation, as -Ab is implicit.*

### 1.3.1 Digitisation Artefacts
(DigitizationArtefactZone)

**Definition:** The DigitizationArtefactZone contains any element external to the document and due to the digitisation process (e.g. mention of the online repository). (Fig. 12)

**MUST be specified by :** -Ab

**MAY be specified by:** N/A

**Special case(s):** N/A

**Potential post-processing:** N/A

**Suggested TEI mapping:** <ab type="digitisation-artefact">

La Grece en ma faveur, est trop inquiétée,
D'un foin plus important, je l'ai cru agitée,
Seigneur, & fur le nom de son Ambassadeur,
j'avois dans fes deffains conçû plus de grandeur.
B 5
( Les

Source gallica.bnf.fr / Bibliothèque nationale de France

<caption>Figure 12. Example of digitisation artefact</caption>

### 1.3.2 Numberings (NumberingZone)

**Definition:** The NumberingZone contains any kind of numbering, be it numbers or letters. It generally contains the page, folio, or document number. (Fig. 13)

**MUST be specified by:** -Ab

**MAY be specified by:** N/A

**Special case(s):** N/A

**Potential post-processing:** N/A

**Suggested TEI mapping:** <fw type="numbering"> or <milestone>

$$E' = -p, E'' = -\frac{B}{V}, E''' = -\frac{B}{V^2}\left(1 - \frac{BV}{B}\right) \quad (3.37)$$

on peut exprimer la pression au 3<sup>ème</sup> ordre :

$$p = B r_0 V_s e e'' \left[ \frac{1}{(e_s V_s)^2} \left\{ 1 - \frac{e_s}{2} \left( \frac{1+B_0}{e_s V_s} + \frac{3 e_s}{(e_s)^2} \right) \right\} \right] \quad (3.38)$$

<caption>Figure 13. NumberingZone example</caption>

### 1.3.3 Running (RunningTitleZone)

**Definition:** The RunningTitleZone traditionally appears at the top of the page or double-page, but in some cases may appear at the bottom. It contains the running title (or abbreviated title) of the current section. (Fig. 14)

**MUST be specified by :** -Ab

**MAY be specified by:** N/A

**Special case(s):** N/A

**Potential post-processing:** N/A

**Suggested TEI mapping:** <fw type="runningTitle">

$$E'' = -p, E''' = -\frac{B}{V}, E'''' = -\frac{B}{V^2}\left(1 - \frac{BV}{B}\right) \quad (3.37)$$

on peut exprimer la pression au 3<sup>ème</sup> ordre :

$$p = B r_0 V_s e e'' \left[ \frac{1}{(e_s V_s)^2} \left\{ 1 - \frac{e_s}{2} \left( \frac{1+B_0}{e_s V_s} + \frac{3 e_s}{(e_s)^2} \right) \right\} \right] \quad (3.38)$$

<caption>Figure 14. RunningTitleZone example</caption>

### 1.3.4 Stamps (StampZone)

**Definition:** Stamps are annotated with a StampZone. It usually refers to library stamps or stamps from a postal service. (Fig. 15)

**MUST be specified by:** N/A

**MAY be specified by:** N/A

**Special case(s):** Whenever there is a stamp of a dateline, the StampZone is prioritised.

**Potential post-processing:** N/A

**Suggested TEI mapping:** <stamp>
<figure><img src="image_12.png" /><figcaption>Figure 15. StampZone example</figcaption></figure>

<table><tr><td>402</td><td>1.3.5 Quire</td><td>Marks</td></tr><tr><td>403</td><td></td><td>(QuireMarksZone)</td></tr><tr><td>404</td><td>Definition:</td><td>The QuireMarksZone contains a quire signature, catchword, or any element relative to the material organisation of the source, with the exclusion of page, folio, or item numbers. It generally appears at the bottom of the page and MUST be close to the text. (Fig. 16)</td></tr><tr><td>405</td><td></td><td></td></tr><tr><td>406</td><td></td><td></td></tr><tr><td>407</td><td></td><td></td></tr><tr><td>408</td><td></td><td></td></tr><tr><td>409</td><td></td><td></td></tr><tr><td>410</td><td></td><td>MUST be specified by: -Ab</td></tr><tr><td>411</td><td></td><td>MAY be specified by: N/A</td></tr><tr><td>412</td><td></td><td>Special case(s): N/A</td></tr><tr><td>413</td><td></td><td>Potential post-processing: N/A</td></tr><tr><td>414</td><td>Suggested TEI mapping:</td><td>&lt;fw</td></tr><tr><td>415</td><td></td><td>type="quiremarks">&gt;</td></tr></table>

<figure><img src="image_13.png" /><figcaption>Figure 16. QuireMarksZone example</figcaption></figure>
## 2 TEI Graphic Level

The following descriptions are in relation to the Level-2 annotations, meaning that they appear after the hyphen. As previously stated, Level-2 labels MUST depend on Level-1 labels, so the following annotations will never be found on their own.

### 2.1 Text

The following zones focus exclusively on the description of textual elements that are visually distinct, either structurally or typographically. These visual differences allow for graphical identification without relying on the meaning of the text. Each zone corresponds to specific TEI tags, enabling the conversion of recognised zones and their textual content into TEI.

#### 2.1.1 Headings (Head)

**Definition:** A heading is a segment of text that appears at the top of a section. It is characterised by a specific typographic variation from the main body of text: bold, italics, upper-case and/or in a larger font size. Headings can be centred and/or numbered. (Fig. 18)

**MUST specify:** N/A

**MAY specify:** MainZone, TitlePageZone, GraphicZone, FigureZone, TableZone, FormZone

**Special case(s):** When there are several levels of headings, each heading level is annotated with its own bounding box.

**Potential post-processing:** N/A

**Suggested TEI mapping:** <head>

<figure><img src="image_14.png" /><figcaption>Figure 17. -Head example</figcaption></figure>

#### 2.1.2 Structured Headings

**Definition:** Like headings, structured headings mark the beginning of a section. They differ in that structured headings are organised through typographic variations (e.g. bold, italics) and punctuation marks (e.g. hyphens, semi-colons, full stops, parentheses), in the same way as structured bibliographic entries.

**MUST specify:** N/A

**MAY specify:** MainZone

**Special case(s):** N/A

**Potential post-processing:** N/A

**Suggested TEI mapping:** <head type="structured">

<figure><img src="image_15.png" /></figure>

<caption>Figure 18. -HeadStructured example</caption>

#### 2.1.3 Paragraphs (P)

**Definition:** A (prose) paragraph is a short part of text, consisting of at least one sentence and beginning on a new line, which can be indented. The classic P paragraph is not numbered. (Fig. 19)

**MUST specify:** N/A

**MAY specify:** MainZone, MarginTextZone, GraphicZone

**Special case(s):** Prose poetry, which is made up of continuous text blocks with few line breaks, is less visually distinct from standard prose paragraphs than verse poetry (annotated Lg). It SHOULD therefore be annotated with P, or PQuoted when the poem is indented.

**Potential post-processing:** Encode lines in prose poetry as <1> in TEI.

**Suggested TEI mapping:** <p>

<footnote n="219">219 Il convient de ne pas omettre le saint Melchisedech.</footnote>

<footnote n="220">220 Il fut en effet le saint prêtre du vrai Dieu.</footnote>

<footnote n="221">221 Le premier il lui offrit en même temps des offrandes de pain et de vin,</footnote>

<footnote n="222">222 Célébrant déjà les sacrements de l'Eglise</footnote>

<footnote n="223">223 Et la foi que le Christ nous enseigna longtemps après.</footnote>

<footnote n="224">224 Aucun doute qu'il ne tint fermement à tous les dogmes.</footnote>
<figure><img src="image_16.png" /><figcaption>Figure 19. -P example</figcaption></figure>

### 2.1.4 Labelled Paragraphs
(PLabelled)

**Definition:** Labelled paragraphs are prose paragraphs beginning with a heading. The heading constitutes the first segment of the paragraph, and is characterised by a typographic variation of the text (e.g. underlining, boldface, italics) and/or a punctuation mark (usually a full stop or a colon). (Fig. 20, 21, 22)

MUST specify N/A

MAY specify: MainZone, MarginTextZone

Special case(s):

* Numbered paragraphs MUST be annotated as labelled paragraphs, and are not to be confused with list items (see the *List Items (Item)* section). As they remain paragraphs, labelled paragraphs (regardless of their length) start with a capital letter and end with a full stop. A series of numbered paragraphs CAN be interrupted by regular prose paragraphs.

* Footnotes SHOULD be annotated PLabelled unless it contains solely a bibliographic reference, in which case it SHOULD be annotated PStructured. We do consider that the footnote number constitutes a label, as with numbered paragraphs.

**Potential post-processing:** Separate the label (name of the speaker, title of the paragraph, etc.) from the paragraph itself.

Suggested TEI mapping: <p> 514
rend="labelled"> 515

<figure><img src="image_17.png" /><figcaption>Figure 20. -PLabelled example</figcaption></figure>

<figure><img src="image_18.png" /><figcaption>Figure 21. Spoken -PLabelled example</figcaption></figure>

DRAFT AGREEMENT BETWEEN THE UNITED NATIONS AND THE INTERNATIONAL MONETARY FUND

Article I

GENERAL

1. This agreement, which is entered into by the United Nations pursuant to the provisions of Article 63 of its Charter, and by the International Monetary Fund (hereinafter called the Fund) pursuant to the provisions of article X of its Articles of Agreement, is intended to define the terms on which the United Nations and the Fund shall be brought into relationship.

2. The Fund is a specialized agency established by agreement among its member Governments and having wide international responsibilities, as defined in its Articles of Agreement, in economic and related fields within the meaning of Article 57 of the Charter of the United Nations. By reason of the nature of its international responsibilities and the terms of its Articles of Agreement, the Fund is, and is required to function as, an independent international organization.

<caption>Figure 22. Numbered -PLabelled example</caption>
### 2.1.5 Structured Paragraphs (PStructured)

**Definition:** Structured paragraphs are not prose paragraphs. They are characterised by the way their information is highly structured and organised through typographic variations (e.g. boldface, italics) and punctuation marks (e.g. hyphen, semi-colon, full stop, parentheses). The most common occurrences of PStructured are bibliographic entries, catalogue entries, and dictionary entries. (Fig. 23)

**MUST specify:** N/A

**MAY specify:** MainZone, MarginTextZone

**Special case(s):**

* Bibliographic entries used as titles are annotated HeadStructured (see 2.1.2).

* In a table of contents (or table of tables, or table of figures), when entries exceed two lines and the page number is not separated from the entry (Fig. 24), each of them SHOULD be annotated PStructured.

**Potential post-processing:** N/A

**Suggested TEI mapping if it is a bibliographic entry AND annotated manually:** <bibl>

**Suggested TEI mapping in any other case:** <p type="structured">

BOSSUET, Jacques-Bénigne. Sermon du mauvais riche (Carême du Louvre, 1662), 1662, 219.

(82) Mais disons les choses par ordre. Premièrement, chrétiens, c'est une fausse imagination des âmes simples et ignorantes, qui n'ont pas expérimenté la fortune, que la possession des

<caption>Figure 23. -PStructured example</caption>

Figure 85: Schéma du processus de reconstruction géométrique 3D du beaupier, objet existant déplace pour lequel les sources n'ont pas permis de le replacer à son emplacement d'origine. 119

Figure 86: Relèvé lasegrammétrique du multaire-aatel : un scanner à décalage de phase à enregistrer la structure générale, un scanner à triangulation optique à numériser les éléments sculptés. Modèle 3D final du multaire-aatel et détail du gisant présentant de nombreux « trous » (© laboratoire MAP (UMR 3495 CNRS/MCC), 2010). 120

<caption>Figure 24. Example of -PStructured in a table of figures</caption>

### 2.1.6 Quoted Paragraphs (PQuoted)

**Definition:** PQuoted is used for long quotation paragraphs. Quoted paragraphs are separated from the main body of text and have larger outer margins. The font size CAN be

smaller than that of the main body of text. Such paragraphs are sometimes enclosed in quotation marks. (Fig. 25)

**MUST specify:** N/A

**MAY specify:** MainZone

**Special case(s):**

* Quoted paragraphs can have a hanging indent, which means that the first line of the paragraph is not indented but the others are.

* If the quoted paragraph begins with opening quotation marks, it MUST be annotated PQuoted (instead of PLabelled) because the paragraph's indentation is more characteristic than the typographic marker in this case. (Fig. 26)

**Potential post-processing:** N/A

**Suggested TEI mapping:** <quote>

Les discours directs construisent l'image d'un locuteur distingué et singulier, que le narrateur décrit dans un paragraphe isolé, situé dans le premier tiers du roman, lorsqu'il arrive en Toscane dans la maison où se trouve Yalda et ses amis :

<figure><img src="image_19.png" /></figure>

Ce passage montre bien que la langue est la cause de l'isolement du narrateur, qui prendra fin dans le dénouement quand il acceptera d'utiliser un parler courant.

<caption>Figure 25. -PQuoted example</caption>

premier rapport¹¹ rédigé par la Commission des droits de l'homme lors de sa dix-neuvième session, ainsi que les comptes rendus des débats que la Commission a consacré à cette question pendant cette session.¹²

Recommande à l'Assemblée générale d'adopter, lors de sa dix-huitième session, le projet de résolution ci-après :

« L'Assemblée générale,

« Reconnaissant la nécessité, au cours de la Décennie des Nations Unies pour le développement, de veiller spécialement, tant à l'échelon national que sur le plan international, à la réalisation de progrès dans le domaine des droits de l'homme et d'encourager l'adoption de mesures destinées à accélérer le mouvement en faveur du respect et de l'observation des droits de l'homme et des libertés fondamentales,

« 1. Prie instamment tous les gouvernements de faire des efforts spéciaux, pendant la Décennie des Nations Unies pour le développement, en vue d'encourager le respect et l'application des droits de l'homme et des libertés fondamentales, et invite notamment les gouvernements des pays en voie de développement à inclure dans leurs plans de développement économique et social, pour autant que les ressources dont ils disposent le leur permettent, des mesures visant à réaliser de nouveaux progrès dans l'application des droits de l'homme et des libertés fondamentales proclamés dans la Déclaration universelle des droits de l'homme;

« 2. Demande aux autorités de l'Organisation des Nations Unies et des institutions spécialisées chargées de l'assistance technique de prêter toute l'aide possible, dans le cadre des programmes qu'elles exécuteront pendant la Décennie pour le développement, en vue de réaliser des progrès dans le domaine des droits de l'homme. »

1280 séance plénière, 12 juillet 1963,

<caption>Figure 26. -PQuoted example</caption>
### 2.1.7 Styled Paragraphs (PStyled)

**Definition:** Styled paragraphs are graphically distinct from regular paragraphs (e.g. between parentheses, in italics, small upper case, centred, etc.). They appear in different contexts: stage directions in theatre corpora, catalogue descriptions in sales catalogues, or abstracts in scientific articles. They generally give a semantic information about the content of the following element(s). (Fig. 27)

**MUST specify:** N/A

**MAY specify:** MainZone, MarginTextZone

**Special case(s):** When an image's caption appears outside of the GraphicZone and within the main body of text, it MUST be annotated MainZone-PStyled.

**Potential post-processing:** Distinguish the style type (e.g. italics, boldface) to specify the value of the @rend attribute.

**Suggested TEI mapping:** <p>rend="styled">

<figure><img src="image_20.png" /><figcaption>Figure 27. -PStyled example</figcaption></figure>

<figure><img src="image_21.png" /><figcaption>Figure 28. Image caption as PStyled</figcaption></figure>

### 2.1.8 List Items (Item)

**Definition:** A list item is a segment of text (usually shorter than a paragraph) in an ordered list of at least two consecutive elements. Items begin with a typographic marker (e.g. bullet point, hyphen, number), end with a comma or semi-colon (except for the list's last item, which ends with a full stop), and does not necessarily begin with a capital letter. (Fig. 29)

**MUST specify:** N/A

**MAY specify:** MainZone, MarginTextZone

**Special case(s):** Lists of names with an intended anaphora and no typographic marker (e.g. "Monsieur M., Monsieur X.") MUST be annotated Item.

**Potential post-processing:** N/A

**Suggested TEI mapping:** <item>

and the division of the epoch in accordance with the stylistics features. According to these features can be established three distinctive stages:

the Cantacuzino - Brancoveanu type stage, "classifiable" (the last two decades of the XVII-th century), is the crystallizing period of the "Brancoveanu" type style, when the traditional fund and the influences received are merged in an indivisible synthesis, which leads to the creation of a style defined as "Brancoveanu" type style;

- the "Brancoveanu" type stage "baroque" (the end the XVII-th century and the first two decades of the XVIII-th century), stage of art maximum bloom;

- the post "Brancoveanu" type stage, which is unfolded after 1720 until the second half of the XVIII-th century, when the legacy of the previous epoch is undertaken by the most important creators both at cult level and popular level.

The second chapter presents the hystorical frame, having four

<caption>Figure 29. -item example</caption>

### 2.1.9 Line Groups (Lg)

**Definition:** Lg is a related group of verse lines. A verse line is defined as a "short fragment (a few words), starting with an uppercase letter and often forming incomplete sentences" (Cambridge English Dictionary). They are mostly found in poetry or theatre texts. (Fig. 30)

**MUST specify:** N/A

**MAY specify:** MainZone, MarginTextZone

**Special case(s):** N/A

**Potential post-processing:** N/A

**Suggested TEI mapping:** <lg>
<figure><img src="image_22.png" /><figcaption>Figure 30. -Lg example</figcaption></figure>

### 2.1.10 Dateline (Dateline)

**Definition:** Dateline is a brief description of the place, date, and time. It is prefixed or suffixed to the main text as a sort of heading or trailer. (Fig. 31)

**MUST specify:** N/A

**MAY specify:** MainZone

**Special case(s):**

* Dateline is very often found in letters, reports, and press articles.

* When a dateline is used as a running title, it MUST be annotated RunningTitleZone because in this case it constitutes noise in the reconstruction of the document.

* Whenever there is a stamp of a dateline, the StampZone is prioritised.

**Potential post-processing:** N/A

**Suggested TEI mapping:** <dateline>

<figure><img src="image_23.png" /><figcaption>Figure 31. -Dateline example</figcaption></figure>

### 2.1.11 Address (Address)

**Definition:** Address is an isolated segment of text with a postal address. It is usually aligned to one side of the page and refers to either a single person, several people, or an organisation. They are mostly found in letters. (Fig. 32)

**MUST specify:** N/A

**MAY specify:** MainZone

**Special case(s):** N/A 642

**Potential post-processing:** N/A 643

**Suggested TEI mapping:** <address> 644

<figure><img src="image_24.png" /><figcaption>Figure 32. -Address example</figcaption></figure>

### 2.1.12 Signed (Signed)

**Definition:** Signed is an isolated segment of text that asserts the responsibility of the text or segment (e.g. author of a letter or report). It is generally aligned on the right. (Fig. 33)

**MUST specify:** N/A 650

**MAY specify:** MainZone 651

**Special case(s):** N/A 652

**Potential post-processing:** N/A 653

**Suggested TEI mapping:** <signed> 654

N'oubliez pas qu'en cas de difficulté, vous pouvez contacter notre ligne SOS au (16 1) 34 64 77 55 : celle-ci est maintenant ouverte le samedi. Vous pouvez aussi taper le 36 15 Nintendo sur votre Minitel.

Bon courage et à bientôt.

<figure><img src="image_25.png" /><figcaption>Figure 33. -Signed example</figcaption></figure>

### 2.1.13 Anonymous Blocks (Ab)

**Definition:** An anonymous block is a piece of (textual) content that does not fit in any of the other classes, but is important to identify. (Fig. 34, 35)

**MUST specify:** 660
DigitisationArtefactZone, NumberingZone, 661
RunningTitleZone, QuireMarksZone, 662
TitlePageZone 663

**MAY specify:** MainZone, MarginTextZone, 664
GraphicZone, FigureZone, TableZone, 665
FormZone 666
## 2.2 Media and Other

The media section focuses on non-textual elements, material artefacts, and mixed-content zones.

### 2.2.1 Part (Part)

**Definition:** Part is a grouping of several elements within a broader zone.

**MUST specify:** N/A

**MAY specify:** GraphicZone, FormZone

**Special case(s):**

* We use **GraphicZone-Part** when there are several media coming with their subcaption within a **GraphicZone**. (Fig. 37)

* **GraphicZone-Part** is also used when there is floating text surrounding a diagram in order to keep its unity.

* In a **FormZone**, when the fields are divided into clear categories, the corresponding fields can be grouped within a **FormZone-Part**. (Fig. 39)

**Potential post-processing:** N/A

**Suggested TEI mapping:** <graphic>

<figure><img src="image_26.png" /><figcaption>Figure 35. Two plans (original de 1722) figure the two main format on passage entre le petit château et les châteaux calédoniens.</figcaption></figure>

<figure><img src="image_27.png" /><figcaption>FIGURE 4.1 - Illustration du problème de factorisation</figcaption></figure>

<figure><img src="image_28.png" /><figcaption>Figure 39. Example of a FormZone-Part (red), encompassing a FormZone-Head (orange) and several FormZone-Fields (yellow)</figcaption></figure>

### 2.2.2 Decoration (Decoration)

**Definition:** Decorations are ornamental visual elements, like decorative headers or separators. (Fig. 40)

**MUST specify:** GraphicZone 724

**MAY specify:** N/A 725

**Special case(s):** N/A 726

**Potential post-processing:** N/A 727

**Suggested TEI mapping:** <graphic type="decoration"> 728

<figure><img src="image_29.png" /><figcaption>Figure 40. -Decoration example</figcaption></figure>
### 2.2.3 Maths (Maths)

731 **Definition:** Maths refers to elements of scientific format language that are distinct from natural language (e.g. mathematical symbols, formulas, chemical equations). It MUST be graphically separate from the main body of text. (Fig. 41)

737 **MUST specify:** N/A

738 **MAY specify:** MainZone

739 **Special case(s):** N/A

740 **Potential post-processing:** N/A

741 **Suggested TEI mapping:** <graphic type="maths">

**Equation de Murnaghan**

La base de cette équation est l'hypothèse de Murnaghan⁶⁰,⁶¹ énonçant que le module de compression, B, est une fonction linéaire de la pression p :

$$B = B_{\text{tr}} + B_{\text{p}} \text{, or } B = -\frac{\partial P}{\partial V} \qquad (3.44)$$

avec

$$\Theta = \frac{F}{F_s} = \eta^{-\gamma} \qquad (3.45)$$

<caption>Figure 41. -Maths example</caption>

### 2.2.4 Manuscript Addenda
(ManuscriptAddendum)

745 **Definition:** ManuscriptAddendum corresponds to any handwritten addition to the document, except for form fields. (Fig. 42)

748 **MUST specify:** MarginTextZone

749 **MAY specify:** N/A

750 **Special case(s):** N/A

751 **Potential post-processing:** N/A

752 **Suggested TEI mapping:** <note type="handwritten">>

<figure><img src="image_30.png" /><figcaption>Figure 42. -ManuscriptAddendum example</figcaption></figure>

### 2.2.5 Field (Field)

754 **Definition:** Field is a specific element that can only be associated with a FormZone. It encompasses both the field's heading (usually printed or typewritten) and the response, which can be handwritten or left empty. (Fig. 43)

755 **MUST specify:** FormZone

756 **MAY specify:** N/A

757 **Special case(s):** When handwritten responses overtake the field's boundaries in a way that the text is explicitly linked to the previous field, the bounding box SHOULD be extended to encompass the whole response.

758 **Potential post-processing:** Use a key-value approach to extract the content of each field (title and response, or lack thereof).

759 **Suggested TEI mapping:** <cell>

<figure><img src="image_31.png" /><figcaption>Figure 43. -Field example</figcaption></figure>

### 2.2.6 Drop Capitals (DropCapital)

771 **Definition:** The DropCapital contains any type of initial letter occupying a space corresponding to several lines of the main text, or bearing significant ornamentation. The drop capital can be a historiated, ornated, flourished, or painted initial excluding the following text line. (Fig. 44)

772 **MUST specify:** N/A

773 **MAY specify:** MainZone

774 **Special case(s):** N/A

775 **Potential post-processing:** Attach the drop capital to its associated word.

<figure><img src="image_32.png" /><figcaption>Figure 44. -DropCapital example</figcaption></figure>
## 3 Full-Page Annotations

The following images are fully annotated using the LADaS Annotation Guidelines. Labels are explicitly written on the pages for improved readability. Colours have been chosen to match each Level-1 category, with gradual variations distinguishing between Level-2 subtypes. The images are also available in SVG format in the project repository if needed. What follows is a description of the annotation choices made for some of the examples, intended to guide the reader through the logic of the tagging.

784

785

786

787

788

789

790
ORGANISATION DE L'EUROPE

L'ACCORD ENTRE EURATOM ET L'AIEA EN APPLICATION
DU TRAITÉ SUR LA NON-PROLIFÉRATION
DES ARMES NUCLÉAIRES
1-MainZone-Head

JAN GIJSSELS

2-MainZone-Signed

I. — INTRODUCTION

3-MainZone-Head

Les 20 et 22 septembre 1972 le texte d'un Accord entre l'Agence Inter-
nationale de l'Energie Atomique (A.I.E.A.), la Communauté Européenne de
l'Energie Atomique (EURATOM) et cinq membres de la Communauté, a
été approuvé par le Conseil des Communautés Européennes et par le
Conseil des Gouverneurs de l'A.I.E.A.
4-MainZone-P

4-MainZone-P

Cet Accord fixe les modalités selon lesquelles sera appliqué sur les
territoires des Etats non dotés d'armes nucléaires (1) qui sont membres de
5-MainZone-P

5-MainZone-P

6-MarginTextZone-PLabelled

7-MarginTextZone-PLabelled

8-MarginTextZone-P

<footnote>(*) Jan GIJSSELS, conseiller juridique de la Commission des Communautés euro-
péennes, chargé de cours à l'Université d'Anvers. Les opinions exposées au présen-
ticle n'engagent que leur auteur.
6-MarginTextZone-PLabelled</footnote>

<footnote>(1) Dans la terminologie du T.N.P. (art. IX, § 3) « un Etat doté d'armes nucléaires est un Etat qui a fabriqué et a fait exploser une arme nucléaire ou un autre dispositif nucléaire explosif avant le 1er janvier 1967 ». Il s'agit donc des Etats-Unis, de l'U.R.S.S. du Royaume-Uni, de la France et de la République Populaire de Chine. Depuis l'admission de cette dernière à l'O.N.U., le 26 octobre 1971, les cinq Etats dotés d'armes nucléaires sont les cinq membres permanents du Conseil de Sécurité. Ni la Chine Populaire, ni la France n'ont signé le T.N.P.</footnote>

<footnote>Les Etats membres de la Communauté qui ne sont pas dotés d'armes nucléaires sont
la Belgique, la République Fédérale d'Allemagne, l'Italie, le Luxembourg et les Pays-Bas
Dans le présent article nous les désignerons par l'expression « les cinq Etats membres ».</footnote>
Figure 45 shows the first page of an article extracted from the Persée website. Following the LADaS Guidelines, we defined several annotation zones:

• MainZone-Head (1, 2, 4): 793

– Main body of text: centre of the page, same font size than the rest of the text in the middle of the page, big margins. 794
795

– Top of a section, bold, centre and larger font size then the rest of the page. Separated from each other and the main body of text by large blank spaces and hyphens. 796
797

• MainZone-Signed (3): 798

– Main body of text: centre of the page, same font size than the rest of the text in the middle of the page, big margins. 799
800

– Isolated segment with name, centred, next to the header and on another line. 801

• MainZone-P (5, 6): 802

– At the centre of the page, with a larger font than the bottom text zones yet smaller font than the headers, no specific typographic informations and a blank separation. 803
804

– Basic prose paragraphs with indentation at the beginning, no label or numbering. 805

• MarginTextZone-P-Labelled (7, 8): 806

– At the bottom of the page, with smaller font than the rest of the text and a visual separation from the above paragraphs. 807
808

– Prose paragraph with indentation and label and immediately followed by another paragraph. 809
810

• MarginTextZone-P (9): 811

– At the bottom of the page, with smaller font than the rest of the text and a visual separation from the MainZone-P. 812
813

– Indented prose paragraph without a label. 814
<figure><img src="image_33.png" /><figcaption>Figure 46. Page from a thesis</figcaption></figure>
Figure 46 shows a page from a thesis extracted from theses.fr platform. We identify the following zones:

• MainZone-Continued (1): 817

– Main body of text: centre of the page, same font size than the rest of the text in the middle of the page, big margins. 818
819

– Paragraph at the top of the page that begins mid-sentence, without a capital letter or indentation. 820
821

• MainZone-P (2, 4, 5, 7): 822

– At the centre of the page, with larger font than the bottom text zones yet smaller font than the headers, no specific typographic informations and a blank separation. 823
824

– Basic prose paragraphs with indentation at the beginning, no label or numbering. 825

• MainZone-PQuoted (3, 6): 826

– At the centre of the page, in the middle of the other MainZone elements. 827

– Fully indented paragraphs, in contrast to the rest. 828

• MarginTextZone-PLabelled (8, 9, 10): 829

– At the bottom of the page, with a smaller font size than the rest of the text and a visual separation from the paragraphs above. 830
831

– Prose paragraph with indentation and label and immediately followed by another paragraph. 832
833

• NumberingZone (11): 834

– Floating text (Ab) at the bottom of the page containing the page number. 835

– For this final zone, which only contains an Ab, the Ab subtype is considered implicit, and thus omitted from the final label. The zone is simply labelled as NumberingZone. 836
837
<figure><img src="image_34.png" /><figcaption>Figure 47. Archaeological form</figcaption></figure>
Figure 47 features an archaeological form.

838

* **FormZone (14):** encompasses the form as a whole. It comes in contrast with the rest of the informational content on the left of the page.

840

- **FormZone-Field (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 17, 18, 19, 20, 23, 24, 25, 28, 29, 30, 31, 34, 35, 36, 37, 39):** Form fields containing both the heading of the field (e.g., location, type, length, witch, etc.) and the handwritten response in cells

841

842

843

- **FormZone-Part (16, 22, 26):** Some elements are grouped in parts by bigger zones around **FormZone-Fields** using lines and rectangles.

844

845

- **FormZone-Head (15, 21, 27):** Title of the **Form-Part**. Graphically (different orientation/blank space/lines) and typographically (bold, numbered, underscored) separated from the rest of the **FormZone-Fields** but within the **FormZone-Part** rectangle.

846

847

848

* **MainZone-Head (1, 32):**

849

- In capital letters, boldface.

850

- Even though the text is rotated at 90 degrees, it is still in the main zone of the document as it is the form's heading.

851

852

- Please note that (32) could also be considered a running title if found on consecutive form pages. However, it is impossible to tell based solely on this specific page. As a result, we opted for **MainZone-Head**.

853

854

855

* **GraphicZone-Decoration (33):** logo of "Cotswold Archaeology". Purely ornamental visual element with no semantic value.

856

857

* **NumberingZone (38):**

858

- Element that appears to be the form number. Graphically separated from the rest of the document, with only numbers in it.

859

860

- Floating text (**Ab**) at the bottom of the page.

861

- For this final zone, which only contains an **Ab**, the **Ab** subtype is considered implicit, and thus omitted from the final label. The zone is simply labelled as **NumberingZone**.

862

863
<figure><img src="image_35.png" /><figcaption>4 - FormZone</figcaption></figure>

<figure><img src="image_36.png" /><figcaption>26- NumberingZone</figcaption></figure>

<caption>Figure 48. Archaeological form</caption>
Figure 48 features an archaeological form.

• MainZone-Head (1):

– Main body of text: centre of the page, same font size than the rest of the text in the middle of the page, big margins.

– Top of a section, bold, underlined, and larger font size than the rest of the page. Separated from the main body of text by a larger blank space.

• FormZone (2, 4): Documents separated from the rest of the page using line segments. Freeform layout with non-uniform row structure and designed for manual entry.

– FormZone-Field (5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25): Form fields containing both the heading of the field (e.g., location, type, length, witch, etc.) and the handwritten response in grid lines.

• MainZone-PStyled (3):

– Below the heading and adds information.

– In parentheses.

• NumberingZone (26):

– Element that appears to be the form number. Graphically separated from the rest of the document.

– Floating text (Ab) at the bottom of the page, but as NumberingZone only contains an Ab, the Ab subtype is considered implicit, and thus omitted from the final label. The zone is simply labelled as NumberingZone.

– Please note that in this case we cannot be 100% sure as to the nature of this label because it cannot be read precisely. We decided on NumberingZone because it is usually the place where we find the form number in forms.
La plupart des régions enregistrent des taux bas (minimum : 0,6% de fuites en Nord-Pas-de-Calais ; 0,9% d'attractions en Corse), même si certaines se démarquent avec des taux de fuites sunérieurs à 6% comme la Picardie (13,0 %), l'Auvergne (8,3%), la Bourgogne (8,1%), la Haute-Normandie (7,9%), le Poitou-Charentes (7,8%) et la région Centre (6,8%).

Les patients de ces régions (Annexe 0, Tableau 27) se dirigent préférentielleMainZone-F

- la Picardie vers l'Ile-de-France (6,0%), la Champagne-Ardenne (2,4%), la Haute-Normandie (1,1%) et le Nord-Pas-de-Calais (3,2%);

- la Haute-Normandie vers l'Ile-de-France (1,9%), la Picardie (1,2%), la région Centre (1,3%) et la Basse-Normandie (3,2%);

- la région Centre vers l'Ile-de-France (3,6%) et la BcMainZone-Item

- l'Auvergne vers la région RhôrMainZone-Item

- le Poitou-Charentes vers la région Centre (1,2%), les Pays-de-l'Île-de-France (3,4%), l'Aquitaine (1,6%) et le Limousin (1,2%);

- la Bourgogne vers l'Ile-de-France (1,3%), la Franche-Comté (1,9%), Rhône-Alpes (1,6%), L'Auvergne (2,0%).

<table><caption>Tableau 11 : hospitalisations pour accouchement, répartition des fuites et aITableZone-Head</caption><thead><tr><th rowspan="2"></th><th colspan="3">Région de résidence Fuites</th><th colspan="3">Région d'hospitalisation Attractions</th></tr><tr><th>Nombre total de séjours</th><th>N</th><th>%</th><th>Nombre total de séjours</th><th>N</th><th>%</th></tr></thead><tbody><tr><td>11 : ILE-DE-FRANCE</td><td>176 995</td><td>2 245</td><td>1,3</td><td>178 595</td><td>3 845</td><td>2,2</td></tr><tr><td>21 : CHAMPAGNE-ARDENNE</td><td>15 244</td><td>773</td><td>5,1</td><td>15 396</td><td>925</td><td>6,0</td></tr><tr><td>22 : PICARDIE</td><td>24 159</td><td>3 131</td><td>13,0</td><td>22 095</td><td>1 067</td><td>4,8</td></tr><tr><td>23 : HAUTE-NORMANDIE</td><td>23 364</td><td>1 839</td><td>7,9</td><td>22 129</td><td>604</td><td>2,7</td></tr><tr><td>24 : CENTRE</td><td>29 479</td><td>2 014</td><td>6,8</td><td>28 604</td><td>1 139</td><td>4,0</td></tr><tr><td>25 : BASSE-NORMANDIE</td><td>15 891</td><td>509</td><td>3,2</td><td>16 771</td><td>1 389</td><td>8,3</td></tr><tr><td>26 : BOURGOGNE</td><td>17 150</td><td>1 393</td><td>8,1</td><td>17 021</td><td>1 264</td><td>7,4</td></tr><tr><td>31 : NORD-PAS-DE-CALAIS</td><td>54 828</td><td>303</td><td>0,6</td><td>55 608</td><td>1 083</td><td>2,0</td></tr><tr><td>41 : LORRAINE</td><td>25 547</td><td>723</td><td>2,8</td><td>25 605</td><td>781</td><td>3,1</td></tr><tr><td>42 : ALSACE</td><td>21 461</td><td>293</td><td>1,4</td><td>21 812</td><td>644</td><td>3,0</td></tr><tr><td>43 : FRANCHE-COMTE</td><td>13 632</td><td>606</td><td>4,5</td><td>13 509</td><td></td><td></td></tr><tr><td>52 : PAYS DE LA LOIRE</td><td>44 024</td><td>1 587</td><td>3,6</td><td>43 809</td><td>1 372</td><td>3,1</td></tr><tr><td>53 : BRETAGNE</td><td>36 029</td><td>392</td><td>1,1</td><td>36 670</td><td>1 033</td><td>2,8</td></tr><tr><td>54 : POITOU-CHARENTES</td><td>18 055</td><td>1 409</td><td>7,8</td><td>17 212</td><td>566</td><td>3,3</td></tr><tr><td>72 : AQUITAINE</td><td>33 765</td><td>551</td><td>1,6</td><td>34 423</td><td>1 209</td><td>3,5</td></tr><tr><td>73 : MIDI-PYRENEES</td><td>32 092</td><td>1 320</td><td>4,1</td><td>31 336</td><td>564</td><td>1,8</td></tr><tr><td>74 : LIMOUSIN</td><td>6 894</td><td>287</td><td>4,2</td><td>7 510</td><td>903</td><td>12,0</td></tr><tr><td>82 : RHONE-ALPES</td><td>81 594</td><td>1 480</td><td>1,8</td><td>81 827</td><td>1 713</td><td>2,1</td></tr><tr><td>83 : AUVERGNE</td><td>13 473</td><td>1 114</td><td>8,3</td><td>13 301</td><td>942</td><td>7,1</td></tr><tr><td>91 : LANGUEDOC-ROUSSILLON</td><td>29 859</td><td>1 367</td><td>4,6</td><td>29 407</td><td>915</td><td>3,1</td></tr><tr><td>93 : PROVENCE-ALPES-COTE D'AZUR</td><td>58 599</td><td>719</td><td>1,2</td><td>59 548</td><td>1 668</td><td>2,8</td></tr><tr><td>94 : CORSE</td><td>2 939</td><td>80</td><td>2,7</td><td>2 885</td><td>26</td><td>0,9</td></tr></tbody><tfoot><tr><td>Total</td><td>775 073</td><td>24 135</td><td>3,1</td><td>775 073</td><td>24 135</td><td>3,1</td></tr></tfoot></table>

<caption>Figure 49. Page from a thesis with a table</caption>
<figure><img src="image_37.png" /><figcaption>FIGURE 2.10 – Complétion par une méthode basée *patch* locale en fonction de la taille du patch. De gauche à droite et de bas en haut, nous avons des *patches de taille 1, 1, 2 et 15 pixels*.</figcaption></figure>

cohérence de la complétion. Elles requièrent aussi plusieurs d'i**MainZone-Continued** une convergence et ainsi raffiner la partie masquée.

SUN *et al.* [Sun+05] proposent de séparer la propagation de la texture de la propagation de la structure. Pour cela, ils invitent d'abord l'utilisateur à indiquer les structures incomplètes en les traçant. Ensuite, chaque pixel appartenant au tracé et **MainZone-P** reçoit un label correspondant à un pixel connu du tracé ; l'attribution du label se fait par une énergie à minimiser. La texture est ensuite complétée par une approche gloutonne [CPT03] de la sous-section précédente.

WEXLER *et al.* [WSI07] proposent une complétion en calculant, pour un pixel du masque, une moyenne pondérée des pixels provenant de plusieurs *patches*, qui sont superposant. Ils définissent également une fonction de cohérence globale qui mesure, pour chaque pixel, la similarité entre les *patches* qui le recouvrent et les *patches* de la zone connue :

$$ \text{Coherence} = \prod_{p \in \Omega} n_{\text{MainZone-Maths}} \qquad (2.20) $$

où $sim_g$ est une fonction de similarité couplée à un noyau gaussien

$$ sim_g(\Psi_p, \Psi_q) = \exp \left( \frac{\tau}{2\sigma^2} \right) \qquad (2.21) $$

où $\sigma$ est l'écart-type du noyau gaussien et $sim$ une fonction de similarité. L'intérêt de cette méthode multi-résolutions est d'utiliser une image construite à une résolution donnée comme initialisation pour la résolution supérieure. Cette **MainZone-Continued** l'algorithme *PatchMatch* est l'approche classique d'inpainting basée *PatchMatch* et notamment utilisée dans le procédé *Content-aware fill* de Photoshop. Elle sera notamment détaillée dans la section 2.4.
<figure><img src="image_38.png" /><figcaption>Figure 51. Page from a 17th-century play</figcaption></figure>
<figure><img src="image_39.png" /><figcaption>Figure 52. Page from a 19th-century encyclopedia</figcaption></figure>
<figure><img src="image_40.png" /><figcaption>Figure 53. Bibliographic entries and commentaries</figcaption></figure>
<figure><img src="image_41.png" /><figcaption>Figure 54. 19th-century document title page</figcaption></figure>
887

# 4 Addendum on Line Segmentation

888

Line segmentation will be done in a second step. The lines will be annotated according to the vocabulary which already exists in SegmOnto, particularly DefaultLine and HeadingLine. It will be possible to assign a subtype to the line type depending on whether the text is typed or printed:

889

890

891

DefaultLine-Typed or DefaultLine-Print.
References

<table><tr><td>Scott Bradner. 1997. Key Words for Use in RFCs to Indicate Requirement Levels. Technical Report RFC 2119, Harvard University. 1</td><td>892</td></tr><tr><td>Thibault Clérice, Juliette Janès, Hugo Scheithauer, Sarah Bénière, Laurent Romary, and Benoît Sagot. 2024. Layout Analysis Dataset with SegmOnto. In DH2024 – Reinvention and Responsibility. 1</td><td>893<br>894<br>895<br>896<br>897</td></tr><tr><td>Simon Gabay, Ariane Pinche, Kelly Christensen, and Jean-Baptiste Camps. 2024. SegmOnto: A Controlled Vocabulary to Describe and Process Digital Facsimiles. Journal of Data Mining and Digital Humanities. 1</td><td>898<br>899<br>900</td></tr><tr><td>TEI Consortium. 2025. TEI P5: Guidelines for Electronic Text Encoding and Interchange, version 4.9.0. 1</td><td>901<br>902</td></tr></table>