Module 6: Primary Sources

You can test what you've learned in the tutorial for TEI by Example Module 6: Primary Sources by taking the following quiz.

It consists of a number of multiple choice questions, each providing a number of possible answers. Select the answer you think is correct by clicking it. There are 2 possibilities:

The answer is correct: hurrah! a popup box appears telling you why this is the correct answer. You can still check why the other answers are incorrect by clicking them. This will not reduce your score, though.
The answer is incorrect: pity, but you get a second chance! A popup box tells you why the answer is incorrect. You can still choose the other answers until you find the correct one. Mind you, until you clicked the correct answer, each incorrect answer will reduce your score.

The @hand attribute on an <add> element specifies:
1. that the addition contains hand written text.
2. who has identified the text as an addition.
3. the hand that has been identified as responsible for the addition.
4. the hand (L / R) with which the addition has been written.
What element is used for a word that had been corrected by the author?
1. <corr>
2. <subst>
3. <wrong>
4. <supplied>
How can transcriptions of primary manuscripts be linked with digital facsimiles?
1. Not at all.
2. By means of a <figure> element for each scan.
3. By means of a <ref> element.
4. By means of a @facs attribute.
What is the <unclear> element used for?
1. To indicate text that is partly legible but can't be transcribed confidently.
2. To indicate text of which the exact meaning is unclear.
3. To indicate that the enclosed text was completely illegible, and that the editor is not 100% sure of the text s/he has supplied.
4. To indicate text whose legibility has suffered from damage.
What is a plausible encoding of following errors:
```
Father liked the Beetles but mother liked the Roling Stones
```
1. ```
Father liked the <sic>Beetles</sic> but mother liked the <sic>Roling Stones</sic>.
```
 Father liked the
 <sic>Beetles</sic>
 but mother liked the
 <sic>Roling Stones</sic>
 .
2. ```
Father liked the <corr>Beetles</corr> but mother liked the <corr>Roling Stones</corr>.
```
 Father liked the
 <corr>Beetles</corr>
 but mother liked the
 <corr>Roling Stones</corr>
 .
3. ```
Father liked the <corr>Beatles</corr> but mother liked the <sic>Roling Stones</sic>.
```
 Father liked the
 <corr>Beatles</corr>
 but mother liked the
 <sic>Roling Stones</sic>
 .
4. ```
Father liked the Be<del>e</del><add>a</add>tles but mother liked the Rol<supplied reason="missing">l</supplied>ing Stones.
```
 Father liked the Be
 <del>e</del>
 <add>a</add>
 tles but mother liked the Rol
 <supplied reason="missing">l</supplied>
 ing Stones.
The <gap> element indicates:
1. unusual space between words
2. missing words in the source document
3. words omitted from the transcription
4. a hole in the support material of the text
A scar in the source material running over 5cm could be encoded as follows:
1. ```
<damage extent="5" unit="cm"/>
```
 <damage extent="5" unit="cm"/>
2. ```
<damage length="5 cm"/>
```
 <damage length="5 cm"/>
3. ```
<scar extent="5cm"/>
```
 <scar extent="5cm"/>
4. ```
<damage unit="cm" quantity="5"/>
```
 <damage unit="cm" quantity="5"/>
How would you encode a deletion of two and a half paragraphs?
1. This can't be done due to conflicting XML structures: the deletions do not nest properly within their paragraphs.
2. ```
<del>
 ...
 ...
</del>
<del>...</del>... 
```
 <del>
 ...
 ...
 </del>
 
 <del>...</del>
 ... 
3. ```
<delSpan spanTo="#delEnd"/>
...
...
...<anchor xml:id="delEnd"/>...
```
 <delSpan spanTo="#delEnd"/>
 ...
 ...
 ...
 <anchor id="delEnd"/>
 ...
4. ```
<delSpan/>
...
...
...<anchor/>...
```
 <delSpan/>
 ...
 ...
 ...
 <anchor/>
 ...

↑Dashboard

Module 6 Sections

Module 6: Primary Sources