XML - User contributions [en]

Retorical structure (ePistolarium)

2018-03-06T11:11:31Z

WRA: Disallow opener and closer elements

Letters usually have opening and closing phrases.
These are encoded with the <code>ana</code> attribute of <code>p</code> and <code>seg</code> elements.

Example: https://correspondence.huygens.knaw.nl/documents/d815d122-68db-4753-bfa4-c8b60bd248f1
(paragraph interpreted as opener)

<pre>
<div type="artifact" subtype="letter">
Mon Révérend Père,
Vous m'interrogez comme si je devais tout savoir, ...
...
</div>
</pre>

Example: https://correspondence.huygens.knaw.nl/documents/d815d122-68db-4753-bfa4-c8b60bd248f1
(paragraph interpreted as closer)

<pre>
<div type="artifact" subtype="letter">
...
Mandez-moi, je vous prie, ... vos bonnes grâces.
Votre très humble Desc.
Ce 12<hi rend="superscript">e</hi> jour de Carême 1630.
</div>
</pre>

Example: https://correspondence.huygens.knaw.nl/documents/f687c50b-6765-4519-bc5f-833c499ae453
(closer in paragraph)

<pre>
<div type="artifact" subtype="letter">
...
Het is dus beter, ...; er wordt al te veel gebabbeld door kwaadwillige menschen. <seg ana="#closer">28 Jull. 1634.</seg>
</div>
</pre>

XML ePistolarium Guidelines

2018-03-06T11:04:48Z

WRA: Disallow opener and closer elements

This section of the XML Wiki documents the TEI as currently used in the ePistolarium project.

The following may serve to get a feel for the structure of the documents in the ePistolarium:
<pre>
<TEI>
<teiHeader>
<meta type="uuid" value="47a2704e-4b7c-423b-905d-a6bfd4853e95"/>
<meta type="id" value="2295"/>
<meta type="date" value="1640-01-05"/>
<meta type="sender" value="knuyt.johan.1587-1654"/>
<meta type="senderloc" value="se:middelburg.nld"/>
<meta type="recipient" value="huygens.constantijn.1596-1687"/>
<meta type="recipientloc" value="se:den-haag.nld" resp="inferred"/>
</teiHeader>
<text>
<body>
<div xml:id="div-1" xml:lang="nl" type="artifact" subtype="letter">
Van de drie genomineerden voor het ‘kieser-ampt’<anchor type="note" n="2-8"/> van <placeName key="se:middelburg.nld">Middelburg</placeName> schijnt <persName>Sijmen van Trijst</persName> de meest geschikte. Ik wil Z.H. met zulk een zaakje niet lastig vallen.
<closer>
Uyt <placeName key="se:middelburg.nld">Middelb.</placeName>, den 5 Januar. 1640.
</closer>
</div>
<div xml:id="div-2" xml:lang="nl" type="notes">
<note n="2-8">Te Middelburg werden de raadsleden gekozen door burgemeesters en schepenen en deze door 24 mannen, van welke 12 de raadsleden waren en de andere 12 aanzienlijke burgers, die zelve geen burgemeester of schepen konden worden. Zij heetten ‘kiezers’, werden door den Stadhouder benoemd en bleven hun leven lang dat recht behouden.</note>
</div>
</body>
</text>
</TEI>
</pre>

Below follows a list of all TEI elements used in the ePistolarium:
{| class="wikitable"
|-
! Element
! Description
! Documentation
|-
| anchor
|
| [[Local annotations (ePistolarium)]]
|-
| body
|
| [[Text structure (ePistolarium)]]
|-
| cell
|
| [[Tables (ePistolarium)]]
|-
| corr
| correction
| [[Transcription (ePistolarium)]]
|-
| date
|
| [[Miscellaneous (ePistolarium)]]
|-
| div
| text division
| [[Text structure (ePistolarium)]]
|-
| figDesc
| figure description
| [[Images (ePistolarium)]]
|-
| figure
|
| [[Images (ePistolarium)]]
|-
| formula
|
| [[Miscellaneous (ePistolarium)]]
|-
| geogName
| grographical name
| [[Names (ePistolarium)]]
|-
| graphic
|
| [[Images (ePistolarium)]]
|-
| head
| heading
| [[Text structure (ePistolarium)]]
|-
| hi
| highlighted
| [[Rendering (ePistolarium)]]
|-
| item
|
| [[Lists (ePistolarium)]]
|-
| l
| line
| [[Poems (ePistolarium)]]
|-
| label
|
| [[Lists (ePistolarium)]]
|-
| lb
| line beginning
| [[Transcription (ePistolarium)]]
|-
| lg
| line group
| [[Poems (ePistolarium)]]
|-
| list
|
| [[Lists (ePistolarium)]]
|-
| meta
| metadata item
| [[Metadata (ePistolarium)]]
|-
| name
|
| [[Names (ePistolarium)]]
|-
| note
|
| [[Local annotations (ePistolarium)]]
|-
| orgName
| organization name
| [[Names (ePistolarium)]]
|-
| p
| paragraph
| [[Text structure (ePistolarium)]]
|-
| pb
| page beginning
| [[Transcription (ePistolarium)]]
|-
| persName
| personal name
| [[Names (ePistolarium)]]
|-
| placeName
| place name
| [[Names (ePistolarium)]]
|-
| quote
| quotation
| [[Miscellaneous (ePistolarium)]]
|-
| ref
| reference
| [[Miscellaneous (ePistolarium)]]
|-
| row
|
| [[Tables (ePistolarium)]]
|-
| rs
| referencing string
| [[Names (ePistolarium)]]
|-
| seg
| arbitrary text segment
| [[Text structure (ePistolarium)]]
|-
| sic
| incorrect text
| [[Transcription (ePistolarium)]]
|-
| space
|
| [[Transcription (ePistolarium)]]
|-
| table
|
| [[Tables (ePistolarium)]]
|-
| TEI
|
| This page
|-
| teiHeader
|
||[[Metadata (ePistolarium)]]
|-
| text
|
| [[Text structure (ePistolarium)]]
|-
| title
|
| [[Names (ePistolarium)]]
|}

Metadata (ePistolarium)

2018-02-15T14:56:47Z

WRA: Clarify use of dates.

The metadata in the ePistolarium documents is contained in the <code>teiHeader</code> element. Each item is a <code>meta</code> milestone element with attributes <code>type</code> and <code>value</code>. The standard types are as follows:
; uuid : the unique identifier of the letter.
; correspondence : the identifier of the correspondence; required.
; id : the identifier of letter in the correspondence; required, must be unique in the correspondence.
; date : the date of writing of the letter. Values are encoded in the [http://www.loc.gov/standards/datetime/ Extended Date/Time Format]. We use the Gregorian calendar, so Julian dates must be converted. Furthermore, if multiple dates are used in a letter, the last one is used because it approximates the date of sending best (ranges are used for uncertainty).
; sender : the identifier of the sender (may occur multiple times); use value "?" if unknown.
; senderloc : the identifier for the location where the letter was sent; use value "?" if unknown.
; recipient : the identifier of the recipient (may occur multiple times); use value "?" if unknown.
; recipientloc : the identifier for the location where the letter was received; use value "?" if unknown.

Each metadata item is allowed only once, except for "sender" and "recipient.

Example: https://correspondence.huygens.knaw.nl/documents/301ba075-dde3-4fa4-a82e-0c9ba668bb06

<pre>
<TEI>
<teiHeader>
<meta type="uuid" value="301ba075-dde3-4fa4-a82e-0c9ba668bb06"/>
<meta type="correspondence" value="desc004"/>
<meta type="id" value="1001"/>
<meta type="date" value="1619-01-24"/>
<meta type="sender" value="descartes.rene.1596-1650"/>
<meta type="senderloc" value="se:breda.nld"/>
<meta type="recipient" value="beeckman.isaac.1588-1637"/>
<meta type="recipientloc" value="se:middelburg.nld"/>
</teiHeader>
...
</pre>

Miscellaneous (ePistolarium)

2018-02-08T09:08:28Z

WRA: Resolved q/quote issue.

Apart from name annotations a number of other elements is used for annotating interpretation of the text.
Note that these elements are not necessarily rendered in a distinctive way.

== Dates ==

The <code>date</code> element contains a date in any format.
Two attributes may be used:
* <code>@when</code> supplies the value of the date in the form <code>yyyy-mm-dd</code>.
* <code>@calendar</code> indicates the calendar to which the date belongs.

Example: https://test.epistolarium.huygens.knaw.nl/documents/dc1c749c-7e17-4c54-93e2-f274409f0797
(simple date)

<pre>
A <placeName>la Haye</placeName> ce <date>17. Mars 1621</date>.
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/80496f14-b59f-4752-b313-8d39a613e7d8
(date with attributes)

<pre>
De <placeName>Berlin</placeName>, ce <date calendar="julian" when="1646-10-10">30<hi rend="superscript">me</hi> de Septembre</date>.
</pre>

== Formulas ==

The <code>formula</code> element contains a mathematical or other formula.

Example: https://test.epistolarium.huygens.knaw.nl/documents/4a760049-e497-4a4a-a7ef-cc44ab1227dc
(simple formulas)

<pre>
Datis itaque positione rectis <formula>BA</formula>, <formula>AC</formula> angulum comprehendentibus,
punctoque intra angulum dato <formula>D</formula>, oporteat per ipsum ducere rectam <formula>BDC</formula>,
ita ut triangulum <formula>BAC</formula> sit omnium quae ita abscindi possunt minimum. Hoc autem satis
facile est. Illud difficilius: posito nimirum angulo <formula>BAC</formula> recto ducere per punctum
<formula>D</formula> intra ipsum dato rectam <formula>BDC</formula> omnium brevissimam.
</pre>

The Descartes correspondence contains <code>formula</code> elements with TeX notation.
However, these elements occur in a <code>figDesc</code> element, which is not rendered.
The rendered form is defined by the <code>graphic</code> element.

Example: https://test.epistolarium.huygens.knaw.nl/documents/686db5cd-8759-4e66-9db5-a6f82fe42b17
(formula in TeX notation)

<pre>
... le côté droit est <figure rend="inline"><graphic url="AM2L156F067.gif"/><figDesc><formula notation="TeX">${\displaystyle\strut Bq\over \displaystyle\strut D}$</formula></figDesc></figure>, ...
</pre>

== Quotations ==

The <code>quote</code> element contains a phrase or passage attributed by the narrator or author to some agency external to the text.
For text that is to be rendered as a block quote the attribute <code>rend="block"</code> is used.
Note that a <code>quote</code> may contain paragraphs, encoded with the <code>p</code> element.

Example: https://correspondence.huygens.knaw.nl/documents/c151aa14-306d-4993-aa1b-e175a469e566
(simple quote)

<pre>
Ick hebbe uwe schrijven van den 9 April wel ontfangen, en daer in enige woorden aldus luijden. <quote>waer door dan het punt <formula>B</formula> lichtelijk gevonden wort, als men alleenlijk op 2 sijden des driehoeks <formula>DFG</formula> circelboogen beschrijft die de gevonden hoeken tot de sijden behoorende begrijpen. want de doorsnijding van sulke 2 boogen is het punt <formula>B</formula>.</quote>
</pre>

Example: https://correspondence.huygens.knaw.nl/documents/839feb23-5c5c-44d3-ab44-868f6644ed53
(block quote)

<pre>
Quam ob causam ego ob communionem studiorum, quae etiam ignotissimos invicem conjunctos reddit iuxta illud: <quote rend="block">Nullus amicitiae gradus est constantior orbe, Quam qui per studii contigit esse modum</quote> intermittere non debui hisce meis literulis tuam dominationem invisere ac per hunc mihi missum tabellarium salutare simulque dolenter significare filium meum unicum, pro ut in literis regiae majestatis inscriptis a filio meo tuae dominationi ad legendum tradendis latius sit deductum, insperanter esse tractatum, nunc apud vos commorari, quem tuis curis commendandum esse duxi hoc modo, cum perdifficile sit apud tantum regem literas hinc transmissas tradi, multo perdifficilius esse super iisdem exoptatum responsum obtinere.
</pre>

== References ==

The <code>ref</code> element contains a textual reference to some information.
Currently only used with attribute <code>@type="bible"</code> to refer to a specific part of the Bible.

Example: https://correspondence.huygens.knaw.nl/documents/f868a963-2b51-4be8-bfca-b2c29cff097d

<pre>
Atqui si <hi rend="italic">multi vocati, pauci electi</hi>, <ref type="bible">Matth. XX. 16</ref>;...
</pre>

N.B. Currently under discussion.

XML ePistolarium Guidelines

2018-02-08T09:01:50Z

WRA: Resolved q/quote issue.

This section of the XML Wiki documents the TEI as currently used in the ePistolarium project.

The following may serve to get a feel for the structure of the documents in the ePistolarium:
<pre>
<TEI>
<teiHeader>
<meta type="uuid" value="47a2704e-4b7c-423b-905d-a6bfd4853e95"/>
<meta type="id" value="2295"/>
<meta type="date" value="1640-01-05"/>
<meta type="sender" value="knuyt.johan.1587-1654"/>
<meta type="senderloc" value="se:middelburg.nld"/>
<meta type="recipient" value="huygens.constantijn.1596-1687"/>
<meta type="recipientloc" value="se:den-haag.nld" resp="inferred"/>
</teiHeader>
<text>
<body>
<div xml:id="div-1" xml:lang="nl" type="artifact" subtype="letter">
Van de drie genomineerden voor het ‘kieser-ampt’<anchor type="note" n="2-8"/> van <placeName key="se:middelburg.nld">Middelburg</placeName> schijnt <persName>Sijmen van Trijst</persName> de meest geschikte. Ik wil Z.H. met zulk een zaakje niet lastig vallen.
<closer>
Uyt <placeName key="se:middelburg.nld">Middelb.</placeName>, den 5 Januar. 1640.
</closer>
</div>
<div xml:id="div-2" xml:lang="nl" type="notes">
<note n="2-8">Te Middelburg werden de raadsleden gekozen door burgemeesters en schepenen en deze door 24 mannen, van welke 12 de raadsleden waren en de andere 12 aanzienlijke burgers, die zelve geen burgemeester of schepen konden worden. Zij heetten ‘kiezers’, werden door den Stadhouder benoemd en bleven hun leven lang dat recht behouden.</note>
</div>
</body>
</text>
</TEI>
</pre>

Below follows a list of all TEI elements used in the ePistolarium:
{| class="wikitable"
|-
! Element
! Description
! Documentation
|-
| anchor
|
| [[Local annotations (ePistolarium)]]
|-
| body
|
| [[Text structure (ePistolarium)]]
|-
| cell
|
| [[Tables (ePistolarium)]]
|-
| closer
|
| [[Retorical structure (ePistolarium)]]
|-
| corr
| correction
| [[Transcription (ePistolarium)]]
|-
| date
|
| [[Miscellaneous (ePistolarium)]]
|-
| div
| text division
| [[Text structure (ePistolarium)]]
|-
| figDesc
| figure description
| [[Images (ePistolarium)]]
|-
| figure
|
| [[Images (ePistolarium)]]
|-
| formula
|
| [[Miscellaneous (ePistolarium)]]
|-
| geogName
| grographical name
| [[Names (ePistolarium)]]
|-
| graphic
|
| [[Images (ePistolarium)]]
|-
| head
| heading
| [[Text structure (ePistolarium)]]
|-
| hi
| highlighted
| [[Rendering (ePistolarium)]]
|-
| item
|
| [[Lists (ePistolarium)]]
|-
| l
| line
| [[Poems (ePistolarium)]]
|-
| label
|
| [[Lists (ePistolarium)]]
|-
| lb
| line beginning
| [[Transcription (ePistolarium)]]
|-
| lg
| line group
| [[Poems (ePistolarium)]]
|-
| list
|
| [[Lists (ePistolarium)]]
|-
| meta
| metadata item
| [[Metadata (ePistolarium)]]
|-
| name
|
| [[Names (ePistolarium)]]
|-
| note
|
| [[Local annotations (ePistolarium)]]
|-
| opener
|
| [[Retorical structure (ePistolarium)]]
|-
| orgName
| organization name
| [[Names (ePistolarium)]]
|-
| p
| paragraph
| [[Text structure (ePistolarium)]]
|-
| pb
| page beginning
| [[Transcription (ePistolarium)]]
|-
| persName
| personal name
| [[Names (ePistolarium)]]
|-
| placeName
| place name
| [[Names (ePistolarium)]]
|-
| quote
| quotation
| [[Miscellaneous (ePistolarium)]]
|-
| ref
| reference
| [[Miscellaneous (ePistolarium)]]
|-
| row
|
| [[Tables (ePistolarium)]]
|-
| rs
| referencing string
| [[Names (ePistolarium)]]
|-
| seg
| arbitrary text segment
| [[Text structure (ePistolarium)]]
|-
| sic
| incorrect text
| [[Transcription (ePistolarium)]]
|-
| space
|
| [[Transcription (ePistolarium)]]
|-
| table
|
| [[Tables (ePistolarium)]]
|-
| TEI
|
| This page
|-
| teiHeader
|
||[[Metadata (ePistolarium)]]
|-
| text
|
| [[Text structure (ePistolarium)]]
|-
| title
|
| [[Names (ePistolarium)]]
|}

Names (ePistolarium)

2018-01-30T14:00:08Z

WRA: Replace geogName and orgName

As a result of automated or manual processing named entities are annotated in the text.
The following TEI elements are used:
<code>name</code>, <code>persName</code>, <code>placeName</code>, <code>rs</code>, and <code>title</code>.

<code>rs</code> (referencing string) contains a general purpose name or referring string.
:The ePistolarium uses this with the following values of the <code>@type</code> attribute.
::<code>type="geo"</code> for geographical names
::<code>type="org"</code> for organization names
::<code>type="person"</code> for person names
::<code>type="place"</code> for place names
:In both cases the references are indirect, for instance "X's sister".
:The <code>@key</code> attribute is used when the name has been identified.

<code>persName</code> (personal name) contains a proper noun or proper-noun phrase referring to a person.
:The <code>@key</code> attribute is used when the name has been identified.

<code>placeName</code> contains an absolute or relative place name.
:The <code>@key</code> attribute is used when the name has been identified.

<code>title</code> contains a title for any kind of work.
:No normalization is used.

<code>name</code> contains a proper noun or noun phrase.
:Used for names that do nor belong to the categories mentioned above.
:The <code>@type</code> attribute is used to assign a category, currently "bible", "code", or "group".

TO DO: After discussion with Peter Boot, we decided on a standard that uses <code>rs</code> is the principal way to annote names, with <code>type</code> to distinguish between categories (person, place, etc.) and <code>key</code> to indicate identifiers for these names.

TO DO: Add examples.

Lists (ePistolarium)

2018-01-30T13:56:25Z

WRA: Remove label example

Lists are encoded with the <code>list</code>, <code>item</code>, and <code>label</code> elements.

* <code>list</code> contains any sequence of items organized as a list;

* <code>item</code> contains one component of a list;

* <code>label</code> contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary.

There should be no bullet, number or other label before an item, unless explicitly indicated by means of a <code>label</code>.

Example: https://correspondence.huygens.knaw.nl/documents/a4e640b1-bd41-4c34-b7ac-a1441c9e97c1
(list)

<pre>
Voici certains livres que je voudrais examiner
<list>
<item>Rebenstock Sermons mensuels de Luther</item>
<item>Mathaesius, Vie de Martin Luther</item>
<item>Jérôme Bolsec, Vita Calvini, Bezae etc.</item>
<item>Simon Starovolscius, Elogia centum illustrium Polonorum.</item>
<item>Caspar Chicocius Entretiens.</item>
<item>Bibliotheca Romana de Prospero Mandosio Rome 1682 4°</item>
<item>Vitae clarissimorum jurisconsultorum éditées avec des notes par Frideric Jacob Leickherr, Juris Utriusque Doctor Leipzig 1686 8°</item>
</list>
Je n'ai guère espoir avec ce livre d'éviter la rencontre de tout obstacle...
</pre>

Example: https://correspondence.huygens.knaw.nl/documents/2b46b15c-e62f-4cf5-9ed6-e1645d2af0ad
(groups a series of mathematical formulas)

<pre>
... Haec adde 7/6<hi rend="italic">y</hi>, fit
<list>
<item>7/6<hi rend="italic">y</hi> + 7/48 <hi rend="italic">z</hi> ∞ 86.</item>
<item>56<hi rend="italic">y</hi> + 7<hi rend="italic">z</hi> ∞ 4128.</item>
<item>7<hi rend="italic">z</hi> ∞ 4128 - 56<hi rend="italic">y.</hi></item>
<item><hi rend="italic">z</hi> ∞ 589 5/7 - 8 <hi rend="italic">y.</hi></item>
</list>
Si ergo haberem numerum <hi rend="italic">y</hi> dierum integrarum, ...
</pre>

TODO: Implement TEI approach (and Huygens standard): <label> and <item> are siblings, don't use <label in <item>.

Miscellaneous (ePistolarium)

2018-01-23T11:59:22Z

WRA: Add note.

Apart from name annotations a number of other elements is used for annotating interpretation of the text.
Note that these elements are not necessarily rendered in a distinctive way.

== Dates ==

The <code>date</code> element contains a date in any format.
Two attributes may be used:
* <code>@when</code> supplies the value of the date in the form <code>yyyy-mm-dd</code>.
* <code>@calendar</code> indicates the calendar to which the date belongs.

Example: https://test.epistolarium.huygens.knaw.nl/documents/dc1c749c-7e17-4c54-93e2-f274409f0797
(simple date)

<pre>
A <placeName>la Haye</placeName> ce <date>17. Mars 1621</date>.
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/80496f14-b59f-4752-b313-8d39a613e7d8
(date with attributes)

<pre>
De <placeName>Berlin</placeName>, ce <date calendar="julian" when="1646-10-10">30<hi rend="superscript">me</hi> de Septembre</date>.
</pre>

== Formulas ==

The <code>formula</code> element contains a mathematical or other formula.

Example: https://test.epistolarium.huygens.knaw.nl/documents/4a760049-e497-4a4a-a7ef-cc44ab1227dc
(simple formulas)

<pre>
Datis itaque positione rectis <formula>BA</formula>, <formula>AC</formula> angulum comprehendentibus,
punctoque intra angulum dato <formula>D</formula>, oporteat per ipsum ducere rectam <formula>BDC</formula>,
ita ut triangulum <formula>BAC</formula> sit omnium quae ita abscindi possunt minimum. Hoc autem satis
facile est. Illud difficilius: posito nimirum angulo <formula>BAC</formula> recto ducere per punctum
<formula>D</formula> intra ipsum dato rectam <formula>BDC</formula> omnium brevissimam.
</pre>

The Descartes correspondence contains <code>formula</code> elements with TeX notation.
However, these elements occur in a <code>figDesc</code> element, which is not rendered.
The rendered form is defined by the <code>graphic</code> element.

Example: https://test.epistolarium.huygens.knaw.nl/documents/686db5cd-8759-4e66-9db5-a6f82fe42b17
(formula in TeX notation)

<pre>
... le côté droit est <figure rend="inline"><graphic url="AM2L156F067.gif"/><figDesc><formula notation="TeX">${\displaystyle\strut Bq\over \displaystyle\strut D}$</formula></figDesc></figure>, ...
</pre>

== Quotes ==

The <code>q</code> element contains material which is distinguished from the surrounding text using quotation marks or a similar method.
For text that is to be rendered as a block quote the attribute <code>rend="bq"</code> is used.

Example: https://correspondence.huygens.knaw.nl/documents/c151aa14-306d-4993-aa1b-e175a469e566
(simple quote)

<pre>
Ick hebbe uwe schrijven van den 9 April wel ontfangen, en daer in enige woorden aldus luijden. <q>waer door dan het punt <formula>B</formula> lichtelijk gevonden wort, als men alleenlijk op 2 sijden des driehoeks <formula>DFG</formula> circelboogen beschrijft die de gevonden hoeken tot de sijden behoorende begrijpen. want de doorsnijding van sulke 2 boogen is het punt <formula>B</formula>.</q>
</pre>

Example: https://correspondence.huygens.knaw.nl/documents/839feb23-5c5c-44d3-ab44-868f6644ed53
(block quote)

<pre>
Quam ob causam ego ob communionem studiorum, quae etiam ignotissimos invicem conjunctos reddit iuxta illud: <q rend="bq">Nullus amicitiae gradus est constantior orbe, Quam qui per studii contigit esse modum</q> intermittere non debui hisce meis literulis tuam dominationem invisere ac per hunc mihi missum tabellarium salutare simulque dolenter significare filium meum unicum, pro ut in literis regiae majestatis inscriptis a filio meo tuae dominationi ad legendum tradendis latius sit deductum, insperanter esse tractatum, nunc apud vos commorari, quem tuis curis commendandum esse duxi hoc modo, cum perdifficile sit apud tantum regem literas hinc transmissas tradi, multo perdifficilius esse super iisdem exoptatum responsum obtinere.
</pre>

== References ==

The <code>ref</code> element contains a textual reference to some information.
Currently only used with attribute <code>@type="bible"</code> to refer to a specific part of the Bible.

Example: https://correspondence.huygens.knaw.nl/documents/f868a963-2b51-4be8-bfca-b2c29cff097d

<pre>
Atqui si <hi rend="italic">multi vocati, pauci electi</hi>, <ref type="bible">Matth. XX. 16</ref>;...
</pre>

N.B. Currently under discussion.

Notes

2018-01-23T11:44:27Z

WRA: Clarify issue

===Principles===
(To be realized step by step)
* All XML documentation on this wiki
* Describe general decisions only once, project-specific changes on project-level pages
* Each project has its own schema, but new elements (not in the general TEI schema) will use a single (Huygens) namespace
* ...

===Whitespace===

When processing all whitespace (like \n\t\t) may be collapsed to a single space character without loss of meaning. If a document is to be re-edited by the author, (s)he will appreciate retrieval with whitespace as it was stored.

===Restjes===

For the transcription of the manuscripts, the aim is to stay as close to the original text as possible. We focus on the production of diplomatic editions. This means that the edition is based on only one source and that the text and all graphic information will be displayed in accordance with this source. We don’t aspire a typographic imitation of the source, but aim for a functional reproduction of the text. As already stated, staying true to the text is key for the transcriptions. This means that deviations from the standard spelling and grammar are copied, changes made during writing - immediately or later - are documented, and if relevant, the physical structure of the source is reproduced.

----------------

For now, we have decided to relate source and destination texts to each other by pointing from the destination to the source at the paragraph and at the term level.

These references may look like:

At paragraph level (in this example there are two source paragraphs):
<pre></pre>

At term level:
<pre>which obscure <term xml:id="t1" corresp="BornInHolland.xml#t3">pure reality</term>.</pre>

===Discussion===
* How to encode blockquote?
** q[rend="block"] (http://www.open.ac.uk/blogs/styleproject/?p=52 and https://www.ct-lc.org/sites/ct-lc.org/files/tei-workshop-2015-01-holton_exercise.pdf)
** q[rend="display"] (http://www.tei-c.org/Vault/ED/edw35.txt)
** q with child p or lg (http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQQ)

* Define when to use <ref>, <ptr>, <anchor>? The TEI Gyudelines say:
** <ptr> (pointer) defines a pointer to another location.
** <ref> (reference) defines a reference to another location, possibly modified by additional text or comment.
** <anchor> (anchor point) attaches an identifier to a point within a text, whether or not it corresponds with a textual element.
In the ePistolarium <ptr> is not used, <ref> is sparingly used for annotation of Bible texts, and <anchor> is used for specifying the target of notes.

Notes

2018-01-23T10:42:09Z

WRA: Resolved issue.

Notes

2018-01-23T10:37:37Z

WRA:

===Principles===
(To be realized step by step)
* All XML documentation on this wiki
* Describe general decisions only once, project-specific changes on project-level pages
* Each project has its own schema, but new elements (not in the general TEI schema) will use a single (Huygens) namespace
* ...

===Restjes===

For the transcription of the manuscripts, the aim is to stay as close to the original text as possible. We focus on the production of diplomatic editions. This means that the edition is based on only one source and that the text and all graphic information will be displayed in accordance with this source. We don’t aspire a typographic imitation of the source, but aim for a functional reproduction of the text. As already stated, staying true to the text is key for the transcriptions. This means that deviations from the standard spelling and grammar are copied, changes made during writing - immediately or later - are documented, and if relevant, the physical structure of the source is reproduced.

----------------

For now, we have decided to relate source and destination texts to each other by pointing from the destination to the source at the paragraph and at the term level.

These references may look like:

At paragraph level (in this example there are two source paragraphs):
<pre></pre>

At term level:
<pre>which obscure <term xml:id="t1" corresp="BornInHolland.xml#t3">pure reality</term>.</pre>

===Discussion===
* How to encode blockquote?
** q[rend="block"] (http://www.open.ac.uk/blogs/styleproject/?p=52 and https://www.ct-lc.org/sites/ct-lc.org/files/tei-workshop-2015-01-holton_exercise.pdf)
** q[rend="display"] (http://www.tei-c.org/Vault/ED/edw35.txt)
** q with child p or lg (http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQQ)

* Define when to use <ref>, <ptr>, <anchor>?

* Could we remove impliciet whitespace like \n\t\t? In other words: the TEI should be collapsable and no data (whitespace) would be lost.

Lists (ePistolarium)

2018-01-23T10:37:01Z

WRA: Add issue.

Lists are encoded with the <code>list</code>, <code>item</code>, and <code>label</code> elements.

* <code>list</code> contains any sequence of items organized as a list;

* <code>item</code> contains one component of a list;

* <code>label</code> contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary.

There should be no bullet, number or other label before an item, unless explicitly indicated by means of a <code>label</code>.

Example: https://correspondence.huygens.knaw.nl/documents/a4e640b1-bd41-4c34-b7ac-a1441c9e97c1
(list without labels)

<pre>
Voici certains livres que je voudrais examiner
<list>
<item>Rebenstock Sermons mensuels de Luther</item>
<item>Mathaesius, Vie de Martin Luther</item>
<item>Jérôme Bolsec, Vita Calvini, Bezae etc.</item>
<item>Simon Starovolscius, Elogia centum illustrium Polonorum.</item>
<item>Caspar Chicocius Entretiens.</item>
<item>Bibliotheca Romana de Prospero Mandosio Rome 1682 4°</item>
<item>Vitae clarissimorum jurisconsultorum éditées avec des notes par Frideric Jacob Leickherr, Juris Utriusque Doctor Leipzig 1686 8°</item>
</list>
Je n'ai guère espoir avec ce livre d'éviter la rencontre de tout obstacle...
</pre>

Example: https://correspondence.huygens.knaw.nl/documents/9acac4d5-ee13-4201-b007-553e4bbebafb
(list with labels)

<pre>
Et voijci les avantages de la menue sur les grosles:
<list>
<item><label>1.</label> J'en suis mieux esclairé.</item>
<item><label>2.</label> J'en consume moins de cire.</item>
<item><label>3.</label> J'en sens moins de fumée.</item>
<item><label>4.</label> J'en ay moins d'embaras.</item>
<item><label>5.</label> Ma lumiere est moins agitée, et pour article capital,</item>
<item><label>6.</label> Je n'aij que faire de moucher ma chandelle.</item>
</list>
Si vous en voulez estre: considerez la simplicité...
</pre>
Note that we exclusively use <code>label</code> inside <code>item</code>.

Example: https://correspondence.huygens.knaw.nl/documents/2b46b15c-e62f-4cf5-9ed6-e1645d2af0ad
(groups a series of mathematical formulas)

<pre>
... Haec adde 7/6<hi rend="italic">y</hi>, fit
<list>
<item>7/6<hi rend="italic">y</hi> + 7/48 <hi rend="italic">z</hi> ∞ 86.</item>
<item>56<hi rend="italic">y</hi> + 7<hi rend="italic">z</hi> ∞ 4128.</item>
<item>7<hi rend="italic">z</hi> ∞ 4128 - 56<hi rend="italic">y.</hi></item>
<item><hi rend="italic">z</hi> ∞ 589 5/7 - 8 <hi rend="italic">y.</hi></item>
</list>
Si ergo haberem numerum <hi rend="italic">y</hi> dierum integrarum, ...
</pre>

TODO: Implement TEI approach (and Huygens standard): <label> and <item> are siblings, don't use <label in <item>.

Notes

2018-01-23T10:27:28Z

WRA: Resolved issue.

===Principles===
(To be realized step by step)
* All XML documentation on this wiki
* Describe general decisions only once, project-specific changes on project-level pages
* Each project has its own schema, but new elements (not in the general TEI schema) will use a single (Huygens) namespace
* ...

===Restjes===

For the transcription of the manuscripts, the aim is to stay as close to the original text as possible. We focus on the production of diplomatic editions. This means that the edition is based on only one source and that the text and all graphic information will be displayed in accordance with this source. We don’t aspire a typographic imitation of the source, but aim for a functional reproduction of the text. As already stated, staying true to the text is key for the transcriptions. This means that deviations from the standard spelling and grammar are copied, changes made during writing - immediately or later - are documented, and if relevant, the physical structure of the source is reproduced.

----------------

For now, we have decided to relate source and destination texts to each other by pointing from the destination to the source at the paragraph and at the term level.

These references may look like:

At paragraph level (in this example there are two source paragraphs):
<pre></pre>

At term level:
<pre>which obscure <term xml:id="t1" corresp="BornInHolland.xml#t3">pure reality</term>.</pre>

===Discussion===
* How to encode blockquote?
** q[rend="block"] (http://www.open.ac.uk/blogs/styleproject/?p=52 and https://www.ct-lc.org/sites/ct-lc.org/files/tei-workshop-2015-01-holton_exercise.pdf)
** q[rend="display"] (http://www.tei-c.org/Vault/ED/edw35.txt)
** q with child p or lg (http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQQ)

* Define when to use <ref>, <ptr>, <anchor>?

* Can we make <label> inside <item> the standard? The <label> preceding the <item> generates invalid HTML in the Pergamon implementation of rendering

* Could we remove impliciet whitespace like \n\t\t? In other words: the TEI should be collapsable and no data (whitespace) would be lost.

Names (ePistolarium)

2018-01-23T09:57:54Z

WRA: Add results of discussion.

As a result of automated or manual processing named entities are annotated in the text.
The following TEI elements are used:
<code>geogName</code>, <code>name</code>, <code>orgName</code>, <code>persName</code>, <code>placeName</code>, <code>rs</code>, and <code>title</code>.

<code>persName</code> (personal name) contains a proper noun or proper-noun phrase referring to a person.
:The <code>@key</code> attribute is used when the name has been identified.

<code>placeName</code> contains an absolute or relative place name.
:The <code>@key</code> attribute is used when the name has been identified.

<code>rs</code> (referencing string) contains a general purpose name or referring string.
:The ePistolarium uses this with either of two values of the <code>@type</code> attribute.
::<code>type="person"</code> for person names
::<code>type="place"</code> for place names
:In both cases the references are indirect, for instance "X's sister".
:The <code>@key</code> attribute is used when the name has been identified.

<code>orgName</code> (organization name) contains an organizational name.
:No normalization is used.

<code>geogName</code> (geographical name) identifies a name associated with some geographical feature.
:Used to annotated names of mountains, rivers, and seas.
:No normalization is used.

<code>title</code> contains a title for any kind of work.
:No normalization is used.

<code>name</code> contains a proper noun or noun phrase.
:Used for names that do nor belong to the categories mentioned above.
:The <code>@type</code> attribute is used to assign a category, currently "bible", "code", or "group".

TO DO: After discussion with Peter Boot, we decided on a standard that uses <code>rs</code> is the principal way to annote names, with <code>type</code> to distinguish between categories (person, place, etc.) and <code>key</code> to indicate identifiers for these names.

TO DO: Add examples.

Notes

2018-01-23T09:49:30Z

WRA: Correction

===Principles===
(To be realized step by step)
* All XML documentation on this wiki
* Describe general decisions only once, project-specific changes on project-level pages
* Each project has its own schema, but new elements (not in the general TEI schema) will use a single (Huygens) namespace
* ...

===Restjes===

For the transcription of the manuscripts, the aim is to stay as close to the original text as possible. We focus on the production of diplomatic editions. This means that the edition is based on only one source and that the text and all graphic information will be displayed in accordance with this source. We don’t aspire a typographic imitation of the source, but aim for a functional reproduction of the text. As already stated, staying true to the text is key for the transcriptions. This means that deviations from the standard spelling and grammar are copied, changes made during writing - immediately or later - are documented, and if relevant, the physical structure of the source is reproduced.

----------------

For now, we have decided to relate source and destination texts to each other by pointing from the destination to the source at the paragraph and at the term level.

These references may look like:

At paragraph level (in this example there are two source paragraphs):
<pre></pre>

At term level:
<pre>which obscure <term xml:id="t1" corresp="BornInHolland.xml#t3">pure reality</term>.</pre>

===Discussion===
* How to encode blockquote?
** q[rend="block"] (http://www.open.ac.uk/blogs/styleproject/?p=52 and https://www.ct-lc.org/sites/ct-lc.org/files/tei-workshop-2015-01-holton_exercise.pdf)
** q[rend="display"] (http://www.tei-c.org/Vault/ED/edw35.txt)
** q with child p or lg (http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQQ)

* Use <rs [type="person"]>, <persName> or both?

* Define when to use <ref>, <ptr>, <anchor>?

* Can we make <label> inside <item> the standard? The <label> preceding the <item> generates invalid HTML in the Pergamon implementation of rendering

* Could we remove impliciet whitespace like \n\t\t? In other words: the TEI should be collapsable and no data (whitespace) would be lost.

Notes

2018-01-23T09:41:56Z

WRA: Resolved issue.

===Principles===
(To be realized step by step)
* All XML documentation on this wiki
* Describe general decisions only once, project-specific changes on project-level pages
* Each project has its own schema, but new elements (not in the general TEI schema) will use a single (Huygens) namespace
* ...

===Restjes===

For the transcription of the manuscripts, the aim is to stay as close to the original text as possible. We focus on the production of diplomatic editions. This means that the edition is based on only one source and that the text and all graphic information will be displayed in accordance with this source. We don’t aspire a typographic imitation of the source, but aim for a functional reproduction of the text. As already stated, staying true to the text is key for the transcriptions. This means that deviations from the standard spelling and grammar are copied, changes made during writing - immediately or later - are documented, and if relevant, the physical structure of the source is reproduced.

----------------

For now, we have decided to relate source and destination texts to each other by pointing from the destination to the source at the paragraph and at the term level.

These references may look like:

At paragraph level (in this example there are two source paragraphs):
<pre></pre>

At term level:
<pre>which obscure <term xml:id="t1" corresp="BornInHolland.xml#t3">pure reality</term>.</pre>

===Discussion===
* How to encode blockquote?
** q[rend="block"] (http://www.open.ac.uk/blogs/styleproject/?p=52 and https://www.ct-lc.org/sites/ct-lc.org/files/tei-workshop-2015-01-holton_exercise.pdf)
** q[rend="display"] (http://www.tei-c.org/Vault/ED/edw35.txt)
** q with child p or lg (http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQQ)

* Use <name[type="person"]>, <persName> or both?

* Define when to use <ref>, <ptr>, <anchor>?

* Can we make <label> inside <item> the standard? The <label> preceding the <item> generates invalid HTML in the Pergamon implementation of rendering

* Could we remove impliciet whitespace like \n\t\t? In other words: the TEI should be collapsable and no data (whitespace) would be lost.

Transcription (ePistolarium)

2018-01-23T09:39:35Z

WRA: Correct link.

The following three milestone elements are used for encoding (part of) the physical structure of documents:

* <code>lb</code> (line beginning) marks the beginning of a new (typographic) line in some edition or version of a text.

* <code>pb</code> (page beginning) marks the beginning of a new page in a paginated document.

* <code>space</code> indicates the location of a significant space in the text. This is used for vertical space only, without specification of the amount.

The following elements are used for encoding editorial interventions:

* <code>corr</code> indicates corrected text

* <code>sic</code> indicates incorrect text.

Note that in the ePistolarium the <corr> and <sic> elements are used in their own right; they are not used in combination with a <choice> element; see [[Transcription#Editorial interventions]].

Transcription (ePistolarium)

2018-01-23T09:37:37Z

WRA: Add link

Transcription

2018-01-23T09:31:04Z

WRA: Add clarification.

The transcriptions that we make usually have a double purpose:
* they document the state of the text as encountered on the (manuscript or printed) page, thereby facilitating the creation of a diplomatic edition,
* they encode all the decsions made by the editors to create a reading text out of the diplomatic transcription, facilitating the display of a reading text.

==Physical structure==
The logical structure was discussed under [[Text structure]]. The physical structure is usually encoded using so-called
milestone (empty) elements: they do not contain their content, but are placed where certain
properties of the text change. The elements that we commonly employ are
* linebreak: <lb>
* page break: <pb>

Linebreaks and page breaks are placed at the beginning of the line or page.

In many of our editions we want to be able to reproduce the physical linebreaks in the ms or printed text,
as well as the logical units that are the result of editorial interpretation. Because of that we usually encode <lb/>
elements even where the onset of a new paragraph or a new verse line would dictate a new linebreak anyway.

==Writing process==
We use the following elements:
* '''<add>''' Addition;
<pre>It is a <add>complete</add> text.</pre>
* '''<del>''' Deletion;
<pre>It is <del type=strikethrough>not</del> a complete text.</pre>
* '''<restore>''' Used to mark an earlier deletion that is undone;
<pre><restore seq="2"><del seq="1">cocktail</del></restore>
<del seq="2"><add seq="1">drink</add></del>
</pre>
* '''<retrace>''' A letter or word retraced to clarify the intended word or letter

===Transpositions===

Two (or more) pieces of text that have switched position are encoded using the hi:transpose element. The transposed texts are written in their original order. The target attribute indicates where the text fragment is moved. Example:

<pre><hi:transpose seq="1" xml:id="i1" target="#i2">development</hi:transpose> <hi:transpose seq="1" xml:id="i2" target="#i1">art</hi:transpose></pre>

==Retorical structure==

===Opener and closer===
The beginning and the ending of e.g. a letter are encoded into <opener> and <closer>.
* In the <opener> common elements are: <address> <date> <salute>, in different orders.
* In the <closer> common elements are: <salute> <signed>, but it is possible to have <address> and <date> in it.
Keep <closer> limited to the really closing elements.

Remarks:
* is not allowed within <opener> and <closer>.
* If the text of a letter starts immediately after the salute, on the same line, we still encode the opener/salute outside of the paragraph.
In this case, the opener ends halfway through the line:
<pre><opener><lb/><salute>Cher ami,</salute></opener>
peux-tu venir me
<lb/>voir demain dans la matinée? … </pre>
* In the same way, the closer need not start on a new line.

===Postscripts===
A postscript is not necessarily indicated by P.S. A postscript is any text added as
an afterthought after a letter has been signed. A postscript contains at least one or more paragraphs:
<pre>
<postscript>
Say hello to your mother.
</postscript>
</pre>
A letter can have multiple postscripts. Postscripts can be numbered (using the n-attribute) to indicated a logical sequence.

==Visual characteristics==
* '''<hi>''' Highlight (if you need to highlight something and then specify how it appears in the source). The content of the rend-attribute is project-specific, though we try to use the same values for the same phenomena in all projects. If you need multiple values (like underlined and superscript) just enter them separated by a space: <hi rend="underline super">.
<pre><hi rend="underline">This text is underlined</hi></pre>
<pre><hi rend="underline bold">This text is underlined and bold</hi></pre>
* '''<hi:sepLine>''' Use for lines (not verselines or manuscript lines but graphical lines) that authors use to separate writing sections. Individual projects may want to further specify the nature of the line using the rend attribute.

==Reproduction of the source==
* '''<space>''' Empty lines, using dim="vertical" and the unit and quantity attributes to indicate the number of lines;
<pre><space dim="vertical" unit="lines" quantity="2"/></pre>
* '''<unclear>''' Uncertain reading of the text, for example due to damage or bad handwriting. If there is a number of possible readings,
group the <unclear> elements within a <choice>:
<pre>A single <unclear>word</unclear> is hard to read.</pre>
<pre>A single wor<choice><unclear>d</unclear><unclear>k</unclear></choice> is hard to read.</pre>
* '''<gap>''' If text is completely illegible and cannot be transcribed at all the <gap> element is used.
The size of the gap can be indicated using the unit and quantity attributes.
<pre>A single <gap quantity="1" unit="word"/> is illegible.</pre>
* '''<metamark>''' Indicates a sign added to aid in reading the text, for instance to indicate where a text is continuing.
* '''<damage>''' Damage or text loss;
<pre><damage extent="whole leaf" agent="rubbing"> ... </damage></pre>

===Hyphenation and other dashes===
<c type="wbh">-</c> is used to encode an end-of-line hyphen. We encode it only where it has been used, not where is should have been used!
Other kinds of hyphen receive no special encoding.

If the source contains:
<pre>
normal-
ly
</pre>
we encode (Don’t introduce whitespace!):
<pre>normal<c type="wbh">-</c><lb/>ly</pre>

If the source contains:
<pre>
Normal
ly
</pre>
we encode:
<pre>normal<lb/>ly</pre>

If the source contains:
<pre>
well-
known brands
</pre>
we encode:
<pre>well-<lb/>known brands</pre>

===Special characters===
* — (mdash): corresponds to unicode code point x2014.

In [[Manual oXygen|Oxygen]], they can be entered through the Symbol button (if needed, add the Symbol toolbar), or use the Edit menu, option Insert from Character Map, or by typing the appropriate code, e.g. &x2014; for the mdash.

==Editorial interventions==

===Incorrect text===
An incorrect text can be encoded in <sic>. The corresponding correction is incoded into <corr>. Both elements go into <choice>, as in the example:
<pre><choice><sic type="grammar">Happely</sic><corr>Happily</corr></choice></pre>
The elements <sic> and <corr> can also be used by themselves, but if the editor provides both the incorrect text and the correction it is advised to group them with <choice>.

===Supplied text===
Where the text is believed to be incomplete, editors can supply information:
<pre>The last letter is missin<supplied>g</supplied>.</pre>

==Attributes==
Some attributes are available on a number of elements to further qualify the content:
* '''@rend''' This is one of the global attributes in TEI, so it is allowed with a lot of elements. It indicates how the element in question was rendered or presented in the source. The allowed values are defined in the schema;
* '''@place''' Indicates the location of (e.g.) an addition (above, below, margin, etc) or the closer;
* '''@type''' Used to classify or sort elements.

Different source types have teheir own special characteristics, and the XML elements that encode these qualities of the text will vary to a certain extent per project.

==See also==
* [[Transcription (MVN)]]
* [[Transcription (Mondrian)]]
* [[XML Huygens]]

[[Category:XML Huygens]]

Images (ePistolarium)

2018-01-17T11:20:54Z

WRA: Add attribute description.

Images are encoded with the <code>figure</code>, <code>graphic</code>, and <code>figDesc</code> elements.

<code>figure</code> groups elements representing or containing graphic information such as an illustration, formula, or figure.
:In the ePistolarium the attribute value <code>rend="inline"</code> is used to indicate that the figure must be rendered in the running text. This is used, for instance, for certain mathematical symbols.

<code>figDesc</code> (description of figure) contains a brief prose description of the appearance or content of a graphic figure,
for use when documenting an image without displaying it.
:In the ePistolarium the contents of this element is not displayed.

<code>graphic</code> indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it.
:<code>@url</code> Refers to the image file to be displayed. Use a relative value, the front converts this to an absolute URL.
:<code>@width</code> Where the media are displayed, indicates the display width.
:<code>@height</code> Where the media are displayed, indicates the display height.
:<code>@scale</code> Where the media are displayed, indicates a scale factor to be applied when generating the desired display size.
:In the ePistolarium these attributes are occasionally used.

Example: https://correspondence.huygens.knaw.nl/documents/3365c937-4b0e-4ba0-909c-6258b32c4e3f
(between text lines)

<pre>
... hoc est ad minimum una hora, ad spatium quod est inter Lunam et Terram, etiam bis pertranseundum, ut patet numeranti.
<figure><graphic url="beec002jour04ill32a.gif"/></figure>
Atque ex his concessis ita sum argumentatus: Sit <formula>ABC</formula> linea recta et, ut possimus idem concludere sive Sol ...
</pre>

Example: https://correspondence.huygens.knaw.nl/documents/999fb392-00a3-48ec-ba55-349c9bc5db4b
(inline)

<pre>
Haec tamen aequatio radicem habet planum ut facillime ostendam si opus est +30<figure rend="inline"><graphic url="huyg003oeuv06fi19.gif"/></figure>Π+<figure rend="inline"><graphic url="huyg003oeuv06fi25.gif"/></figure>.
</pre>

Example: https://correspondence.huygens.knaw.nl/documents/8e59eff5-e44f-434a-af77-a3014924797a
(scaled)

<pre>
Een ander
Zoekt twee getallen, zoo men die te zamen multipliceert, uytkomt 22 2/9 en zoo men 't grootste door 't kleynste divideert, uyt komt 2. Vraage na de getallen?
<figure><graphic url="nier005-11-02.gif" width="1294" height="357" scale="0.25"/></figure>
Nog een ander.
</pre>

Metadata (ePistolarium)

2018-01-17T11:15:59Z

WRA: Add restrictions.

The metadata in the ePistolarium documents is contained in the <code>teiHeader</code> element. Each item is a <code>meta</code> milestone element with attributes <code>type</code> and <code>value</code>. The standard types are as follows:
; uuid : the unique identifier of the letter.
; correspondence : the identifier of the correspondence; required.
; id : the identifier of letter in the correspondence; required, must be unique in the correspondence.
; date : the date of writing of the letter. Values are encoded in the [http://www.loc.gov/standards/datetime/ Extended Date/Time Format].
; sender : the identifier of the sender (may occur multiple times); use value "?" if unknown.
; senderloc : the identifier for the location where the letter was sent; use value "?" if unknown.
; recipient : the identifier of the recipient (may occur multiple times); use value "?" if unknown.
; recipientloc : the identifier for the location where the letter was received; use value "?" if unknown.

Each metadata item is allowed only once, except for "sender" and "recipient.

Example: https://correspondence.huygens.knaw.nl/documents/301ba075-dde3-4fa4-a82e-0c9ba668bb06

<pre>
<TEI>
<teiHeader>
<meta type="uuid" value="301ba075-dde3-4fa4-a82e-0c9ba668bb06"/>
<meta type="correspondence" value="desc004"/>
<meta type="id" value="1001"/>
<meta type="date" value="1619-01-24"/>
<meta type="sender" value="descartes.rene.1596-1650"/>
<meta type="senderloc" value="se:breda.nld"/>
<meta type="recipient" value="beeckman.isaac.1588-1637"/>
<meta type="recipientloc" value="se:middelburg.nld"/>
</teiHeader>
...
</pre>

Miscellaneous (ePistolarium)

2017-11-30T12:16:33Z

WRA: Add page

Apart from name annotations a number of other elements is used for annotating interpretation of the text.

The <code>ref</code> element contains a textual reference to some information.
Currently only used with attribute <code>@type="bible"</code> to refer to a specific part of the Bible.

Example: https://test.epistolarium.huygens.knaw.nl/documents/f868a963-2b51-4be8-bfca-b2c29cff097d

<pre>
Atqui si <hi rend="italic">multi vocati, pauci electi</hi>, <ref type="bible">Matth. XX. 16</ref>;...
</pre>

Main Page

2017-11-30T12:03:14Z

WRA: Add link to new page

This wiki provides guidelines and manuals helpful in creating XML-based digital editions at Huygens ING. Both general guidelines and project-level implemenation and specifics are available here.

===XML at Huygens===
# [[About XML|XML, XML schemas, XML namespaces]]
# [[Assigning project content to files]]
# [[Global division of the XML/TEI file]]
# [[TEI Header]]
# [[Text structure]]
# [[Transcription]]
# [[Annotation and indexing]]
# [[Translation]]
# Tekstvergelijking
# [[Secondary files]]
# [[Subversion]]

===Display===
* [[Default display of TEI elements]]

===Manuals===
* [[Manual oXygen]]
* [[Manual Subversion]]

===Project specifics===
====Mondrian Project====
* [[XML Mondrian Guidelines]]
* [[XML schema (Mondrian)]]
* [[TEI Header (Mondrian)]]
* [[Facsimile (Mondrian)]]
* [[Text structure (Mondrian)]]
* [[Transcription (Mondrian)]]
* [[Theoretical writings (Mondrian)]]
* [[Annotation and indexing (Mondrian)]]
* [[Secondary files (Mondrian)]]
* [[Project procedure (Mondrian)]]
* [[Mondrian: further guidelines]]

====MVN Project====
* [[XML MVN Guidelines]]
* [[Introduction (MVN)]]
* [[TEI Header (MVN)]]
* [[Transcription (MVN)]]
* [[Secondary files (MVN)]]

====ePistolarium Project====
* [[XML ePistolarium Guidelines]]
* [[Text structure (ePistolarium)]]
* [[Rendering (ePistolarium)]]
* [[Retorical structure (ePistolarium)]]
* [[Lists (ePistolarium)]]
* [[Poems (ePistolarium)]]
* [[Images (ePistolarium)]]
* [[Names (ePistolarium)]]
* [[Miscellaneous (ePistolarium)]]

===Plan for this site===
* [[Set-up|set-up]] for XML documentation

===Working notes (temporary)===
* [[Notes]]

Names (ePistolarium)

2017-11-30T11:58:22Z

WRA: Styling

Retorical structure (ePistolarium)

2017-11-30T11:22:42Z

WRA: Add page

Letters usually have opening and closing phrases.
These are encoded with <code>opener</code> and <code>closer</code> elements, respectively.
Both elements can contain paragraphs, or can be contained in paragraphs.

Example: https://test.epistolarium.huygens.knaw.nl/documents/d815d122-68db-4753-bfa4-c8b60bd248f1
(opener containing paragraph)

<pre>
<div type="artifact" subtype="letter">
<opener>
Mon Révérend Père,
</opener>
Vous m'interrogez comme si je devais tout savoir, ...
...
</div>
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/d815d122-68db-4753-bfa4-c8b60bd248f1
(closer containing paragraphs)

<pre>
<div type="artifact" subtype="letter">
...
Mandez-moi, je vous prie, ... vos bonnes grâces.
<closer>
Votre très humble Desc.
Ce 12<hi rend="superscript">e</hi> jour de Carême 1630.
</closer>
</div>
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/f687c50b-6765-4519-bc5f-833c499ae453
(closer in paragraph)

<pre>
<div type="artifact" subtype="letter">
...
Het is dus beter, ...; er wordt al te veel gebabbeld door kwaadwillige menschen. <closer>28 Jull. 1634.</closer>
</div>
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/6652e6a5-9375-4e5c-b589-7245359a3c39
(text after closer)

<pre>
<div type="artifact" subtype="letter">
...
<closer>
IV Oct. CIƆIƆCVI.
Tui reverentissimus <lb/> H. Grotius.
</closer>
De pecunia, quae typographo restat, scire aveo.
</div>
</pre>

Main Page

2017-11-30T10:58:33Z

WRA:

This wiki provides guidelines and manuals helpful in creating XML-based digital editions at Huygens ING. Both general guidelines and project-level implemenation and specifics are available here.

===XML at Huygens===
# [[About XML|XML, XML schemas, XML namespaces]]
# [[Assigning project content to files]]
# [[Global division of the XML/TEI file]]
# [[TEI Header]]
# [[Text structure]]
# [[Transcription]]
# [[Annotation and indexing]]
# [[Translation]]
# Tekstvergelijking
# [[Secondary files]]
# [[Subversion]]

===Display===
* [[Default display of TEI elements]]

===Manuals===
* [[Manual oXygen]]
* [[Manual Subversion]]

===Project specifics===
====Mondrian Project====
* [[XML Mondrian Guidelines]]
* [[XML schema (Mondrian)]]
* [[TEI Header (Mondrian)]]
* [[Facsimile (Mondrian)]]
* [[Text structure (Mondrian)]]
* [[Transcription (Mondrian)]]
* [[Theoretical writings (Mondrian)]]
* [[Annotation and indexing (Mondrian)]]
* [[Secondary files (Mondrian)]]
* [[Project procedure (Mondrian)]]
* [[Mondrian: further guidelines]]

====MVN Project====
* [[XML MVN Guidelines]]
* [[Introduction (MVN)]]
* [[TEI Header (MVN)]]
* [[Transcription (MVN)]]
* [[Secondary files (MVN)]]

====ePistolarium Project====
* [[XML ePistolarium Guidelines]]
* [[Text structure (ePistolarium)]]
* [[Rendering (ePistolarium)]]
* [[Retorical structure (ePistolarium)]]
* [[Lists (ePistolarium)]]
* [[Poems (ePistolarium)]]
* [[Images (ePistolarium)]]
* [[Names (ePistolarium)]]

===Plan for this site===
* [[Set-up|set-up]] for XML documentation

===Working notes (temporary)===
* [[Notes]]

Names (ePistolarium)

2017-11-23T15:28:52Z

WRA: Add page

As a result of automated or manual processing named entities are annotated in the text.
The following TEI elements are used:
<code>geogName</code>, <code>name</code>, <code>orgName</code>, <code>persName</code>, <code>placeName</code>, <code>rs</code>, and <code>title</code>.

<persName> (personal name) contains a proper noun or proper-noun phrase referring to a person.
:The <code>@key</code> attribute is used when the name has been identified.

<code>placeName</code> contains an absolute or relative place name.
:The <code>@key</code> attribute is used when the name has been identified.

<code>rs</code> (referencing string) contains a general purpose name or referring string.
:The ePistolarium uses this with either of two values of the <code>@type</code> attribute.
::<code>type="person"</code> for person names
::<code>type="place"</code> for place names
:In both cases the references are indirect, for instance "X's sister".
:The <code>@key</code> attribute is used when the name has been identified.

<code>orgName</code> (organization name) contains an organizational name.
:No normalization is used.

<code>geogName</code> (geographical name) identifies a name associated with some geographical feature.
:Used to annotated names of mountains, rivers, and seas.
:No normalization is used.

<code>title</code> contains a title for any kind of work.
:No normalization is used.

<code>name</code> contains a proper noun or noun phrase.
:Used for names that do nor belong to the categories mentioned above.
:The <code>@type</code> attribute is used to assign a category, currently "bible", "code", or "group".

TO DO: Add examples.

Main Page

2017-11-23T15:02:53Z

WRA: Add link to names page

This wiki provides guidelines and manuals helpful in creating XML-based digital editions at Huygens ING. Both general guidelines and project-level implemenation and specifics are available here.

===XML at Huygens===
# [[About XML|XML, XML schemas, XML namespaces]]
# [[Assigning project content to files]]
# [[Global division of the XML/TEI file]]
# [[TEI Header]]
# [[Text structure]]
# [[Transcription]]
# [[Annotation and indexing]]
# [[Translation]]
# Tekstvergelijking
# [[Secondary files]]
# [[Subversion]]

===Display===
* [[Default display of TEI elements]]

===Manuals===
* [[Manual oXygen]]
* [[Manual Subversion]]

===Project specifics===
====Mondrian Project====
* [[XML Mondrian Guidelines]]
* [[XML schema (Mondrian)]]
* [[TEI Header (Mondrian)]]
* [[Facsimile (Mondrian)]]
* [[Text structure (Mondrian)]]
* [[Transcription (Mondrian)]]
* [[Theoretical writings (Mondrian)]]
* [[Annotation and indexing (Mondrian)]]
* [[Secondary files (Mondrian)]]
* [[Project procedure (Mondrian)]]
* [[Mondrian: further guidelines]]

====MVN Project====
* [[XML MVN Guidelines]]
* [[Introduction (MVN)]]
* [[TEI Header (MVN)]]
* [[Transcription (MVN)]]
* [[Secondary files (MVN)]]

====ePistolarium Project====
* [[XML ePistolarium Guidelines]]
* [[Text structure (ePistolarium)]]
* [[Rendering (ePistolarium)]]
* [[Lists (ePistolarium)]]
* [[Poems (ePistolarium)]]
* [[Images (ePistolarium)]]
* [[Names (ePistolarium)]]

===Plan for this site===
* [[Set-up|set-up]] for XML documentation

===Working notes (temporary)===
* [[Notes]]

Images (ePistolarium)

2017-11-23T14:46:48Z

WRA: Add page

Images are encoded with the <code>figure</code>, <code>graphic</code>, and <code>figDesc</code> elements.

<code>figure</code> groups elements representing or containing graphic information such as an illustration, formula, or figure.
:In the ePistolarium the attribute value <code>rend="inline"</code> is used to indicate that the figure must be rendered in the running text. This is used, for instance, for certain mathehatical symbols.

<code>figDesc</code> (description of figure) contains a brief prose description of the appearance or content of a graphic figure,
for use when documenting an image without displaying it.
:In the ePistolarium the contents of this element is not displayed.

<code>graphic</code> indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it.
:<code>@width</code> Where the media are displayed, indicates the display width.
:<code>@height</code> Where the media are displayed, indicates the display height.
:<code>@scale</code> Where the media are displayed, indicates a scale factor to be applied when generating the desired display size.
:In the ePistolarium these attributes are occasionally used.

Example: https://test.epistolarium.huygens.knaw.nl/documents/3365c937-4b0e-4ba0-909c-6258b32c4e3f
(between text lines)

<pre>
... hoc est ad minimum una hora, ad spatium quod est inter Lunam et Terram, etiam bis pertranseundum, ut patet numeranti.
<figure><graphic url="beec002jour04ill32a.gif"/></figure>
Atque ex his concessis ita sum argumentatus: Sit <formula>ABC</formula> linea recta et, ut possimus idem concludere sive Sol ...
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/999fb392-00a3-48ec-ba55-349c9bc5db4b
(inline)

<pre>
Haec tamen aequatio radicem habet planum ut facillime ostendam si opus est +30<figure rend="inline"><graphic url="huyg003oeuv06fi19.gif"/></figure>Π+<figure rend="inline"><graphic url="huyg003oeuv06fi25.gif"/></figure>.
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/8e59eff5-e44f-434a-af77-a3014924797a
(scaled)

<pre>
Een ander
Zoekt twee getallen, zoo men die te zamen multipliceert, uytkomt 22 2/9 en zoo men 't grootste door 't kleynste divideert, uyt komt 2. Vraage na de getallen?
<figure><graphic url="nier005-11-02.gif" width="1294" height="357" scale="0.25"/></figure>
Nog een ander.
</pre>

Main Page

2017-11-23T14:40:54Z

WRA: Add link to images page

This wiki provides guidelines and manuals helpful in creating XML-based digital editions at Huygens ING. Both general guidelines and project-level implemenation and specifics are available here.

===XML at Huygens===
# [[About XML|XML, XML schemas, XML namespaces]]
# [[Assigning project content to files]]
# [[Global division of the XML/TEI file]]
# [[TEI Header]]
# [[Text structure]]
# [[Transcription]]
# [[Annotation and indexing]]
# [[Translation]]
# Tekstvergelijking
# [[Secondary files]]
# [[Subversion]]

===Display===
* [[Default display of TEI elements]]

===Manuals===
* [[Manual oXygen]]
* [[Manual Subversion]]

===Project specifics===
====Mondrian Project====
* [[XML Mondrian Guidelines]]
* [[XML schema (Mondrian)]]
* [[TEI Header (Mondrian)]]
* [[Facsimile (Mondrian)]]
* [[Text structure (Mondrian)]]
* [[Transcription (Mondrian)]]
* [[Theoretical writings (Mondrian)]]
* [[Annotation and indexing (Mondrian)]]
* [[Secondary files (Mondrian)]]
* [[Project procedure (Mondrian)]]
* [[Mondrian: further guidelines]]

====MVN Project====
* [[XML MVN Guidelines]]
* [[Introduction (MVN)]]
* [[TEI Header (MVN)]]
* [[Transcription (MVN)]]
* [[Secondary files (MVN)]]

====ePistolarium Project====
* [[XML ePistolarium Guidelines]]
* [[Text structure (ePistolarium)]]
* [[Rendering (ePistolarium)]]
* [[Lists (ePistolarium)]]
* [[Poems (ePistolarium)]]
* [[Images (ePistolarium)]]

===Plan for this site===
* [[Set-up|set-up]] for XML documentation

===Working notes (temporary)===
* [[Notes]]

Lists (ePistolarium)

2017-11-23T13:16:42Z

WRA: Add page

Lists are encoded with the <code>list</code>, <code>item</code>, and <code>label</code> elements.

<code>list</code> contains any sequence of items organized as a list.

<code>item</code> contains one component of a list.

<code>label</code> contains any label or heading used to identify part of a text, typically but not exclusively in a list or glossary.

There should be no bullet, number or other label before an item, unless it is explicitly indicated.

Example: https://test.epistolarium.huygens.knaw.nl/documents/a4e640b1-bd41-4c34-b7ac-a1441c9e97c1
(list without labels)

<pre>
Voici certains livres que je voudrais examiner
<list>
<item>Rebenstock Sermons mensuels de Luther</item>
<item>Mathaesius, Vie de Martin Luther</item>
<item>Jérôme Bolsec, Vita Calvini, Bezae etc.</item>
<item>Simon Starovolscius, Elogia centum illustrium Polonorum.</item>
<item>Caspar Chicocius Entretiens.</item>
<item>Bibliotheca Romana de Prospero Mandosio Rome 1682 4°</item>
<item>Vitae clarissimorum jurisconsultorum éditées avec des notes par Frideric Jacob Leickherr, Juris Utriusque Doctor Leipzig 1686 8°</item>
</list>
Je n'ai guère espoir avec ce livre d'éviter la rencontre de tout obstacle...
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/9acac4d5-ee13-4201-b007-553e4bbebafb
(list with labels)

<pre>
Et voijci les avantages de la menue sur les grosles:
<list>
<label>1.</label><item>J'en suis mieux esclairé.</item>
<label>2.</label><item>J'en consume moins de cire.</item>
<label>3.</label><item>J'en sens moins de fumée.</item>
<label>4.</label><item>J'en ay moins d'embaras.</item>
<label>5.</label><item>Ma lumiere est moins agitée, et pour article capital,</item>
<label>6.</label><item>Je n'aij que faire de moucher ma chandelle.</item>
</list>
Si vous en voulez estre: considerez la simplicité...
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/2b46b15c-e62f-4cf5-9ed6-e1645d2af0ad
(groups a series of mathematical formulas)

<pre>
... Haec adde 7/6<hi rend="italic">y</hi>, fit
<list>
<item>7/6<hi rend="italic">y</hi> + 7/48 <hi rend="italic">z</hi> ∞ 86.</item>
<item>56<hi rend="italic">y</hi> + 7<hi rend="italic">z</hi> ∞ 4128.</item>
<item>7<hi rend="italic">z</hi> ∞ 4128 - 56<hi rend="italic">y.</hi></item>
<item><hi rend="italic">z</hi> ∞ 589 5/7 - 8 <hi rend="italic">y.</hi></item>
</list>
Si ergo haberem numerum <hi rend="italic">y</hi> dierum integrarum, ...
</pre>

Main Page

2017-11-23T13:15:26Z

WRA: Add reference

This wiki provides guidelines and manuals helpful in creating XML-based digital editions at Huygens ING. Both general guidelines and project-level implemenation and specifics are available here.

===XML at Huygens===
# [[About XML|XML, XML schemas, XML namespaces]]
# [[Assigning project content to files]]
# [[Global division of the XML/TEI file]]
# [[TEI Header]]
# [[Text structure]]
# [[Transcription]]
# [[Annotation and indexing]]
# [[Translation]]
# Tekstvergelijking
# [[Secondary files]]
# [[Subversion]]

===Display===
* [[Default display of TEI elements]]

===Manuals===
* [[Manual oXygen]]
* [[Manual Subversion]]

===Project specifics===
====Mondrian Project====
* [[XML Mondrian Guidelines]]
* [[XML schema (Mondrian)]]
* [[TEI Header (Mondrian)]]
* [[Facsimile (Mondrian)]]
* [[Text structure (Mondrian)]]
* [[Transcription (Mondrian)]]
* [[Theoretical writings (Mondrian)]]
* [[Annotation and indexing (Mondrian)]]
* [[Secondary files (Mondrian)]]
* [[Project procedure (Mondrian)]]
* [[Mondrian: further guidelines]]

====MVN Project====
* [[XML MVN Guidelines]]
* [[Introduction (MVN)]]
* [[TEI Header (MVN)]]
* [[Transcription (MVN)]]
* [[Secondary files (MVN)]]

====ePistolarium Project====
* [[XML ePistolarium Guidelines]]
* [[Text structure (ePistolarium)]]
* [[Rendering (ePistolarium)]]
* [[Lists (ePistolarium)]]
* [[Poems (ePistolarium)]]

===Plan for this site===
* [[Set-up|set-up]] for XML documentation

===Working notes (temporary)===
* [[Notes]]

Poems (ePistolarium)

2017-11-23T12:24:20Z

WRA: Add page

Poems are encoded with the <code>lg</code> and <code>l</code> elements.

<code>lg</code> (line group) contains one or more verse lines functioning as a formal unit.
Its <code>@type</code> attribute may have values <code>poem</code> and <code>stanza</code>.

<code>l</code> (verse line) contains a single, possibly incomplete, line of verse.

Example: https://test.epistolarium.huygens.knaw.nl/documents/abf2028c-1ff5-4649-aaf0-38773cb4b29b

<pre>
Vale nobilissime ac candidissime Hugeni, ac saepius istiusmodi mihi criminationes intende.
Scripsisti ista non serio, sed ad vexandum dogmaticum Philosophum, more Scepticorum.
Quod si non satisfecero, si perges scribere,
<lg type="poem">
<l>Hunc vatem fugit uterque Ducum,</l>
</lg>
regeram ego,
<lg type="poem">
<l>Barlaei mentem noscit uterque Ducum.</l>
</lg>
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/8b1d5db7-297f-48b2-9d9d-e80e64fc1618

<pre>
<lg type="poem">
<lg type="stanza">
<l>Multa Muijdensem levat aura cycnum,</l>
<l>Tendit, Hugeni, quoties in altos</l>
<l>Nubium tractus. Ego apis Batavae</l>
<l>More, modoque</l>
</lg>
<lg type="stanza">
<l>Grata carpentis thyma, per laborem</l>
<l>Plurimum, circa placidas amoeni</l>
<l>Fluminis ripas, operosa parvus</l>
<l>Carmina fingo.</l>
</lg>
<lg type="stanza">
<l>Tu canes maiore poeta plectro</l>
<l>Principem, quandoque trahet feroces</l>
<l>Impares ferro, domitosque clivis</l>
<l>Nuper Iberos.</l>
</lg>
</lg>
</pre>

Main Page

2017-11-23T12:22:41Z

WRA: Add link to poems page

This wiki provides guidelines and manuals helpful in creating XML-based digital editions at Huygens ING. Both general guidelines and project-level implemenation and specifics are available here.

===XML at Huygens===
# [[About XML|XML, XML schemas, XML namespaces]]
# [[Assigning project content to files]]
# [[Global division of the XML/TEI file]]
# [[TEI Header]]
# [[Text structure]]
# [[Transcription]]
# [[Annotation and indexing]]
# [[Translation]]
# Tekstvergelijking
# [[Secondary files]]
# [[Subversion]]

===Display===
* [[Default display of TEI elements]]

===Manuals===
* [[Manual oXygen]]
* [[Manual Subversion]]

===Project specifics===
====Mondrian Project====
* [[XML Mondrian Guidelines]]
* [[XML schema (Mondrian)]]
* [[TEI Header (Mondrian)]]
* [[Facsimile (Mondrian)]]
* [[Text structure (Mondrian)]]
* [[Transcription (Mondrian)]]
* [[Theoretical writings (Mondrian)]]
* [[Annotation and indexing (Mondrian)]]
* [[Secondary files (Mondrian)]]
* [[Project procedure (Mondrian)]]
* [[Mondrian: further guidelines]]

====MVN Project====
* [[XML MVN Guidelines]]
* [[Introduction (MVN)]]
* [[TEI Header (MVN)]]
* [[Transcription (MVN)]]
* [[Secondary files (MVN)]]

====ePistolarium Project====
* [[XML ePistolarium Guidelines]]
* [[Text structure (ePistolarium)]]
* [[Rendering (ePistolarium)]]
* [[Poems (ePistolarium)]]

===Plan for this site===
* [[Set-up|set-up]] for XML documentation

===Working notes (temporary)===
* [[Notes]]

Rendering (ePistolarium)

2017-11-23T12:16:06Z

WRA: Add attribute value

Rendering of TEI elements may be controlled with their <code>@rend</code> attribute.
However, it is mainly used on the <code>hi</code> element.

Attribute values used:
* <code>bold</code>
* <code>case(smallcaps)</code>
* <code>italic</code>
* <code>strikethrough</code>
* <code>subscript</code>
* <code>superscript</code>
* <code>underline</code>
* <code>align(right)</code> (on <code>p</code> elements)

Example: https://test.epistolarium.huygens.knaw.nl/documents/e405b5dc-a25c-41be-9882-5fc9fe5d9abf

<pre>
... dienvolgende gelieft uEdelheijt voor de voorgaande opgegeven getallen
<hi rend="bold">232,</hi> 159, <hi rend="bold">104,</hi> te stellen de rechte
<hi rend="bold">231,</hi> 159, <hi rend="bold">105,</hi> ofte deze 77, 53, 35.
...
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/b797e0a5-59c8-466a-aa36-368cb692f361

<pre>
... ces paroles du premier Avertissement, <hi rend="case(smallcaps)">Bien entendu
qu'on cherchera toujours ce qui sera pour le mieux</hi>. Par ces paroles toutes
...
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/c846d786-3eee-42f5-8030-a232a8594a58

<pre>
Pour la seconde, à savoir: <hi rend="italic">cognitâ hac linguâ, caeteras omnes, ut ejus dialectos, cognoscere</hi>,
ce n'est que pour faire valoir la drogue; ...
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/754efb24-b47f-49b8-9e93-b76009241979

<pre>
... il faut mieux qu'elle aille devant <hi rend="strikethrough">que d[...]en aller ensemble.
<hi rend="underline">peut estre que vous changerez encor de volonté, avant vostre partemant</hi>.
Dirk bout est icy, ...
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/849def28-fbcb-44bf-9479-b10a236cb990

<pre>
<note>De kristallen die L. heeft weergegeven in de fig. 3 tot en met 6 (F, G, H en I),
zullen waarschijnlijk piperine, C<hi rend="subscript">17</hi>H<hi rend="subscript">19</hi>NO<hi rend="subscript">3</hi>,
geweest zijn. Dit kan in verschillende vormen kristalliseren: naald-, prisma- en lensvormig. [Kl. en Swt.]</note>
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/0164c9ab-e0ca-4c31-80c5-ae60c73c0e29

<pre>
Au bateau de S. Ex.<hi rend="superscript">e</hi> contre terre à 3/4 heures dessus Heusden, le 3<hi rend="superscript">e</hi> de Septemb. 1634, vers minuict.
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/7e57c582-225c-44d7-9845-4449c80152ed

<pre>
<hi rend="italic">- - - - Humano capiti</hi>, &c. aut
Delphinum silvis appingit, fluctibus aprum.
5 Id. Ian. 1629.
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/df5eefe2-172d-43d2-b656-8a9232b84047

<pre>
[Sedan,] le 14 janvier 1678
Monsieur et tres honoré pere,
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/047cdbd9-6e08-4aa9-b9ee-a0fc07fcfca2

<pre>
A Monsieur Monsieur C. Huygens, Secretaire de Son Altesse. <lb/> A L'armée. <lb/> <seg rend="italic">met een rolle papier</seg>.
</pre>

Rendering (ePistolarium)

2017-11-23T12:08:01Z

WRA: Created page with "Rendering of TEI elements may be controlled with their <code>@rend</code> attribute. However, it is mainly used on the <code>hi</code> element. Attribute values used: * <code..."

Rendering of TEI elements may be controlled with their <code>@rend</code> attribute.
However, it is mainly used on the <code>hi</code> element.

Attribute values used:
* <code>bold</code>
* <code>case(smallcaps)</code>
* <code>italic</code>
* <code>strikethrough</code>
* <code>subscript</code>
* <code>superscript</code>
* <code>underline</code>

Example: https://test.epistolarium.huygens.knaw.nl/documents/e405b5dc-a25c-41be-9882-5fc9fe5d9abf

<pre>
... dienvolgende gelieft uEdelheijt voor de voorgaande opgegeven getallen
<hi rend="bold">232,</hi> 159, <hi rend="bold">104,</hi> te stellen de rechte
<hi rend="bold">231,</hi> 159, <hi rend="bold">105,</hi> ofte deze 77, 53, 35.
...
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/b797e0a5-59c8-466a-aa36-368cb692f361

<pre>
... ces paroles du premier Avertissement, <hi rend="case(smallcaps)">Bien entendu
qu'on cherchera toujours ce qui sera pour le mieux</hi>. Par ces paroles toutes
...
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/c846d786-3eee-42f5-8030-a232a8594a58

<pre>
Pour la seconde, à savoir: <hi rend="italic">cognitâ hac linguâ, caeteras omnes, ut ejus dialectos, cognoscere</hi>,
ce n'est que pour faire valoir la drogue; ...
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/754efb24-b47f-49b8-9e93-b76009241979

<pre>
... il faut mieux qu'elle aille devant <hi rend="strikethrough">que d[...]en aller ensemble.
<hi rend="underline">peut estre que vous changerez encor de volonté, avant vostre partemant</hi>.
Dirk bout est icy, ...
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/849def28-fbcb-44bf-9479-b10a236cb990

<pre>
<note>De kristallen die L. heeft weergegeven in de fig. 3 tot en met 6 (F, G, H en I),
zullen waarschijnlijk piperine, C<hi rend="subscript">17</hi>H<hi rend="subscript">19</hi>NO<hi rend="subscript">3</hi>,
geweest zijn. Dit kan in verschillende vormen kristalliseren: naald-, prisma- en lensvormig. [Kl. en Swt.]</note>
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/0164c9ab-e0ca-4c31-80c5-ae60c73c0e29

<pre>
Au bateau de S. Ex.<hi rend="superscript">e</hi> contre terre à 3/4 heures dessus Heusden, le 3<hi rend="superscript">e</hi> de Septemb. 1634, vers minuict.
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/7e57c582-225c-44d7-9845-4449c80152ed

<pre>
<hi rend="italic">- - - - Humano capiti</hi>, &c. aut
Delphinum silvis appingit, fluctibus aprum.
5 Id. Ian. 1629.
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/df5eefe2-172d-43d2-b656-8a9232b84047

<pre>
[Sedan,] le 14 janvier 1678
Monsieur et tres honoré pere,
</pre>

Example: https://test.epistolarium.huygens.knaw.nl/documents/047cdbd9-6e08-4aa9-b9ee-a0fc07fcfca2

<pre>
A Monsieur Monsieur C. Huygens, Secretaire de Son Altesse. <lb/> A L'armée. <lb/> <seg rend="italic">met een rolle papier</seg>.
</pre>

Main Page

2017-11-23T11:40:41Z

WRA:

This wiki provides guidelines and manuals helpful in creating XML-based digital editions at Huygens ING. Both general guidelines and project-level implemenation and specifics are available here.

===XML at Huygens===
# [[About XML|XML, XML schemas, XML namespaces]]
# [[Assigning project content to files]]
# [[Global division of the XML/TEI file]]
# [[TEI Header]]
# [[Text structure]]
# [[Transcription]]
# [[Annotation and indexing]]
# [[Translation]]
# Tekstvergelijking
# [[Secondary files]]
# [[Subversion]]

===Display===
* [[Default display of TEI elements]]

===Manuals===
* [[Manual oXygen]]
* [[Manual Subversion]]

===Project specifics===
====Mondrian Project====
* [[XML Mondrian Guidelines]]
* [[XML schema (Mondrian)]]
* [[TEI Header (Mondrian)]]
* [[Facsimile (Mondrian)]]
* [[Text structure (Mondrian)]]
* [[Transcription (Mondrian)]]
* [[Theoretical writings (Mondrian)]]
* [[Annotation and indexing (Mondrian)]]
* [[Secondary files (Mondrian)]]
* [[Project procedure (Mondrian)]]
* [[Mondrian: further guidelines]]

====MVN Project====
* [[XML MVN Guidelines]]
* [[Introduction (MVN)]]
* [[TEI Header (MVN)]]
* [[Transcription (MVN)]]
* [[Secondary files (MVN)]]

====ePistolarium Project====
* [[XML ePistolarium Guidelines]]
* [[Text structure (ePistolarium)]]
* [[Rendering (ePistolarium)]]

===Plan for this site===
* [[Set-up|set-up]] for XML documentation

===Working notes (temporary)===
* [[Notes]]

Text structure (ePistolarium)

2017-11-23T11:37:43Z

WRA: Use of group discontinued

Text structure (ePistolarium)

2017-10-31T13:00:59Z

WRA: Initial version

The documents in the ePistolarium have the following basic structure:

<pre>
<text>
<body>
<div xml:id="div-1" type="artifact" subtype="letter">
...
</div>
<div xml:id="div-2" type="para">
...
</div>
<div xml:id="div-3" type="notes">
...
</div>
</body>
</text>
</pre>

However, a number of documents in the Pierre Bayle corpus contain both a text and its translation, encoded using the group element:

<pre>
<text type="composite">
<group>
<text type="original">
<body>
<div xml:id="div-1" xml:lang="la" type="artifact" subtype="letter">
...
</div>
</body>
</text>
<text type="translation">
<body>
<div xml:id="div-2" xml:lang="fr" type="artifact" subtype="letter">
...
</div>
</body>
</text>
</group>
</text>
</pre>

Main Page

2017-10-31T12:51:07Z

WRA: Typo

This wiki provides guidelines and manuals helpful in creating XML-based digital editions at Huygens ING. Both general guidelines and project-level implemenation and specifics are available here.

===XML at Huygens===
# [[About XML|XML, XML schemas, XML namespaces]]
# [[Assigning project content to files]]
# [[Global division of the XML/TEI file]]
# [[TEI Header]]
# [[Text structure]]
# [[Transcription]]
# [[Annotation and indexing]]
# [[Translation]]
# Tekstvergelijking
# [[Secondary files]]
# [[Subversion]]

===Display===
* [[Default display of TEI elements]]

===Manuals===
* [[Manual oXygen]]
* [[Manual Subversion]]

===Project specifics===
====Mondrian Project====
* [[XML Mondrian Guidelines]]
* [[XML schema (Mondrian)]]
* [[TEI Header (Mondrian)]]
* [[Facsimile (Mondrian)]]
* [[Text structure (Mondrian)]]
* [[Transcription (Mondrian)]]
* [[Theoretical writings (Mondrian)]]
* [[Annotation and indexing (Mondrian)]]
* [[Secondary files (Mondrian)]]
* [[Project procedure (Mondrian)]]
* [[Mondrian: further guidelines]]

====MVN Project====
* [[XML MVN Guidelines]]
* [[Introduction (MVN)]]
* [[TEI Header (MVN)]]
* [[Transcription (MVN)]]
* [[Secondary files (MVN)]]

====ePistolarium Project====
* [[XML ePistolarium Guidelines]]
* [[Text structure (ePistolarium)]]

===Plan for this site===
* [[Set-up|set-up]] for XML documentation

===Working notes (temporary)===
* [[Notes]]

Main Page

2017-10-31T12:49:47Z

WRA: Add page

This wiki provides guidelines and manuals helpful in creating XML-based digital editions at Huygens ING. Both general guidelines and project-level implemenation and specifics are available here.

===XML at Huygens===
# [[About XML|XML, XML schemas, XML namespaces]]
# [[Assigning project content to files]]
# [[Global division of the XML/TEI file]]
# [[TEI Header]]
# [[Text structure]]
# [[Transcription]]
# [[Annotation and indexing]]
# [[Translation]]
# Tekstvergelijking
# [[Secondary files]]
# [[Subversion]]

===Display===
* [[Default display of TEI elements]]

===Manuals===
* [[Manual oXygen]]
* [[Manual Subversion]]

===Project specifics===
====Mondrian Project====
* [[XML Mondrian Guidelines]]
* [[XML schema (Mondrian)]]
* [[TEI Header (Mondrian)]]
* [[Facsimile (Mondrian)]]
* [[Text structure (Mondrian)]]
* [[Transcription (Mondrian)]]
* [[Theoretical writings (Mondrian)]]
* [[Annotation and indexing (Mondrian)]]
* [[Secondary files (Mondrian)]]
* [[Project procedure (Mondrian)]]
* [[Mondrian: further guidelines]]

====MVN Project====
* [[XML MVN Guidelines]]
* [[Introduction (MVN)]]
* [[TEI Header (MVN)]]
* [[Transcription (MVN)]]
* [[Secondary files (MVN)]]

====ePistolarium Project====
* [[XML ePistolarium Guidelines]]
* [[Text structure (ePstolarium)]]

===Plan for this site===
* [[Set-up|set-up]] for XML documentation

===Working notes (temporary)===
* [[Notes]]

XML ePistolarium Guidelines

2017-10-31T12:38:36Z

WRA: Add sample document.

XML ePistolarium Guidelines

2017-10-31T12:30:26Z

WRA: Created page.

This section of the XML Wiki documents the TEI as currently used in the ePistolarium project.

Main Page

2017-10-31T12:24:23Z

WRA:

This wiki provides guidelines and manuals helpful in creating XML-based digital editions at Huygens ING. Both general guidelines and project-level implemenation and specifics are available here.

===XML at Huygens===
# [[About XML|XML, XML schemas, XML namespaces]]
# [[Assigning project content to files]]
# [[Global division of the XML/TEI file]]
# [[TEI Header]]
# [[Text structure]]
# [[Transcription]]
# [[Annotation and indexing]]
# [[Translation]]
# Tekstvergelijking
# [[Secondary files]]
# [[Subversion]]

===Display===
* [[Default display of TEI elements]]

===Manuals===
* [[Manual oXygen]]
* [[Manual Subversion]]

===Project specifics===
====Mondrian Project====
* [[XML Mondrian Guidelines]]
* [[XML schema (Mondrian)]]
* [[TEI Header (Mondrian)]]
* [[Facsimile (Mondrian)]]
* [[Text structure (Mondrian)]]
* [[Transcription (Mondrian)]]
* [[Theoretical writings (Mondrian)]]
* [[Annotation and indexing (Mondrian)]]
* [[Secondary files (Mondrian)]]
* [[Project procedure (Mondrian)]]
* [[Mondrian: further guidelines]]

====MVN Project====
* [[XML MVN Guidelines]]
* [[Introduction (MVN)]]
* [[TEI Header (MVN)]]
* [[Transcription (MVN)]]
* [[Secondary files (MVN)]]

====ePistolarium Project====
* [[XML ePistolarium Guidelines]]

===Plan for this site===
* [[Set-up|set-up]] for XML documentation

===Working notes (temporary)===
* [[Notes]]