XML - User contributions [en]

Mondrian: Decisions during eDITem project

2023-02-07T14:00:57Z

PBO:

These are decisions taken during the eDITem project that have to be worked into the rest of the documentation. For the moment, we document them here.

Superscript: to be silently removed and usually replaced by '.': e.g. Mr., No.

Unusual abbreviations: to be coded as <choice><abbr><expan>

We will not be using sic and corr, but orig and reg

we only keep the changed (added, deleted) string within the element and keep the unchanged part out of these elements

For now we regularise layout of postcards the way we do letters

Mondrian: Decisions during eDITem project

2023-02-07T13:01:46Z

PBO:

These are decisions taken during the eDITem project that have to be worked into the rest of the documentation. For the moment, we document them here.

Superscript: to be silently removed and usually replaced by '.': e.g. Mr., No.

Unusual abbreviations: to be coded as <choice><abbr><expan>

We will not be using sic and corr, but orig and reg

For now we regularise layout of postcards the way we do letters

Mondrian: Decisions during eDITem project

2023-02-07T12:52:53Z

PBO: Created page with " These are decisions taken during the eDITem project that have to be worked into the rest of the documentation. For the moment, we document them here."

These are decisions taken during the eDITem project that have to be worked into the rest of the documentation. For the moment, we document them here.

Main Page

2023-02-07T12:51:00Z

PBO: /* Mondrian Project */

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]]
* [[Mondrian: Decisions during eDITem project]]

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

====ePistolarium Project====
* [[XML ePistolarium Guidelines]]
* [[Metadata (ePistolarium)]]
* [[Text structure (ePistolarium)]]
* [[Local annotations (ePistolarium)]]
* [[Transcription (ePistolarium)]]
* [[Rendering (ePistolarium)]]
* [[Retorical structure (ePistolarium)]]
* [[Lists (ePistolarium)]]
* [[Tables (ePistolarium)]]
* [[Poems (ePistolarium)]]
* [[Images (ePistolarium)]]
* [[Names (ePistolarium)]]
* [[Miscellaneous (ePistolarium)]]
* [[epistolarium naar regulier TEI]]

====Isidore Project====
* [[XML Isidore Guidelines]]

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

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

Main Page

2021-09-10T09:33:28Z

PBO: test

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]]
* [[Metadata (ePistolarium)]]
* [[Text structure (ePistolarium)]]
* [[Local annotations (ePistolarium)]]
* [[Transcription (ePistolarium)]]
* [[Rendering (ePistolarium)]]
* [[Retorical structure (ePistolarium)]]
* [[Lists (ePistolarium)]]
* [[Tables (ePistolarium)]]
* [[Poems (ePistolarium)]]
* [[Images (ePistolarium)]]
* [[Names (ePistolarium)]]
* [[Miscellaneous (ePistolarium)]]
* [[epistolarium naar regulier TEI]]

====Isidore Project====
* [[XML Isidore Guidelines]]

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

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

Main Page

2021-09-10T09:33:14Z

PBO: test

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]]
* [[Metadata (ePistolarium)]]
* [[Text structure (ePistolarium)]]
* [[Local annotations (ePistolarium)]]
* [[Transcription (ePistolarium)]]
* [[Rendering (ePistolarium)]]
* [[Retorical structure (ePistolarium)]]
* [[Lists (ePistolarium)]]
* [[Tables (ePistolarium)]]
* [[Poems (ePistolarium)]]
* [[Images (ePistolarium)]]
* [[Names (ePistolarium)]]
* [[Miscellaneous (ePistolarium)]]
* [[epistolarium naar regulier TEI]]

====Isidore Project====
* [[XML Isidore Guidelines]]

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

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

XML Isidore Guidelines

2021-03-25T09:53:46Z

PBO:

For the encoding the glosses in the Etymologiae, we use these guidelines.

==Witnesses==
For each of the manuscripts for which the glosses have been transcribed, we describe its location in an <msDesc>-element
in the <sourceDesc>. We also describe the relevant hands in a <handNote> in a <handDesc> in the <physDesc>.
For each hand we give a <date>.

For example:
<pre>
<msDesc xml:id="Clm4541">
<msIdentifier>
<settlement>Munich</settlement>
<institution>Bayerische Staatsbibliothek</institution>
<idno>Clm 4541</idno>
</msIdentifier>
<physDesc>
<handDesc>
<handNote xml:id="Clm4541_main">main hand<date when-iso="800/900">9th
century</date></handNote>
<handNote xml:id="Clm4541_g1">glossing hand 1<date when-iso="1000/1100">11th
century</date></handNote>
</handDesc>
</physDesc>
</msDesc>
</pre>

==Isidore's text==
Isidore's text is given in the <text> <body>. Only Book I is present. Each chapter is a div, each paragraph an <ab>.
<pb> elements provide the link to <surface>s in the various manuscripts using the @corresp attribute. Glossed text fragments are
identified using <seg> elements. Their @xml:id attributes are used by the <glossGrp>s further on in the file.

For example:
<pre>
<div n="II" type="chapter">
<head><seg xml:id="L2.1.1">DE SEPTEM LIBERALIBVS
DISCIPLINIS.</seg></head>
<ab n="1">Disciplinae <seg xml:id="L2.1.2">liberalium artium</seg> septem sunt. Prima
<seg xml:id="L2.1.3">grammatica</seg>, id est loquendi <seg xml:id="L2.1.4"
>peritia</seg>. Secunda <seg xml:id="L2.1.5">rhetorica</seg>, quae propter <seg
xml:id="L2.1.6">nitorem</seg> et <seg xml:id="L2.1.7">copiam</seg>
<seg xml:id="L2.1.8">eloquentiae</seg> suae maxime in <seg xml:id="L2.1.9"
>civilibus</seg> quaestionibus necessaria <seg xml:id="L2.1.10"
>existimatur</seg>. Tertia <seg xml:id="L2.1.11">dialectica</seg>
<pb corresp="#Harley3941_2v"/>
...
</ab>
...
</div>
</pre>

Quotations in Isidore's text are identified using the <quote>-element. The <quote>'s @source
attribute points to an element in the list of works (<listBibl>) in the <standoff>-element

For example:
<pre>
<quote source="#ApocalypsisI8">Ego sum <seg xml:id="L3.9.8">Α</seg> et Ω.</quote>
</pre>

==The glosses==
The glosses are defined by <gloss>-elements within <hi:glossGrp>s referring to <seg>s in the text. All <hi:glossGrp>s
are contained in a <hi:glossGrpList> in the file's <standoff>-element. The glosses use the @corresp-attribute to point to
the manuscript that contains them and the @hand attribute to point to the responsible hand. The <gloss>'s @weight-attribute
gives a researcher-assigned weight for the non-triviality of the gloss.

Similarity between glosses is defined by <linkGrp>s. A <linkGrp> contains pointers (<ptr>) to similar glosses.
<linkGrp>s are, by convention, placed in the <glossGrp> that contains the <gloss>s that most of its <ptr>-members point to.
<linkGrp>s have an @ana-attribute that can be used to group related groups of similarities. It points to groups that
can be described (but as yet are not) in an <interpGrp> at the bottom of the file.

For example:
<pre>
<hi:glossGrp target="#L37.35.17" witCount="5">
<linkGrp ana="#E" type="simgroup">
<ptr target="#L37.35.17_2"/>
<ptr target="#L37.35.17_5"/>
</linkGrp>
<linkGrp ana="#F" type="simgroup">
<ptr target="#L37.35.17_3"/>
<ptr target="#L37.35.17_4"/>
</linkGrp>
<gloss xml:id="L37.35.17_1" corresp="#Bologna797">id est Eneas</gloss>
<gloss xml:id="L37.35.17_2" corresp="#GothaI147" weight="4">id est Aenias de patre suo
dicit</gloss>
<gloss xml:id="L37.35.17_3" corresp="#Harley3941" weight="4">Aeneas dixit quando voluit
visitare patrem suum in infer[no]</gloss>
<gloss xml:id="L37.35.17_4" corresp="#Orleans296" weight="4">Aeneas dixit quando voluit
visitare patrem suum in inferno</gloss>
<gloss xml:id="L37.35.17_5" corresp="#Paris7585" weight="4">scilicet Aeneas de patre suo
dicit</gloss>
</hi:glossGrp>
</pre>

==Textual details==
Gaps in the text are encoded as <gap>, unclear passages as <unclear>, corrections as (see example):

<pre>
<choice>
<orig>partiones</orig>
<corr>partitiones</corr>
</choice>
</pre>

XML Isidore Guidelines

2021-02-01T16:02:30Z

PBO: First version

For the encoding the glosses in the Etymologiae, we use these guidelines.

==Witnesses==
For each of the manuscripts for which the glosses have been transcribed, we describe its location in an <msDesc>-element
in the <sourceDesc>. We also describe the relevant hands in a <handNote> in a <handDesc> in the <physDesc>.
For each hand we give a <date>.

For example:
<pre>
<msDesc xml:id="Clm4541">
<msIdentifier>
<settlement>Munich</settlement>
<institution>Bayerische Staatsbibliothek</institution>
<idno>Clm 4541</idno>
</msIdentifier>
<physDesc>
<handDesc>
<handNote xml:id="Clm4541_main">main hand<date when-iso="800/900">9th
century</date></handNote>
<handNote xml:id="Clm4541_g1">glossing hand 1<date when-iso="1000/1100">11th
century</date></handNote>
</handDesc>
</physDesc>
</msDesc>
</pre>

==Isidore's text==
Isidore's text is given in the <text> <body>. Only Book I is present. Each chapter is a div, each paragraph an <ab>.
<pb> elements provide the link to <surface>s in the various manuscripts using the @corresp attribute. Glossed text fragments are
identified using <seg> elements. Their @xml:id attributes are used by the <glossGrp>s further on in the file.

For example:
<pre>
<div n="II" type="chapter">
<head rend="script(ruscaps)"><seg xml:id="L2.1.1">DE SEPTEM LIBERALIBVS
DISCIPLINIS.</seg></head>
<ab n="1">Disciplinae <seg xml:id="L2.1.2">liberalium artium</seg> septem sunt. Prima
<seg xml:id="L2.1.3">grammatica</seg>, id est loquendi <seg xml:id="L2.1.4"
>peritia</seg>. Secunda <seg xml:id="L2.1.5">rhetorica</seg>, quae propter <seg
xml:id="L2.1.6">nitorem</seg> et <seg xml:id="L2.1.7">copiam</seg>
<seg xml:id="L2.1.8">eloquentiae</seg> suae maxime in <seg xml:id="L2.1.9"
>civilibus</seg> quaestionibus necessaria <seg xml:id="L2.1.10"
>existimatur</seg>. Tertia <seg xml:id="L2.1.11">dialectica</seg>
<pb corresp="#Harley3941_2v"/>
...
</ab>
...
</div>
</pre>

Quotations in Isidore's text are identified using the <quote>-element. The <quote>'s @source
attribute points to an element in the list of works (<listBibl>) in the <standoff>-element

For example:
<pre>
<quote source="#ApocalypsisI8">Ego sum <seg xml:id="L3.9.8">Α</seg> et Ω.</quote>
</pre>

==The glosses==
The glosses are defined by <gloss>-elements within <hi:glossGrp>s referring to <seg>s in the text. All <hi:glossGrp>s
are contained in a <hi:glossGrpList> in the file's <standoff>-element. The glosses use the @corresp-attribute to point to
the manuscript that contains them and the @hand attribute to point to the responsible hand. The <gloss>'s @weight-attribute
gives a researcher-assigned weight for the non-triviality of the gloss.

Similarity between glosses is defined by <linkGrp>s. A <linkGrp> contains pointers (<ptr>) to similar glosses.
<linkGrp>s are, by convention, placed in the <glossGrp> that contains the <gloss>s that most of its <ptr>-members point to.
<linkGrp>s have an @ana-attribute that can be used to group related groups of similarities. It points to groups that
can be described (but as yet are not) in an <interpGrp> at the bottom of the file.

For example:
<pre>
<hi:glossGrp target="#L37.35.17" witCount="5">
<linkGrp ana="#E" type="simgroup">
<ptr target="#L37.35.17_2"/>
<ptr target="#L37.35.17_5"/>
</linkGrp>
<linkGrp ana="#F" type="simgroup">
<ptr target="#L37.35.17_3"/>
<ptr target="#L37.35.17_4"/>
</linkGrp>
<gloss xml:id="L37.35.17_1" corresp="#Bologna797">id est Eneas</gloss>
<gloss xml:id="L37.35.17_2" corresp="#GothaI147" weight="4">id est Aenias de patre suo
dicit</gloss>
<gloss xml:id="L37.35.17_3" corresp="#Harley3941" weight="4">Aeneas dixit quando voluit
visitare patrem suum in infer[no]</gloss>
<gloss xml:id="L37.35.17_4" corresp="#Orleans296" weight="4">Aeneas dixit quando voluit
visitare patrem suum in inferno</gloss>
<gloss xml:id="L37.35.17_5" corresp="#Paris7585" weight="4">scilicet Aeneas de patre suo
dicit</gloss>
</hi:glossGrp>
</pre>

==Textual details==
Gaps in the text are encoded as <gap>, unclear passages as <unclear>, corrections as (see example):

<pre>
<choice>
<orig>partiones</orig>
<corr>partitiones</corr>
</choice>
</pre>

XML Isidore Guidelines

2021-02-01T15:57:54Z

PBO: First version

For the encoding the glosses the Etymologiae, we use the following guidelines

==Witnesses==
For each of the manuscripts for which the glosses have been transcribed, we describe its location in an <msDesc>-element
in the <sourceDesc>. We also describe the relevant hands in a <handNote> in a <handDesc> in the <physDesc>.
For each hand we give a <date>.

For example:
<pre>
<msDesc xml:id="Clm4541">
<msIdentifier>
<settlement>Munich</settlement>
<institution>Bayerische Staatsbibliothek</institution>
<idno>Clm 4541</idno>
</msIdentifier>
<physDesc>
<handDesc>
<handNote xml:id="Clm4541_main">main hand<date when-iso="800/900">9th
century</date></handNote>
<handNote xml:id="Clm4541_g1">glossing hand 1<date when-iso="1000/1100">11th
century</date></handNote>
</handDesc>
</physDesc>
</msDesc>
</pre>

==Isidore's text==
Isidore's text is given in the <text> <body>. Only Book I is present. Each chapter is a div, each paragraph an <ab>.
<pb> elements provide the link to <surface>s in the various manuscripts using the @corresp attribute. Glossed text fragments are
identified using <seg> elements. Their @xml:id attributes are used by the <glossGrp>s further on in the file.

For example:
<pre>
<div n="II" type="chapter">
<head rend="script(ruscaps)"><seg xml:id="L2.1.1">DE SEPTEM LIBERALIBVS
DISCIPLINIS.</seg></head>
<ab n="1">Disciplinae <seg xml:id="L2.1.2">liberalium artium</seg> septem sunt. Prima
<seg xml:id="L2.1.3">grammatica</seg>, id est loquendi <seg xml:id="L2.1.4"
>peritia</seg>. Secunda <seg xml:id="L2.1.5">rhetorica</seg>, quae propter <seg
xml:id="L2.1.6">nitorem</seg> et <seg xml:id="L2.1.7">copiam</seg>
<seg xml:id="L2.1.8">eloquentiae</seg> suae maxime in <seg xml:id="L2.1.9"
>civilibus</seg> quaestionibus necessaria <seg xml:id="L2.1.10"
>existimatur</seg>. Tertia <seg xml:id="L2.1.11">dialectica</seg>
<pb corresp="#Harley3941_2v"/>
...
</ab>
...
</div>
</pre>

Quotations in Isidore's text are identified using the <quote>-element. The <quote>'s @source
attribute points to an element in the list of works (<listBibl>) in the <standoff>-element

For: example:
<pre>
<quote source="#ApocalypsisI8">Ego sum <seg xml:id="L3.9.8">Α</seg> et Ω.</quote>
</pre>

==The glosses==
The glosses are defined by <gloss>-elements within <hi:glossGrp>s referring to <seg>s in the text. All <hi:glossGrp>s
are contained in a <hi:glossGrpList> in the file's <standoff>-element. The glosses use the @corresp-attribute to point to
the manuscript that contains them and the @hand attribute to point to the responsible hand. The <gloss>'s @weight-attribute
gives a researcher-assigned weight for the non-triviality of the gloss.

Similarity between glosses is defined by <linkGrp>s. A <linkGrp> contains pointers (<ptr>) to similar glosses.
<linkGrp>s are, by convention, placed in the <glossGrp> that contains the <gloss>s that most of its <ptr>-members point to.
<linkGrp>s have an @ana-attribute that can be used to group related groups of similarities. It points to groups that
can be described (but as yet are not) in an <interpGrp> at the bottom of the file.

For example:
<pre>
<hi:glossGrp target="#L37.35.17" witCount="5">
<linkGrp ana="#E" type="simgroup">
<ptr target="#L37.35.17_2"/>
<ptr target="#L37.35.17_5"/>
</linkGrp>
<linkGrp ana="#F" type="simgroup">
<ptr target="#L37.35.17_3"/>
<ptr target="#L37.35.17_4"/>
</linkGrp>
<gloss xml:id="L37.35.17_1" corresp="#Bologna797">id est Eneas</gloss>
<gloss xml:id="L37.35.17_2" corresp="#GothaI147" weight="4">id est Aenias de patre suo
dicit</gloss>
<gloss xml:id="L37.35.17_3" corresp="#Harley3941" weight="4">Aeneas dixit quando voluit
visitare patrem suum in infer[no]</gloss>
<gloss xml:id="L37.35.17_4" corresp="#Orleans296" weight="4">Aeneas dixit quando voluit
visitare patrem suum in inferno</gloss>
<gloss xml:id="L37.35.17_5" corresp="#Paris7585" weight="4">scilicet Aeneas de patre suo
dicit</gloss>
</hi:glossGrp>
</pre>

==Textual details==
Gaps in the text are encoded as <gap>, unclear passages as <unclear>, corrections as (see example):

<pre>
<choice>
<orig>partiones</orig>
<corr>partitiones</corr>
</choice>
</pre>

XML Isidore Guidelines

2021-02-01T15:53:16Z

PBO: First version

For the encoding the glosses the Etymologiae, we use the following guidelines

==Witnesses==
For each of the manuscripts fow which the glosses have been transcribed, we describe its location in an <msDesc>
element in the <sourceDesc>. We also describe the relevant hands in a <handNote> in a <handDesc> in the <physDescDesc>.
For each hand we give a <date>.

For example:
<pre>
<msDesc xml:id="Clm4541">
<msIdentifier>
<settlement>Munich</settlement>
<institution>Bayerische Staatsbibliothek</institution>
<idno>Clm 4541</idno>
</msIdentifier>
<physDesc>
<handDesc>
<handNote xml:id="Clm4541_main">main hand<date when-iso="800/900">9th
century</date></handNote>
<handNote xml:id="Clm4541_g1">glossing hand 1<date when-iso="1000/1100">11th
century</date></handNote>
</handDesc>
</physDesc>
</msDesc>
</pre>

==Isidore's text==
Isidore's text is given in the <text> <body>. Only Book I is present. Each chapter is a div, each paragraph an <ab>.
<pb> elements provide the link to surfaces in the various manuscripts using the @corresp attribute. Glossed text fragments are
identified using <seg> elements. Their @xml:id attributes are by the <glossGrp>s further on in the file.

For example:
<pre>
<div n="II" type="chapter">
<head rend="script(ruscaps)"><seg xml:id="L2.1.1">DE SEPTEM LIBERALIBVS
DISCIPLINIS.</seg></head>
<ab n="1">Disciplinae <seg xml:id="L2.1.2">liberalium artium</seg> septem sunt. Prima
<seg xml:id="L2.1.3">grammatica</seg>, id est loquendi <seg xml:id="L2.1.4"
>peritia</seg>. Secunda <seg xml:id="L2.1.5">rhetorica</seg>, quae propter <seg
xml:id="L2.1.6">nitorem</seg> et <seg xml:id="L2.1.7">copiam</seg>
<seg xml:id="L2.1.8">eloquentiae</seg> suae maxime in <seg xml:id="L2.1.9"
>civilibus</seg> quaestionibus necessaria <seg xml:id="L2.1.10"
>existimatur</seg>. Tertia <seg xml:id="L2.1.11">dialectica</seg>
<pb corresp="#Harley3941_2v"/>
...
</ab>
...
</div>
</pre>

Quotations in Isidore's text are identified using the <quote>-element. The <quote>'s @source
attribute points to a list of works (<listBibl>) in the <standoff>-element

For: example:
<pre>
<quote source="#ApocalypsisI8">Ego sum <seg xml:id="L3.9.8">Α</seg> et Ω.</quote>
</pre>

==The glosses==
The glosses are defined by <gloss>-elements within <hi:glossGrp>s referring to <seg>s in the text. All <hi:glossGrp>s
are contained in a <hi:glossGrpList> in the file's <standoff>-element. They use the @corresp-attribute to point to
the manuscript that contains them and the @hand attribute to point to the responsible hand. The <gloss>'s @weight-attribute
gives a researcher-assigned weight for the non-triviality of the gloss.

Similarity between glosses is defined by <linkGrp>s. A <linkGrp> contains pointers (<ptr>) to similar glosses.
<linkGrp>s are, by convention, placed in the <glossGrp> that contains the <gloss>s that most of its <ptr>-members point to.
<linkGrp>s have an @ana-attribute that can be used to group related groups of similarities. It points to groups that
can be defined in an <interpGrp> at the bottom of the file.

For example:
<pre>
<hi:glossGrp target="#L37.35.17" witCount="5">
<linkGrp ana="#E" type="simgroup">
<ptr target="#L37.35.17_2"/>
<ptr target="#L37.35.17_5"/>
</linkGrp>
<linkGrp ana="#F" type="simgroup">
<ptr target="#L37.35.17_3"/>
<ptr target="#L37.35.17_4"/>
</linkGrp>
<gloss xml:id="L37.35.17_1" corresp="#Bologna797">id est Eneas</gloss>
<gloss xml:id="L37.35.17_2" corresp="#GothaI147" weight="4">id est Aenias de patre suo
dicit</gloss>
<gloss xml:id="L37.35.17_3" corresp="#Harley3941" weight="4">Aeneas dixit quando voluit
visitare patrem suum in infer[no]</gloss>
<gloss xml:id="L37.35.17_4" corresp="#Orleans296" weight="4">Aeneas dixit quando voluit
visitare patrem suum in inferno</gloss>
<gloss xml:id="L37.35.17_5" corresp="#Paris7585" weight="4">scilicet Aeneas de patre suo
dicit</gloss>
</hi:glossGrp>
</pre>

==Textual details==
Gaps in the text are encoded as <gap>, unclear passages as <unclear>, corrections as (see example):

<pre>
<choice>
<orig>partiones</orig>
<corr>partitiones</corr>
</choice>
</pre>

Main Page

2021-02-01T15:12:16Z

PBO:

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]]
* [[Metadata (ePistolarium)]]
* [[Text structure (ePistolarium)]]
* [[Local annotations (ePistolarium)]]
* [[Transcription (ePistolarium)]]
* [[Rendering (ePistolarium)]]
* [[Retorical structure (ePistolarium)]]
* [[Lists (ePistolarium)]]
* [[Tables (ePistolarium)]]
* [[Poems (ePistolarium)]]
* [[Images (ePistolarium)]]
* [[Names (ePistolarium)]]
* [[Miscellaneous (ePistolarium)]]
* [[epistolarium naar regulier TEI]]

====Isidore Project====
* [[XML Isidore Guidelines]]

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

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

User:PBO

2020-01-22T15:53:22Z

PBO:

Hallo. Ik ben [https://www.huygens.knaw.nl/medewerkers/peter-boot/ Peter Boot], de beheerder van deze verzameling XML-richtlijnen, in gebruik bij [https://www.huygens.knaw.nl/ Huygens ING]. Voor vragen en commentaar ben ik bijvoorbeeld via de [mailto:peter.boot@huygens.knaw.nl mail] te bereiken.

User:PBO

2020-01-22T15:52:55Z

PBO: Created page with "Hallo. Ik ben [https://www.huygens.knaw.nl/medewerkers/peter-boot/ Peter Boot], de beheerder van deze verzameling XML-richtlijnen, in gebruik bij [https://www.huygens.knaw.nl/..."

Hallo. Ik ben [https://www.huygens.knaw.nl/medewerkers/peter-boot/ Peter Boot], de beheerder van deze verzameling XML-richtlijnen, in gebruik bij [https://www.huygens.knaw.nl/ Huygens ING]. Voor commentaar vragen ben ik bijvoorbeeld via de [mailto:peter.boot@huygens.knaw.nl mail] te bereiken.

TEI Header (Mondrian)

2020-01-22T15:44:42Z

PBO:

== The teiHeader ==
The <teiHeader> contains the letter's or manuscript's metadata. In an earlier stage of the
project we used encoding guidelines for the header derived from the [https://ctb.kantl.be/project/dalf/dalfdoc/index.html DALF project].
We switched to a more modern encoding that uses the <correspDesc> element.
The elements of the teiHeader that we use are the:
* fileDesc
* profileDesc
* revisionDesc

This looks as follows:
<pre>
<teiHeader>
<fileDesc>
...
</fileDesc>
<profileDesc>
...
</profileDesc>
<revisionDesc>
...
</revisionDesc>
<teiHeader>
</pre>

== The fileDesc ==
A typical fileDersc will contain a fileStmt, a publicationStmt and sourceDesc. The sourceDesc
will contain a msDesc (manuscript description) that contains an msIdentifier detailing the location of the manuscript
as well as alternate identifiers. The msDesc will also contain a physDesc (physical description) that identifies the type of
the manuscript (brief or briefkaart) and describe decoration, if any.

It may look like this:
<pre>
<fileDesc>
<titleStmt>
<title>Briefkaart aan <ref target="bio.xml#MondriaanCarel">Carel</ref> en <ref target="bio.xml#MondriaanLouis">Louis Mondriaan</ref>. Hengelo, maandag 22 oktober 1906 (poststempel).</title>
<editor xml:id="wc">Wietse Coppes</editor>
<editor xml:id="lj">Leo Jansen</editor>
<sponsor>Mondriaan Editieproject</sponsor>
</titleStmt>
<publicationStmt>
<p>(to be provided later)</p>
</publicationStmt>
<sourceDesc>
<msDesc>
<msIdentifier>
<country>Nederland</country>
<settlement>Den Haag</settlement>
<institution>RKD</institution>
<idno>150.558</idno>
<altIdentifier><idno type="letterId">19061022_MOND_C+L_0012</idno></altIdentifier>
<altIdentifier><idno type="def"/></altIdentifier>
</msIdentifier>
<physDesc>
<objectDesc form="briefkaart"/>
<decoDesc>
<decoNote/>
</decoDesc>
</physDesc>
</msDesc>
</sourceDesc>
</fileDesc>
</pre>

== The profileDesc ==
The profileDesc describes the 'correspondence actions'. For example:

<pre>
<profileDesc>
<correspDesc>
<correspAction type="sent">
<name key="56854">Piet Mondriaan</name>
<date when="1906-10-22">maandag 22 oktober 1906</date>
<placeName>Hengelo</placeName>
</correspAction>
<correspAction type="received">
<name key="...">Carel Mondriaan</name>
<name key="...">Louis Mondriaan</name>
</correspAction>
</correspDesc>
</profileDesc>
</pre>

====About the dating====

The text of <date> in <correspAction type="sent"> is what you want to appear in the edition. The @when attribute indicates the precise
date; if necessary use @notBefore and/or @notAfter to indicate a range (in this case, the @when attribute is what will be used for sorting).
In the attributes, the dates are entered as yyyy-mm-dd.
* Single date:
<pre><date when="1935-03-13">March 13, 1935</date></pre>
* Date range:
<pre><date when="1935-03-13" notAfter="1935-03-14"
notBefore="1935-03-13">March 13 or March 14, 1935</date></pre>

== The revisionDesc ==
The revisionDesc is used to track the progress of the editorial work on the specific letter or manuscript.

====Some remarks====

The md:type attribute contains the type of document and has one of the values: letter, postcard, telegram (or manuscript, article?)

The elements <author> and <addressee> are required to have a @key, which points to a resource about the person mentioned (in this case, the RKDartists inventory)

<author> and <addressee> can also have @attested and @accepted; <placeLet> and <dateLet> can just have @attested. We vullen attested/accepted in. (Attested: expliciet gedocumenteerd; accepted: inductief)

More information on how these elements are used is available in [[Creating Mondrian: further guidelines]]

<s>In <letContents>, informations can be organized in one or more paragraphs <p>, keywords <keywords> or as notes <note>.</s> We probably won't use this.

<envOcc> is a required element, with a required @occ, to encode the presence of an envelope.

==See also==
* [[XML Mondrian Guidelines]]

[[Category:XML Mondrian]]

Annotation and indexing (Mondrian)

2020-01-22T14:57:29Z

PBO:

==Annotation at the level of the letter==
Annotation for which the [[TEI_Header_(Mondrian)|teiHeader]] provides a natural place is stored there. Besides that,
each letter or manuscript contains a <div> containing annotation, structured as follows:
* a number of typed notes with fixed subjects (now: source of transcription, dating and remarks)
* zero or more of ongoing topic notes
* zero or more notes to specific locations in the text

An example:
<pre>
<div type="annotation">
<div type="typednotes" xml:lang="nl">
<note type="transcrSource">Manuscript.</note>
<note type="dating">Poststempel.</note>
<note type="remarks">Beeldzijde: watermolen bij Delden, nabij Hengelo; cf. ongoing topic.</note>
</div>
<div type="ogtnotes">
<note target="MEP_0011.xml#verblijfplaats">Mondriaans verblijf in Hengelo bij Hulshoff Pol.</note>
</div>
<div type="notes" xml:lang="nl">
<note xml:id="openingTeekening">De tentoonstelling <ref target="exhibitions.xml"><hi rend="italics">Aquarellen, Teekeningen en ... </note>
</div>
</div>
</pre>

==Explanatory notes==
To create a note
* Put into the transcription or translation a pointer (<ptr/>), with @target consisting of '#' and a short keyword (start with letter, no spaces) and @type=“note”.
* Create a <note> into the <div type=“notes”> with the text of the note. Its @xml:id must must be the keyword used in the pointer's @target.
* Put all notes in a single language in the same div element.
* Order the notes by their referred location (technically irrelevant, but helpful to the human eye)

For example:
<pre>
<p>This is an example<anchor target="#nootje" type= "note"/> of how to create a note</p>

<div type="notes" xml:lang="en">
<note xml:id="nootje">This is the note</note>
… other notes in English…
</div>

<div type="notes" xml:lang="nl">
<note n="nootje">Dit is de noot</note>
… other notes in Dutch …
</div>
</pre>

==Recurring annotation==

See [[Secondary files (Mondrian)#Recurring notes to persons and other subjects|Recurring notes to persons and other subjects]].

==<rs>==

Referencing string. Into <rs> are encoded names, with attributes, so they can be easily identified (i.e. You have different spellings of the same person's name and you want that they point to the same person), retrieved, indexed.
* '''@type''' kind of entity encoded (i.e. Person, exhibition, museum, journals, location, etc). The available types have been defined in the schema
* '''@ref''' to indicate an external url (RDKarchive url)
* '''@key''' a coded value that identifies the entity encoded (i.e. a number, a normalised spelling, etc.) We prefer to use @key rather than @ref.

It is possible to use multiple values in the key or ref attributes.

In the postal data (transcription of envelope) we don’t use <rs> to index the addressee, as his role is known from the letter metadata. Similarly, we don’t index persons saluted at the beginning or end of a letter, if these are addressees. (But we do tag ‘Jan’ in ‘Give my love to Jan’ if Jan is not an addressee).

When encoding a referring phrase as <rs>, we only tag the noun. This avoids potential problems with other words that need their own encoding.

Not:
<pre>
<rs>the woman who lives next door</rs>
</pre>
but
<pre>
the <rs>woman</rs> who lives next door
</pre>

In the case of multiple references to a person within a single paragraph, we encode each of them.

==References==

The element <ref> points to another resource and it is used for instance when a letter, a painting or another resource is mentioned in the text. @target provides the resource location (local or not).

<ref> is also used for pointing to the [[Secondary files (Mondrian)|bibliography]]. For example:
<pre>
... as mentioned in <ref target="biblio.xml#Andersen1861">Andersen 1861</ref>, we ...
</pre>
Here, 'Andersen1861' should be an entry in the bibliography.

==See also==
* [[Transcription: structure (Mondrian)]]
* [[Transcription: representation of the source (Mondrian)]]
* [[Transcription (Mondrian)]]

[[Category:XML Mondrian]]

Annotation and indexing (Mondrian)

2020-01-22T14:39:13Z

PBO: note reference system changed

==Explanatory notes==
To create a note
* Put into the transcription or translation a pointer (<ptr/>), with @target consisting of '#' and a short keyword (start with letter, no spaces) and @type=“note”.
* Create a <note> into the <div type=“notes”> with the text of the note. Its @xml:id must must be the keyword used in the pointer's @target.
* Put all notes in a single language in the same div element.
* Order the notes by their referred location (technically irrelevant, but helpful to the human eye)

For example:
<pre>
<p>This is an example<anchor target="#nootje" type= "note"/> of how to create a note</p>

<div type="notes" xml:lang="en">
<note xml:id="nootje">This is the note</note>
… other notes in English…
</div>

<div type="notes" xml:lang="nl">
<note n="nootje">Dit is de noot</note>
… other notes in Dutch …
</div>
</pre>

==Recurring annotation==

See [[Secondary files (Mondrian)#Recurring notes to persons and other subjects|Recurring notes to persons and other subjects]].

==<rs>==

Referencing string. Into <rs> are encoded names, with attributes, so they can be easily identified (i.e. You have different spellings of the same person's name and you want that they point to the same person), retrieved, indexed.
* '''@type''' kind of entity encoded (i.e. Person, exhibition, museum, journals, location, etc). The available types have been defined in the schema
* '''@ref''' to indicate an external url (RDKarchive url)
* '''@key''' a coded value that identifies the entity encoded (i.e. a number, a normalised spelling, etc.) We prefer to use @key rather than @ref.

It is possible to use multiple values in the key or ref attributes.

In the postal data (transcription of envelope) we don’t use <rs> to index the addressee, as his role is known from the letter metadata. Similarly, we don’t index persons saluted at the beginning or end of a letter, if these are addressees. (But we do tag ‘Jan’ in ‘Give my love to Jan’ if Jan is not an addressee).

When encoding a referring phrase as <rs>, we only tag the noun. This avoids potential problems with other words that need their own encoding.

Not:
<pre>
<rs>the woman who lives next door</rs>
</pre>
but
<pre>
the <rs>woman</rs> who lives next door
</pre>

In the case of multiple references to a person within a single paragraph, we encode each of them.

==References==

The element <ref> points to another resource and it is used for instance when a letter, a painting or another resource is mentioned in the text. @target provides the resource location (local or not).

<ref> is also used for pointing to the [[Secondary files (Mondrian)|bibliography]]. For example:
<pre>
... as mentioned in <ref target="biblio.xml#Andersen1861">Andersen 1861</ref>, we ...
</pre>
Here, 'Andersen1861' should be an entry in the bibliography.

==See also==
* [[Transcription: structure (Mondrian)]]
* [[Transcription: representation of the source (Mondrian)]]
* [[Transcription (Mondrian)]]

[[Category:XML Mondrian]]

Epistolarium naar regulier TEI

2018-03-22T15:27:20Z

PBO:

Wat moet er aan ePistolarium XML gebeuren om het meer in lijn te brengen met TEI

1. Omzetting naar TEI P5: alle elementen naar TEI namespace

2. Omzetting van de meta-elementen

Een optie zou zijn: <xenodata>
Maar dan maak je je er een beetje van af

Nog onduidelijk:
<meta type="uuid" value="54ddae9b-ec6c-41e3-bc99-eb5387b4af26"/>
Wat gebeurt hiermee?

<meta type="dataset" value="ckcc"/>
En hiermee? Hebben we meerdere datasets?

<meta type="correspondence" value="desc004"/>
Classificatie binnen CKCC, neem ik aan

<meta type="id" value="1046"/>
<meta type="alt_id" value="AM1-208-046"/>
<meta type="alt_id" value="AT038"/>
<meta type="alt_id" value="EJB049"/>
worden idno's met type
Kennelijk heeft alleen Descartes zoveel verschillende types.
Het hoofd-id is een volgnummer binnen CKCC, neem ik aan

<meta type="date" value="1631-10/1631-11"/>
--> correspDesc/correspAction type=sent/date
en hier de betreffende waarde weergeven middels when, notBefore en notAfter.
Maar zie: http://www.loc.gov/standards/datetime/.
Misschien een when_custom dan?

<meta type="sender" value="descartes.rene.1596-1650"/>
--> correspDesc/correspAction type=sent/persName
en hier de betreffende waarde weergeven in key-attribuut.
Alternatief: sta person toe in correspAction

<meta type="senderloc" value="se.amsterdam.nld"/>
--> correspDesc/correspAction type=sent/placeName
en hier de betreffende waarde weergeven in key-attribuut.
Alternatief: sta place toe in correspAction.
Hier kan ook een resp-attribuut op staan.

<meta type="recipient" value="mersenne.marin.1588-1648"/>
<meta type="recipientloc" value="se.paris.fra" resp="#EJB"/>
Als bij sender

<meta type="status" value="OK"/>
Geeft dit een status van verwerking aan?
--> revisionDesc status = OK.
Moet leeg kunnen zijn.
Kan aangeven dat geen tekst aanwezig is, of kan verwijzen naar andere brief. (ca. 100 gevallen).

En meta type=type?? voor bijlagen
meta type=link met id van corresponderend document

3. Element formula
Opnemen in schema. Maar kennelijk gebeurt er niets mee? Althans binnen figure, daarbuiten wel. (voorbeelden desc004.208-046.xml)

4. Type attributen op div
Moeten we dat uniformeren? Wat is een type=artifact? (de echte brief)

5. xml:lang attributen
in elk geval onbekend coderen als unk
Rare combinatie van 2 en 3 letter codes?

6. <ref type="bible">Matth. XX. 16</ref>

7. en deze inline notes:
<div type="para">
<p><seg type="note">Adres:</seg> (A Mon)sieur Monsieur Grotius à Paris.</p>
<p><seg type="note">In dorso schreef Grotius:</seg> 6 Jan. 1629 N. Reigersberg.</p>
</div>

8. En wat te doen met de openers en de closers?
Denk aan de situatie van een openende/sluitende alinea, van meerdere van zulke alinea's en van een openend/afsluitend stukje tekst in een alinea.

Wat zou dit schema voor Mondriaan betekenen
- over naar correspDesc
- namespace wvan de nieuwe elementen wordt hi: http://huygens.knaw.nl

https://correspondence.huygens.knaw.nl/documents/c151aa14-306d-4993-aa1b-e175a469e566
Geeft heel rare foutboodschap.
"The tag <quote> is not implemented!
Wrapped on: "waer door dan het punt B lichtelijk gevonden wort, als men alleenlijk op 2 sijden des driehoeks DFG circelboogen beschrijft die de gevonden hoeken tot de sijden behoorende begrijpen. want de doorsnijding van sulke 2 boogen is het punt B."
This tag is not part of the Huygens ING TEI standard. Please visit Servicedesk.huygens.knaw.nl to request support of this tag."

Epistolarium naar regulier TEI

2018-03-13T15:59:53Z

PBO:

Wat moet er aan ePistolarium XML gebeuren om het meer in lijn te brengen met TEI

1. Omzetting naar TEI P5: alle elementen naar TEI namespace

2. Omzetting van de meta-elementen

Een optie zou zijn: <xenodata>
Maar dan maak je je er een beetje van af

Nog onduidelijk:
<meta type="uuid" value="54ddae9b-ec6c-41e3-bc99-eb5387b4af26"/>
Wat gebeurt hiermee?

<meta type="dataset" value="ckcc"/>
En hiermee? Hebben we meerdere datasets?

<meta type="correspondence" value="desc004"/>
Classificatie binnen CKCC, neem ik aan

<meta type="id" value="1046"/>
<meta type="alt_id" value="AM1-208-046"/>
<meta type="alt_id" value="AT038"/>
<meta type="alt_id" value="EJB049"/>
worden idno's met type
Kennelijk heeft alleen Descartes zoveel verschillende types.
Het hoofd-id is een volgnummer binnen CKCC, neem ik aan

<meta type="date" value="1631-10/1631-11"/>
--> correspDesc/correspAction type=sent/date
en hier de betreffende waarde weergeven middels when, notBefore en notAfter.
Maar zie: http://www.loc.gov/standards/datetime/.
Misschien een when_custom dan?

<meta type="sender" value="descartes.rene.1596-1650"/>
--> correspDesc/correspAction type=sent/persName
en hier de betreffende waarde weergeven in key-attribuut.
Alternatief: sta person toe in correspAction

<meta type="senderloc" value="se.amsterdam.nld"/>
--> correspDesc/correspAction type=sent/placeName
en hier de betreffende waarde weergeven in key-attribuut.
Alternatief: sta place toe in correspAction.
Hier kan ook een resp-attribuut op staan.

<meta type="recipient" value="mersenne.marin.1588-1648"/>
<meta type="recipientloc" value="se.paris.fra" resp="#EJB"/>
Als bij sender

<meta type="status" value="OK"/>
Geeft dit een status van verwerking aan?
--> revisionDesc status = OK.
Moet leeg kunnen zijn.
Kan aangeven dat geen tekst aanwezig is, of kan verwijzen naar andere brief. (ca. 100 gevallen).

En meta type=type?? voor bijlagen
meta type=link met id van corresponderend document

3. Element formula
Opnemen in schema. Maar kennelijk gebeurt er niets mee? Althans binnen figure, daarbuiten wel. (voorbeelden desc004.208-046.xml)

4. Type attributen op div
Moeten we dat uniformeren? Wat is een type=artifact? (de echte brief)

5. xml:lang attributen
in elk geval onbekend coderen als unk
Rare combinatie van 2 en 3 letter codes?

6. <ref type="bible">Matth. XX. 16</ref>

7. en deze inline notes:
<div type="para">
<p><seg type="note">Adres:</seg> (A Mon)sieur Monsieur Grotius à Paris.</p>
<p><seg type="note">In dorso schreef Grotius:</seg> 6 Jan. 1629 N. Reigersberg.</p>
</div>

8. En wat te doen met de openers en de closers?
Denk aan de situatie van een openende/sluitende alinea, van meerdere van zulke alinea's en van een openend/afsluitend stukje tekst in een alinea.

https://correspondence.huygens.knaw.nl/documents/c151aa14-306d-4993-aa1b-e175a469e566
Geeft heel rare foutboodschap.
"The tag <quote> is not implemented!
Wrapped on: "waer door dan het punt B lichtelijk gevonden wort, als men alleenlijk op 2 sijden des driehoeks DFG circelboogen beschrijft die de gevonden hoeken tot de sijden behoorende begrijpen. want de doorsnijding van sulke 2 boogen is het punt B."
This tag is not part of the Huygens ING TEI standard. Please visit Servicedesk.huygens.knaw.nl to request support of this tag."

Epistolarium naar regulier TEI

2018-03-13T09:51:06Z

PBO:

Wat moet er aan ePistolarium XML gebeuren om het meer in lijn te brengen met TEI

1. Omzetting naar TEI P5: alle elementen naar TEI namespace

2. Omzetting van de meta-elementen

Een optie zou zijn: <xenodata>
Maar dan maak je je er een beetje van af

Nog onduidelijk:
<meta type="uuid" value="54ddae9b-ec6c-41e3-bc99-eb5387b4af26"/>
Wat gebeurt hiermee?

<meta type="dataset" value="ckcc"/>
En hiermee? Hebben we meerdere datasets?

<meta type="correspondence" value="desc004"/>
Classificatie binnen CKCC, neem ik aan

<meta type="id" value="1046"/>
<meta type="alt_id" value="AM1-208-046"/>
<meta type="alt_id" value="AT038"/>
<meta type="alt_id" value="EJB049"/>
worden idno's met type
Kennelijk heeft alleen Descartes zoveel verschillende types.
Het hoofd-id is een volgnummer binnen CKCC, neem ik aan

<meta type="date" value="1631-10/1631-11"/>
--> correspDesc/correspAction type=sent/date
en hier de betreffende waarde weergeven middels when, notBefore en notAfter.
Maar zie: http://www.loc.gov/standards/datetime/.
Misschien een when_custom dan?

<meta type="sender" value="descartes.rene.1596-1650"/>
--> correspDesc/correspAction type=sent/persName
en hier de betreffende waarde weergeven in key-attribuut.
Alternatief: sta person toe in correspAction

<meta type="senderloc" value="se.amsterdam.nld"/>
--> correspDesc/correspAction type=sent/placeName
en hier de betreffende waarde weergeven in key-attribuut.
Alternatief: sta place toe in correspAction.
Hier kan ook een resp-attribuut op staan.

<meta type="recipient" value="mersenne.marin.1588-1648"/>
<meta type="recipientloc" value="se.paris.fra" resp="#EJB"/>
Als bij sender

<meta type="status" value="OK"/>
Geeft dit een status van verwerking aan?
--> revisionDesc status = OK.
Moet leeg kunnen zijn.

En meta type=type??

3. Element formula
Opnemen in schema. Maar kennelijk gebeurt er niets mee? Althans binnen figure, daarbuiten wel. (voorbeelden desc004.208-046.xml)

4. Type attributen op div
Moeten we dat uniformeren? Wat is een type=artifact? (de echte brief)

5. xml:lang attributen
in elk geval onbekend coderen als unk
Rare combinatie van 2 en 3 letter codes?

6. <ref type="bible">Matth. XX. 16</ref>

7. en deze inline notes:
<div type="para">
<p><seg type="note">Adres:</seg> (A Mon)sieur Monsieur Grotius à Paris.</p>
<p><seg type="note">In dorso schreef Grotius:</seg> 6 Jan. 1629 N. Reigersberg.</p>
</div>

8. En wat te doen met de openers en de closers?
Denk aan de situatie van een openende/sluitende alinea, van meerdere van zulke alinea's en van een openend/afsluitend stukje tekst in een alinea.

https://correspondence.huygens.knaw.nl/documents/c151aa14-306d-4993-aa1b-e175a469e566
Geeft heel rare foutboodschap.
"The tag <quote> is not implemented!
Wrapped on: "waer door dan het punt B lichtelijk gevonden wort, als men alleenlijk op 2 sijden des driehoeks DFG circelboogen beschrijft die de gevonden hoeken tot de sijden behoorende begrijpen. want de doorsnijding van sulke 2 boogen is het punt B."
This tag is not part of the Huygens ING TEI standard. Please visit Servicedesk.huygens.knaw.nl to request support of this tag."

Epistolarium naar regulier TEI

2018-03-13T09:40:22Z

PBO:

Wat moet er aan ePistolarium XML gebeuren om het meer in lijn te brengen met TEI

1. Omzetting naar TEI P5: alle elementen naar TEI namespace

2. Omzetting van de meta-elementen

Een optie zou zijn: <xenodata>
Maar dan maak je je er een beetje van af

Nog onduidelijk:
<meta type="uuid" value="54ddae9b-ec6c-41e3-bc99-eb5387b4af26"/>
Wat gebeurt hiermee?

<meta type="dataset" value="ckcc"/>
En hiermee? Hebben we meerdere datasets?

<meta type="correspondence" value="desc004"/>
Classificatie binnen CKCC, neem ik aan

<meta type="id" value="1046"/>
<meta type="alt_id" value="AM1-208-046"/>
<meta type="alt_id" value="AT038"/>
<meta type="alt_id" value="EJB049"/>
worden idno's met type
Kennelijk heeft alleen Descartes zoveel verschillende types.
Het hoofd-id is een volgnummer binnen CKCC, neem ik aan

<meta type="date" value="1631-10/1631-11"/>
--> correspDesc/correspAction type=sent/date
en hier de betreffende waarde weergeven middels when, notBefore en notAfter.
Maar zie: http://www.loc.gov/standards/datetime/.
Misschien een when_custom dan?

<meta type="sender" value="descartes.rene.1596-1650"/>
--> correspDesc/correspAction type=sent/persName
en hier de betreffende waarde weergeven in key-attribuut.
Alternatief: sta person toe in correspAction

<meta type="senderloc" value="se.amsterdam.nld"/>
--> correspDesc/correspAction type=sent/placeName
en hier de betreffende waarde weergeven in key-attribuut.
Alternatief: sta place toe in correspAction.
Hier kan ook een resp-attribuut op staan.

<meta type="recipient" value="mersenne.marin.1588-1648"/>
<meta type="recipientloc" value="se.paris.fra" resp="#EJB"/>
Als bij sender

<meta type="status" value="OK"/>
Geeft dit een status van verwerking aan?
--> revisionDesc status = OK.
Moet leeg kunnen zijn.

En meta type=type??

3. Element formula
Opnemen in schema. Maar kennelijk gebeurt er niets mee? Althans binnen figure, daarbuiten wel. (voorbeelden desc004.208-046.xml)

4. Type attributen op div
Moeten we dat uniformeren? Wat is een type=artifact? (de echte brief)

5. xml:lang attributen
in elk geval onbekend coderen als unk
Rare combinatie van 2 en 3 letter codes?

6. <ref type="bible">Matth. XX. 16</ref>

7. en deze inline notes:
<div type="para">
<p><seg type="note">Adres:</seg> (A Mon)sieur Monsieur Grotius à Paris.</p>
<p><seg type="note">In dorso schreef Grotius:</seg> 6 Jan. 1629 N. Reigersberg.</p>
</div>

8. En wat te doen met de openers en de closers?

https://correspondence.huygens.knaw.nl/documents/c151aa14-306d-4993-aa1b-e175a469e566
Geeft heel rare foutboodschap.
"The tag <quote> is not implemented!
Wrapped on: "waer door dan het punt B lichtelijk gevonden wort, als men alleenlijk op 2 sijden des driehoeks DFG circelboogen beschrijft die de gevonden hoeken tot de sijden behoorende begrijpen. want de doorsnijding van sulke 2 boogen is het punt B."
This tag is not part of the Huygens ING TEI standard. Please visit Servicedesk.huygens.knaw.nl to request support of this tag."

About XML

2018-03-12T08:33:55Z

PBO:

==XML at Huygens ING==
Huygens ING uses XML to create many of its scholarly editions. XML is a plain text format that uses tags to delimit
and name structural elements within the text and to provide additional information about these elements.
[https://www.w3.org/XML/ XML] was defined by the [https://www.w3.org/ W3C]. For scholarly editing (and many other purposes)
[http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ Guidelines] for how to use XML were developed by the [http://www.tei-c.org/ Text Encoding Initiative] (TEI).
Huygens ING follows the TEI Guidelines whenever possible.

This wiki documents the choices that we make in using the TEI Guidelines, which occasionally describe multiple ways of
encoding a single phenomenon. Sometimes, the documents that we edit have special requirements that TEI does not yet support.
In the general pages here we describe the project independent choices that we made, in project-level pages we describe
project-specific additions and modifications. Often, these additions will be related to secundary, editorial material
rather than to original material, as the secundary material tends to be more project-specific than the primary material.

==XML basics==
We clearly cannot provide a full introduction into XML here. Online training is available at many locations,
e.g. at [https://www.w3schools.com/xml/ W3schools]. The TEI also maintains a page with information [http://www.tei-c.org/Support/Learn/ for learning TEI]. Or you can attend formal training, e.g. at the [http://www.dhoxss.net/ Oxford summer school in Digital Humanities].

Still, for those getting started at XML without patience for more formal training, a few XML basics:

* <starting tag>...</ending tag> (! attention to the position of / ), i.e.
<pre><address>Prins Willem-Alexanderhof 5</address></pre>

* <tag without content/>, i.e.
<pre><lb/> linebreak</pre>

* An element can have an attribute. An attribute has a value " ":
<pre>
<hi rend="super">st</hi>
hi is the element (highlight)
rend is the attribute
super is the value of the attribute.</pre>

* @xml:id is an attribute that provides a unique identifier for an element. To point to it use "#".
<pre>
E.g. a page surface may be defined as: <surface n="1r" xml:id="s1r">
Later in the document we refer to the xml:id "s1r" using the pointer "#s1r" on the facs attribute of the page element (pb):
<pb f="1r" n="1" facs="#s1r"/></pre>

* In an XML document, physical linebreaks ('enters'), even multiple ones, don't matter.
If you want a linebreak in a text you have to encode one using <lb/>.
<pre>
The line is too → The line is too short
short

The line <lb/> is too short → The line
is too short.

(The arrow (→) shows what an encoded text will usually look like when published)
</pre>

* XML documents are whitespace sensitive (whitespace includes spaces, tabs and newlines):
<pre>
normal<lb/>ly → normally
normal <lb/> ly → normal ly
normal<lb/>
ly → normal ly
</pre>

* Any comment (if you want to take a note on something for you or for other transcribers) is encoded in this way:
<pre>



</pre>

==XML namespace and schema==

===Namespaces===
Elements in XML documents can be placed in so-called [https://www.w3schools.com/xml/xml_namespaces.asp namespaces]. This is a way to be able to distinguish different XML vocabularies.
The default namespace for elements in Huygens ING projects is http://www.tei-c.org/ns/1.0 (the TEI namespace). For new elements, the namespace
that we will use is http://xmlschema.huygens.knaw.nl/ns/1.0. We refer to the namespace with the prefix 'hi', for exemple <hi:addressee>

(Existing projects still have there own namespaces, e.g. for Mondrian: http://mondrian.huygens.knaw.nl/. These project-specific namespaces will be phased out.

We define prefix and namespaces on the root level element of the XML document, as follows:

<pre><TEI xmlns="http://www.tei-c.org/ns/1.0" xmlns:hi="http://xmlschema.huygens.knaw.nl/ns/1.0"></pre>

===Schema===
In XML editing, a so-called schema is used to provide the editor with information about suitable elements,
attributes and attribute values in the context that he or she is editing. Schemas are indispensable for proper
editing as they help assure the XML files conform to the agreed encodings.

There are multiple schema languages. We use the [http://relaxng.org/ Relax NG] language (pronounce: 'relaxing') in its XML notation.

For each of our projects, we define a specific schema (or multiple specific schemas, if we have multiple types of documents).
The schema is defined by the project's XML consultant. It is generated from a sourcefile (a so-called ODD-file) maintained in the project's
repository. The generated schema is stored there as well.

The schemas will be placed on the web on e.g. (Mondrian example): http://xmlschema.huygens.knaw.nl/md.rng

===Chained schemas (in development)===

We will be working towards a situation where a single schema defines the Huygens TEI subset-with-additions. Project-specific schemas will be derived from the Huygens schema.

We start with the Mondrian (letter) schema, modified so as to use the correspDesc elements now available in TEI and to include the features needed for the ePistolarium.

==See also==
* [[XML Huygens]]

[[Category:XML Huygens]]

Epistolarium naar regulier TEI

2018-03-07T15:41:02Z

PBO:

Wat moet er aan ePistolarium XML gebeuren om het meer in lijn te brengen met TEI

1. Omzetting naar TEI P5: alle elementen naar TEI namespace

2. Omzetting van de meta-elementen

Een optie zou zijn: <xenodata>
Maar dan maak je je er een beetje van af

Nog onduidelijk:
<meta type="uuid" value="54ddae9b-ec6c-41e3-bc99-eb5387b4af26"/>
Wat gebeurt hiermee?

<meta type="dataset" value="ckcc"/>
En hiermee? Hebben we meerdere datasets?

<meta type="correspondence" value="desc004"/>
Classificatie binnen CKCC, neem ik aan

<meta type="id" value="1046"/>
<meta type="alt_id" value="AM1-208-046"/>
<meta type="alt_id" value="AT038"/>
<meta type="alt_id" value="EJB049"/>
worden idno's met type
Kennelijk heeft alleen Descartes zoveel verschillende types.
Het hoofd-id is een volgnummer binnen CKCC, neem ik aan

<meta type="date" value="1631-10/1631-11"/>
--> correspDesc/correspAction type=sent/date
en hier de betreffende waarde weergeven middels when, notBefore en notAfter.
Maar zie: http://www.loc.gov/standards/datetime/.
Misschien een when_custom dan?

<meta type="sender" value="descartes.rene.1596-1650"/>
--> correspDesc/correspAction type=sent/persName
en hier de betreffende waarde weergeven in key-attribuut.
Alternatief: sta person toe in correspAction

<meta type="senderloc" value="se.amsterdam.nld"/>
--> correspDesc/correspAction type=sent/placeName
en hier de betreffende waarde weergeven in key-attribuut.
Alternatief: sta place toe in correspAction

<meta type="recipient" value="mersenne.marin.1588-1648"/>
<meta type="recipientloc" value="se.paris.fra" resp="#EJB"/>
Als bij sender

<meta type="status" value="OK"/>
Geeft dit een status van verwerking aan?
--> revisionDesc status = OK

En meta type=type??

3. Element formula
Opnemen in schema. Maar kennelijk gebeurt er niets mee? Althans binnen figure, daarbuiten wel. (voorbeelden desc004.208-046.xml)

4. Type attributen op div
Moeten we dat uniformeren? Wat is een type=artifact? (de echte brief)

5. xml:lang attributen
in elk geval onbekend coderen als unk
Rare combinatie van 2 en 3 letter codes?

6. <ref type="bible">Matth. XX. 16</ref>

7. en deze inline notes:
<div type="para">
<p><seg type="note">Adres:</seg> (A Mon)sieur Monsieur Grotius à Paris.</p>
<p><seg type="note">In dorso schreef Grotius:</seg> 6 Jan. 1629 N. Reigersberg.</p>
</div>

https://correspondence.huygens.knaw.nl/documents/c151aa14-306d-4993-aa1b-e175a469e566
Geeft heel rare foutboodschap.
"The tag <quote> is not implemented!
Wrapped on: "waer door dan het punt B lichtelijk gevonden wort, als men alleenlijk op 2 sijden des driehoeks DFG circelboogen beschrijft die de gevonden hoeken tot de sijden behoorende begrijpen. want de doorsnijding van sulke 2 boogen is het punt B."
This tag is not part of the Huygens ING TEI standard. Please visit Servicedesk.huygens.knaw.nl to request support of this tag."

Epistolarium naar regulier TEI

2018-03-07T15:16:30Z

PBO:

Main Page

2018-03-07T14:32:55Z

PBO:

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]]
* [[Metadata (ePistolarium)]]
* [[Text structure (ePistolarium)]]
* [[Local annotations (ePistolarium)]]
* [[Transcription (ePistolarium)]]
* [[Rendering (ePistolarium)]]
* [[Retorical structure (ePistolarium)]]
* [[Lists (ePistolarium)]]
* [[Tables (ePistolarium)]]
* [[Poems (ePistolarium)]]
* [[Images (ePistolarium)]]
* [[Names (ePistolarium)]]
* [[Miscellaneous (ePistolarium)]]
* [[epistolarium naar regulier TEI]]

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

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

Epistolarium naar regulier TEI

2018-03-07T14:31:57Z

PBO: PBO moved page EPistolarium naar regulier TEI to Epistolarium naar regulier TEI without leaving a redirect: typefout

Epistolarium naar regulier TEI

2018-03-07T14:31:13Z

PBO:

Epistolarium naar regulier TEI

2018-03-07T14:25:18Z

PBO:

Epistolarium naar regulier TEI

2018-03-07T14:02:02Z

PBO: Created page with "Wat moet er aan ePistolarium XML gebeuren om het meer in lijn te brengen met TEI 1. Omzetting naar TEI P5: alle elementen naar TEI namespace 2. Omzetting van de meta-elementen"

Wat moet er aan ePistolarium XML gebeuren om het meer in lijn te brengen met TEI

1. Omzetting naar TEI P5: alle elementen naar TEI namespace

2. Omzetting van de meta-elementen

Main Page

2018-03-07T13:59:46Z

PBO:

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]]
* [[Metadata (ePistolarium)]]
* [[Text structure (ePistolarium)]]
* [[Local annotations (ePistolarium)]]
* [[Transcription (ePistolarium)]]
* [[Rendering (ePistolarium)]]
* [[Retorical structure (ePistolarium)]]
* [[Lists (ePistolarium)]]
* [[Tables (ePistolarium)]]
* [[Poems (ePistolarium)]]
* [[Images (ePistolarium)]]
* [[Names (ePistolarium)]]
* [[Miscellaneous (ePistolarium)]]
* [[ePistolarium naar regulier TEI]]

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

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

Default display of TEI elements

2017-10-18T13:35:09Z

PBO: Created page with "For each TEI element, we define a standard display. This page will dscribe the display for all elements that we use. ====<ab>==== http://www.tei-c.org/release/doc/tei-p5-doc..."

For each TEI element, we define a standard display. This page will dscribe the display for all elements that we use.

====<ab>====
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html

====<add>====
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-add.html

====<facsimile>====
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-facsimile.html

====<lb>====
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-lb.html

====<pb>====
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-pb.html

====<restore>====
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-restore.html

====<retrace>====
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-retrace.html

====<surface>====
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-surface.html

====<zone>====
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-zone.html

Main Page

2017-10-18T13:25:25Z

PBO:

Transcription

2017-06-01T14:31:14Z

PBO: /* Visual characteristics */

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:
* <p> 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>
<p>peux-tu venir me
<lb/>voir demain dans la matinée? … </p></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>
<p>Say hello to your mother.<p>
</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 goes into <choice>, as in the example:
<pre><choice><sic type="grammar">Happely</sic><corr>Happily</corr></choice></pre>

===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]]

Transcription

2017-06-01T14:30:51Z

PBO: /* Visual characteristics */

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:
* <p> 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>
<p>peux-tu venir me
<lb/>voir demain dans la matinée? … </p></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>
<p>Say hello to your mother.<p>
</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 goes into <choice>, as in the example:
<pre><choice><sic type="grammar">Happely</sic><corr>Happily</corr></choice></pre>

===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]]

Transcription: annotations (Mondrian)

2017-06-01T14:22:46Z

PBO: /* Explanatory notes */

==Explanatory notes==

For the preferred mechanism of placing notes, see [[Annotation and indexing]].

For Mondrian, the types of editorial notes that we distinguish are 'source', 'explanation', 'bibiliography'.

==Recurring annotation==

See [[Secondary files (Mondrian)#Recurring notes to persons and other subjects|Recurring notes to persons and other subjects]].

==<rs>==

Referencing string. Into <rs> are encoded names, with attributes, so they can be easily identified (i.e. You have different spellings of the same person's name and you want that they point to the same person), retrieved, indexed.
* '''@type''' kind of entity encoded (i.e. Person, exhibition, museum, journals, location, etc). The available types have been defined in the schema
* '''@ref''' to indicate an external url (RDKarchive url)
* '''@key''' a coded value that identifies the entity encoded (i.e. a number, a normalised spelling, etc.) We prefer to use @key rather than @ref.

It is possible to use multiple values in the key or ref attributes.

In the postal data (transcription of envelope) we don’t use <rs> to index the addressee, as his role is known from the letter metadata. Similarly, we don’t index persons saluted at the beginning or end of a letter, if these are addressees. (But we do tag ‘Jan’ in ‘Give my love to Jan’ if Jan is not an addressee).

When encoding a referring phrase as <rs>, we only tag the noun. This avoids potential problems with other words that need their own encoding.

Not:
<pre>
<rs>the woman who lives next door</rs>
</pre>
but
<pre>
the <rs>woman</rs> who lives next door
</pre>

In the case of multiple references to a person within a single paragraph, we encode each of them.

==References==

The element <ref> points to another resource and it is used for instance when a letter, a painting or another resource is mentioned in the text. @target provides the resource location (local or not).

<ref> is also used for pointing to the [[Secondary files (Mondrian)|bibliography]]. For example:
<pre>
... as mentioned in <ref target="biblio.xml#Andersen1861">Andersen 1861</ref>, we ...
</pre>
Here, 'Andersen1861' should be an entry in the bibliography.

==See also==
* [[Transcription: structure (Mondrian)]]
* [[Transcription: representation of the source (Mondrian)]]
* [[Transcription (Mondrian)]]

[[Category:XML Mondrian]]

Transcription: annotations (Mondrian)

2017-06-01T14:22:27Z

PBO:

==Explanatory notes==

For the preferred mechanism of placing notes, see [[Annotation and indexing]].
For Mondrian, the type of editorial notes that we distinguish are 'source', 'explanation', 'bibiliography'.

==Recurring annotation==

See [[Secondary files (Mondrian)#Recurring notes to persons and other subjects|Recurring notes to persons and other subjects]].

==<rs>==

Referencing string. Into <rs> are encoded names, with attributes, so they can be easily identified (i.e. You have different spellings of the same person's name and you want that they point to the same person), retrieved, indexed.
* '''@type''' kind of entity encoded (i.e. Person, exhibition, museum, journals, location, etc). The available types have been defined in the schema
* '''@ref''' to indicate an external url (RDKarchive url)
* '''@key''' a coded value that identifies the entity encoded (i.e. a number, a normalised spelling, etc.) We prefer to use @key rather than @ref.

It is possible to use multiple values in the key or ref attributes.

In the postal data (transcription of envelope) we don’t use <rs> to index the addressee, as his role is known from the letter metadata. Similarly, we don’t index persons saluted at the beginning or end of a letter, if these are addressees. (But we do tag ‘Jan’ in ‘Give my love to Jan’ if Jan is not an addressee).

When encoding a referring phrase as <rs>, we only tag the noun. This avoids potential problems with other words that need their own encoding.

Not:
<pre>
<rs>the woman who lives next door</rs>
</pre>
but
<pre>
the <rs>woman</rs> who lives next door
</pre>

In the case of multiple references to a person within a single paragraph, we encode each of them.

==References==

The element <ref> points to another resource and it is used for instance when a letter, a painting or another resource is mentioned in the text. @target provides the resource location (local or not).

<ref> is also used for pointing to the [[Secondary files (Mondrian)|bibliography]]. For example:
<pre>
... as mentioned in <ref target="biblio.xml#Andersen1861">Andersen 1861</ref>, we ...
</pre>
Here, 'Andersen1861' should be an entry in the bibliography.

==See also==
* [[Transcription: structure (Mondrian)]]
* [[Transcription: representation of the source (Mondrian)]]
* [[Transcription (Mondrian)]]

[[Category:XML Mondrian]]

Transcription: annotations (Mondrian)

2017-06-01T14:19:12Z

PBO:

==Explantory notes==

See [[Annotation and indexing]]

To create a note
* Put into the transcription or translation an <anchor/>, with @n (short keyword) and @type=“note”.
* Create a <note> into the <div type=“notes”> with the text of the note. It must have the same @n.
* Put all notes in a single language in the same div element.
* Order the notes by their referred location (technically irrelevant, but helpful to the human eye)

For example:
<pre>
<p>This is an exemple<anchor n=“nootje” type= “note”/> of how to create a note</p>

<div type=“notes” xml:lang=“en”>
<note n=“nootje”>This is the note</note>
… other notes in English…
</div>

<div type=“notes” xml:lang=“nl”>
<note n=“nootje”>Dit is de noot</note>
… other notes in Dutch …
</div>
</pre>

==Recurring annotation==

See [[Secondary files (Mondrian)#Recurring notes to persons and other subjects|Recurring notes to persons and other subjects]].

==<rs>==

Referencing string. Into <rs> are encoded names, with attributes, so they can be easily identified (i.e. You have different spellings of the same person's name and you want that they point to the same person), retrieved, indexed.
* '''@type''' kind of entity encoded (i.e. Person, exhibition, museum, journals, location, etc). The available types have been defined in the schema
* '''@ref''' to indicate an external url (RDKarchive url)
* '''@key''' a coded value that identifies the entity encoded (i.e. a number, a normalised spelling, etc.) We prefer to use @key rather than @ref.

It is possible to use multiple values in the key or ref attributes.

In the postal data (transcription of envelope) we don’t use <rs> to index the addressee, as his role is known from the letter metadata. Similarly, we don’t index persons saluted at the beginning or end of a letter, if these are addressees. (But we do tag ‘Jan’ in ‘Give my love to Jan’ if Jan is not an addressee).

When encoding a referring phrase as <rs>, we only tag the noun. This avoids potential problems with other words that need their own encoding.

Not:
<pre>
<rs>the woman who lives next door</rs>
</pre>
but
<pre>
the <rs>woman</rs> who lives next door
</pre>

In the case of multiple references to a person within a single paragraph, we encode each of them.

==References==

The element <ref> points to another resource and it is used for instance when a letter, a painting or another resource is mentioned in the text. @target provides the resource location (local or not).

<ref> is also used for pointing to the [[Secondary files (Mondrian)|bibliography]]. For example:
<pre>
... as mentioned in <ref target="biblio.xml#Andersen1861">Andersen 1861</ref>, we ...
</pre>
Here, 'Andersen1861' should be an entry in the bibliography.

==Theoretical writings==

See [[Theoretical writings (Mondrian)]]

==See also==
* [[Transcription: structure (Mondrian)]]
* [[Transcription: representation of the source (Mondrian)]]
* [[Transcription (Mondrian)]]

[[Category:XML Mondrian]]

Transcription: annotations (Mondrian)

2017-06-01T14:11:26Z

PBO: /* Explantory notes */

==Explantory notes==
To create a note
* Put into the transcription or translation an <anchor/>, with @n (short keyword) and @type=“note”.
* Create a <note> into the <div type=“notes”> with the text of the note. It must have the same @n.
* Put all notes in a single language in the same div element.
* Order the notes by their referred location (technically irrelevant, but helpful to the human eye)

For example:
<pre>
<p>This is an exemple<anchor n=“nootje” type= “note”/> of how to create a note</p>

<div type=“notes” xml:lang=“en”>
<note n=“nootje”>This is the note</note>
… other notes in English…
</div>

<div type=“notes” xml:lang=“nl”>
<note n=“nootje”>Dit is de noot</note>
… other notes in Dutch …
</div>
</pre>

==Recurring annotation==

See [[Secondary files (Mondrian)#Recurring notes to persons and other subjects|Recurring notes to persons and other subjects]].

==<rs>==

Referencing string. Into <rs> are encoded names, with attributes, so they can be easily identified (i.e. You have different spellings of the same person's name and you want that they point to the same person), retrieved, indexed.
* '''@type''' kind of entity encoded (i.e. Person, exhibition, museum, journals, location, etc). The available types have been defined in the schema
* '''@ref''' to indicate an external url (RDKarchive url)
* '''@key''' a coded value that identifies the entity encoded (i.e. a number, a normalised spelling, etc.) We prefer to use @key rather than @ref.

It is possible to use multiple values in the key or ref attributes.

In the postal data (transcription of envelope) we don’t use <rs> to index the addressee, as his role is known from the letter metadata. Similarly, we don’t index persons saluted at the beginning or end of a letter, if these are addressees. (But we do tag ‘Jan’ in ‘Give my love to Jan’ if Jan is not an addressee).

When encoding a referring phrase as <rs>, we only tag the noun. This avoids potential problems with other words that need their own encoding.

Not:
<pre>
<rs>the woman who lives next door</rs>
</pre>
but
<pre>
the <rs>woman</rs> who lives next door
</pre>

In the case of multiple references to a person within a single paragraph, we encode each of them.

==References==

The element <ref> points to another resource and it is used for instance when a letter, a painting or another resource is mentioned in the text. @target provides the resource location (local or not).

<ref> is also used for pointing to the [[Secondary files (Mondrian)|bibliography]]. For example:
<pre>
... as mentioned in <ref target="biblio.xml#Andersen1861">Andersen 1861</ref>, we ...
</pre>
Here, 'Andersen1861' should be an entry in the bibliography.

==Theoretical writings==

See [[Theoretical writings (Mondrian)]]

==See also==
* [[Transcription: structure (Mondrian)]]
* [[Transcription: representation of the source (Mondrian)]]
* [[Transcription (Mondrian)]]

[[Category:XML Mondrian]]

Transcription: annotations (Mondrian)

2017-06-01T14:10:09Z

PBO: /* Theoretical writings */

Theoretical writings (Mondrian)

2017-06-01T14:09:45Z

PBO: /* The notebooks */

We have insufficient knowledge of the properties of the theoretical writings to make final decisions about their encoding. Decisions documented here should be regarded as provisional.

==The notebooks==
Properties of the notebooks that we have to deal with are:
* Each notebook is transcribed in a separate XML file
* Texts may be written starting from the first page towards the last page or the other way around
* Texts may have been rotated with respect to the normal writing direction
* Texts may be discontinuous (interrupted by sketch)
* Sometimes sketches may be overwritten by texts
* multiple numberings of the pages in the notebooks exist; the editors will introduce a new numbering
* pages may be missing
* pages may be empty

To take this into account, we use the following system:
* The sequence of the surface elements in the facsimile element follows the physical sequence of the notebook, as best we can determine. We ignore missing pages, but include pages that are empty.
* The content of the notebook is transcribed in div elements. Page breaks are inserted in the writing order: when Mondrian wrote a tekst that starts at p. 100 and continues on page 99, we encode:
<pre>
<div>
<pb n="100"/>
... content ...
<pb n="99"/>
... content ...
</div>
</pre>
* the n attribute on the <pb> elements uses the nubering system chosen by the editors
* to discuss: whether and how to encode previous numberings (in order to support cross-references from existing literature)
* Sketches without commentary are contained (as a figure element) in their own div
* Divs can (of course) also contain texts and accompanying sketches
* When an earlier sketch is overwritten by a new text, we will have two divs where the same page number occurs. The situation will presumably be clarified in a note.
<pre>
<div>
<pb n="88"/>
<figure> ... </figure>
</div>
<div>
...
<pb n="88"/>
... transcribed text ...
</div>
</pre>
* As the physical sequence is determined by the sequence of the surfaces, and the logical sequence by the sequence of the transcription, no particular meaning is to be assigned to the sequence of the main divs in the transcription.
* Rotation of the writing surface is encoded on the zones within the surfaces:
{| class="wikitable"
|-
|No rotate-attribute or rotate=”0”
|Zone contains normal writing
|-
|rotate=”90”
|Zone contains writing sideways/downward
|-
|rotate=”-90”
|Zone contains writing sideways/upward
|-
|rotate=”180”
|Zone contains top-down writing
|}
* Stages of writing: we do not expect to use what TEI calls ‘revision campaigns’, see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PH-changes. (They can be referred to on div’s and other elements using the change-attribute. The change attributes points to change-elements collected in a listChange-element in the header (in profileDesc/creation). listChange-elements can nest, in order to describe groups of related changes.) Rather, we will probably clarify the probable dating of the various section in prose.

===Article in installments===

The problem is here that what is conceptually a single article was published as sections in multiple installments of the journal ''De Stijl''. A documentary TEI encoding would include elements that connect two installments but are unnecessary from the conceptual point of view. It might also want to represent e.g. note numbers as they appeared in the original installments, rather than in a unified and continuous numbering.

We agreed upon the following:
* the article as a whole will be transcribed in a single XML file
* the article is a single div with subdivs for the installments
* the facsimile element will contain surfaces for all of the pages from the different installments that contain text of the article; as usual page break elements in the transcription will refer to the relevant surfaces. The n attribute on the <pb> elements will give the original page number.
* the transcription will ignore metatext that is merely there to point readers to the following or previous installments
* notes by Mondrian will be in a separate div (type = notes) at the same hierarchic level of the article (notes encoded as <origNote>s). The notes div will contain page break elements to faciltate page by page display of the original version. Notes will have their original numbers in their n-attributes.

Transcription: annotations (Mondrian)

2017-06-01T14:09:32Z

PBO:

==Explantory notes==
To create a note
* Put into the transcription or translation an <anchor/>, with @n (short keyword) and @type=“note”.
* Create a <note> into the <div type=“notes”> with the text of the note. It must have the same @n.
* Put all notes in a single language in the same div element.
* Order the notes by their referred location (technically irrelevant, but helpful to the human eye)

For example:
<pre>
<p>This is an exemple<anchor n=“nootje” type= “note”/> of how to create a note</p>

<div type=“notes” xml:lang=“en”>
<note n=“nootje”>This is the note</note>
… other notes in English…
</div>

<div type=“notes” xml:lang=“nl”>
<note n=“nootje”>Dit is de noot</note>
… other notes in Dutch …
</div>
</pre>

==Recurring annotation==

See [[Secondary files (Mondrian)#Recurring notes to persons and other subjects|Recurring notes to persons and other subjects]].

==<rs>==

Referencing string. Into <rs> are encoded names, with attributes, so they can be easily identified (i.e. You have different spellings of the same person's name and you want that they point to the same person), retrieved, indexed.
* '''@type''' kind of entity encoded (i.e. Person, exhibition, museum, journals, location, etc). The available types have been defined in the schema
* '''@ref''' to indicate an external url (RDKarchive url)
* '''@key''' a coded value that identifies the entity encoded (i.e. a number, a normalised spelling, etc.) We prefer to use @key rather than @ref.

It is possible to use multiple values in the key or ref attributes.

In the postal data (transcription of envelope) we don’t use <rs> to index the addressee, as his role is known from the letter metadata. Similarly, we don’t index persons saluted at the beginning or end of a letter, if these are addressees. (But we do tag ‘Jan’ in ‘Give my love to Jan’ if Jan is not an addressee).

When encoding a referring phrase as <rs>, we only tag the noun. This avoids potential problems with other words that need their own encoding.

Not:
<pre>
<rs>the woman who lives next door</rs>
</pre>
but
<pre>
the <rs>woman</rs> who lives next door
</pre>

In the case of multiple references to a person within a single paragraph, we encode each of them.

==References==

The element <ref> points to another resource and it is used for instance when a letter, a painting or another resource is mentioned in the text. @target provides the resource location (local or not).

<ref> is also used for pointing to the [[Secondary files (Mondrian)|bibliography]]. For example:
<pre>
... as mentioned in <ref target="biblio.xml#Andersen1861">Andersen 1861</ref>, we ...
</pre>
Here, 'Andersen1861' should be an entry in the bibliography.

==Theoretical writings==

See [[Editing Theoretical writings (Mondrian)]]

==See also==
* [[Transcription: structure (Mondrian)]]
* [[Transcription: representation of the source (Mondrian)]]
* [[Transcription (Mondrian)]]

[[Category:XML Mondrian]]

Theoretical writings (Mondrian)

2017-06-01T14:06:26Z

PBO:

We have insufficient knowledge of the properties of the theoretical writings to make final decisions about their encoding. Decisions documented here should be regarded as provisional.

==The notebooks==
Properties of the notebooks that we have to deal with are:
* Texts may be written starting from the first page towards the last page or the other way around
* Texts may have been rotated with respect to the normal writing direction
* Texts may be discontinuous (interrupted by sketch)
* Sometimes sketches may be overwritten by texts
* multiple numberings of the pages in the notebooks exist; the editors will introduce a new numbering
* pages may be missing
* pages may be empty

To take this into account, we use the following system:
* The sequence of the surface elements in the facsimile element follows the physical sequence of the notebook, as best we can determine. We ignore missing pages, but include pages that are empty.
* The content of the notebook is transcribed in div elements. Page breaks are inserted in the writing order: when Mondrian wrote a tekst that starts at p. 100 and continues on page 99, we encode:
<pre>
<div>
<pb n="100"/>
... content ...
<pb n="99"/>
... content ...
</div>
</pre>
* the n attribute on the <pb> elements uses the nubering system chosen by the editors
* to discuss: whether and how to encode previous numberings (in order to support cross-references from existing literature)
* Sketches without commentary are contained (as a figure element) in their own div
* Divs can (of course) also contain texts and accompanying sketches
* When an earlier sketch is overwritten by a new text, we will have two divs where the same page number occurs. The situation will presumably be clarified in a note.
<pre>
<div>
<pb n="88"/>
<figure> ... </figure>
</div>
<div>
...
<pb n="88"/>
... transcribed text ...
</div>
</pre>
* As the physical sequence is determined by the sequence of the surfaces, and the logical sequence by the sequence of the transcription, no particular meaning is to be assigned to the sequence of the main divs in the transcription.
* Rotation of the writing surface is encoded on the zones within the surfaces:
{| class="wikitable"
|-
|No rotate-attribute or rotate=”0”
|Zone contains normal writing
|-
|rotate=”90”
|Zone contains writing sideways/downward
|-
|rotate=”-90”
|Zone contains writing sideways/upward
|-
|rotate=”180”
|Zone contains top-down writing
|}
* Stages of writing: we do not expect to use what TEI calls ‘revision campaigns’, see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PH-changes. (They can be referred to on div’s and other elements using the change-attribute. The change attributes points to change-elements collected in a listChange-element in the header (in profileDesc/creation). listChange-elements can nest, in order to describe groups of related changes.) Rather, we will probably clarify the probable dating of the various section in prose.

===Article in installments===

The problem is here that what is conceptually a single article was published as sections in multiple installments of the journal ''De Stijl''. A documentary TEI encoding would include elements that connect two installments but are unnecessary from the conceptual point of view. It might also want to represent e.g. note numbers as they appeared in the original installments, rather than in a unified and continuous numbering.

We agreed upon the following:
* the article as a whole will be transcribed in a single XML file
* the article is a single div with subdivs for the installments
* the facsimile element will contain surfaces for all of the pages from the different installments that contain text of the article; as usual page break elements in the transcription will refer to the relevant surfaces. The n attribute on the <pb> elements will give the original page number.
* the transcription will ignore metatext that is merely there to point readers to the following or previous installments
* notes by Mondrian will be in a separate div (type = notes) at the same hierarchic level of the article (notes encoded as <origNote>s). The notes div will contain page break elements to faciltate page by page display of the original version. Notes will have their original numbers in their n-attributes.

Notes

2017-06-01T13:52:18Z

PBO: /* Restjes */

===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><p xml:id="p2" corresp="BornInHollandTest.xml#p1 BornInHollandTest.xml#p3"></pre>

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

Theoretical writings (Mondrian)

2017-06-01T13:52:11Z

PBO:

We have insufficient knowledge of the properties of the theoretical writings to make final decisions about their encoding. Decisions documented here should be regarded as provisional.

==The notebooks==
Properties of the notebooks that we have to deal with are:
* Texts may be written starting from the first page towards the last page or the other way around
* Texts may have been rotated with respect to the normal writing direction
* Texts may be discontinuous (interrupted by sketch)
* Sometimes sketches may be overwritten by texts
* pages may be missing
* pages may be empty

To take this into account, we use the following system:
* The sequence of the surface elements in the facsimile element follows the physical sequence of the notebook, as best we can determine.
* The content of the notebook is transcribed in div elements. Page breaks are inserted in the writing order: when Mondrian wrote a tekst that starts at p. 100 and continues on page 99, we encode:
<pre>
<div>
<pb n="100"/>
... content ...
<pb n="99"/>
... content ...
</div>
</pre>
* Sketches without commentary are contained (as a figure element) in their own div
* Divs can (of course) also contain texts and accompanying sketches
* When an earlier sketch is overwritten by a new text, we will have two divs where the same page number occurs. The situation will presumably be clarified in a note.
<pre>
<div>
<pb n="88"/>
<figure> ... </figure>
</div>
<div>
...
<pb n="88"/>
... transcribed text ...
</div>
</pre>
* As the physical sequence is determined by the sequence of the surfaces, and the logical sequence by the sequence of the transcription, no particular meaning is to be assigned to the sequence of the main divs in the transcription.
* Rotation of the writing surface is encoded on the zones within the surfaces:
{| class="wikitable"
|-
|No rotate-attribute or rotate=”0”
|Zone contains normal writing
|-
|rotate=”90”
|Zone contains writing sideways/downward
|-
|rotate=”-90”
|Zone contains writing sideways/upward
|-
|rotate=”180”
|Zone contains top-down writing
|}
* Stages of writing: we do not expect to use what TEI calls ‘revision campaigns’, see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PH-changes. (They can be referred to on div’s and other elements using the change-attribute. The change attributes points to change-elements collected in a listChange-element in the header (in profileDesc/creation). listChange-elements can nest, in order to describe groups of related changes.) Rather, we will probably clarify the probable dating of the various section in prose.

===Article in installments===

The problem is here that what is conceptually a single article was published as sections in multiple installments of the journal ''De Stijl''. A documentary TEI encoding would include elements that connect two installments but are unnecessary from the conceptual point of view. It might also want to represent e.g. note numbers as they appeared in the original installments, rather than in a unified and continuous numbering.

We agreed upon the following:
* the article as a whole will be transcribed in a single XML file
* the article is a single div with subdivs for the installments
* the facsimile element will contain surfaces for all of the pages from the different installments that contain text of the article; as usual page break elements in the transcription will refer to the relevant surfaces. The n attribute on the <pb> elements will give the original page number.
* the transcription will ignore metatext that is merely there to point readers to the following or previous installments
* notes by Mondrian will be in a separate div (type = notes) at the same hierarchic level of the article (notes encoded as <origNote>s). The notes div will contain page break elements to faciltate page by page display of the original version. Notes will have their original numbers in their n-attributes.

Theoretical writings (Mondrian)

2017-06-01T13:51:32Z

PBO: /* Article in installments */

We have insufficient knowledge of the properties of the theoretical writings to make final decisions about their encoding. Decisions documented here should be regarded as provisional.

==The notebooks==
Properties of the notebooks that we have to deal with are:
* Texts may be written starting from the first page towards the last page or the other way around
* Texts may have been rotated with respect to the normal writing direction
* Texts may be discontinuous (interrupted by sketch)
* Sometimes sketches may be overwritten by texts

To take this into account, we use the following system:
* The sequence of the surface elements in the facsimile element follows the physical sequence of the notebook, as best we can determine.
* The content of the notebook is transcribed in div elements. Page breaks are inserted in the writing order: when Mondrian wrote a tekst that starts at p. 100 and continues on page 99, we encode:
<pre>
<div>
<pb n="100"/>
... content ...
<pb n="99"/>
... content ...
</div>
</pre>
* Sketches without commentary are contained (as a figure element) in their own div
* Divs can (of course) also contain texts and accompanying sketches
* When an earlier sketch is overwritten by a new text, we will have two divs where the same page number occurs. The situation will presumably be clarified in a note.
<pre>
<div>
<pb n="88"/>
<figure> ... </figure>
</div>
<div>
...
<pb n="88"/>
... transcribed text ...
</div>
</pre>
* As the physical sequence is determined by the sequence of the surfaces, and the logical sequence by the sequence of the transcription, no particular meaning is to be assigned to the sequence of the main divs in the transcription.
* Rotation of the writing surface is encoded on the zones within the surfaces:
{| class="wikitable"
|-
|No rotate-attribute or rotate=”0”
|Zone contains normal writing
|-
|rotate=”90”
|Zone contains writing sideways/downward
|-
|rotate=”-90”
|Zone contains writing sideways/upward
|-
|rotate=”180”
|Zone contains top-down writing
|}
* Stages of writing: we do not expect to use what TEI calls ‘revision campaigns’, see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PH-changes. (They can be referred to on div’s and other elements using the change-attribute. The change attributes points to change-elements collected in a listChange-element in the header (in profileDesc/creation). listChange-elements can nest, in order to describe groups of related changes.) Rather, we will probably clarify the probable dating of the various section in prose.

===Article in installments===

The problem is here that what is conceptually a single article was published as sections in multiple installments of the journal ''De Stijl''. A documentary TEI encoding would include elements that connect two installments but are unnecessary from the conceptual point of view. It might also want to represent e.g. note numbers as they appeared in the original installments, rather than in a unified and continuous numbering.

We agreed upon the following:
* the article as a whole will be transcribed in a single XML file
* the article is a single div with subdivs for the installments
* the facsimile element will contain surfaces for all of the pages from the different installments that contain text of the article; as usual page break elements in the transcription will refer to the relevant surfaces. The n attribute on the <pb> elements will give the original page number.
* the transcription will ignore metatext that is merely there to point readers to the following or previous installments
* notes by Mondrian will be in a separate div (type = notes) at the same hierarchic level of the article (notes encoded as <origNote>s). The notes div will contain page break elements to faciltate page by page display of the original version. Notes will have their original numbers in their n-attributes.

Theoretical writings (Mondrian)

2017-06-01T13:35:08Z

PBO:

We have insufficient knowledge of the properties of the theoretical writings to make final decisions about their encoding. Decisions documented here should be regarded as provisional.

==The notebooks==
Properties of the notebooks that we have to deal with are:
* Texts may be written starting from the first page towards the last page or the other way around
* Texts may have been rotated with respect to the normal writing direction
* Texts may be discontinuous (interrupted by sketch)
* Sometimes sketches may be overwritten by texts

To take this into account, we use the following system:
* The sequence of the surface elements in the facsimile element follows the physical sequence of the notebook, as best we can determine.
* The content of the notebook is transcribed in div elements. Page breaks are inserted in the writing order: when Mondrian wrote a tekst that starts at p. 100 and continues on page 99, we encode:
<pre>
<div>
<pb n="100"/>
... content ...
<pb n="99"/>
... content ...
</div>
</pre>
* Sketches without commentary are contained (as a figure element) in their own div
* Divs can (of course) also contain texts and accompanying sketches
* When an earlier sketch is overwritten by a new text, we will have two divs where the same page number occurs. The situation will presumably be clarified in a note.
<pre>
<div>
<pb n="88"/>
<figure> ... </figure>
</div>
<div>
...
<pb n="88"/>
... transcribed text ...
</div>
</pre>
* As the physical sequence is determined by the sequence of the surfaces, and the logical sequence by the sequence of the transcription, no particular meaning is to be assigned to the sequence of the main divs in the transcription.
* Rotation of the writing surface is encoded on the zones within the surfaces:
{| class="wikitable"
|-
|No rotate-attribute or rotate=”0”
|Zone contains normal writing
|-
|rotate=”90”
|Zone contains writing sideways/downward
|-
|rotate=”-90”
|Zone contains writing sideways/upward
|-
|rotate=”180”
|Zone contains top-down writing
|}
* Stages of writing: we do not expect to use what TEI calls ‘revision campaigns’, see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PH-changes. (They can be referred to on div’s and other elements using the change-attribute. The change attributes points to change-elements collected in a listChange-element in the header (in profileDesc/creation). listChange-elements can nest, in order to describe groups of related changes.) Rather, we will probably clarify the probable dating of the various section in prose.

===Article in installments===

The problem is here that what is conceptually a single article was published as sections in multiple installments of the journal ''De Stijl''. A documentary TEI encoding would include elements that connect two installments but are unnecessary from the conceptual point of view. It might also want to represent e.g. note numbers as they appeared in the original installments, rather than in a unified and continuous numbering.

We agreed upon the following:
* the article as a whole will be transcribed in a single XML file
* the article is a single div with subdivs for the installments
* the facsimile element will contain surfaces for all of the pages from different installments that contain text of the article; as usual page break elements will refer to the
* the transcription will ignore metatext that is merely there to point readers to the following or previous installments
* notes by Mondrian will be in a separate div (type = notes) at the same hierarchic level of the article. The notes div will contain page break elements
*

Theoretical writings (Mondrian)

2017-05-02T14:51:45Z

PBO:

We have insufficient knowledge of the properties of the theoretical writings to make final decisions about their encoding. Decisions documented here should be regarded as provisional.

==The notebooks==
Properties of the notebooks that we have to deal with are:
* Texts may be written starting from the first page towards the last page or the other way around
* Texts may have been rotated with respect to the normal writing direction
* Texts may be discontinuous (interrupted by sketch)
* Sometimes sketches may be overwritten by texts

To take this into account, we use the following system:
* The sequence of the surface elements in the facsimile element follows the physical sequence of the notebook, as best we can determine.
* The content of the notebook is transcribed in div elements. Page breaks are inserted in the writing order: when Mondrian wrote a tekst that starts at p. 100 and continues on page 99, we encode:
<pre>
<div>
<pb n="100"/>
... content ...
<pb n="99"/>
... content ...
</div>
</pre>
* Sketches without commentary are contained (as a figure element) in their own div
* Divs can (of course) also contain texts and accompanying sketches
* When an earlier sketch is overwritten by a new text, we will have two dives where the same page number occurs. The situation will presumably be clarified in a note.
<pre>
<div>
<pb n="88"/>
<figure> ... </figure>
</div>
<div>
...
<pb n="88"/>
... transcribed text ...
</div>
</pre>
* As the physical sequence is determined by the sequence of the surfaces, and the logical sequence by the sequence of the transcription, no particular meaning is to be assigned to the sequence of the divs in the transcription.

===Article in installments===

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><p xml:id="p2" corresp="BornInHollandTest.xml#p1 BornInHollandTest.xml#p3"></pre>

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

Stages of writing: the TEI also uses the term ‘revision campaigns’, see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PH-changes. They are identified on div’s and other elements using the change-attribute. The change attributes points to change-elements collected in a listChange-element in the header (in profileDesc/creation). listChange-elements can nest, in order to describe groups of related changes.
To be decided: how do the values in the change attribute relate to the values in the seq-attribute on add’s and dels?

Rotation of the writing surface is encoded on the zones within the surfaces:

{| class="wikitable"
|-
|No rotate-attribute or rotate=”0”
|Zone contains normal writing
|-
|rotate=”90”
|Zone contains writing sideways/downward
|-
|rotate=”-90”
|Zone contains writing sideways/upward
|-
|rotate=”180”
|Zone contains top-down writing
|}

Annotation and indexing

2017-04-26T15:04:06Z

PBO:

In a digital edition, annotation can be provided in several ways and at several levels. The most simple form of annotation are
notes anchored to a location in the text. It is also possible to hyperlink certain stretches of text (e.g. those that refer to
persons or other named entitites to external information, created by the project or elsewhere. Annotation can also be provided
at a higher level, for instance about a chapter or a letter in a collection. Most projects will also have some level of annotation
at the level of the entire work or collection being edited, for instance about its publication history or its literary context.

Often, it will be desirable to create annotations of multiple types, e.g. in order to filter the display of annotations by type.
This can occur at the levels of annotation.

Indexing is related to annotation in that it can be used to link stretches of text to an index term, often provided with explanations.

==Local annotations==
Local annotations are annotations anchored to a location in the test. We assume here that a point in the text is sufficient and that
there is no need to mark a stretch of text as the target of annotation (but see Indexing, below).

In the TEI it is possible to create 'embedded' notes, where the note element is contained within the transcription
at the place where it applies. The disadvantage of this approach is that is diminishes the legibility of the text for the encoder.
Therefore, at Huygens ING the preffered method for local annotation is to create an anchor in the text that identifies
the place where a note should be inserted. The actual notes are stored in a separate <div> in the same file.

In order to create an annotation, we place an empty <anchor/> element within the transcription. The anchor should contain
a @n attribute with a short keyword and a @type="note". A corresponding <note> element
should be inserted in the <div type="notes"> element elsewhere in the document. The @n must have the same value in both elements.
The notes div can contain subdivisions by language and further subdivisions based on the type attribute of the note.
Within each subdivision, the notes should be arranged based on their location in the text. For example:

<pre>
<p>This is an example<anchor n="mynote" type= "note"/> of how to create a note</p>

<div type="notes">
<div xml:lang="en">
<note n="mynote">This is the note</note>
… other notes in English…
</div>

<div xml:lang="nl">
<note n="mynote">Dit is de noot</note>
… other notes in Dutch …
</div>
</div>
</pre>

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

[[Category:XML Huygens]]

Annotation and indexing

2017-04-26T15:03:02Z

PBO:

In a digital edition, annotation can be provided in several ways and at several levels. The most simple form of annotation are
notes anchored to a location in the text. It is also possible to hyperlink certain stretches of text (e.g. those that refer to
persons or other named entitites to external information, created by the project or elsewhere. Annotation can also be provided
at a higher level, for instance about a chapter or a letter in a collection. Most projects will also have some level of annotation
at the level of the entire work or collection being edited, for instance about its publication history or its literary context.

Often, it will be desirable to create annotations of multiple types, e.g. in order to filter the display of annotations by type.
This can occur at the levels of annotation.

Indexing is related to annotation in that it can be used to link stretches of text to an index term, often provided with explanations.

==Local annotations==
Local annotations are annotations anchored to a location in the test. We assume here that a point in the text is sufficient and that
there is no need to mark a stretch of text as the target of annotation (but see Indexing, below).

In the TEI it is possible to create 'embedded' notes, where the note element is contained within the transcription
at the place where it applies. The disadvantage of this approach is that is diminishes the legibility of the text for the encoder.
Therefore, at Huygens ING the preffered method for local annotation is to create an anchor in the text that identifies
the place where a note should be inserted. The actual notes are stored in a separate <div> in the same file.

In order to create an annotation, we place an empty <anchor/> element within the transcription. The anchor should contain
a @n attribute with a short keyword and a @type="note". A corresponding <note> element
should be inserted in the <div type="notes"> element elsewhere in the document. The @n must have the same value in both elements.
The notes div can contain subdivisions by language and further subdivisions based on the type attribute of the note.
Within each subdivision, the notes should be arranged based on their location in the text. For example:

<pre>
<p>This is an example<anchor n="nootje" type= "note"/> of how to create a note</p>

<div type="notes">
<div xml:lang="en">
<note n="mynote">This is the note</note>
… other notes in English…
</div>

<div xml:lang="nl">
<note n="mynote">Dit is de noot</note>
… other notes in Dutch …
</div>
</div>
</pre>

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

[[Category:XML Huygens]]

Annotation and indexing

2017-04-26T15:00:18Z

PBO:

In a digital edition, annotation can be provided in several ways and at several levels. The most simple form of annotation are
notes anchored to a location in the text. It is also possible to hyperlink certain stretches of text (e.g. those that refer to
persons or other named entitites to external information, created by the project or elsewhere. Annotation can also be provided
at a higher level, for instance about a chapter or a letter in a collection. Most projects will also have some level of annotation
at the level of the entire work or collection being edited, for instance about its publication history or its literary context.

Often, it will be desirable to create annotations of multiple types, e.g. in order to filter the display of annotations by type.
This can occur at the levels of annotation.

Indexing is related to annotation in that it can be used to link stretches of text to an index term, often provided with explanations.

==Local annotations==
Local annotations are annotations anchored to a location in the test. We assume here that a point in the text is sufficient and that
there is no need to mark a stretch of text as the target of annotation (but see Indexing, below).

In the TEI it is possible to create 'embedded' notes, where the note element is contained within the transcription
at the place where it applies. The disadvantage of this approach is that is diminishes the legibility of the text for the encoder.
Therefore, at Huygens ING the preffered method for local annotation is to create an anchor in the text that identifies
the place where a note should be inserted. The actual notes are stored in a separate <div> in the same file.

In order to create an annotation, we place an empty <anchor/> element within the transcription. The anchor should contain
a @n attribute with a short keyword and a @type="note". A corresponding <note> element
should be inserted in the <div type="notes"> element elsewhere in the document. The @n must have the same value in both elements.
The notes div can contain subdivisions by language and further subdivisions based on the type attribute of the note.
Within each subdivision, the notes should be arranged based on their location in the text. For example:

<pre>
<p>This is an example<anchor n="nootje" type= "note"/> of how to create a note</p>

<div type=“notes” xml:lang=“en”>
<note n=“nootje”>This is the note</note>
… other notes in English…
</div>

<div type=“notes” xml:lang=“nl”>
<note n=“nootje”>Dit is de noot</note>
… other notes in Dutch …
</div>
</pre>

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

[[Category:XML Huygens]]

Annotation and indexing

2017-04-26T14:59:28Z

PBO:

In a digital edition, annotation can be provided in several ways and at several levels. The most simple form of annotation are
notes anchored to a location in the text. It is also possible to hyperlink certain stretches of text (e.g. those that refer to
persons or other named entitites to external information, created by the project or elsewhere. Annotation can also be provided
at a higher level, for instance about a chapter or a letter in a collection. Most projects will also have some level of annotation
at the level of the entire work or collection being edited, for instance about its publication history or its literary context.

Often, it will be desirable to create annotations of multiple types, e.g. in order to filter the display of annotations by type.
This can occur at the levels of annotation.

Indexing is related to annotation in that it can be used to link stretches of text to an index term, often provided with explanations.

==Local annotations==
Local annotations are annotations anchored to a location in the test. We assume here that a point in the text is sufficient and that
there is no need to mark a stretch of text as the target of annotation (but see Indexing, below).

In the TEI it is possible to create 'embedded' notes, where the note element is contained within the transcription
at the place where it applies. The disadvantage of this approach is that is diminishes the legibility of the text for the encoder.
Therefore, at Huygens ING the preffered method for local annotation is to create an anchor in the text that identifies
the place where a note should be inserted. The actual notes are stored in a separate <div> in the same file.

In order to create an annotation, we place an empty <anchor/> element within the transcription. The anchor should contain
a @n attribute with a short keyword and a @type="note". A corresponding <note> element
should be inserted inthe <div type="notes"> element elsewhere in the document. The @n must have the same value in both elements.
The notes div can contain subdivisions by language and further subdivisions based on the type attribute of the note.
Within each subdivision, the notes should be arranged based on their location in the text. For example:

<pre>
<p>This is an example<anchor n="nootje" type= "note"/> of how to create a note</p>

<div type=“notes” xml:lang=“en”>
<note n=“nootje”>This is the note</note>
… other notes in English…
</div>

<div type=“notes” xml:lang=“nl”>
<note n=“nootje”>Dit is de noot</note>
… other notes in Dutch …
</div>
</pre>

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

[[Category:XML Huygens]]