TEIWiki - User contributions [en]

File:Jtei-oxygen-dist.zip

2015-03-13T23:18:48Z

Rvdb: uploaded a new version of "File:Jtei-oxygen-dist.zip": updated to latest version

(Package of encoding tools (ODD file, documentation, schemas, and rendering tools) in the form of an Oxygen project, for authors wishing to submit articles to the Journal of the Text Encoding Initiative in TEI P5 XML.)

File:Jtei-oxygen-dist.zip

2015-03-13T23:18:26Z

Rvdb: uploaded a new version of "File:Jtei-oxygen-dist.zip": Reverted to version as of 19:06, 14 November 2014

File:Jtei-oxygen-dist.zip

2015-03-13T23:17:54Z

Rvdb: uploaded a new version of "File:Jtei-oxygen-dist.zip"

File:Jtei-oxygen-dist.zip

2014-10-13T19:00:39Z

Rvdb: uploaded a new version of "File:Jtei-oxygen-dist.zip": small fixes do documentation and Schematron feedback messages

Package containing authoring tools for creating an article for the Journal of the TEI in TEI XML.

SIG:Correspondence/RequestForModule

2012-11-08T07:55:14Z

Rvdb: /* Wrapper Element for Correspondence Meta Data */ corrected typo

< back to [[SIG:Correspondence]]

==Request for a correspondence module and a wrapper element for correspondence meta data==

===Introduction===

It was in 2008 at the London TEI Members' meeting when the SIG on Correspondence held its first meeting. On the SIG's agenda has since then been the creation of a dedicated ODD file for documenting a best practice model of encoding correspondence material. There have been several P4 projects with a dedicated correspondence schema but the Carl-Maria-von-Weber-Gesamtausgabe (WeGA) was---to my knowledge---the first to publish a P5 schema.<ref>http://wiki.tei-c.org/index.php/SIG:Correspondence/ODD_work</ref>

Meanwhile Ron van den Branden has published a (preliminary) DALF P5 proposal<ref>http://ctb.kantl.be/project/dalf/P5/DALF_P5-p0.1.zip</ref>
which in fact has several parts in common with the WeGA schema. Hence I think it is time to merge the comparable parts into the standard TEI schema.

I do actually tentatively propose (only) two things which I think to be widely acceptable and so shall be discussed during our meeting:

* a correspondence module
* a wrapper element for correspondence meta data

If there was positive agreement about these issues by the group, this proposal can then be elaborated as a feature request to the TEI technical council and will hopefully make it into the TEI standard.

===Correspondence Module===

Both ODD schemata (DALF and WeGA) define a special purpose module for grouping together their additions to the vanilla TEI schema. This module simply serves as a (virtual) container for any new element or class etc. and would facilitate future additions. If there was agreement to introduce such a module, the only issue would probably be the name. Since the SIG is named "Correspondence" and the term is broader than "Letter", I do favor this one. On the other hand there is a possible clash with the attribute @corresp that could lead to misinterpretation.

===Wrapper Element for Correspondence Meta Data===

Another common denominator of the two schemata is their addition of a special purpose element <dalf:letDesc> or <wega:correspDesc> respectively. Both elements are injected into <sourceDesc> and act as a wrapper element for information regarding the sender, addressee, place of sender etc. Their is one little structural difference though: while the WeGA schema introduces <wega:sender>, <wega:addressee> etc. directly within <wega:correspDesc>, DALF has an intermediate <dalf:letHeading>.

Hence I do propose an element <''wrapper''> (it should be decided on the real tag name during the meeting) with the following content:

* sender(s)
* addressee(s)
* place of sender(s)
* place of addressee(s)
* start date of shipment (= when was it sent by the sender)
* end date of shipment (= when was it received by the addressee)

While I do think that agreement can be reached about the overall goal, I do see a lot of points that need to be discussed:
# where to put <''wrapper''>? While both schemata put it into <sourceDesc>, one could argue as well to put it into <profileDesc>.
# What structure to adopt for <''wrapper''>? A flat one as it is done by the WeGA or a deeper one as modeled by DALF?
# Tag names, content models etc. need to get fleshed out. While we could decide about some sort of a naming convention maybe, the actual ODD definitions need to be developed after the meeting most likely (due to time constraints).

===Notes===
<references />

TEI LookUp

2011-11-18T19:41:02Z

Rvdb: /* User commentary */ added reference to updated version in TEI-L

[[Category:Tools]]

[[Category:Development tools]]

== Synopsis ==
# A javascript pop-up query which brings up the page of information for the element/attribute/class/datatype/etc. you choose (from www.tei-c.org). It should also work if you first highlight the name of an element on a webpage.
# A javascript pop-up query which brings the element spec from the eXist database (on tei.oucs.ox.ac.uk). It should also work if you first highlight the name of an element on a webpage.

== Features ==
* javascript bookmarklet
* swift navigation to TEI reference pages

== User commentary ==
'''Please sign all comments.'''

This is a basic search bookmarklet derived from http://www.bookmarklets.com/mk.phtml which allows users to construct their own javascript bookmarklets as long as the search term appears in the url somewhere. [[User:James|James]] 05:13, 4 July 2008 (EDT)

The original version works up to Firefox 8.0, which apparently introduced some subtle changes in its Javascript engine. Fortunately, Martin Holmes has found out a fix and kindly posted it on the [http://markmail.org/message/wq32ia3gbxxb4coj TEI-L] mailing list. [[User:Rvdb|Rvdb]]

== System requirements ==
* Mozilla Firefox

== Source code and licensing ==

The web page and its content are all licensed Creative Commons Attribute, ver. 3.0 Unported

== Support for TEI ==

It assists users to look things up in the public TEI documentation quickly.

== Language(s) ==

The language of english is hard-coded in the URL, however users may change this to any of the internationalised versions of the TEI, and it might work.

== Documentation ==

Only documentation is the web page at http://james.cummingsfamily.org.uk/TEI/TEI-LookUp.html

== Tech support ==
[[User:James]] is happy to take suggestions, corrections, improvements, etc. But it isn't really meant to be a heavy tool!

== User community ==

== Current version number and date of release ==
Version 1.0, 31 October 2007.

== History of versions ==
Version 1.0 -- update to confirm everything works with released TEI P5 ver. 1.0.
Version 0.9 -- update to work with slight change of package layout
Version 0.1 -- initial release

== How to download or buy ==

http://james.cummingsfamily.org.uk/TEI/TEI-LookUp.html

== Additional notes ==

c.f. http://james.cummingsfamily.org.uk/TEI/TEI-LookUp.html

SIG:Correspondence

2011-10-15T12:44:42Z

Rvdb: /* Completed Projects */

== News ==

* I created a [[SIG:Correspondence/ODD_work|new page]] for the discussion of a ''correspondence odd file''--[[User:Pstadler|pstadler]] 09:43, 4 July 2011 (EDT)

== Introduction ==
The TEI Special Interest Group on Correspondence seeks to bring together scholars interested in creating digital scholarly editions of correspondence. The goal of the SIG will be to discuss and develop sample tagsets (including suggesting additions/modifications to the TEI Guidelines) for varying forms of correspondence as well as to create tutorials and best practice models.

Because the initiative for this SIG emerged from editorial work with 19th century letters, the organizers of this SIG have focused on these types of materials. However, we want this SIG to be more encompassing, embracing varying types of historical and literary correspondence including epistles, telegrams, postcards, etc., and perhaps other types of documents that share features with physical written correspondence like diaries, diary entries, letters to the editor, e-mail, blogs, etc.

The common feature of these sorts of text is a generally formalized physical appearance (e.g., an envelope for letters) and structure of content (i.e. address field, special formulas for opener and closer). [http://www.tei-c.org/Activities/Projects/da03.xml DALF] was one of the best documented projects in this area developing specific DTDs for those needs in P4: this may be a starting point for further work in P5.

Initial topics for the SIG Correspondence may include:
* the handling of the envelope and postal addresses
* the formal description of correspondence as a written dialogue between an author and an addressee
* correspondence-specific bibliographical data within the metadata section

== Activities ==

The SIG runs a mailing list, which you can join by visiting http://listserv.brown.edu/tei-corresp-sig.html .

=== Topics currently under discussion ===
* The content of a special '''correspDesc''' element
* The content model of '''postscript''': look at the [[Collection of Postscript-Examples]] and the contributions to the [[ps-discussion]].
* How to deal with '''enclosures''' or '''attachements''' to a letter
* The content model of opener/closer and their connection with salute, signed, dateline, etc.
* diary entries
* definition of <signed> does not correspond with its actual use in the P5 guidelines
* address now in but not in <div>: maybe not a good idea
* notification of addresses (different in different parts of the world). Could this be handled more adequately than just with datelines?

=== Meetings ===

==== Wuerzburg, Oct 15, 2011 ====

The meeting at Wuerzburg will be on Oct 15, 2011 from 9am to 10:30am in room 1.003. Proposal of an Agenda:
* 1. New members / projects / demands
* 2. Short survey of the development of the SIG and the topics discussed
* 3. Views of the group about proposing a <correspDesc> (or similar) element or not
* 4. Future activities of the SIG: P5-Customizations for Correspondence ("Dalfy" et al.) / Special Guidelines (TEI by example) / Proposals / Next Steps
* 5. Roadmap for 2012
* 6. Website and Wiki

==== Zadar, Nov 13, 2010 ====

Participation: around 5 people

1. Peter gave a report on last year's activities
* Task force ‘Dalfy’ was established after the Ann Arbor Meeting: Markus Flatscher, Bert Van Raemdonck, Peter Stadler
* Goal: Mapping of DALF (P4) to TEI P5 as a basis for further work on a correspondence customization
* But: Momentum got lost …
* Further: Some discussion on TEI-L about "signed vs. salute"

2. A brief look on open questions
* Correspondence meta data: correspDesc?
* The content model of postscript (cf. the Collection of Postscript-Examples and the contributions to the ps-discussion.)
* The content model of opener/closer and their connection with salute, signed, dateline, byline etc.

3. Attempt to create a roadmap for 2011
* Peter suggested a second attempt for a grant to achieve the mapping of DALF to P5
* Discussion about possible fundings for such an attempt
* review of the last failed TEI grant proposal: it was criticized by the present panel members that no preliminary work was (visibly) carried out
* Susan suggested to first initiate a survey on the correspondence list

4. AOB
* nothing

==== Ann Arbor, Nov 14, 2009 ====

Business and working meeting during the annual members meeting.
'''Participants''': Syd Bauman (SB), Markus Flatscher (MF), Elena Pierazzo (EP), Malte Rehbein (MR), Paul Schaffner (PSc), Peter Stadler (PSt), Bert Van Raemdonck (BV)

The business meeting was attended by MF, PSc, PSt and BV and - since the number of participants allowed it - was an informal talk about the different projects, the last meeting at London and the "correspDesc" PS had proposed there as well as the question whether editing correspondence from printed (secondary) material needs to treated differently than correspondence from manuscript source material. Work on the roadmap was postponed to the working meeting.

The working meeting was attended by all above mentioned participants who agreed on the need for a customization of some of the P5 elements (and element classes) for encoding correspondence. Question is of course: how?
* P5 has introduced some elements that were inspired by what had been done earlier in DALF (P4), but not all P4 customizations in DALF are actually rendered in P5 (and vice versa). Hence, a comparison of both should be a good starting point to eventually come to a new ODD for encoding correspondence, and maybe even for introducing an actual module for future TEI Guidelines.
* MF, PSt and BV agree on doing such a mapping together. Since BV is like the only DALF original left, he will coordinate this: he will split the work up, and will be contacting MF and PSt for further arrangements. [UPDATE: Edward Vanhoutte and Ron Van den Branden agreed to work on this with BV face to face and then get back to MF and PSt afterwards. --[[User:Pstadler|pstadler]] 07:04, 27 November 2009 (EST)]
* Before X-mas, there should be a conference call to catch up on how the mapping proceeds. PSt will contact Dan O'Donnell for funding.
* Bugs and absurdities in P5 regarding correspondence should be posted on Sourceforge. Elena Pierazzo will be the liaison between the SIG and the TEI Council. She will help SIG members to report our findings through Sourceforge or otherwise.
* The mapping should result in a new ODD. SB is willing to help us create it. The new ODD should somehow be more or less DALF-like. Hence, the working title of the ODD is 'Dalfy'. Dalfy will be an oddified version of DALF where obviously identical concepts will already be mapped to their P5 equivalents (therefore Dalfy != DALF).
* After the mapping is done, useful elements (or concepts, structures) that are neither in DALF or in P5 yet, should be listed. Members of the SIG are welcome to suggest their own 'favourite missing elements'.
* With Dalfy as starting point we can than try to rearrange and modify it to come to a new Correspondence ODD (no code name yet!) that should resolve all problems and satisfy all needs...
* Issues that came up during the meetings concern <address> (and multiple addresses within one letter) (SB and EP), <signed> (everyone), endorsements as well as correspondence by committee (PSc)
* Besides the work on Dalfy PSt shall finish his work on oddifying his <correspDesc>.
'''Roadmap/Milestones''':
* Before Christmas: Teleconference about the mapping (MF, PSt, BV)
* Febr. 10, 2010: Mapping done
* July, 2010: Next SIG meeting at Digital Humanities conference (London) on new ODD

[Minutes PSt and BV]

==== London, Nov 8, 2008 ====

The first section (14-15:30) saw short presentations of current projects by:
* Tim McLoughlin: James Barry's letters
* Hilde Bøe: eMunch project (assisted by Ellen Nessheim Wiger with the Henrik Ibsen correspondence)
* Peter Boot: correspondence of Vincent van Gogh
* David Sewell: correspondence projects published via ROTUNDA
* Deborah K. Wright: correspondence of Matthew Prior
* Peter Stadler: correspondence of Carl Maria von Weber

The second section (16-16:45) had to be shortened due to organisational necessities but saw general discussion about
* the content model of postscript which is rather restricted and does not allow for an i.e. '''head''' element. Everyone was encouraged to send examples via the list. [Let me add that the same holds true for '''address''' --[[User:Pstadler|pstadler]]]
* the need and the possible content for an '''correspDesc''' element within '''sourceDesc'''. I will try to create an odd file with the necessary additions to the schema as a starting point for further expertise. --[[User:Pstadler|pstadler]].
* correspondence as an event. Lou pointed this out as similar topics were discussed in the ontologies SIG.

== Correspondence Projects ==

Please add your projects alphabetically with link and (if possible) a short description!

=== Ongoing Projects ===

* [http://gams.uni-graz.at/fedora/get/container:rollett/bdef:Container/get The Letters of Alexander Rollett]. A project of the Center for Information Modeling in the Humanities (ZIM) at the University of Graz.
* Alfred Escher Correspondence. A project of the Alfred Escher Foundation, Zurich [http://www.alfred-escher.ch (Alfred Escher-Stiftung)]. Edition of the correspondence of Alfred Escher, influential 19th century Swiss politician and entrepreneur (e.g. Credit Suisse, Gotthard railway), comprising several thousand letters. At first, an edition of selected letters to and from Escher will be published in book form, including rich annotations. The first volume of the series is already available. Later on, the correspondence of Alfred Escher will be made available online. The correspondence covers topics as diverse as politics, economics, education, railways, banks, insurance.
* Digital Archive of Letters in Flanders authors and composers from the 19th & 20th century, [http://www.kantl.be/ctb/project/dalf/ DALF]
* ''Emily Dickinson's Correspondences'' (public version not yet online), to be published under the [http://rotunda.upress.virginia.edu Rotunda] imprint by University of Virginia Press. An edition of selected correspondence to and from American poet Emily Dickinson, with MS facsimiles and rich metadata capturing physical details of the manuscripts.
* Gundolf-Elli. Correspondence between Friedrich Gundolf and Elisabeth Salomon (George-Kreis). Project at the German Literature Archive. There is no website, yet. For more information use the mailing list.
* eMunch. Edvard Munch's written material: Complete letters, diaries and writings, [http://www.emunch.no/eng/index.htm] (Updated and expanded 15.06.2009)
* Weber, C.M.v.: Complete letters, diaries, writings and compositions, [http://www.weber-gesamtausgabe.de/ Carl-Maria-von-Weber-Gesamtausgabe] (at the moment german only)

=== Completed Projects ===
* [http://rotunda.upress.virginia.edu/dmde The Dolley Madison Digital Edition], part of the University of Virginia Press's [http://rotunda.upress.virginia.edu/ Rotunda] series. This is an ongoing publication, but the first two "volumes" are online. Currently the underlying data is tagged using the [http://adh.sc.edu/ Model Editions Partnership] variant of TEI (P4), but we are also exporting and transforming the documents to TEI P5 for interoperability with other material. (Contact: [mailto:dsewell@virginia.edu David Sewell])
* [http://www.vnsbrieven.org/VNS/?lang=en Van Nu en Straks: Brieven / Letters], Online edition of the correspondence concerning the literary journal 'Van Nu en Straks' (1419 letters). The annotated letters contain references to ca 2500 persons, 500 places, 1000 titles of books, 650 journal articles and 350 poems. A network of 3600 hyperlinks facilitates intuitive and associative consulting. Project at the [http://www.ctb.kantl.be Centre for Scholarly Editing and Document Studies] / Royal Academy of Dutch Language and Literature (KANTL-CTB, Ghent-Belgium) and Ghent University (Belgium). This project is part of the broader [http://www.kantl.be/ctb/project/dalf/ DALF-project].
* [http://www.vangoghletters.org/vg/ Vincent van Gogh, The letters]. A full edition of all the extant correspondence of Vincent van Gogh (900 letters). The edition includes full transcriptions (in Dutch and French), translation into English, facsimiles, extensive annotations and about 2000 illustrations.

[[Category:SIG|Correspondence]]

EXist

2011-04-27T20:16:30Z

Rvdb: /* Sample implementations */ added current CTB web applications (see http://ctb.kantl.be/)

[[Category:Tools]]

[[Category:Querying tools]]
[[Category:Publishing and delivery tools]]
[[Category:XQuery]]

== Synopsis ==
[http://exist.sourceforge.net/ eXist] is a Native XML Database, used for storing and querying XML files. Since the first versions, made available between 2000 and 2001, eXist has considerably evolved, thanks also to an active community of developers and users, and in its latest releases, it has several functions, such as support for [http://www.w3.org/TR/xquery/ XQuery], [http://www.w3.org/2001/XInclude XInclude] and [http://xmldb-org.sourceforge.net/xupdate/ XUpdate]. Through an integration with [[ApacheCocoon]], [http://www.w3.org/TR/xslt XSLT] processing can be added to the whole workflow, using the pipeline concept of the [http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html Sitemap]. In this way data and documents can be queried and transformed using together, in the same process, [http://www.w3.org/TR/xquery/ XQuery] and [http://www.w3.org/TR/xslt XSLT]. Moreover [http://exist.sourceforge.net/ eXist] can be integrated as a block in [[ApacheCocoon]], so to use all the modules of this framework, and not the limited version shipped with this database. Recently, starting from version 1.1, [http://exist.sourceforge.net/ eXist] has changed the indexing core, becoming more efficient in being used with complex document-centric files, such as TEI encoded texts.

== Features ==
* Persistent storing and indexing of the XML documents
* Database administration functions (data management, backup, recoveries)
* Management of the stored documents in collections
* XQuery engine with extentions for full-text search
* Support for XQuery, XSLT, XInclude and XPointer (partial), XUpdate
* [http://xmldb-org.sourceforge.net/xapi/ XMLDB Api]
* Use of network protocols (HTTP/REST, XML-RPC, SOAP, WebDAV)
* Integration with [[ApacheCocoon]]

== User commentary ==
'''Please sign all comments.'''

Can be very sensitive to placement of certain files, in particular collection.xconf. Silently ignores config files in the wrong place. [[User:Stuartyeates|Stuartyeates]] 18:15, 26 April 2011 (EDT)

== System requirements ==
eXist is written in Java, and therefore requires a [http://java.sun.com/javase/downloads/index.jsp JDK] > 1.4. Being a Java application it can be used on most operating systems, from Windows 2000/XP to Linux or Mac OS X, and it can be deployed in several ways, as a standalone application, as a web application inside a servlet container (such as [http://tomcat.apache.org/ Apache Tomcat] or [http://www.mortbay.org/ Jetty]) or as a Java library in a larger application.

== Source code and licensing ==
eXist is open-source, released under the [http://www.gnu.org/copyleft/lesser.html GNU LGPL] license.

== Support for TEI ==
Support for TEI is not out of the box, meaning that in the standard distribution there are not ready to use XQuery or XSLT files for TEI documents, even as examples. Notwithstanding implementation with TEI is really straightforward and there are several applications based on this software. In particular the development of the new indexing core, for a better management of complex document-centric file, such as TEI documents, has been supported by the TAPoR node of [http://tapor.uvic.ca/home.php University of Victoria].

== Language(s) ==
As wrote before, eXist is a Java application. Anyway, whole applications can be created without writing any line of programming code, but using only XQuery, XSLT, (X)HTML, CSS and Javascript. Using the available network interfaces is possible to query eXist not only with Java, and there are already available several modules for other languages ([http://www.bmuskalla.de/DB_eXist/ PHP], [http://query-exist.sourceforge.net/ Perl]) and frameworks ([http://sourceforge.net/projects/springxmldb/ Spring], [http://www.throwingbeans.org/tech/xml_databases_with_exist_and_coldfusion.html ColdFusion], [http://www.zope.org/Members/spilloz/existda Zope]).
The [http://exist-db.org/documentation.html documentation] is available only in english.

== Documentation ==
http://exist-db.org/documentation.html

== Tech support ==
Technical support is provived mainly throught the [http://sourceforge.net/mail/?group_id=17691 mailing list]. Being eXist open-source all kind of support and help is made voluntarily and with no obligations. Anyway the support it is very efficient, and almost all the requests are answered in a complete and qualified way.

== User community ==
The user community is very active and, as for the technical support, the main way of communication is the [http://sourceforge.net/mail/?group_id=17691 mailing list]. Many participants of this list are also part of the TEI Community. There is also a [http://wiki.exist-db.org wiki] and an IRC channel: #existdb at irc.freenode.net.

== Sample implementations ==
* [http://demo.exist-db.org/examples.xml official demo] (without TEI related examples)
* [http://web.uvic.ca/hrd/achallc2005/abstracts.htm ACH/ALLC 2005: Conference Program and Abstracts]
* [http://www.tapor.uvic.ca:8080/cocoon/graves/ Diary of Robert Graves]
* [http://193.204.255.27/operaliber/index.php?page=/operaLiber/home OperaLiber]
* [http://www.anglo-norman.net/ The Anglo-Norman Dictionary]
* [http://mith2.umd.edu/eada/ Early Americas Digital Archive]
* [http://buddhistinformatics.ddbc.edu.tw/BZA/ A Digital Comparative Edition and Translation of the Shorter Chinese Saṃyukta Āgama]
* [http://history.state.gov/ Foreign Relations of the United States and other publications of the Office of the Historian, U.S. Department of State]
* [https://github.com/stuartyeates/He-Kupu-Tawhito Multilingual Concordances with TEI]
* [http://vnsletters.org/VNS/ VNS letters online]: digital edition of letters concerning the Belgian literary journal 'Van nu en Straks'
* [http://ctb.kantl.be/corpora/CPWNL/ Corpus Pieter Willems]: searchable facsimile edition of the first Dutch dialect survey ever
* [http://tbe.kantl.be/TBE/xquery/TBEvalidator.xq TEI validator]: interactive validating app for TEI documents using eXist's XML validation functions

== Current version number and date of release ==
eXist 1.4 - 2009-09-08

== How to download ==
[http://exist-db.org/index.html#download http://exist-db.org/index.html#download].

== See also ==
* [[Berkeley DB XML]]
* [[Base-X]]
* [[TEI Web Publishing]]

Prosopography

2010-10-20T08:26:39Z

Rvdb: added category

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.

[[Category:Markup]]

Prosopography

2010-10-20T08:05:20Z

Rvdb: /* Mixing Prose and Structure */ reformatted code

Prosopography

2010-10-20T07:55:30Z

Rvdb: created page

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.