TEIWiki - User contributions [en]

Prosopography

2011-03-09T08:19:52Z

Tfinney: /* Relations */

Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERS 13.3 Prosopography] of the TEI Guidelines discusses how the elements and attributes from the TEI P5 [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#index-body.1_div.13_div.4 namesdates module] can be used to mark up prosopographical data.

This wiki page attempts to summarise a number of issues in recording prosopographical data, and aims to provide a (sometimes personal) starting point for discussion and sharing of encoding experiences and insights. Rather than a documentation of best practice, it focuses on possible approaches for encoding some prosopographical phenomena, and tries to find sensible ones.

==Dating==
===Unknown dates vs. lacking dates===
Birth and death dates can only be recorded if they are known. Yet, omitting the <death> element from a <person> description may lead to ambiguity. Consider following example:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth when="1935">1935</birth>
</person>
</pre>

Does this indicate:
* that the person is still living?
* that the person has died but the date of death is unknown?
(Obviously, this ambiguity does not hold for birth dates, as can be assumed that all existing persons must have been born.)

In order to resolve this ambiguity, it could be assumed that a description in a <person> element withouth <death> element would relate to a living person. When the person is known to have died, a <death> statement would then be required. If only the birth date is known, this can be used as a lower bound for the possible date of death:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth when="1935">1935</birth>
<death notBefore="1935" precision="low">?</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rahtz on TEI-L])

Note how the @notBefore attribute is used to specify this lower bound, in combination with the @precision attribute to indicate the precision of this statement. One could equally infer an upper bound by assuming that nobody lives longer than 120 years, and document this with the @notAfter attribute on the <death> element. The status of this conjecture and its certainty could be indicated by @evidence and @cert attributes, respectively:
<pre>
<person>
<persName>Corey Adams</persName>
<birth when="1835">1835</birth>
<death notAfter="1955" precision="low" cert="high" evidence="conjecture">?</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2524 Syd Bauman on TEI-L])

The lacking data could be represented by e.g. a question mark as text content of the <death> element.

When no birth nor death date is known for a dead person, no precise dates (or approximations) can be given in attributes. Still, it could make sense to have <birth> and <death> elements, whose text contents indicate this knowledge gap:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth>?</birth>
<death>?</death>
</person>
</pre>

===Circa Dates===
This issue has been raised on the [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind0903&L=TEI-L&D=0&P=18661 TEI-L mailing list]. Currently, TEI P5 only offers implicit means to indicate that a date is only an approximation:

<pre>
<person>
<persName>Aischylos</persName>
<birth precision="low" when="-0525">ca. 525 b.C.</birth>
<death precision="low" when="-0456">ca. 456 b.C.</death>
</person>
</pre>

...with the @precision attribute indicating the low precision of these statements.
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=3128 Gabriel Bodard on TEI-L])

Yet, depending on the requirements of the encoding, an ideal representation of circa dates could get quite complex, and touches on broader issues concerning an accurate representation of uncertainty. See following resources:
* [http://www.tfinney.net/Uncertainty/ Tim Finney: 'Uncertainty in text, markup and beyond']
* [http://sourceforge.net/tracker/?func=detail&aid=3060909&group_id=106328&atid=644065 feature request by Tim Finney]

===Alternative Dates===
Sometimes, multiple possibilities exist for determining the date of birth or death of a person. When both dates are successive, one could encode this as a date range, with @notBefore and @notAfter, as in this case with two possible birth dates:
<pre>
<person>
<persName>Duncan, Isadora</persName>
<birth notBefore="1877" notAfter="1878">[1877 or] 1878</birth>
<death when="1927">1927</death>
</person>
</pre>

(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rahtz on TEI-L])

When, on the other hand, both dates are non-successive, multiple <birth> or <death> dates can be provided, with an @exclude attribute indicating their exclusive alternation:
<pre>
<person>
<persName>Vanhautte, Delphien</persName>
<birth when="1869-09-02">
<placeName>Ardooie</placeName>
<date>02.09.1869</date>
</birth>
<death when="1944-02-03" xml:id="d19440203" exclude="#d19441203">
<placeName>Edewalle (Handzame)</placeName>
<date>03.02/12(?).1944</date>
</death>
<death when="1944-12-03" xml:id="d19441203" exclude="#d19440203">
<placeName>Edewalle (Handzame)</placeName>
<date>03.02/12(?).1944</date>
</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2524 Syd Bauman on TEI-L])

===Only a period is known===
Sometimes no exact dates of birth or death are known, while the lifetime can be approximated in a period. As has been remarked by [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rathtz on TEI-L], the period can be approximated by @notBefore and @notAfter attributes on <birth> and <death> elements, while the ambiguity can be recorded in a <floruit> element:
<pre>
<person>
<persName>Regina van Alisa</persName>
<birth notBefore="0201"/>
<death notAfter="0300"/>
<floruit>3rd cent</floruit>
</person>
</pre>

In his response, [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=3128 Gabriel Bodard on TEI-L] makes a refinement. If the period mentioned does not literally apply to birth and death dates, and in the previous example rather conveys that this person lived the better part of her life in the 3rd century (while she might have been born or died before the start or after the end of that century), the most accurate way of representing this would imply an inversion of the @notBefore and @notAfter attributes on respectively <birth> and <death>:
<pre>
<person>
<persName>Regina van Alisa</persName>
<birth notAfter="0300"/>
<death notBefore="0201"/>
<floruit>3rd cent</floruit>
</person>
</pre>

==Naming==
===Pseudonyms===
Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERSEps 13.3.2.2 Personal States] of the TEI Guidelines describes how multiple <persName>s are allowed for a person, possibly categorised with a @type attribute. For pseudonyms, the value 'pseudo' can be used. Hence, the guitarist commonly known as Slash could be described as follows:
<pre>
<person>
<persName>
<surname>Hudson</surname>
<forename>Saul</forename>
</persName>
<persName type="pseudo">Slash</persName>
</person>
</pre>

This may raise an issue regarding the 'canonicity' of either name. In this case, a bibliographic entry would probably use the pseudonym 'Slash', whereas for less famous people the actual name may be preferred. This 'preference' could be recorded implicitly by the order of the <persNames>, or with the @sort attribute:
<pre>
<person>
<persName sort="2">
<surname>Hudson</surname>
<forename>Saul</forename>
</persName>
<persName type="pseudo" sort="1">Slash</persName>
</person>
</pre>

This could then mean that the pseudonym is the 'canonical' name for this person.

Another question is whether the actual name should then be typed as @type='real'?

===Alternative Names===
A related issue arises when people are commonly known by another name than their real name. For example, Joe English, a Belgian painter, is actually called Joseph English. I wonder whether a regularisation with <reg> would be the most suitable solution to encode this?

<pre>
<person>
<persName>
<reg>English, Joe A.M.</reg>
<surname>English</surname>
<forename>Joseph A.M.</forename>
</persName>
</person>
</pre>

==Mixing Prose and Structure==
The TEI P5 Guidelines define the contents <person> as either a collection of highly structured biographical 'fields' (using dedicated elements like <trait>, <occupation>, ...), or a collection of loose prose paragraphs (). Especially when transforming existing biographical records to TEI P5, this exclusive alternation can be unsatisfactory:
* splitting up all biographical prose into biographical fields may be too demanding
* OTOH, choosing to retain the description in prose paragraphs also prohibits the specification of basic biographical data in specific fields (<birth>, <death>, <persName>) inside <person>

One (tentative) solution could be to extract record-like information into biographical fields, while grouping the prose descriptions as paragraphs into a <note> element:

<pre>
<person xml:id="FJ">
<persName>
<reg>Fabricius, Jan</reg>
<surname>Fabricius</surname>
<forename>Jan</forename>
</persName>
<birth when="1871-09-30">
<placeName>Assen</placeName>
<date>30.09.1871</date>
</birth>
<death when="1964-11-23">
<placeName>Wimborne, Dorset</placeName>
<date>23.11.1964</date>
</death>
<note type="bio">
Journalist, Nederlands toneelschrijver.
Vader van de schrijver Johan Fabricius. Hoofdredacteur van verschillende bladen, zowel in Nederlands-Indië als in Nederland.
In 1938 vestigde hij zich in Engeland. Hoewel Fabricius op latere leeftijd ook enkele romans en drie delen memoires heeft
gepubliceerd, ligt zijn betekenis in zijn toneelwerk. Zijn technische vaardigheid en meesterschap in het schrijven van een
dialoog, maken zijn stukken goed speelbaar. Kind van een tijd die het realisme beoefende (Heijermans, Hauptmann), kon hij
toch niet de romantiek geheel laten varen. Het handelingsverloop is vaak gewild; er wordt dan bewust aangestuurd op een
aandoenlijke werking, zodat sommige van zijn stukken het predikaat 'melodramatisch' verdienen. Gedreven door een sterk gevoel
voor rechtvaardigheid zocht hij zijn gegevens in de problematiek van milieus die hem vertrouwd waren: het boerenland van
Groningen en Drente, de planterswereld van Indië. Fabricius' werk werd in Nederland en ook in het buitenland met succes opgevoerd.
Tot zijn bekendste werken behoren <title>Eenzaam</title> (1907) en <title>Dolle Hans</title> (1916). Sommige stukken zijn vertaald
in het Frans, Duits, Engels, Noors, Deens, Fries en Gronings.

</note>
<note type="ref">

<ptr ref="http://www.dbnl.org/auteurs/borkv/Fabr004.htm"/>

</note>
</person>
</pre>

This allows to group other types of information into other notes as well, distinguished by means of appropriate values for their @type attributes.

==Traits, States, and Events==
The Guidelines use traits, states, and events as basic categories for prosopography. Traits differ from states in being generally immutable. It may be that the distinction between states and traits is unnecessary. Almost every member of model.persTraitLike (age faith langKnowledge nationality s*x socecStatus trait) can change. Dropping "trait" leaves a simple yet expressive model where entities are described by states and state-transitions (i.e. events).

==Relations==
At the moment, relations are defined by attributes such as name, active and passive:

<pre><relation name="parent" active="#p1 #p2" passive="#p3 #p4"/></pre>

An alternative would be to use RDF-like subject, predicate, object triples:

<pre><relation subject="#p1" predicate="child-of" object="#p2"/></pre>

If the relation element could be placed inside the element which describes the subject (e.g. a person element) then the subject attribute would be implicit.

[[Category:Markup]]

Prosopography

2011-03-09T08:17:09Z

Tfinney: /* Relations */

Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERS 13.3 Prosopography] of the TEI Guidelines discusses how the elements and attributes from the TEI P5 [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#index-body.1_div.13_div.4 namesdates module] can be used to mark up prosopographical data.

This wiki page attempts to summarise a number of issues in recording prosopographical data, and aims to provide a (sometimes personal) starting point for discussion and sharing of encoding experiences and insights. Rather than a documentation of best practice, it focuses on possible approaches for encoding some prosopographical phenomena, and tries to find sensible ones.

==Dating==
===Unknown dates vs. lacking dates===
Birth and death dates can only be recorded if they are known. Yet, omitting the <death> element from a <person> description may lead to ambiguity. Consider following example:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth when="1935">1935</birth>
</person>
</pre>

Does this indicate:
* that the person is still living?
* that the person has died but the date of death is unknown?
(Obviously, this ambiguity does not hold for birth dates, as can be assumed that all existing persons must have been born.)

In order to resolve this ambiguity, it could be assumed that a description in a <person> element withouth <death> element would relate to a living person. When the person is known to have died, a <death> statement would then be required. If only the birth date is known, this can be used as a lower bound for the possible date of death:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth when="1935">1935</birth>
<death notBefore="1935" precision="low">?</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rahtz on TEI-L])

Note how the @notBefore attribute is used to specify this lower bound, in combination with the @precision attribute to indicate the precision of this statement. One could equally infer an upper bound by assuming that nobody lives longer than 120 years, and document this with the @notAfter attribute on the <death> element. The status of this conjecture and its certainty could be indicated by @evidence and @cert attributes, respectively:
<pre>
<person>
<persName>Corey Adams</persName>
<birth when="1835">1835</birth>
<death notAfter="1955" precision="low" cert="high" evidence="conjecture">?</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2524 Syd Bauman on TEI-L])

The lacking data could be represented by e.g. a question mark as text content of the <death> element.

When no birth nor death date is known for a dead person, no precise dates (or approximations) can be given in attributes. Still, it could make sense to have <birth> and <death> elements, whose text contents indicate this knowledge gap:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth>?</birth>
<death>?</death>
</person>
</pre>

===Circa Dates===
This issue has been raised on the [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind0903&L=TEI-L&D=0&P=18661 TEI-L mailing list]. Currently, TEI P5 only offers implicit means to indicate that a date is only an approximation:

<pre>
<person>
<persName>Aischylos</persName>
<birth precision="low" when="-0525">ca. 525 b.C.</birth>
<death precision="low" when="-0456">ca. 456 b.C.</death>
</person>
</pre>

...with the @precision attribute indicating the low precision of these statements.
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=3128 Gabriel Bodard on TEI-L])

Yet, depending on the requirements of the encoding, an ideal representation of circa dates could get quite complex, and touches on broader issues concerning an accurate representation of uncertainty. See following resources:
* [http://www.tfinney.net/Uncertainty/ Tim Finney: 'Uncertainty in text, markup and beyond']
* [http://sourceforge.net/tracker/?func=detail&aid=3060909&group_id=106328&atid=644065 feature request by Tim Finney]

===Alternative Dates===
Sometimes, multiple possibilities exist for determining the date of birth or death of a person. When both dates are successive, one could encode this as a date range, with @notBefore and @notAfter, as in this case with two possible birth dates:
<pre>
<person>
<persName>Duncan, Isadora</persName>
<birth notBefore="1877" notAfter="1878">[1877 or] 1878</birth>
<death when="1927">1927</death>
</person>
</pre>

(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rahtz on TEI-L])

When, on the other hand, both dates are non-successive, multiple <birth> or <death> dates can be provided, with an @exclude attribute indicating their exclusive alternation:
<pre>
<person>
<persName>Vanhautte, Delphien</persName>
<birth when="1869-09-02">
<placeName>Ardooie</placeName>
<date>02.09.1869</date>
</birth>
<death when="1944-02-03" xml:id="d19440203" exclude="#d19441203">
<placeName>Edewalle (Handzame)</placeName>
<date>03.02/12(?).1944</date>
</death>
<death when="1944-12-03" xml:id="d19441203" exclude="#d19440203">
<placeName>Edewalle (Handzame)</placeName>
<date>03.02/12(?).1944</date>
</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2524 Syd Bauman on TEI-L])

===Only a period is known===
Sometimes no exact dates of birth or death are known, while the lifetime can be approximated in a period. As has been remarked by [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rathtz on TEI-L], the period can be approximated by @notBefore and @notAfter attributes on <birth> and <death> elements, while the ambiguity can be recorded in a <floruit> element:
<pre>
<person>
<persName>Regina van Alisa</persName>
<birth notBefore="0201"/>
<death notAfter="0300"/>
<floruit>3rd cent</floruit>
</person>
</pre>

In his response, [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=3128 Gabriel Bodard on TEI-L] makes a refinement. If the period mentioned does not literally apply to birth and death dates, and in the previous example rather conveys that this person lived the better part of her life in the 3rd century (while she might have been born or died before the start or after the end of that century), the most accurate way of representing this would imply an inversion of the @notBefore and @notAfter attributes on respectively <birth> and <death>:
<pre>
<person>
<persName>Regina van Alisa</persName>
<birth notAfter="0300"/>
<death notBefore="0201"/>
<floruit>3rd cent</floruit>
</person>
</pre>

==Naming==
===Pseudonyms===
Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERSEps 13.3.2.2 Personal States] of the TEI Guidelines describes how multiple <persName>s are allowed for a person, possibly categorised with a @type attribute. For pseudonyms, the value 'pseudo' can be used. Hence, the guitarist commonly known as Slash could be described as follows:
<pre>
<person>
<persName>
<surname>Hudson</surname>
<forename>Saul</forename>
</persName>
<persName type="pseudo">Slash</persName>
</person>
</pre>

This may raise an issue regarding the 'canonicity' of either name. In this case, a bibliographic entry would probably use the pseudonym 'Slash', whereas for less famous people the actual name may be preferred. This 'preference' could be recorded implicitly by the order of the <persNames>, or with the @sort attribute:
<pre>
<person>
<persName sort="2">
<surname>Hudson</surname>
<forename>Saul</forename>
</persName>
<persName type="pseudo" sort="1">Slash</persName>
</person>
</pre>

This could then mean that the pseudonym is the 'canonical' name for this person.

Another question is whether the actual name should then be typed as @type='real'?

===Alternative Names===
A related issue arises when people are commonly known by another name than their real name. For example, Joe English, a Belgian painter, is actually called Joseph English. I wonder whether a regularisation with <reg> would be the most suitable solution to encode this?

<pre>
<person>
<persName>
<reg>English, Joe A.M.</reg>
<surname>English</surname>
<forename>Joseph A.M.</forename>
</persName>
</person>
</pre>

==Mixing Prose and Structure==
The TEI P5 Guidelines define the contents <person> as either a collection of highly structured biographical 'fields' (using dedicated elements like <trait>, <occupation>, ...), or a collection of loose prose paragraphs (). Especially when transforming existing biographical records to TEI P5, this exclusive alternation can be unsatisfactory:
* splitting up all biographical prose into biographical fields may be too demanding
* OTOH, choosing to retain the description in prose paragraphs also prohibits the specification of basic biographical data in specific fields (<birth>, <death>, <persName>) inside <person>

One (tentative) solution could be to extract record-like information into biographical fields, while grouping the prose descriptions as paragraphs into a <note> element:

<pre>
<person xml:id="FJ">
<persName>
<reg>Fabricius, Jan</reg>
<surname>Fabricius</surname>
<forename>Jan</forename>
</persName>
<birth when="1871-09-30">
<placeName>Assen</placeName>
<date>30.09.1871</date>
</birth>
<death when="1964-11-23">
<placeName>Wimborne, Dorset</placeName>
<date>23.11.1964</date>
</death>
<note type="bio">
Journalist, Nederlands toneelschrijver.
Vader van de schrijver Johan Fabricius. Hoofdredacteur van verschillende bladen, zowel in Nederlands-Indië als in Nederland.
In 1938 vestigde hij zich in Engeland. Hoewel Fabricius op latere leeftijd ook enkele romans en drie delen memoires heeft
gepubliceerd, ligt zijn betekenis in zijn toneelwerk. Zijn technische vaardigheid en meesterschap in het schrijven van een
dialoog, maken zijn stukken goed speelbaar. Kind van een tijd die het realisme beoefende (Heijermans, Hauptmann), kon hij
toch niet de romantiek geheel laten varen. Het handelingsverloop is vaak gewild; er wordt dan bewust aangestuurd op een
aandoenlijke werking, zodat sommige van zijn stukken het predikaat 'melodramatisch' verdienen. Gedreven door een sterk gevoel
voor rechtvaardigheid zocht hij zijn gegevens in de problematiek van milieus die hem vertrouwd waren: het boerenland van
Groningen en Drente, de planterswereld van Indië. Fabricius' werk werd in Nederland en ook in het buitenland met succes opgevoerd.
Tot zijn bekendste werken behoren <title>Eenzaam</title> (1907) en <title>Dolle Hans</title> (1916). Sommige stukken zijn vertaald
in het Frans, Duits, Engels, Noors, Deens, Fries en Gronings.

</note>
<note type="ref">

<ptr ref="http://www.dbnl.org/auteurs/borkv/Fabr004.htm"/>

</note>
</person>
</pre>

This allows to group other types of information into other notes as well, distinguished by means of appropriate values for their @type attributes.

==Traits, States, and Events==
The Guidelines use traits, states, and events as basic categories for prosopography. Traits differ from states in being generally immutable. It may be that the distinction between states and traits is unnecessary. Almost every member of model.persTraitLike (age faith langKnowledge nationality s*x socecStatus trait) can change. Dropping "trait" leaves a simple yet expressive model where entities are described by states and state-transitions (i.e. events).

==Relations==
At the moment, relations are defined by attributes such as name, active and passive:

<pre><relation name="parent" active="#p1 #p2" passive="#p3 #p4"/></pre>

An alternative would be to use RDF-like subject, predicate, object triples:

<pre><relation subject="#p1" predicate="child-of" object="#p2"/></pre>

If the relation element was allowed inside a person element (which would be a good thing) then the subject would be implicit and need not be specified.

[[Category:Markup]]

Prosopography

2011-03-09T08:14:51Z

Tfinney: /* Traits, States, and Events */

Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERS 13.3 Prosopography] of the TEI Guidelines discusses how the elements and attributes from the TEI P5 [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#index-body.1_div.13_div.4 namesdates module] can be used to mark up prosopographical data.

This wiki page attempts to summarise a number of issues in recording prosopographical data, and aims to provide a (sometimes personal) starting point for discussion and sharing of encoding experiences and insights. Rather than a documentation of best practice, it focuses on possible approaches for encoding some prosopographical phenomena, and tries to find sensible ones.

==Dating==
===Unknown dates vs. lacking dates===
Birth and death dates can only be recorded if they are known. Yet, omitting the <death> element from a <person> description may lead to ambiguity. Consider following example:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth when="1935">1935</birth>
</person>
</pre>

Does this indicate:
* that the person is still living?
* that the person has died but the date of death is unknown?
(Obviously, this ambiguity does not hold for birth dates, as can be assumed that all existing persons must have been born.)

In order to resolve this ambiguity, it could be assumed that a description in a <person> element withouth <death> element would relate to a living person. When the person is known to have died, a <death> statement would then be required. If only the birth date is known, this can be used as a lower bound for the possible date of death:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth when="1935">1935</birth>
<death notBefore="1935" precision="low">?</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rahtz on TEI-L])

Note how the @notBefore attribute is used to specify this lower bound, in combination with the @precision attribute to indicate the precision of this statement. One could equally infer an upper bound by assuming that nobody lives longer than 120 years, and document this with the @notAfter attribute on the <death> element. The status of this conjecture and its certainty could be indicated by @evidence and @cert attributes, respectively:
<pre>
<person>
<persName>Corey Adams</persName>
<birth when="1835">1835</birth>
<death notAfter="1955" precision="low" cert="high" evidence="conjecture">?</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2524 Syd Bauman on TEI-L])

The lacking data could be represented by e.g. a question mark as text content of the <death> element.

When no birth nor death date is known for a dead person, no precise dates (or approximations) can be given in attributes. Still, it could make sense to have <birth> and <death> elements, whose text contents indicate this knowledge gap:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth>?</birth>
<death>?</death>
</person>
</pre>

===Circa Dates===
This issue has been raised on the [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind0903&L=TEI-L&D=0&P=18661 TEI-L mailing list]. Currently, TEI P5 only offers implicit means to indicate that a date is only an approximation:

<pre>
<person>
<persName>Aischylos</persName>
<birth precision="low" when="-0525">ca. 525 b.C.</birth>
<death precision="low" when="-0456">ca. 456 b.C.</death>
</person>
</pre>

...with the @precision attribute indicating the low precision of these statements.
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=3128 Gabriel Bodard on TEI-L])

Yet, depending on the requirements of the encoding, an ideal representation of circa dates could get quite complex, and touches on broader issues concerning an accurate representation of uncertainty. See following resources:
* [http://www.tfinney.net/Uncertainty/ Tim Finney: 'Uncertainty in text, markup and beyond']
* [http://sourceforge.net/tracker/?func=detail&aid=3060909&group_id=106328&atid=644065 feature request by Tim Finney]

===Alternative Dates===
Sometimes, multiple possibilities exist for determining the date of birth or death of a person. When both dates are successive, one could encode this as a date range, with @notBefore and @notAfter, as in this case with two possible birth dates:
<pre>
<person>
<persName>Duncan, Isadora</persName>
<birth notBefore="1877" notAfter="1878">[1877 or] 1878</birth>
<death when="1927">1927</death>
</person>
</pre>

(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rahtz on TEI-L])

When, on the other hand, both dates are non-successive, multiple <birth> or <death> dates can be provided, with an @exclude attribute indicating their exclusive alternation:
<pre>
<person>
<persName>Vanhautte, Delphien</persName>
<birth when="1869-09-02">
<placeName>Ardooie</placeName>
<date>02.09.1869</date>
</birth>
<death when="1944-02-03" xml:id="d19440203" exclude="#d19441203">
<placeName>Edewalle (Handzame)</placeName>
<date>03.02/12(?).1944</date>
</death>
<death when="1944-12-03" xml:id="d19441203" exclude="#d19440203">
<placeName>Edewalle (Handzame)</placeName>
<date>03.02/12(?).1944</date>
</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2524 Syd Bauman on TEI-L])

===Only a period is known===
Sometimes no exact dates of birth or death are known, while the lifetime can be approximated in a period. As has been remarked by [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rathtz on TEI-L], the period can be approximated by @notBefore and @notAfter attributes on <birth> and <death> elements, while the ambiguity can be recorded in a <floruit> element:
<pre>
<person>
<persName>Regina van Alisa</persName>
<birth notBefore="0201"/>
<death notAfter="0300"/>
<floruit>3rd cent</floruit>
</person>
</pre>

In his response, [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=3128 Gabriel Bodard on TEI-L] makes a refinement. If the period mentioned does not literally apply to birth and death dates, and in the previous example rather conveys that this person lived the better part of her life in the 3rd century (while she might have been born or died before the start or after the end of that century), the most accurate way of representing this would imply an inversion of the @notBefore and @notAfter attributes on respectively <birth> and <death>:
<pre>
<person>
<persName>Regina van Alisa</persName>
<birth notAfter="0300"/>
<death notBefore="0201"/>
<floruit>3rd cent</floruit>
</person>
</pre>

==Naming==
===Pseudonyms===
Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERSEps 13.3.2.2 Personal States] of the TEI Guidelines describes how multiple <persName>s are allowed for a person, possibly categorised with a @type attribute. For pseudonyms, the value 'pseudo' can be used. Hence, the guitarist commonly known as Slash could be described as follows:
<pre>
<person>
<persName>
<surname>Hudson</surname>
<forename>Saul</forename>
</persName>
<persName type="pseudo">Slash</persName>
</person>
</pre>

This may raise an issue regarding the 'canonicity' of either name. In this case, a bibliographic entry would probably use the pseudonym 'Slash', whereas for less famous people the actual name may be preferred. This 'preference' could be recorded implicitly by the order of the <persNames>, or with the @sort attribute:
<pre>
<person>
<persName sort="2">
<surname>Hudson</surname>
<forename>Saul</forename>
</persName>
<persName type="pseudo" sort="1">Slash</persName>
</person>
</pre>

This could then mean that the pseudonym is the 'canonical' name for this person.

Another question is whether the actual name should then be typed as @type='real'?

===Alternative Names===
A related issue arises when people are commonly known by another name than their real name. For example, Joe English, a Belgian painter, is actually called Joseph English. I wonder whether a regularisation with <reg> would be the most suitable solution to encode this?

<pre>
<person>
<persName>
<reg>English, Joe A.M.</reg>
<surname>English</surname>
<forename>Joseph A.M.</forename>
</persName>
</person>
</pre>

==Mixing Prose and Structure==
The TEI P5 Guidelines define the contents <person> as either a collection of highly structured biographical 'fields' (using dedicated elements like <trait>, <occupation>, ...), or a collection of loose prose paragraphs (). Especially when transforming existing biographical records to TEI P5, this exclusive alternation can be unsatisfactory:
* splitting up all biographical prose into biographical fields may be too demanding
* OTOH, choosing to retain the description in prose paragraphs also prohibits the specification of basic biographical data in specific fields (<birth>, <death>, <persName>) inside <person>

One (tentative) solution could be to extract record-like information into biographical fields, while grouping the prose descriptions as paragraphs into a <note> element:

<pre>
<person xml:id="FJ">
<persName>
<reg>Fabricius, Jan</reg>
<surname>Fabricius</surname>
<forename>Jan</forename>
</persName>
<birth when="1871-09-30">
<placeName>Assen</placeName>
<date>30.09.1871</date>
</birth>
<death when="1964-11-23">
<placeName>Wimborne, Dorset</placeName>
<date>23.11.1964</date>
</death>
<note type="bio">
Journalist, Nederlands toneelschrijver.
Vader van de schrijver Johan Fabricius. Hoofdredacteur van verschillende bladen, zowel in Nederlands-Indië als in Nederland.
In 1938 vestigde hij zich in Engeland. Hoewel Fabricius op latere leeftijd ook enkele romans en drie delen memoires heeft
gepubliceerd, ligt zijn betekenis in zijn toneelwerk. Zijn technische vaardigheid en meesterschap in het schrijven van een
dialoog, maken zijn stukken goed speelbaar. Kind van een tijd die het realisme beoefende (Heijermans, Hauptmann), kon hij
toch niet de romantiek geheel laten varen. Het handelingsverloop is vaak gewild; er wordt dan bewust aangestuurd op een
aandoenlijke werking, zodat sommige van zijn stukken het predikaat 'melodramatisch' verdienen. Gedreven door een sterk gevoel
voor rechtvaardigheid zocht hij zijn gegevens in de problematiek van milieus die hem vertrouwd waren: het boerenland van
Groningen en Drente, de planterswereld van Indië. Fabricius' werk werd in Nederland en ook in het buitenland met succes opgevoerd.
Tot zijn bekendste werken behoren <title>Eenzaam</title> (1907) en <title>Dolle Hans</title> (1916). Sommige stukken zijn vertaald
in het Frans, Duits, Engels, Noors, Deens, Fries en Gronings.

</note>
<note type="ref">

<ptr ref="http://www.dbnl.org/auteurs/borkv/Fabr004.htm"/>

</note>
</person>
</pre>

This allows to group other types of information into other notes as well, distinguished by means of appropriate values for their @type attributes.

==Traits, States, and Events==
The Guidelines use traits, states, and events as basic categories for prosopography. Traits differ from states in being generally immutable. It may be that the distinction between states and traits is unnecessary. Almost every member of model.persTraitLike (age faith langKnowledge nationality s*x socecStatus trait) can change. Dropping "trait" leaves a simple yet expressive model where entities are described by states and state-transitions (i.e. events).

==Relations==
At the moment, relations are defined by attributes such as name, active and passive:

<pre><relation name="parent" active="#p1 #p2" passive="#p3 #p4"/></pre>

An alternative would be to use RDF-like subject, predicate, object triples:

<pre><relation subject="#p1" predicate="child-of" object="#p2"/></pre>

If the relation object was allowed inside a person element then the subject would be implicit.

[[Category:Markup]]

Prosopography

2011-03-09T08:14:15Z

Tfinney: /* Traits, States, and Events */

Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERS 13.3 Prosopography] of the TEI Guidelines discusses how the elements and attributes from the TEI P5 [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#index-body.1_div.13_div.4 namesdates module] can be used to mark up prosopographical data.

This wiki page attempts to summarise a number of issues in recording prosopographical data, and aims to provide a (sometimes personal) starting point for discussion and sharing of encoding experiences and insights. Rather than a documentation of best practice, it focuses on possible approaches for encoding some prosopographical phenomena, and tries to find sensible ones.

==Dating==
===Unknown dates vs. lacking dates===
Birth and death dates can only be recorded if they are known. Yet, omitting the <death> element from a <person> description may lead to ambiguity. Consider following example:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth when="1935">1935</birth>
</person>
</pre>

Does this indicate:
* that the person is still living?
* that the person has died but the date of death is unknown?
(Obviously, this ambiguity does not hold for birth dates, as can be assumed that all existing persons must have been born.)

In order to resolve this ambiguity, it could be assumed that a description in a <person> element withouth <death> element would relate to a living person. When the person is known to have died, a <death> statement would then be required. If only the birth date is known, this can be used as a lower bound for the possible date of death:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth when="1935">1935</birth>
<death notBefore="1935" precision="low">?</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rahtz on TEI-L])

Note how the @notBefore attribute is used to specify this lower bound, in combination with the @precision attribute to indicate the precision of this statement. One could equally infer an upper bound by assuming that nobody lives longer than 120 years, and document this with the @notAfter attribute on the <death> element. The status of this conjecture and its certainty could be indicated by @evidence and @cert attributes, respectively:
<pre>
<person>
<persName>Corey Adams</persName>
<birth when="1835">1835</birth>
<death notAfter="1955" precision="low" cert="high" evidence="conjecture">?</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2524 Syd Bauman on TEI-L])

The lacking data could be represented by e.g. a question mark as text content of the <death> element.

When no birth nor death date is known for a dead person, no precise dates (or approximations) can be given in attributes. Still, it could make sense to have <birth> and <death> elements, whose text contents indicate this knowledge gap:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth>?</birth>
<death>?</death>
</person>
</pre>

===Circa Dates===
This issue has been raised on the [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind0903&L=TEI-L&D=0&P=18661 TEI-L mailing list]. Currently, TEI P5 only offers implicit means to indicate that a date is only an approximation:

<pre>
<person>
<persName>Aischylos</persName>
<birth precision="low" when="-0525">ca. 525 b.C.</birth>
<death precision="low" when="-0456">ca. 456 b.C.</death>
</person>
</pre>

...with the @precision attribute indicating the low precision of these statements.
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=3128 Gabriel Bodard on TEI-L])

Yet, depending on the requirements of the encoding, an ideal representation of circa dates could get quite complex, and touches on broader issues concerning an accurate representation of uncertainty. See following resources:
* [http://www.tfinney.net/Uncertainty/ Tim Finney: 'Uncertainty in text, markup and beyond']
* [http://sourceforge.net/tracker/?func=detail&aid=3060909&group_id=106328&atid=644065 feature request by Tim Finney]

===Alternative Dates===
Sometimes, multiple possibilities exist for determining the date of birth or death of a person. When both dates are successive, one could encode this as a date range, with @notBefore and @notAfter, as in this case with two possible birth dates:
<pre>
<person>
<persName>Duncan, Isadora</persName>
<birth notBefore="1877" notAfter="1878">[1877 or] 1878</birth>
<death when="1927">1927</death>
</person>
</pre>

(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rahtz on TEI-L])

When, on the other hand, both dates are non-successive, multiple <birth> or <death> dates can be provided, with an @exclude attribute indicating their exclusive alternation:
<pre>
<person>
<persName>Vanhautte, Delphien</persName>
<birth when="1869-09-02">
<placeName>Ardooie</placeName>
<date>02.09.1869</date>
</birth>
<death when="1944-02-03" xml:id="d19440203" exclude="#d19441203">
<placeName>Edewalle (Handzame)</placeName>
<date>03.02/12(?).1944</date>
</death>
<death when="1944-12-03" xml:id="d19441203" exclude="#d19440203">
<placeName>Edewalle (Handzame)</placeName>
<date>03.02/12(?).1944</date>
</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2524 Syd Bauman on TEI-L])

===Only a period is known===
Sometimes no exact dates of birth or death are known, while the lifetime can be approximated in a period. As has been remarked by [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rathtz on TEI-L], the period can be approximated by @notBefore and @notAfter attributes on <birth> and <death> elements, while the ambiguity can be recorded in a <floruit> element:
<pre>
<person>
<persName>Regina van Alisa</persName>
<birth notBefore="0201"/>
<death notAfter="0300"/>
<floruit>3rd cent</floruit>
</person>
</pre>

In his response, [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=3128 Gabriel Bodard on TEI-L] makes a refinement. If the period mentioned does not literally apply to birth and death dates, and in the previous example rather conveys that this person lived the better part of her life in the 3rd century (while she might have been born or died before the start or after the end of that century), the most accurate way of representing this would imply an inversion of the @notBefore and @notAfter attributes on respectively <birth> and <death>:
<pre>
<person>
<persName>Regina van Alisa</persName>
<birth notAfter="0300"/>
<death notBefore="0201"/>
<floruit>3rd cent</floruit>
</person>
</pre>

==Naming==
===Pseudonyms===
Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERSEps 13.3.2.2 Personal States] of the TEI Guidelines describes how multiple <persName>s are allowed for a person, possibly categorised with a @type attribute. For pseudonyms, the value 'pseudo' can be used. Hence, the guitarist commonly known as Slash could be described as follows:
<pre>
<person>
<persName>
<surname>Hudson</surname>
<forename>Saul</forename>
</persName>
<persName type="pseudo">Slash</persName>
</person>
</pre>

This may raise an issue regarding the 'canonicity' of either name. In this case, a bibliographic entry would probably use the pseudonym 'Slash', whereas for less famous people the actual name may be preferred. This 'preference' could be recorded implicitly by the order of the <persNames>, or with the @sort attribute:
<pre>
<person>
<persName sort="2">
<surname>Hudson</surname>
<forename>Saul</forename>
</persName>
<persName type="pseudo" sort="1">Slash</persName>
</person>
</pre>

This could then mean that the pseudonym is the 'canonical' name for this person.

Another question is whether the actual name should then be typed as @type='real'?

===Alternative Names===
A related issue arises when people are commonly known by another name than their real name. For example, Joe English, a Belgian painter, is actually called Joseph English. I wonder whether a regularisation with <reg> would be the most suitable solution to encode this?

<pre>
<person>
<persName>
<reg>English, Joe A.M.</reg>
<surname>English</surname>
<forename>Joseph A.M.</forename>
</persName>
</person>
</pre>

==Mixing Prose and Structure==
The TEI P5 Guidelines define the contents <person> as either a collection of highly structured biographical 'fields' (using dedicated elements like <trait>, <occupation>, ...), or a collection of loose prose paragraphs (). Especially when transforming existing biographical records to TEI P5, this exclusive alternation can be unsatisfactory:
* splitting up all biographical prose into biographical fields may be too demanding
* OTOH, choosing to retain the description in prose paragraphs also prohibits the specification of basic biographical data in specific fields (<birth>, <death>, <persName>) inside <person>

One (tentative) solution could be to extract record-like information into biographical fields, while grouping the prose descriptions as paragraphs into a <note> element:

<pre>
<person xml:id="FJ">
<persName>
<reg>Fabricius, Jan</reg>
<surname>Fabricius</surname>
<forename>Jan</forename>
</persName>
<birth when="1871-09-30">
<placeName>Assen</placeName>
<date>30.09.1871</date>
</birth>
<death when="1964-11-23">
<placeName>Wimborne, Dorset</placeName>
<date>23.11.1964</date>
</death>
<note type="bio">
Journalist, Nederlands toneelschrijver.
Vader van de schrijver Johan Fabricius. Hoofdredacteur van verschillende bladen, zowel in Nederlands-Indië als in Nederland.
In 1938 vestigde hij zich in Engeland. Hoewel Fabricius op latere leeftijd ook enkele romans en drie delen memoires heeft
gepubliceerd, ligt zijn betekenis in zijn toneelwerk. Zijn technische vaardigheid en meesterschap in het schrijven van een
dialoog, maken zijn stukken goed speelbaar. Kind van een tijd die het realisme beoefende (Heijermans, Hauptmann), kon hij
toch niet de romantiek geheel laten varen. Het handelingsverloop is vaak gewild; er wordt dan bewust aangestuurd op een
aandoenlijke werking, zodat sommige van zijn stukken het predikaat 'melodramatisch' verdienen. Gedreven door een sterk gevoel
voor rechtvaardigheid zocht hij zijn gegevens in de problematiek van milieus die hem vertrouwd waren: het boerenland van
Groningen en Drente, de planterswereld van Indië. Fabricius' werk werd in Nederland en ook in het buitenland met succes opgevoerd.
Tot zijn bekendste werken behoren <title>Eenzaam</title> (1907) en <title>Dolle Hans</title> (1916). Sommige stukken zijn vertaald
in het Frans, Duits, Engels, Noors, Deens, Fries en Gronings.

</note>
<note type="ref">

<ptr ref="http://www.dbnl.org/auteurs/borkv/Fabr004.htm"/>

</note>
</person>
</pre>

This allows to group other types of information into other notes as well, distinguished by means of appropriate values for their @type attributes.

==Traits, States, and Events==
The Guidelines use traits, states, and events as basic categories. Traits differ from states in being generally immutable. It may be that the distinction between states and traits is unnecessary. Almost every member of model.persTraitLike (age faith langKnowledge nationality s*x socecStatus trait) can change. Dropping "trait" leaves a simple yet expressive model where entities are described by states and state-transitions (i.e. events).

==Relations==
At the moment, relations are defined by attributes such as name, active and passive:

<pre><relation name="parent" active="#p1 #p2" passive="#p3 #p4"/></pre>

An alternative would be to use RDF-like subject, predicate, object triples:

<pre><relation subject="#p1" predicate="child-of" object="#p2"/></pre>

If the relation object was allowed inside a person element then the subject would be implicit.

[[Category:Markup]]

Prosopography

2011-03-09T08:12:39Z

Tfinney: /* Relations */

Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERS 13.3 Prosopography] of the TEI Guidelines discusses how the elements and attributes from the TEI P5 [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#index-body.1_div.13_div.4 namesdates module] can be used to mark up prosopographical data.

This wiki page attempts to summarise a number of issues in recording prosopographical data, and aims to provide a (sometimes personal) starting point for discussion and sharing of encoding experiences and insights. Rather than a documentation of best practice, it focuses on possible approaches for encoding some prosopographical phenomena, and tries to find sensible ones.

==Dating==
===Unknown dates vs. lacking dates===
Birth and death dates can only be recorded if they are known. Yet, omitting the <death> element from a <person> description may lead to ambiguity. Consider following example:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth when="1935">1935</birth>
</person>
</pre>

Does this indicate:
* that the person is still living?
* that the person has died but the date of death is unknown?
(Obviously, this ambiguity does not hold for birth dates, as can be assumed that all existing persons must have been born.)

In order to resolve this ambiguity, it could be assumed that a description in a <person> element withouth <death> element would relate to a living person. When the person is known to have died, a <death> statement would then be required. If only the birth date is known, this can be used as a lower bound for the possible date of death:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth when="1935">1935</birth>
<death notBefore="1935" precision="low">?</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rahtz on TEI-L])

Note how the @notBefore attribute is used to specify this lower bound, in combination with the @precision attribute to indicate the precision of this statement. One could equally infer an upper bound by assuming that nobody lives longer than 120 years, and document this with the @notAfter attribute on the <death> element. The status of this conjecture and its certainty could be indicated by @evidence and @cert attributes, respectively:
<pre>
<person>
<persName>Corey Adams</persName>
<birth when="1835">1835</birth>
<death notAfter="1955" precision="low" cert="high" evidence="conjecture">?</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2524 Syd Bauman on TEI-L])

The lacking data could be represented by e.g. a question mark as text content of the <death> element.

When no birth nor death date is known for a dead person, no precise dates (or approximations) can be given in attributes. Still, it could make sense to have <birth> and <death> elements, whose text contents indicate this knowledge gap:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth>?</birth>
<death>?</death>
</person>
</pre>

===Circa Dates===
This issue has been raised on the [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind0903&L=TEI-L&D=0&P=18661 TEI-L mailing list]. Currently, TEI P5 only offers implicit means to indicate that a date is only an approximation:

<pre>
<person>
<persName>Aischylos</persName>
<birth precision="low" when="-0525">ca. 525 b.C.</birth>
<death precision="low" when="-0456">ca. 456 b.C.</death>
</person>
</pre>

...with the @precision attribute indicating the low precision of these statements.
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=3128 Gabriel Bodard on TEI-L])

Yet, depending on the requirements of the encoding, an ideal representation of circa dates could get quite complex, and touches on broader issues concerning an accurate representation of uncertainty. See following resources:
* [http://www.tfinney.net/Uncertainty/ Tim Finney: 'Uncertainty in text, markup and beyond']
* [http://sourceforge.net/tracker/?func=detail&aid=3060909&group_id=106328&atid=644065 feature request by Tim Finney]

===Alternative Dates===
Sometimes, multiple possibilities exist for determining the date of birth or death of a person. When both dates are successive, one could encode this as a date range, with @notBefore and @notAfter, as in this case with two possible birth dates:
<pre>
<person>
<persName>Duncan, Isadora</persName>
<birth notBefore="1877" notAfter="1878">[1877 or] 1878</birth>
<death when="1927">1927</death>
</person>
</pre>

(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rahtz on TEI-L])

When, on the other hand, both dates are non-successive, multiple <birth> or <death> dates can be provided, with an @exclude attribute indicating their exclusive alternation:
<pre>
<person>
<persName>Vanhautte, Delphien</persName>
<birth when="1869-09-02">
<placeName>Ardooie</placeName>
<date>02.09.1869</date>
</birth>
<death when="1944-02-03" xml:id="d19440203" exclude="#d19441203">
<placeName>Edewalle (Handzame)</placeName>
<date>03.02/12(?).1944</date>
</death>
<death when="1944-12-03" xml:id="d19441203" exclude="#d19440203">
<placeName>Edewalle (Handzame)</placeName>
<date>03.02/12(?).1944</date>
</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2524 Syd Bauman on TEI-L])

===Only a period is known===
Sometimes no exact dates of birth or death are known, while the lifetime can be approximated in a period. As has been remarked by [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rathtz on TEI-L], the period can be approximated by @notBefore and @notAfter attributes on <birth> and <death> elements, while the ambiguity can be recorded in a <floruit> element:
<pre>
<person>
<persName>Regina van Alisa</persName>
<birth notBefore="0201"/>
<death notAfter="0300"/>
<floruit>3rd cent</floruit>
</person>
</pre>

In his response, [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=3128 Gabriel Bodard on TEI-L] makes a refinement. If the period mentioned does not literally apply to birth and death dates, and in the previous example rather conveys that this person lived the better part of her life in the 3rd century (while she might have been born or died before the start or after the end of that century), the most accurate way of representing this would imply an inversion of the @notBefore and @notAfter attributes on respectively <birth> and <death>:
<pre>
<person>
<persName>Regina van Alisa</persName>
<birth notAfter="0300"/>
<death notBefore="0201"/>
<floruit>3rd cent</floruit>
</person>
</pre>

==Naming==
===Pseudonyms===
Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERSEps 13.3.2.2 Personal States] of the TEI Guidelines describes how multiple <persName>s are allowed for a person, possibly categorised with a @type attribute. For pseudonyms, the value 'pseudo' can be used. Hence, the guitarist commonly known as Slash could be described as follows:
<pre>
<person>
<persName>
<surname>Hudson</surname>
<forename>Saul</forename>
</persName>
<persName type="pseudo">Slash</persName>
</person>
</pre>

This may raise an issue regarding the 'canonicity' of either name. In this case, a bibliographic entry would probably use the pseudonym 'Slash', whereas for less famous people the actual name may be preferred. This 'preference' could be recorded implicitly by the order of the <persNames>, or with the @sort attribute:
<pre>
<person>
<persName sort="2">
<surname>Hudson</surname>
<forename>Saul</forename>
</persName>
<persName type="pseudo" sort="1">Slash</persName>
</person>
</pre>

This could then mean that the pseudonym is the 'canonical' name for this person.

Another question is whether the actual name should then be typed as @type='real'?

===Alternative Names===
A related issue arises when people are commonly known by another name than their real name. For example, Joe English, a Belgian painter, is actually called Joseph English. I wonder whether a regularisation with <reg> would be the most suitable solution to encode this?

<pre>
<person>
<persName>
<reg>English, Joe A.M.</reg>
<surname>English</surname>
<forename>Joseph A.M.</forename>
</persName>
</person>
</pre>

==Mixing Prose and Structure==
The TEI P5 Guidelines define the contents <person> as either a collection of highly structured biographical 'fields' (using dedicated elements like <trait>, <occupation>, ...), or a collection of loose prose paragraphs (). Especially when transforming existing biographical records to TEI P5, this exclusive alternation can be unsatisfactory:
* splitting up all biographical prose into biographical fields may be too demanding
* OTOH, choosing to retain the description in prose paragraphs also prohibits the specification of basic biographical data in specific fields (<birth>, <death>, <persName>) inside <person>

One (tentative) solution could be to extract record-like information into biographical fields, while grouping the prose descriptions as paragraphs into a <note> element:

<pre>
<person xml:id="FJ">
<persName>
<reg>Fabricius, Jan</reg>
<surname>Fabricius</surname>
<forename>Jan</forename>
</persName>
<birth when="1871-09-30">
<placeName>Assen</placeName>
<date>30.09.1871</date>
</birth>
<death when="1964-11-23">
<placeName>Wimborne, Dorset</placeName>
<date>23.11.1964</date>
</death>
<note type="bio">
Journalist, Nederlands toneelschrijver.
Vader van de schrijver Johan Fabricius. Hoofdredacteur van verschillende bladen, zowel in Nederlands-Indië als in Nederland.
In 1938 vestigde hij zich in Engeland. Hoewel Fabricius op latere leeftijd ook enkele romans en drie delen memoires heeft
gepubliceerd, ligt zijn betekenis in zijn toneelwerk. Zijn technische vaardigheid en meesterschap in het schrijven van een
dialoog, maken zijn stukken goed speelbaar. Kind van een tijd die het realisme beoefende (Heijermans, Hauptmann), kon hij
toch niet de romantiek geheel laten varen. Het handelingsverloop is vaak gewild; er wordt dan bewust aangestuurd op een
aandoenlijke werking, zodat sommige van zijn stukken het predikaat 'melodramatisch' verdienen. Gedreven door een sterk gevoel
voor rechtvaardigheid zocht hij zijn gegevens in de problematiek van milieus die hem vertrouwd waren: het boerenland van
Groningen en Drente, de planterswereld van Indië. Fabricius' werk werd in Nederland en ook in het buitenland met succes opgevoerd.
Tot zijn bekendste werken behoren <title>Eenzaam</title> (1907) en <title>Dolle Hans</title> (1916). Sommige stukken zijn vertaald
in het Frans, Duits, Engels, Noors, Deens, Fries en Gronings.

</note>
<note type="ref">

<ptr ref="http://www.dbnl.org/auteurs/borkv/Fabr004.htm"/>

</note>
</person>
</pre>

This allows to group other types of information into other notes as well, distinguished by means of appropriate values for their @type attributes.

==Traits, States, and Events==
The Guidelines use traits, states, and events as basic categories. Traits differ from states in being generally immutable. It may be that the distinction between states and traits is unnecessary. Almost every member of model.persTraitLike (age faith langKnowledge nationality s*x socecStatus trait) can change. Dropping "trait" leaves a simple yet expressive model where entities are defined by states and state-transitions (i.e. events).

==Relations==
At the moment, relations are defined by attributes such as name, active and passive:

<pre><relation name="parent" active="#p1 #p2" passive="#p3 #p4"/></pre>

An alternative would be to use RDF-like subject, predicate, object triples:

<pre><relation subject="#p1" predicate="child-of" object="#p2"/></pre>

If the relation object was allowed inside a person element then the subject would be implicit.

[[Category:Markup]]

Prosopography

2011-03-09T08:07:01Z

Tfinney: /* Traits, States, and Events */

Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERS 13.3 Prosopography] of the TEI Guidelines discusses how the elements and attributes from the TEI P5 [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#index-body.1_div.13_div.4 namesdates module] can be used to mark up prosopographical data.

This wiki page attempts to summarise a number of issues in recording prosopographical data, and aims to provide a (sometimes personal) starting point for discussion and sharing of encoding experiences and insights. Rather than a documentation of best practice, it focuses on possible approaches for encoding some prosopographical phenomena, and tries to find sensible ones.

==Dating==
===Unknown dates vs. lacking dates===
Birth and death dates can only be recorded if they are known. Yet, omitting the <death> element from a <person> description may lead to ambiguity. Consider following example:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth when="1935">1935</birth>
</person>
</pre>

Does this indicate:
* that the person is still living?
* that the person has died but the date of death is unknown?
(Obviously, this ambiguity does not hold for birth dates, as can be assumed that all existing persons must have been born.)

In order to resolve this ambiguity, it could be assumed that a description in a <person> element withouth <death> element would relate to a living person. When the person is known to have died, a <death> statement would then be required. If only the birth date is known, this can be used as a lower bound for the possible date of death:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth when="1935">1935</birth>
<death notBefore="1935" precision="low">?</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rahtz on TEI-L])

Note how the @notBefore attribute is used to specify this lower bound, in combination with the @precision attribute to indicate the precision of this statement. One could equally infer an upper bound by assuming that nobody lives longer than 120 years, and document this with the @notAfter attribute on the <death> element. The status of this conjecture and its certainty could be indicated by @evidence and @cert attributes, respectively:
<pre>
<person>
<persName>Corey Adams</persName>
<birth when="1835">1835</birth>
<death notAfter="1955" precision="low" cert="high" evidence="conjecture">?</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2524 Syd Bauman on TEI-L])

The lacking data could be represented by e.g. a question mark as text content of the <death> element.

When no birth nor death date is known for a dead person, no precise dates (or approximations) can be given in attributes. Still, it could make sense to have <birth> and <death> elements, whose text contents indicate this knowledge gap:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth>?</birth>
<death>?</death>
</person>
</pre>

===Circa Dates===
This issue has been raised on the [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind0903&L=TEI-L&D=0&P=18661 TEI-L mailing list]. Currently, TEI P5 only offers implicit means to indicate that a date is only an approximation:

<pre>
<person>
<persName>Aischylos</persName>
<birth precision="low" when="-0525">ca. 525 b.C.</birth>
<death precision="low" when="-0456">ca. 456 b.C.</death>
</person>
</pre>

...with the @precision attribute indicating the low precision of these statements.
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=3128 Gabriel Bodard on TEI-L])

Yet, depending on the requirements of the encoding, an ideal representation of circa dates could get quite complex, and touches on broader issues concerning an accurate representation of uncertainty. See following resources:
* [http://www.tfinney.net/Uncertainty/ Tim Finney: 'Uncertainty in text, markup and beyond']
* [http://sourceforge.net/tracker/?func=detail&aid=3060909&group_id=106328&atid=644065 feature request by Tim Finney]

===Alternative Dates===
Sometimes, multiple possibilities exist for determining the date of birth or death of a person. When both dates are successive, one could encode this as a date range, with @notBefore and @notAfter, as in this case with two possible birth dates:
<pre>
<person>
<persName>Duncan, Isadora</persName>
<birth notBefore="1877" notAfter="1878">[1877 or] 1878</birth>
<death when="1927">1927</death>
</person>
</pre>

(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rahtz on TEI-L])

When, on the other hand, both dates are non-successive, multiple <birth> or <death> dates can be provided, with an @exclude attribute indicating their exclusive alternation:
<pre>
<person>
<persName>Vanhautte, Delphien</persName>
<birth when="1869-09-02">
<placeName>Ardooie</placeName>
<date>02.09.1869</date>
</birth>
<death when="1944-02-03" xml:id="d19440203" exclude="#d19441203">
<placeName>Edewalle (Handzame)</placeName>
<date>03.02/12(?).1944</date>
</death>
<death when="1944-12-03" xml:id="d19441203" exclude="#d19440203">
<placeName>Edewalle (Handzame)</placeName>
<date>03.02/12(?).1944</date>
</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2524 Syd Bauman on TEI-L])

===Only a period is known===
Sometimes no exact dates of birth or death are known, while the lifetime can be approximated in a period. As has been remarked by [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rathtz on TEI-L], the period can be approximated by @notBefore and @notAfter attributes on <birth> and <death> elements, while the ambiguity can be recorded in a <floruit> element:
<pre>
<person>
<persName>Regina van Alisa</persName>
<birth notBefore="0201"/>
<death notAfter="0300"/>
<floruit>3rd cent</floruit>
</person>
</pre>

In his response, [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=3128 Gabriel Bodard on TEI-L] makes a refinement. If the period mentioned does not literally apply to birth and death dates, and in the previous example rather conveys that this person lived the better part of her life in the 3rd century (while she might have been born or died before the start or after the end of that century), the most accurate way of representing this would imply an inversion of the @notBefore and @notAfter attributes on respectively <birth> and <death>:
<pre>
<person>
<persName>Regina van Alisa</persName>
<birth notAfter="0300"/>
<death notBefore="0201"/>
<floruit>3rd cent</floruit>
</person>
</pre>

==Naming==
===Pseudonyms===
Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERSEps 13.3.2.2 Personal States] of the TEI Guidelines describes how multiple <persName>s are allowed for a person, possibly categorised with a @type attribute. For pseudonyms, the value 'pseudo' can be used. Hence, the guitarist commonly known as Slash could be described as follows:
<pre>
<person>
<persName>
<surname>Hudson</surname>
<forename>Saul</forename>
</persName>
<persName type="pseudo">Slash</persName>
</person>
</pre>

This may raise an issue regarding the 'canonicity' of either name. In this case, a bibliographic entry would probably use the pseudonym 'Slash', whereas for less famous people the actual name may be preferred. This 'preference' could be recorded implicitly by the order of the <persNames>, or with the @sort attribute:
<pre>
<person>
<persName sort="2">
<surname>Hudson</surname>
<forename>Saul</forename>
</persName>
<persName type="pseudo" sort="1">Slash</persName>
</person>
</pre>

This could then mean that the pseudonym is the 'canonical' name for this person.

Another question is whether the actual name should then be typed as @type='real'?

===Alternative Names===
A related issue arises when people are commonly known by another name than their real name. For example, Joe English, a Belgian painter, is actually called Joseph English. I wonder whether a regularisation with <reg> would be the most suitable solution to encode this?

<pre>
<person>
<persName>
<reg>English, Joe A.M.</reg>
<surname>English</surname>
<forename>Joseph A.M.</forename>
</persName>
</person>
</pre>

==Mixing Prose and Structure==
The TEI P5 Guidelines define the contents <person> as either a collection of highly structured biographical 'fields' (using dedicated elements like <trait>, <occupation>, ...), or a collection of loose prose paragraphs (). Especially when transforming existing biographical records to TEI P5, this exclusive alternation can be unsatisfactory:
* splitting up all biographical prose into biographical fields may be too demanding
* OTOH, choosing to retain the description in prose paragraphs also prohibits the specification of basic biographical data in specific fields (<birth>, <death>, <persName>) inside <person>

One (tentative) solution could be to extract record-like information into biographical fields, while grouping the prose descriptions as paragraphs into a <note> element:

<pre>
<person xml:id="FJ">
<persName>
<reg>Fabricius, Jan</reg>
<surname>Fabricius</surname>
<forename>Jan</forename>
</persName>
<birth when="1871-09-30">
<placeName>Assen</placeName>
<date>30.09.1871</date>
</birth>
<death when="1964-11-23">
<placeName>Wimborne, Dorset</placeName>
<date>23.11.1964</date>
</death>
<note type="bio">
Journalist, Nederlands toneelschrijver.
Vader van de schrijver Johan Fabricius. Hoofdredacteur van verschillende bladen, zowel in Nederlands-Indië als in Nederland.
In 1938 vestigde hij zich in Engeland. Hoewel Fabricius op latere leeftijd ook enkele romans en drie delen memoires heeft
gepubliceerd, ligt zijn betekenis in zijn toneelwerk. Zijn technische vaardigheid en meesterschap in het schrijven van een
dialoog, maken zijn stukken goed speelbaar. Kind van een tijd die het realisme beoefende (Heijermans, Hauptmann), kon hij
toch niet de romantiek geheel laten varen. Het handelingsverloop is vaak gewild; er wordt dan bewust aangestuurd op een
aandoenlijke werking, zodat sommige van zijn stukken het predikaat 'melodramatisch' verdienen. Gedreven door een sterk gevoel
voor rechtvaardigheid zocht hij zijn gegevens in de problematiek van milieus die hem vertrouwd waren: het boerenland van
Groningen en Drente, de planterswereld van Indië. Fabricius' werk werd in Nederland en ook in het buitenland met succes opgevoerd.
Tot zijn bekendste werken behoren <title>Eenzaam</title> (1907) en <title>Dolle Hans</title> (1916). Sommige stukken zijn vertaald
in het Frans, Duits, Engels, Noors, Deens, Fries en Gronings.

</note>
<note type="ref">

<ptr ref="http://www.dbnl.org/auteurs/borkv/Fabr004.htm"/>

</note>
</person>
</pre>

This allows to group other types of information into other notes as well, distinguished by means of appropriate values for their @type attributes.

==Traits, States, and Events==
The Guidelines use traits, states, and events as basic categories. Traits differ from states in being generally immutable. It may be that the distinction between states and traits is unnecessary. Almost every member of model.persTraitLike (age faith langKnowledge nationality s*x socecStatus trait) can change. Dropping "trait" leaves a simple yet expressive model where entities are defined by states and state-transitions (i.e. events).

==Relations==
At the moment, relations are defined by attributes such as name, active and passive:

<pre><relation name="parent" active="#p1 #p2" passive="#p3 #p4"/></pre>

[[Category:Markup]]

Prosopography

2011-03-09T08:02:32Z

Tfinney: Add my opinions concerning traits and relations.

Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERS 13.3 Prosopography] of the TEI Guidelines discusses how the elements and attributes from the TEI P5 [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#index-body.1_div.13_div.4 namesdates module] can be used to mark up prosopographical data.

This wiki page attempts to summarise a number of issues in recording prosopographical data, and aims to provide a (sometimes personal) starting point for discussion and sharing of encoding experiences and insights. Rather than a documentation of best practice, it focuses on possible approaches for encoding some prosopographical phenomena, and tries to find sensible ones.

==Dating==
===Unknown dates vs. lacking dates===
Birth and death dates can only be recorded if they are known. Yet, omitting the <death> element from a <person> description may lead to ambiguity. Consider following example:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth when="1935">1935</birth>
</person>
</pre>

Does this indicate:
* that the person is still living?
* that the person has died but the date of death is unknown?
(Obviously, this ambiguity does not hold for birth dates, as can be assumed that all existing persons must have been born.)

In order to resolve this ambiguity, it could be assumed that a description in a <person> element withouth <death> element would relate to a living person. When the person is known to have died, a <death> statement would then be required. If only the birth date is known, this can be used as a lower bound for the possible date of death:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth when="1935">1935</birth>
<death notBefore="1935" precision="low">?</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rahtz on TEI-L])

Note how the @notBefore attribute is used to specify this lower bound, in combination with the @precision attribute to indicate the precision of this statement. One could equally infer an upper bound by assuming that nobody lives longer than 120 years, and document this with the @notAfter attribute on the <death> element. The status of this conjecture and its certainty could be indicated by @evidence and @cert attributes, respectively:
<pre>
<person>
<persName>Corey Adams</persName>
<birth when="1835">1835</birth>
<death notAfter="1955" precision="low" cert="high" evidence="conjecture">?</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2524 Syd Bauman on TEI-L])

The lacking data could be represented by e.g. a question mark as text content of the <death> element.

When no birth nor death date is known for a dead person, no precise dates (or approximations) can be given in attributes. Still, it could make sense to have <birth> and <death> elements, whose text contents indicate this knowledge gap:
<pre>
<person>
<persName>Elvis Presley</persName>
<birth>?</birth>
<death>?</death>
</person>
</pre>

===Circa Dates===
This issue has been raised on the [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind0903&L=TEI-L&D=0&P=18661 TEI-L mailing list]. Currently, TEI P5 only offers implicit means to indicate that a date is only an approximation:

<pre>
<person>
<persName>Aischylos</persName>
<birth precision="low" when="-0525">ca. 525 b.C.</birth>
<death precision="low" when="-0456">ca. 456 b.C.</death>
</person>
</pre>

...with the @precision attribute indicating the low precision of these statements.
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=3128 Gabriel Bodard on TEI-L])

Yet, depending on the requirements of the encoding, an ideal representation of circa dates could get quite complex, and touches on broader issues concerning an accurate representation of uncertainty. See following resources:
* [http://www.tfinney.net/Uncertainty/ Tim Finney: 'Uncertainty in text, markup and beyond']
* [http://sourceforge.net/tracker/?func=detail&aid=3060909&group_id=106328&atid=644065 feature request by Tim Finney]

===Alternative Dates===
Sometimes, multiple possibilities exist for determining the date of birth or death of a person. When both dates are successive, one could encode this as a date range, with @notBefore and @notAfter, as in this case with two possible birth dates:
<pre>
<person>
<persName>Duncan, Isadora</persName>
<birth notBefore="1877" notAfter="1878">[1877 or] 1878</birth>
<death when="1927">1927</death>
</person>
</pre>

(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rahtz on TEI-L])

When, on the other hand, both dates are non-successive, multiple <birth> or <death> dates can be provided, with an @exclude attribute indicating their exclusive alternation:
<pre>
<person>
<persName>Vanhautte, Delphien</persName>
<birth when="1869-09-02">
<placeName>Ardooie</placeName>
<date>02.09.1869</date>
</birth>
<death when="1944-02-03" xml:id="d19440203" exclude="#d19441203">
<placeName>Edewalle (Handzame)</placeName>
<date>03.02/12(?).1944</date>
</death>
<death when="1944-12-03" xml:id="d19441203" exclude="#d19440203">
<placeName>Edewalle (Handzame)</placeName>
<date>03.02/12(?).1944</date>
</death>
</person>
</pre>
(source: [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2524 Syd Bauman on TEI-L])

===Only a period is known===
Sometimes no exact dates of birth or death are known, while the lifetime can be approximated in a period. As has been remarked by [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=2337 Sebastian Rathtz on TEI-L], the period can be approximated by @notBefore and @notAfter attributes on <birth> and <death> elements, while the ambiguity can be recorded in a <floruit> element:
<pre>
<person>
<persName>Regina van Alisa</persName>
<birth notBefore="0201"/>
<death notAfter="0300"/>
<floruit>3rd cent</floruit>
</person>
</pre>

In his response, [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1010&L=TEI-L&P=3128 Gabriel Bodard on TEI-L] makes a refinement. If the period mentioned does not literally apply to birth and death dates, and in the previous example rather conveys that this person lived the better part of her life in the 3rd century (while she might have been born or died before the start or after the end of that century), the most accurate way of representing this would imply an inversion of the @notBefore and @notAfter attributes on respectively <birth> and <death>:
<pre>
<person>
<persName>Regina van Alisa</persName>
<birth notAfter="0300"/>
<death notBefore="0201"/>
<floruit>3rd cent</floruit>
</person>
</pre>

==Naming==
===Pseudonyms===
Section [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPERSEps 13.3.2.2 Personal States] of the TEI Guidelines describes how multiple <persName>s are allowed for a person, possibly categorised with a @type attribute. For pseudonyms, the value 'pseudo' can be used. Hence, the guitarist commonly known as Slash could be described as follows:
<pre>
<person>
<persName>
<surname>Hudson</surname>
<forename>Saul</forename>
</persName>
<persName type="pseudo">Slash</persName>
</person>
</pre>

This may raise an issue regarding the 'canonicity' of either name. In this case, a bibliographic entry would probably use the pseudonym 'Slash', whereas for less famous people the actual name may be preferred. This 'preference' could be recorded implicitly by the order of the <persNames>, or with the @sort attribute:
<pre>
<person>
<persName sort="2">
<surname>Hudson</surname>
<forename>Saul</forename>
</persName>
<persName type="pseudo" sort="1">Slash</persName>
</person>
</pre>

This could then mean that the pseudonym is the 'canonical' name for this person.

Another question is whether the actual name should then be typed as @type='real'?

===Alternative Names===
A related issue arises when people are commonly known by another name than their real name. For example, Joe English, a Belgian painter, is actually called Joseph English. I wonder whether a regularisation with <reg> would be the most suitable solution to encode this?

<pre>
<person>
<persName>
<reg>English, Joe A.M.</reg>
<surname>English</surname>
<forename>Joseph A.M.</forename>
</persName>
</person>
</pre>

==Mixing Prose and Structure==
The TEI P5 Guidelines define the contents <person> as either a collection of highly structured biographical 'fields' (using dedicated elements like <trait>, <occupation>, ...), or a collection of loose prose paragraphs (). Especially when transforming existing biographical records to TEI P5, this exclusive alternation can be unsatisfactory:
* splitting up all biographical prose into biographical fields may be too demanding
* OTOH, choosing to retain the description in prose paragraphs also prohibits the specification of basic biographical data in specific fields (<birth>, <death>, <persName>) inside <person>

One (tentative) solution could be to extract record-like information into biographical fields, while grouping the prose descriptions as paragraphs into a <note> element:

<pre>
<person xml:id="FJ">
<persName>
<reg>Fabricius, Jan</reg>
<surname>Fabricius</surname>
<forename>Jan</forename>
</persName>
<birth when="1871-09-30">
<placeName>Assen</placeName>
<date>30.09.1871</date>
</birth>
<death when="1964-11-23">
<placeName>Wimborne, Dorset</placeName>
<date>23.11.1964</date>
</death>
<note type="bio">
Journalist, Nederlands toneelschrijver.
Vader van de schrijver Johan Fabricius. Hoofdredacteur van verschillende bladen, zowel in Nederlands-Indië als in Nederland.
In 1938 vestigde hij zich in Engeland. Hoewel Fabricius op latere leeftijd ook enkele romans en drie delen memoires heeft
gepubliceerd, ligt zijn betekenis in zijn toneelwerk. Zijn technische vaardigheid en meesterschap in het schrijven van een
dialoog, maken zijn stukken goed speelbaar. Kind van een tijd die het realisme beoefende (Heijermans, Hauptmann), kon hij
toch niet de romantiek geheel laten varen. Het handelingsverloop is vaak gewild; er wordt dan bewust aangestuurd op een
aandoenlijke werking, zodat sommige van zijn stukken het predikaat 'melodramatisch' verdienen. Gedreven door een sterk gevoel
voor rechtvaardigheid zocht hij zijn gegevens in de problematiek van milieus die hem vertrouwd waren: het boerenland van
Groningen en Drente, de planterswereld van Indië. Fabricius' werk werd in Nederland en ook in het buitenland met succes opgevoerd.
Tot zijn bekendste werken behoren <title>Eenzaam</title> (1907) en <title>Dolle Hans</title> (1916). Sommige stukken zijn vertaald
in het Frans, Duits, Engels, Noors, Deens, Fries en Gronings.

</note>
<note type="ref">

<ptr ref="http://www.dbnl.org/auteurs/borkv/Fabr004.htm"/>

</note>
</person>
</pre>

This allows to group other types of information into other notes as well, distinguished by means of appropriate values for their @type attributes.

==Traits, States, and Events==
The Guidelines use traits, states, and events as basic categories. Traits differ from states in being generally immutable. It may be that the distinction between states and traits is unnecessary. Almost every member of model.persTraitLike (age faith langKnowledge nationality s*x socecStatus trait) can change. Why have traits when states will do? This would simply leave states and events for describing a person, organization, etc. Every change of state could have an associated event.

==Relations==
At the moment, relations are defined by attributes such as name, active and passive:

<pre><relation name="parent" active="#p1 #p2" passive="#p3 #p4"/></pre>

[[Category:Markup]]

Samples of TEI texts

2010-10-25T01:55:26Z

Tfinney: /* Texts */

[[Category: Markup]]
[[Category: TEI:P4]]
[[Category: TEI:P5]]
Please add links below to any TEI sample texts that are freely available for use by developers working on TEI-related software. By listing the texts here you are allowing the developers the right to test their software with your texts, but are not necessarily licensing any other use of these texts. Developers should ask permission of the text owners should they wish to make any more in-depth use of these materials.

== Texts ==

* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ala2004] ([[EpiDoc]] XML) from the [http://insaph.kcl.ac.uk/ala2004 '''Aphrodisias in Late Antiquity'''] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)

* [http://archimedespalimpsest.net/ '''Archimedes Palimpsest'''], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5

* [http://www.ota.ox.ac.uk/headers/2493.xml The '''Auchinleck Manuscript'''], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.

* [http://papyri.info/idp_static/current/ '''Duke Databank'''/Heidelberg] ([[EpiDoc]] XML) aggregated data from the Duke Databank of Documentary Papyri (DDbDP: transcribed Greek texts) and the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV: metadata). Approx 55,000 XML files released under Creative Commons Attribution license (CC-BY), by the [http://idp.atlantides.org/trac/idp/wiki Integrating Digital Papyrology] project. Format: TEI P5.

* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html '''EpiDoc Demo''' Website], a growing collection of sample [[EpiDoc]] XML files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)

* A subset of [http://www.gutenberg.org/ Project '''Gutenberg'''] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.

* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html '''IAph2007''' ([[EpiDoc]] XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)

* [http://irt.kcl.ac.uk/irt2009/inscr/xmlrepo.html '''Inscriptions of Roman Tripolitania''' 2009] ([[EpiDoc]] XML), about 1000 Latin and Greek inscriptions available for download under Creative Commons Attribution (CC-BY) licence. Format: TEI P4.

* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "'''Manuscript Markup'''," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/assets/U16/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/assets/U16/U16.xsl transform], a [http://www.sbl-site.org/assets/U16/U16.css stylesheet] and a [http://www.sbl-site.org/assets/U16/U16.htm web page] produced from the transcription by the transform. (Format: TEI P5)

* The [http://www.nzetc.org/ NZETC] has a range of '''New Zealand and Pacific-Islands''' texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:
** Use of <revisionDesc> and <change> tags to implement workflow
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).

* The [http://www.perseus.tufts.edu/hopper/opensource Perseus Project] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.

* The [http://buddhistinformatics.chibs.edu.tw/BZA/bzaComCatWeb.html '''Samyukta Agama''' Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. This is an ongoing project, planned to end in winter 2008. Once the project is concluded markup documentation, schemas and stylesheets will be made available at the website.

* The [http://www.tei-c.org/Activities/MI/Samples/ '''Migration Samples'''] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.

* The [http://www.bvh.univ-tours.fr/ BVH] project ('''Virtual Humanistic Libraries''') is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr/Epistemon/index.htm Epistemon]. These files are licenced under Creative Commons Attribution.

* Some work is ongoing about the possibility to use the TEI to edit and archive [http://www.iso.org ISO] documents. Relevant tips and documentation are provided under [[TEI for ISO]]

* TEI in dspace example http://dspace.nitle.org/handle/10090/11695 (P4?)

* The [[http://sarit.indology.info SARIT]] project has recently brought out an electronic TEI-encoded edition of a 2007 print publication. It is a work on Buddhist tantric religion: Christian K. Wedemeyer, ed., ''Āryadeva's Lamp that Integrates the Practices (Caryāmelāpakapradīpa): The Gradual Path of Vajrayāna Buddhism According to the Esoteric Community Noble Tradition - Part Three: Critically Edited Sanskrit Text of Āryadeva's Caryāmelāpakapradīpa,'' (New York: The American Institute of Buddhist Studies at Columbia University in New York with Columbia University's Center for Buddhist Studies and Tibet House US, 2007). E-details and full text can be seen [[http://sarit.indology.info/newphilo/navigate.pl?indologica.6 here]]. Clicking [[http://sarit.indology.info/downloads.shtml Downloads]] on the above screen offers downloadable TEI, PDF and HTML versions of this e-text, and several others. The interesting thing about this e-text from the TEI point of view is the encoding and display of the manuscript variants to the critical edition. It was good of the publishers and editors to give their permission for the e-dissemination of this work just three years after print publication. Best, Dr Dominik Wujastyk.

== Dictionaries ==
* [[FreeDict]] is a repository of various TEI P4-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Some are now in P5, for example http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/swa-eng/swa-eng.tei
* [http://ducange.enc.sorbonne.fr/ Du Cange] is a medieval latin dictionary (mostly written during XVIIe XVIIIe). The printed text is encoded in TEI-P5, freely available at http://ducange.enc.sorbonne.fr/src/, the TEI choices are [http://ducange.enc.sorbonne.fr/src/schema.htm documented] (in french).

== See also ==
* [[TEI by example]]

Samples of TEI texts

2010-10-25T01:53:11Z

Tfinney: /* Texts */

[[Category: Markup]]
[[Category: TEI:P4]]
[[Category: TEI:P5]]
Please add links below to any TEI sample texts that are freely available for use by developers working on TEI-related software. By listing the texts here you are allowing the developers the right to test their software with your texts, but are not necessarily licensing any other use of these texts. Developers should ask permission of the text owners should they wish to make any more in-depth use of these materials.

== Texts ==

* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ala2004] ([[EpiDoc]] XML) from the [http://insaph.kcl.ac.uk/ala2004 '''Aphrodisias in Late Antiquity'''] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)

* [http://archimedespalimpsest.net/ '''Archimedes Palimpsest'''], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5

* [http://www.ota.ox.ac.uk/headers/2493.xml The '''Auchinleck Manuscript'''], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.

* [http://papyri.info/idp_static/current/ '''Duke Databank'''/Heidelberg] ([[EpiDoc]] XML) aggregated data from the Duke Databank of Documentary Papyri (DDbDP: transcribed Greek texts) and the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV: metadata). Approx 55,000 XML files released under Creative Commons Attribution license (CC-BY), by the [http://idp.atlantides.org/trac/idp/wiki Integrating Digital Papyrology] project. Format: TEI P5.

* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html '''EpiDoc Demo''' Website], a growing collection of sample [[EpiDoc]] XML files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)

* A subset of [http://www.gutenberg.org/ Project '''Gutenberg'''] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.

* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html '''IAph2007''' ([[EpiDoc]] XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)

* [http://irt.kcl.ac.uk/irt2009/inscr/xmlrepo.html '''Inscriptions of Roman Tripolitania''' 2009] ([[EpiDoc]] XML), about 1000 Latin and Greek inscriptions available for download under Creative Commons Attribution (CC-BY) licence. Format: TEI P4.

* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "'''Manuscript Markup'''," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/assets/U16/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/assets/U16/U16.xsl transform], a [http://www.sbl-site.org/assets/U16/U16.css stylesheet] and a [http://www.sbl-site.org/assets/U16/U16.html web page] produced from the transcription by the transform. (Format: TEI P5)

* The [http://www.nzetc.org/ NZETC] has a range of '''New Zealand and Pacific-Islands''' texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:
** Use of <revisionDesc> and <change> tags to implement workflow
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).

* The [http://www.perseus.tufts.edu/hopper/opensource Perseus Project] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.

* The [http://buddhistinformatics.chibs.edu.tw/BZA/bzaComCatWeb.html '''Samyukta Agama''' Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. This is an ongoing project, planned to end in winter 2008. Once the project is concluded markup documentation, schemas and stylesheets will be made available at the website.

* The [http://www.tei-c.org/Activities/MI/Samples/ '''Migration Samples'''] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.

* The [http://www.bvh.univ-tours.fr/ BVH] project ('''Virtual Humanistic Libraries''') is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr/Epistemon/index.htm Epistemon]. These files are licenced under Creative Commons Attribution.

* Some work is ongoing about the possibility to use the TEI to edit and archive [http://www.iso.org ISO] documents. Relevant tips and documentation are provided under [[TEI for ISO]]

* TEI in dspace example http://dspace.nitle.org/handle/10090/11695 (P4?)

* The [[http://sarit.indology.info SARIT]] project has recently brought out an electronic TEI-encoded edition of a 2007 print publication. It is a work on Buddhist tantric religion: Christian K. Wedemeyer, ed., ''Āryadeva's Lamp that Integrates the Practices (Caryāmelāpakapradīpa): The Gradual Path of Vajrayāna Buddhism According to the Esoteric Community Noble Tradition - Part Three: Critically Edited Sanskrit Text of Āryadeva's Caryāmelāpakapradīpa,'' (New York: The American Institute of Buddhist Studies at Columbia University in New York with Columbia University's Center for Buddhist Studies and Tibet House US, 2007). E-details and full text can be seen [[http://sarit.indology.info/newphilo/navigate.pl?indologica.6 here]]. Clicking [[http://sarit.indology.info/downloads.shtml Downloads]] on the above screen offers downloadable TEI, PDF and HTML versions of this e-text, and several others. The interesting thing about this e-text from the TEI point of view is the encoding and display of the manuscript variants to the critical edition. It was good of the publishers and editors to give their permission for the e-dissemination of this work just three years after print publication. Best, Dr Dominik Wujastyk.

== Dictionaries ==
* [[FreeDict]] is a repository of various TEI P4-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Some are now in P5, for example http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/swa-eng/swa-eng.tei
* [http://ducange.enc.sorbonne.fr/ Du Cange] is a medieval latin dictionary (mostly written during XVIIe XVIIIe). The printed text is encoded in TEI-P5, freely available at http://ducange.enc.sorbonne.fr/src/, the TEI choices are [http://ducange.enc.sorbonne.fr/src/schema.htm documented] (in french).

== See also ==
* [[TEI by example]]

U16.xsl

2008-04-29T04:37:06Z

Tfinney:

== Summary ==

This converts a TEI P5 transcription of part of a biblical manuscript to HTML. It makes use of the msDescription element.

== Required Input ==

The input is a TEI P5 transcription of part of a biblical manuscript found [http://purl.org/tfinney/Freer/U16.xml here].

== Expected Output ==

An HTML version of the transcription.

== Known Restrictions or Problems ==

This is only known to work with the transcription linked above.

== Stylesheet ==

The stylesheet is found [http://purl.org/tfinney/Freer/U16.xsl here].

[[Category:XSLT]]

U16.xsl

2008-04-29T04:25:21Z

Tfinney: New page: == Summary == This is a quick XSLT script for removing the namespaces from any document. It will remove the prefix as well. I think I picked it up off the XSL-List run by mulberry-tech. ...

== Summary ==
This is a quick XSLT script for removing the namespaces from any document.
It will remove the prefix as well. I think I picked it up off the XSL-List
run by mulberry-tech. This is sometimes a good first step to remove namespaces
from a set of files some of which use namespaces and some of which don't.

Add any comments to the 'discussion' tab.

== Required Input ==

This document will take any XML file, not just TEI XML, and remove a namespace from it if it exists.
If there are entities in the document, these will naturally be expanded.

== Expected Output ==

Same document, but with the namespaces and namespace prefix removed.

== Known Restrictions or Problems ==
Obviously, if you need the namespaces then this might not be as useful to you. For example, where
you have documents which use elements from different namespaces with the exact same local-name (for example,
TEI's <title> and HTML's <title> then flattening the document to remove
namespaces would be problematic.

== Stylesheet ==
<pre>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" indent="no"/>

<xsl:template match="/|comment()|processing-instruction()">
<xsl:copy>
<xsl:apply-templates/>
</xsl:copy>
</xsl:template>

<xsl:template match="*">
<xsl:element name="{local-name()}">
<xsl:apply-templates select="@*|node()"/>
</xsl:element>
</xsl:template>

<xsl:template match="@*">
<xsl:attribute name="{local-name()}">
<xsl:value-of select="."/>
</xsl:attribute>
</xsl:template>
</xsl:stylesheet>
</pre>

[[Category:XSLT]]

Samples of TEI texts

2007-09-26T02:25:27Z

Tfinney: /* Texts */

[[Category: Markup]]
[[Category: TEI:P4]]
[[Category: TEI:P5]]
= Samples of TEI Texts =

Please add links below to any TEI sample texts that are freely available for use by developers working on TEI-related software. By listing the texts here you are allowing the developers the right to test their software with your texts, but are not necessarily licensing any other use of these texts. Developers should ask permission of the text owners should they wish to make any more in-depth use of these materials.

== Texts ==

* [http://www.ota.ox.ac.uk/texts/2493.html The Auchinleck Manuscript], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.

* The [http://www.tei-c.org/Activities/MI/Samples/ Migration Samples] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.

* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "Manuscript Markup," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/Resources/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/Resources/U16.xsl transform], a [http://www.sbl-site.org/Resources/U16.css stylesheet] and a [http://www.sbl-site.org/Resources/U16.html web page] produced from the transcription by the transform.