TEIWiki - User contributions [en]

Prosopography

2015-08-02T03:18:24Z

Joewiz: /* Projects */ updated link to william still project - the old one yielded a 404 error

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.

==Projects==

This is a list of projects which have significant prosopography components. Feel free to add your project here. If possible, include links to the XML resources you have created.

*[http://mapoflondon.uvic.ca/ The Map of Early Modern London] ([http://mapoflondon.uvic.ca/PERS1.xml XML personography])
*[http://bcgenesis.uvic.ca/ The Colonial Despatches of BC and Vancouver Island] ([http://bcgenesis.uvic.ca/bios.xml XML personography])
*[http://hsp.org/history-online/digital-history-projects/uncovering-william-stills-underground-railroad The William Still Digital History Project]

[[Category:Markup]]

EXist

2011-08-30T15:53:50Z

Joewiz: /* Support for TEI */ Updated link to 2011 files

[[Category:Tools]]

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

== Synopsis ==

[http://exist.sourceforge.net/ eXist-db] is an open source database management system built using [http://en.wikipedia.org/wiki/XML XML] technology. It stores XML data according to the XML data model and features efficient, index-based XQuery processing.

eXist-db supports many [http://en.wikipedia.org/wiki/Web_2 Web 2.0] technology standards, making
it an excellent platform for developing web-based applications:

*Technologies: [http://www.w3.org/TR/xquery/ XQuery 1.0], [http://www.w3.org/TR/xpath20/ XPath 2.0], [http://www.w3.org/TR/xslt XSLT 1.0] (based on [http://http://xalan.apache.org/ Apache Xalan]) or [http://www.w3.org/TR/xslt20 XSLT 2.0] [http://saxon.sourceforge.net/ Saxon]

*Interfaces: [http://en.wikipedia.org/wiki/Representational_State_Transfer REST], [http://www.webdav.org/ WebDAV], [http://www.w3.org/TR/soap/ SOAP], [http://en.wikipedia.org/wiki/XML-RPC XML-RPC], and [http://en.wikipedia.org/wiki/Atom_(standard) Atom Publishing Protocol]

*XML database specific features: [http://xmldb-org.sourceforge.net/xupdate/index.html XML:DB], [http://xmldb-org.sourceforge.net/xupdate/ XUpdate], [http://exist.sourceforge.net/update_ext.html XQuery update extensions] (to be aligned with the new [http://www.w3.org/TR/xquery-update-10/ XQuery Update Facility 1.0]).

The [http://exist.sourceforge.net/download.html 1.4 version] adds a new full text index based on [http://lucene.apache.org/java/docs/index.html Apache Lucene], a lightweight [http://en.wikipedia.org/wiki/Rewrite_engine URL rewriting] and [http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller Model–view–controller] framework, as well as support for [http://xproc.org/ XProc]. With version 1.4, the XQuery engine has seen a major redesign, resulting in improved performance.

eXist-db is highly compliant with the [http://www.w3.org/TR/xquery/ XQuery standard] (current [http://www.w3.org/XML/Query/test-suite/ XQuery Test Suite] score is [http://www.w3.org/XML/Query/test-suite/XQTSReportSimple.html 99.4%]).

The query engine is extensible and features a large collection of [http://demo.exist-db.org/exist/xquery/functions.xql XQuery Function Modules].

eXist-db provides a powerful environment for the development of web applications
based on XQuery and related standards. Entire web applications can be written in
XQuery, using XSLT, XHTML, CSS and Javascript (for AJAX functionality).



== 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 ==
A TEI module distributed as an eXist application is under development. This protoype can be downloaded from [http://exist.svn.sourceforge.net/viewvc/exist/apps/TEIXLingual/?pathrev=14317 Sourceforge]. The app requires eXist 1.5. To install on a Unix-like system, cd into the directory and call ant. This will create a file named "encyclopedia-0.1.xar" inside the build directory. On your local eXist home page, access the Admin panel, click on Package Reposistory, choose the xar file, and upload and install it. The app can now be accessed from [http://localhost:8080/exist/apps/encyclopedia/ http://localhost:8080/exist/apps/encyclopedia/] on a default installation.

The app is not a full-blown TEI module yet, lacking some fairly obvious features, such as display of metadata about the texts displayed and the ability to browse through texts and marked-up items; these features will be added in May-June 2011. The app contains faceted search feeding off the markup, it makes possible "translingual" searches utilising unique (mainly, dbpedia) references added manually to different name forms, it contains an inline (WYMeditor-based) editor for marking up simple TEI (name) structures and supplying them with key attributes, and it has a general ATOM-based commenting function.

The app uses XQuery only; no XSLT is used.

The installation will store a number of very basic TEI documents in the data directory. These files are excepts from encyclopaedias, whence the present name of the app. In order to generate some example results, select lemma and search for "nation", select term and search for "ars", select name and search for "marx", select text and search for "gouvernement", or select key and search for "http://dbpedia.org/page/French_Revolution".

Joe Wicentowski has a step-by-step introduction with full example files on how to publish TEI texts with eXist, presented at the Digital.Humanities@Oxford Summer School in 2011; see the [http://digital.humanities.ox.ac.uk/DHSS2011/sessions.html#xmldb session description, slides, and sample materials].


There is a comprehensive discussion of optimising eXist/xQuery for TEI on [http://exist.2174344.n4.nabble.com/eXist-optimisation-and-large-TEI-collections-td3487406.html the eXist-open mailing list]

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

In August 2011, a dedicated email list was created on using eXist with TEI resources. For information or to subscribe, go to the [https://lists.sourceforge.net/lists/listinfo/exist-teixml eXist-TEIXML] information page.

== Sample implementations ==
* [http://www.weber-gesamtausgabe.de/ Carl-Maria-von-Weber-Gesamtausgabe (WeGA)] The correspondence, diaries, writings and works of Carl Maria von Weber
* [http://web.uvic.ca/hrd/achallc2005/abstracts.htm ACH/ALLC 2005: Conference Program and Abstracts]
* [http://graves.uvic.ca/ 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
* [http://thesaurus.sermones.net/voragine/index.xsp Sermones.net : éditions électroniques de sermons latins médiévaux]: l’édition électronique de corpus de sermons, dont le premier est la série de sermons de Carême de Jacques de Voragine.
* [http://ciham.ish-lyon.cnrs.fr/paleographie/index.php?l=en Interactive Album of Mediaeval Palaeography]: website for training in practical palaeographical skills.
* [http://bcgenesis.uvic.ca/ Colonial Despatches]: the colonial despatches of Vancouver Island and British Columbia 1846-1871.
* [http://mariage.uvic.ca/ Le mariage sous L'Ancien Régime]
* [http://scancan.net/ Scandinavian-Canadian Studies / Études scandinaves au Canada]
* [http://voice.univie.ac.at Vienna-Oxford International Corpus of English]: a corpus of transcripts of spoken ELF interactions in TEI format.



== Current version number and date of release ==
Current stable release: eXist 1.4.0-rev10440 - 2009-11-11

== How to download ==
Download the current stable version (version 1.4, April 2011) from the [http://exist-db.org/index.html#download eXist Home Page]; check out the current trunk version from "svn co <nowiki>https://exist.svn.sourceforge.net/svnroot/exist/trunk/eXist</nowiki>".

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

EXist

2011-05-04T14:32:37Z

Joewiz: /* Support for TEI */ Corrected description of TEI@Oxford presentation

[[Category:Tools]]

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

== Synopsis ==

[http://exist.sourceforge.net/ eXist-db] is an open source database management system built using [http://en.wikipedia.org/wiki/XML XML] technology. It stores XML data according to the XML data model and features efficient, index-based XQuery processing.

eXist-db supports many [http://en.wikipedia.org/wiki/Web_2 Web 2.0] technology standards, making
it an excellent platform for developing web-based applications:

*Technologies: [http://www.w3.org/TR/xquery/ XQuery 1.0], [http://www.w3.org/TR/xpath20/ XPath 2.0], [http://www.w3.org/TR/xslt XSLT 1.0] (based on [http://http://xalan.apache.org/ Apache Xalan]) or [http://www.w3.org/TR/xslt20 XSLT 2.0] [http://saxon.sourceforge.net/ Saxon]

*Interfaces: [http://en.wikipedia.org/wiki/Representational_State_Transfer REST], [http://www.webdav.org/ WebDAV], [http://www.w3.org/TR/soap/ SOAP], [http://en.wikipedia.org/wiki/XML-RPC XML-RPC], and [http://en.wikipedia.org/wiki/Atom_(standard) Atom Publishing Protocol]

*XML database specific features: [http://xmldb-org.sourceforge.net/xupdate/index.html XML:DB], [http://xmldb-org.sourceforge.net/xupdate/ XUpdate], [http://exist.sourceforge.net/update_ext.html XQuery update extensions] (to be aligned with the new [http://www.w3.org/TR/xquery-update-10/ XQuery Update Facility 1.0]).

The [http://exist.sourceforge.net/download.html 1.4 version] adds a new full text index based on [http://lucene.apache.org/java/docs/index.html Apache Lucene], a lightweight [http://en.wikipedia.org/wiki/Rewrite_engine URL rewriting] and [http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller Model–view–controller] framework, as well as support for [http://xproc.org/ XProc]. With version 1.4, the XQuery engine has seen a major redesign, resulting in improved performance.

eXist-db is highly compliant with the [http://www.w3.org/TR/xquery/ XQuery standard] (current [http://www.w3.org/XML/Query/test-suite/ XQuery Test Suite] score is [http://www.w3.org/XML/Query/test-suite/XQTSReportSimple.html 99.4%]).

The query engine is extensible and features a large collection of [http://demo.exist-db.org/exist/xquery/functions.xql XQuery Function Modules].

eXist-db provides a powerful environment for the development of web applications
based on XQuery and related standards. Entire web applications can be written in
XQuery, using XSLT, XHTML, CSS and Javascript (for AJAX functionality).



== 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 ==
A TEI module distributed as an eXist application is under development. This protoype can be downloaded from [http://exist.svn.sourceforge.net/viewvc/exist/apps/TEIXLingual/?pathrev=14317 Sourceforge]. The app requires eXist 1.5. To install on a Unix-like system, cd into the directory and call ant. This will create a file named "encyclopedia-0.1.xar" inside the build directory. On your local eXist home page, access the Admin panel, click on Package Reposistory, choose the xar file, and upload and install it. The app can now be accessed from [http://localhost:8080/exist/apps/encyclopedia/ http://localhost:8080/exist/apps/encyclopedia/] on a default installation.

The app is not a full-blown TEI module yet, lacking some fairly obvious features, such as display of metadata about the texts displayed and the ability to browse through texts and marked-up items; these features will be added in May-June 2011. The app contains faceted search feeding off the markup, it makes possible "translingual" searches utilising unique (mainly, dbpedia) references added manually to different name forms, it contains an inline (WYMeditor-based) editor for marking up simple TEI (name) structures and supplying them with key attributes, and it has a general ATOM-based commenting function.

The app uses XQuery only; no XSLT is used.

The installation will store a number of very basic TEI documents in the data directory. These files are excepts from encyclopaedias, whence the present name of the app. In order to generate some example results, select lemma and search for "nation", select term and search for "ars", select name and search for "marx", select text and search for "gouvernement", or select key and search for "http://dbpedia.org/page/French_Revolution".

Joe Wicentowski has a step-by-step introduction with full example files on how to publish TEI texts with eXist, presented at the TEI@Oxford Summer School in 2010; see [http://tei.oucs.ox.ac.uk/Oxford/2010-07-oxford/materials/workshops/eXist/ oxford/materials/workshops/eXist].


There is a comprehensive discussion of optimising eXist/xQuery for TEI on [http://exist.2174344.n4.nabble.com/eXist-optimisation-and-large-TEI-collections-td3487406.html the eXist-open mailing list]

== 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://graves.uvic.ca/ 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
* [http://thesaurus.sermones.net/voragine/index.xsp Sermones.net : éditions électroniques de sermons latins médiévaux]: l’édition électronique de corpus de sermons, dont le premier est la série de sermons de Carême de Jacques de Voragine.
* [http://ciham.ish-lyon.cnrs.fr/paleographie/index.php?l=en Interactive Album of Mediaeval Palaeography]: website for training in practical palaeographical skills.
* [http://bcgenesis.uvic.ca/ Colonial Despatches]: the colonial despatches of Vancouver Island and British Columbia 1846-1871.
* [http://mariage.uvic.ca/ Le mariage sous L'Ancien Régime]
* [http://scancan.net/ Scandinavian-Canadian Studies / Études scandinaves au Canada]
* [http://voice.univie.ac.at Vienna-Oxford International Corpus of English]: a corpus of transcripts of spoken ELF interactions in TEI format.



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

== How to download ==
Download the current stable version (version 1.4, April 2011) from the [http://exist-db.org/index.html#download eXist Home Page]; check out the current trunk version from "svn co <nowiki>https://exist.svn.sourceforge.net/svnroot/exist/trunk/eXist</nowiki>".

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

Talk:Recommended Practices

2010-10-19T12:15:39Z

Joewiz:

Am I right that this page is specifically for the [[SIG:Scholarly_Publishing]] page? If so, there's no indication that it is. --[[User:Joewiz|Joewiz]] 12:02, 18 October 2010 (EDT)
:Thanks, Joe. A single naming scheme is probably unenforceable, and there are quite a lot of pages with very general titles like this one. What I (and others) can do is create categories to bind them, which I did now in this case. [[User:Piotr Banski|Piotr]] 04:26, 19 October 2010 (EDT)
::Thanks, Piotr! The category idea is great. --[[User:Joewiz|Joewiz]] 08:15, 19 October 2010 (EDT)

Talk:Recommended Practices

2010-10-18T16:02:07Z

Joewiz: New page: Am I right that this page is specifically for the SIG:Scholarly_Publishing page? If so, there's no indication that it is. --~~~~

Am I right that this page is specifically for the [[SIG:Scholarly_Publishing]] page? If so, there's no indication that it is. --[[User:Joewiz|Joewiz]] 12:02, 18 October 2010 (EDT)

Talk:TEI Web Publishing

2010-03-09T03:08:53Z

Joewiz: /* Ranked list of methods to publishing TEI content to the web */ Added info about the eXist example

How easy should it be?

If we're really serious about making publishing easy, surely the easiest is to insert the following at the top of the TEI?

<pre><nowiki>
<?xml-stylesheet href="path/to/stylehseet.xsl" type="text/xsl"?>
</nowiki></pre>

(said Stuart at 04:06, 6 March 2010)

:But that would work only if we want to publish a single TEI document rather than a collection of them. (xi:include will not always help, sometimes the relationship between documents should be expressed as reference rather than inclusion).
:So maybe let's turn your question into a possible basic condition: how to publish a set of TEI documents ''without'' having to modify them manually with e.g. stylesheet PIs? [[User:Piotr Banski|Piotr]] 05:05, 6 March 2010 (EST)

::The first sentence of the page talks about 'a single TEI document' [[User:Stuartyeates|Stuartyeates]] 15:00, 6 March 2010 (EST)
:::Maybe it shouldn't be steps but rather issues. Still, the 2nd sentence talks about a set of documents, so we can make the assumption that the 1st one talks about a single-membered set, as a particular case. (Or we can make a different assumption :-)) [[User:Piotr Banski|Piotr]] 15:59, 6 March 2010 (EST)
::::I think the issue here is that we're conflating '''documents''' and '''files''', both of which are further conflated in the minds of many users with '''works'''. [[User:Stuartyeates|Stuartyeates]] 21:41, 6 March 2010 (EST)
:::::That would make a fine introduction. Indeed, xinclude has nothing to do with ''documents'' (or has as much to do with them as inter-paragraph spacing, perhaps). Let me rephrase (still as an exercise, to see if we can get anything interesting out of it):
:::::Given a document encoded in the TEI, what are the available publishing strategies?
:::::* One is to add the PI (to the (main) file containing the document) and count on a client-side engine in a browser (if this is what you meant, Stuart). The XSL list suggests it may be a tough task, especially where cross-platform, cross-browser portability is intended. (expertise involved: XSLT, browser XSLT engine quirks)
:::::* Another is to prepare a transformation scenario, possibly including a pipe, and run a processor on it. (expertise involved: XSLT + Saxon/Xalan/xsltproc -- these are at least well-documented)
:::::* The next scenario would involve a native TEI db (which? let's say eXist for starters; expertise: +XQuery; and aren't we looking here at a slightly different range of applications?)
:::::* Next is Thomas Crombez' Google Docs suggestion, which may involve an easy step (->HTML) using default stylesheets.
:::::* Ready-made TEI publishing solutions (other than Sebastian's stylesheets) -- if there were any such full-fledged systems, would we bother doing this?
:::::* Basic command of (X)HTML/CSS is a given. Somewhere on the way, one should possibly mention Cocoon, XProc... am I making any sense? If I am, it begins to look like a book... :-/ But something could be carved out of this as one of the possible examples to follow. There are lots of sources on XSLT, and Thomas has a tutorial for people who want the Google way; as Martin noted, there is little documentation on the database scenario, and this is where this might go.
:::::At this point, my interests are in the use of a native XML database for the purpose of manipulating dictionaries and corpora, so I would be glad to help develop documentation on that on the understanding that there are going to be areas where I will be learning and experimenting, so not really contributing from an expert's position. [[User:Piotr Banski|Piotr]] 17:30, 7 March 2010 (EST)

Stuart, that's ''some'' beginning! :-) Minor points: "XSLT 1.0" can just be XSLT (1.0 is xsltproc's demand; I'm not sure about Xalan anymore), hmm, I'll just go ahead and edit it in two passes, so that the "1.0" step is easy to revert if you had something specific in mind. [[User:Piotr Banski|Piotr]] 07:58, 8 March 2010 (EST)

== Ranked list of methods to publishing TEI content to the web ==

Here are two separate tables, one describes the form of the content presented on the web, the other describes how that might be hosted

{| class="wikitable" border="1"
|+ Table of ways to serve TEI on the web
|-
! Method
! Pros
! Cons
! Skills needed
! Searching possible
! Dynamic KWIC etc, possible
! Examples
|-
| Publish as single plain TEI/XML file
| Simplest possible solution
| Meaningless to a standard web browser / user
| None
| No
| No
|
|-
| Single TEI file + XSL Processing Instruction (PI)
| Very simple two-file solution
| Some obscure XSLT features not supported by all browsers
| XML, TEI, [[XSLT]]
| No
| No
|
|-
| Single web page from (single TEI file + single XSL file)
| A web page like any other.
| Because TEI is hidden, third party repurposing or validation is impossible
| XML, TEI, XSLT
| No
| No
|
|-
| Single web page from (single TEI file + single XSL file) + TEI file
| A web page like any other, but a link to web
|
| XML, TEI, XSLT
| No
| No
|
|-
| Multiple web page from (multiple TEI files + xinclude + XSL file(s) ) + TEI files
| A web page like any other, but a link to web
| Multiple files enable large, complex structures and corpora
| XML, TEI, XSLT, [[XPointer]]
| No
| No
|
|-
| Multiple TEI files in eXist database + XSL and/or XQuery for conversion of fragments to HTML
| Native XML database means no shredding XML into tables, and rapid fulltext query across some/all TEI files; built-in full-featured web server with URL rewriting for cool URLs; cross platform
| Requires own server (real or virtual)
| XML, TEI, XSLT, [[XQuery]]
| Yes
| Yes
| [http://history.state.gov/ U.S. State Department]
|-
| Multiple TEI files in postgres database + XSL conversion of fragments to HTML
| Makes inter-linking with other information sources easy
| Requires own server (real or virtual)
| XML, TEI, XSLT, SQL
| Yes
| No (in theory yes, but hard)
| [http://www.nzetc.org/ NZETC]
|}

Remember that for polished websites at least some CSS (Cascading StyleSheets) skills are going to required. For pages with at least some dynamism (drop down menus, expanding sections, etc), a little javascript skill goes a long way.

{| class="wikitable" border="1"
|+ How to host your TEI website
|-
! Method
! Pros
! Cons
! Examples
|-
| Local server
| Full control. Can dual-use a server (or desktop)
| Need hardware. Need reliable internet connection. Need technical skills. Backups important
| [http://www.nzetc.org/ NZETC]
|-
| Shared server
| Pooled skilled and resources
| Conflicting requirements. Need reliable internet connection. Backups important
| [http://www.nzetc.org/ NZETC]
|-
| Virtual server
| Full control. Security handled by third party.
| Need technical skills. Costs $. Backups important
|
|-
| Hosting on google sites
| Free, unlimited HTML pages (size and number)
| No dynamic content (no [[eXist]] or other databases possible). Backups important
|
|}
===Domains===

The root url of your published TEI needs to be consistent, but to enable google searching and to allow uses to re-find your content. The URL can also be an important part of the branding of your project.
* Some projects choose to be in subdomains of academic institutions ( http://epidoc.cch.kcl.ac.uk/inscriptions/index.html , http://www.ota.ox.ac.uk/ , etc) these subdomains are typically free and brand the project with the institutions identity.
* Others choose to have their own domains (http://papyri.info/idp_static/current/ http://www.freedict.org/) these are most commonly cross-institutional collaborations, these domains typically cost money to maintain.
* Some hosted services (i.e. google sites) have their own fixed domain that users get little or no say in.

===Filenames===
Many systems have difficulty with filenames containing non-ASCII characters or spaces (this is very common with poorly written scripted system on UNIX platforms). Others have difficulties with multiple filesnames which differ only by case (DOS-compatible filesystems are unable to make this distinction). It is recommended that you avoid these unless absolutely necessary or you have already tested that thery're permitted on your choose system.

PopUpFootNotes.xsl

2010-03-01T15:21:06Z

Joewiz:

From: Joe Wicentowski (user: joewiz, domain: GMAIL.COM) 

This footnote implementation (using CSS and XSL) gives you "pop-up"
text for footnotes when you hover over them in the text, and places a
copy of the footnote text below the text. Though not all browsers
support the CSS, this implementation degrades gracefully in my
testing; you can click on footnote numbers and go back and forth
between the text and the footnote text. (Note: This implementation
assumes you provide the footnote number in the form <note n="1">, but
it's fairly simple to have the XSL generate footnote numbers for you.)

Source text:
<pre><nowiki>TEI is an interesting markup language.<note n="1">See tei-c.org.</note></nowiki></pre>

XSLT:
<pre><nowiki>

<xsl:template name="document">
<html:div class="document">
<xsl:apply-templates/>
<xsl:if test="count(//tei:note) > 0">
<html:hr/>
<html:div class="footnotes">
<xsl:apply-templates select="//tei:note" mode="endlist"/>
</html:div>
</xsl:if>
</html:div>
</xsl:template>


<xsl:template match="tei:note">
<xsl:variable name="inc">
<xsl:number level="any" count="tei:note"/>
</xsl:variable>
<html:a href="#fn{$inc}" name="fnref{$inc}">
<html:sup>
<xsl:value-of select="@n"/>
</html:sup>
<html:span class="footnoteinline"><xsl:value-of
select="@n"/>. <xsl:value-of
select="."/></html:span>
</html:a>
</xsl:template>


<xsl:template match="tei:note" mode="endlist">
<xsl:variable name="incr">
<xsl:number level="any" count="tei:note"/>
</xsl:variable>
<html:p><html:a href="#fnref{$incr}" name="fn{$incr}"
title="Return to text">
<html:sup>
<xsl:value-of select="@n"/>
</html:sup>
</html:a> <xsl:value-of select="."/><xsl:text/></html:p>
</xsl:template>
</nowiki></pre>
CSS:
<pre><nowiki>
/* sup is used for footnote reference numbers */
sup {
vertical-align: super;
font-size: smaller;
line-height: 0em;
background-color:#F0F2EC;
border: solid 1px #CCCCCC;
padding: 1px 3px 1px 3px;
}

/* sets up line height for document paragraphs so the footnote
superscript fits */
div.document p {
line-height: 1.7em;
margin-top: 1.5em;
}

/* controls the rendering of text in the footnote div */
div.footnotes, div.footnotes p {
font-weight: normal;
font-size: .973em;
}

/* suppresses display of inline footnote text, setting up the pop-up on hover */
a span.footnoteinline {
display: none;
}

/* turns on inline footnote text on hover, producing the pop-up */
a:hover span.footnoteinline {
display: block;
position: relative;
margin: 5px;
padding: 7px;
font-size: .825em;
line-height: 1.75em;
text-transform: none;
font-weight: normal;
background-color:#F0F2EC;
outline-style:solid;
outline-width:1px;
outline-color:#CCCCCC;
}
</nowiki></pre>
[[Category: CSS]]
[[Category: XSLT]]

XQuery

2010-02-27T07:09:00Z

Joewiz: /* Additional notes */ Added XQuery wikibook

[[Category:Tools]]

[[Category:Conversion and preprocessing tools]]
[[Category:Publishing and delivery tools]]
[[Category:Querying tools]]
[[Category:XQuery|!]]

== Synopsis ==
Originally designed to query XML databases, but can do all types of transformation that XSLT can do. (See http://www.xml.com/pub/a/2005/03/09/xquery-v-xslt.html .)

== Features ==

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

== Source code and licensing ==
Standard is copyrighted by W3C, which grants a license to reproduce it in its original form.

== Support for TEI ==

== Language(s) ==

== Documentation ==
Documentation is available from W3C in English: http://www.w3.org/XML/Query/ .

== User community ==

== Sample implementations ==

* http://www.tei-c.org.uk/wiki/index.php/Category:XQuery
* Open-source implementation available in Michael Kay's [[Saxon]].
* Others listed at http://www.w3.org/XML/Query/ .

== Current version number and date of release ==
1.0 (W3C Recommendation 2007 January 23)

== History of versions ==
See http://www.w3.org/XML/Query/ .

== Additional notes ==
Introductory readings:

# http://www.xml.com/pub/a/2005/03/02/xquery.html
# http://www.xml.com/pub/a/2005/03/23/xquery-2.html
# http://www.xml.com/pub/a/2006/06/14/scaling-up-with-xquery-part-1.html
# http://www.xml.com/pub/a/2006/06/21/scaling-up-with-xquery-part-2.html
# http://en.wikibooks.org/wiki/XQuery

Milestone-chunk.xquery

2010-02-27T07:03:06Z

Joewiz: /* Implementation in eXist */ link improvements

== Authorship ==
{|
| ''Author''
| David Sewell, University of Virginia, [mailto:dsewell@virginia.edu dsewell@virginia.edu]
|-
| ''Last revised''
| 2007-05-02
|-
| ''Previous version''
| none
|}

== Summary ==
This is an XQuery 1.0 function that will return all of the content between two milestone elements such as '''pb'''
while preserving the hierarchical structure of the containing elements. For example, given content like this in a TEI document:
<pre><nowiki>
<TEI>
<text>
<body>
<div1 type="chapter" n="1"> 
<div2 xml:id="doc100">
An example<pb n="3"/>of a very short page<pb n="4"/>here.
</div2> 
</div1>
</body>
</text>
</TEI>
</nowiki></pre>

the function would produce the following XML fragment as output when asked to return content between '''pb/@n=3''' and '''pb/@n=4'''
with the '''text''' element as the ancestor:

<pre><nowiki>
<text>
<body>
<div1 type="chapter" n="1">
<div2 xml:id="doc100">
<pb n="3"/>of a very short page
</div2>
</div1>
</body>
</text>
</nowiki></pre>

In other words, the full hierarchical structure of the ancestor elements, including their attributes, is preserved, but only the nodal content between the milestons is included.

== Required Input ==

The function signature is
<pre><nowiki>
local:milestone-chunk(
$ms1 as element(),
$ms2 as element(),
$node as node()*
)
</nowiki></pre>

'''$node''' is an element known to be a common ancestor of the two milestones. For example, it could be '''TEI/text''', or '''TEI/text/body''', or even '''TEI/text/body/div1[3]''' if the milestone parameters are both descendants of that div1.

'''$ms1''' is the first milestone element; '''$ms2''' is the second milestone element.

For example, the output in "Summary" above might have been produced by the call

<pre><nowiki>
let $input := doc("mydoc.xml")/tei:TEI/tei:text
return local:milestone-chunk($input//pb[@n="3"], $input//pb[@n="4"], $input)
</nowiki></pre>

If '''$input''' had been
doc("mydoc.xml")/tei:TEI/tei:text/tei:body
then the output would have started at the '''body''' element, etc.

'''$ms1''' and '''$ms2''' do not need to be adjacent milestones. You can, for example, return content between '''pb/@n=4''' and '''pb/@n=7'''. Nor do the milestones need to be of the same type; you can return content between the '''pb''' for page 4 and an arbitrary anchor or pointer element later in the document.

== Expected Output ==

As indicated in the example in "Summary" above, the output should be a single XML element reflecting the structure of the input ancestor element and its descendants, but otherwise containing only the nodal content between the two milestone elements in the original input.

== Known Restrictions or Problems ==
The output will contain a copy of the first milestone element, but not of the second (closing) one. This is a consequence of the need to use pseudo-milestones for the second milestone in some cases; see next paragraph.

When using this function to generate content between TEI '''pb''' elements, an obvious problem is that the final page will not have a final '''pb''' milestone. In this case, use a pseudo-milestone such as the last node in the input element. For example, using the sample document in "Summary" above, the content of page 4 ("here.") would be output via the call
<pre><nowiki>
let $input := doc("mydoc.xml")/tei:TEI/tei:text
local:milestone-chunk($input//pb[@n="4"], ($input//node())[last()], $input)
</nowiki></pre>

If you use this function to recurse over all the '''pb''' elements in a document, you will need to use a strategy like this when '''$ms1''' has no following '''pb''' element.

The function will not gracefully handle invalid input, but will probably throw run-time errors. You should be sure that the parameters passed to it reflect actual milestone elements with a common ancestor.

== Code ==
<pre><nowiki>
declare function local:milestone-chunk(
$ms1 as element(),
$ms2 as element(),
$node as node()*
) as node()*
{
typeswitch ($node)
case element() return
if ($node is $ms1) then $node
else if ( some $n in $node/descendant::* satisfies ($n is $ms1 or $n is $ms2) )
then
element { name($node) }
{ for $i in ( $node/node() | $node/@* )
return local:milestone-chunk($ms1, $ms2, $i) }
else if ( $node >> $ms1 and $node << $ms2 ) then $node
else ()
case attribute() return $node (: will never match attributes outside non-returned elements :)
default return
if ( $node >> $ms1 and $node << $ms2 ) then $node
else ()
};
</nowiki></pre>

== Implementation in eXist ==
This function is implemented in [[eXist]] (as a function called [http://demo.exist-db.org/exist/functions/util/get-fragment-between util:get-fragment-between()]) by Josef Willenborg, Max Planck Institute for the History of Science [mailto:jwillenborg@mpiwg-berlin.mpg.de jwillenborg@mpiwg-berlin.mpg.de]:

<pre><nowiki>
util:get-fragment-between($beginning-node as node()?, $ending-node as node()?, $make-fragment as xs:boolean?) xs:string

Returns an xml fragment or a sequence of nodes between two elements (normally milestone elements). The $beginning-node represents the first node/milestone element, $ending-node, the second one. The third argument, $make-fragment, is a boolean value for the path completion. If it is set to true() the result sequence is wrapped into a parent element node.

Example call of the function for getting the fragment between two TEI page break element nodes:
let $fragment := util:get-fragment-between(//pb[1], //pb[2], true())
</nowiki></pre>

[[Category:XQuery]]

EXist

2010-02-27T06:57:27Z

Joewiz: /* System requirements */

[[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.'''

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

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

EXist

2010-02-27T06:56:03Z

Joewiz: /* Current version number and date of release */ Updated version number

[[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.'''

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

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

EXist

2010-02-27T06:53:30Z

Joewiz: /* Sample implementations */ Added Office of the Historian

[[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.'''

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

== Current version number and date of release ==
New Indexing Core: eXist 1.2 - 2008-01-16

Old Indexing Core: eXist 1.0.2 - 2007-02-25

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

== See also ==
* [[Berkeley DB XML]]