TEIWiki - User contributions [en]

TXM

2019-05-30T17:24:55Z

Kshawkin: /* Current version number and date of release */

[[Category:Tools]]

[[Category:Administrative tools]]
[[Category:Development tools]]
[[Category:Conversion and preprocessing tools]]
[[Category:Publishing and delivery tools]]
[[Category:Querying tools]]
[[Category:Analysis tools]]
[[Category:All-in-one Tools]]
[[Category:Interfaces]]

[[Category:Discovering]]
[[Category:Comparing]]
[[Category:Sampling]]
[[Category:Illustrating]]
[[Category:Representing]]

== Synopsis ==

[http://textometrie.ens-lyon.fr/?lang=en TXM] is a free and open-source XML & TEI compatible textual corpus analysis framework and graphical client based on the CQP search engine and the R statistical software. It is available as a [http://textometrie.ens-lyon.fr/spip.php?rubrique61 desktop software] for Microsoft Windows, Linux, Mac OS X and as a J2EE [https://sourceforge.net/projects/txm/files/software/TXM%20portal/ web portal software]<ref>See a [https://groupes.renater.fr/wiki/txm-users/public/references_portails list of public portals]</ref>.

== Features ==

=== Provides qualitative analysis tools ===

* kwic '''concordances''' of word patterns based on the efficient [http://cwb.sourceforge.net CQP] full text search engine and its powerfull CQL query language
* word pattern '''frequency lists''' based on any word property (graphical form or type, lemma, pos...)
* word pattern '''progression graphics'''
* Examples of word patterns, expressed in the CQL query language which is based on word & structural level properties:
** "aiming" to simply search for the word 'aiming'
** ".*ing" to search for words ending in "ing" (including mainly verb forms)
** [pos="VERB" & word=".*ing"] to search for verb forms ending in ".ing" (where Part of Speech annotation is present)
** [lemma="group"] []{0,3} [pos="VERB" & word=".*ing"] to search for the collocation <group lemma> followed by a <verb with progressive aspect> with at most 3 words in between
* rich HTML-based text edition navigation with links from all other tools

=== Provides quantitative analysis tools, based on [http://www.r-project.org R packages] ===
* '''factorial correspondance analysis'''
* '''cluster analysis'''
* '''specific''' word patterns analysis
* '''collocations''' analysis

=== Helps to build various corpus configurations ===
(for contrastive analysis between text structures or word selections)
* '''sub-corpora'''
* '''partitions'''

=== Large spectrum of input formats ===
* several text formats (from raw to rich):
** '''Unicode TXT'''
** '''ODT'''
** '''XML'''
** '''XML/w''' (where some or all word limits and properties can be pre-encoded)
** XML-'''TEI P4''' (according to Perseus project practice)
** XML-'''TEI P5''' (according to various projects practice: BFM, BVH, NLTK, etc.)
* speech transcription: XML-'''TRS''' (from Transcriber software, with time synchro)
* aligned corpora: XML-'''TMX''' (with texts in relation of translation or versioning)
* news portal articles: XML-'''PPS''' (Factiva), Europresse
* etc.

=== And more ===
* Applies various NLP tools on the fly on texts before analysis (e.g. '''TreeTagger''' for lemmatization and pos tagging)
* Indexes words and their properties as well as hierarchical structure of texts
* Indexes external or internal text metadata or speaker metadata
* '''Export'''s any result in CSV, XML or SVG format
* Provides Scripting facilities for repetitive or lengthy tasks automation or for platform extension (in '''Groovy'''/Java dynamic language)
* Includes a complete '''text editor''' to edit data sources, results and scripts
* Runs as a desktop application for '''Windows''', '''Mac OS X''' or '''Linux'''
* Runs also as '''web portal''' to give corpora access and analysis online through any web browser (including account and access control management)
* '''Open source''' licence: based on the best open source components for text analysis: CQP, R and Java & XSLT libraries
* Modular architecture (Eclipse RCP OSGi and J2EE conformant): one toolbox connecting all core components to build the applications
* Efficient Eclipse or Netbeans powered development framework

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

== System requirements ==
The desktop version runs on:
* Windows - 32bit or 64bit (tested on XP, Vista, 7 and 8)
* Mac OS X (tested on 10.5, 10.6, 10.7, 10.8 and 10.9)
* Linux - 32bit or 64bit (tested on Ubuntu and Debian)

The portal server runs on any J2EE capable platform (tested in Tomcat and Glassfish).

== Source code and licensing ==
Open Source under GPL V3 licence: [http://sourceforge.net/p/txm/code/HEAD/tree/trunk http://sourceforge.net/p/txm/code/HEAD/tree/trunk].

== Support for TEI ==
Supports TEI and TEI Lite "out of the box" '''at XML level semantics''': words will be tokenized inside any #PCDATA and all the XML structure will be imported directly as textual structure.

Supports various flavours of TEI P5 encoding semantics '''at TEI level semantics''':
* words and their properties: <nowiki>#PCDATA, <w>, <num>...</nowiki>
* editorial markup: <nowiki><sic>, <corr>...</nowiki>
* texts and their properties: <nowiki><TEI>, <text>...</nowiki>
* intermediate text structures and their properties: <nowiki><div>, ...</nowiki>
* edition rendering: <nowiki><pb/>, , <lb/>...</nowiki>
* what should not be indexed but considered for edition rendering: <nowiki><teiHeader>, <note>...</nowiki>
* alignment between texts: <nowiki><teiCorpus>, <linkGrp>, <link>...</nowiki>
* words identifier policy: <nowiki>@xml:id</nowiki>
* language declaration policy: <nowiki>@xml:lang</nowiki>
See the "BFM encoding manual" for an example of TEI encoding practice interpreted by TXM, in French, http://bfm.ens-lyon.fr/article.php3?id_article=158.

The "TEI P5 BFM" TXM import module consists of Groovy and XSL scripts: they can be adapted directly by the user to any specific TEI encoding usage.

TXM Import Modules also provide various import parameters to tune each import process to specific data sources.

TEI sources from the following projects are currently imported into TXM at TEI level semantics:
* Perseus Digital Library (classical latin, old greek): http://www.perseus.tufts.edu/hopper
* TextGrid (german): http://www.textgrid.de/en
* Base de Français Médiéval - BFM (old french): http://bfm.ens-lyon.fr
* BVH Epistemon (middle french): http://www.bvh.univ-tours.fr/Epistemon & https://groupes.renater.fr/wiki/txm-users/public/mise_en_ligne_du_corpus_bvh_avec_txm
* PROCLAC mesopotamian tablets (akkadian): https://groupes.renater.fr/wiki/txm-users/public/umr_proclac_corpus_akkadien
* Bouvard&Pécuchet (french): http://dossiers-flaubert.ish-lyon.cnrs.fr
* NLTK - Brown Corpus - TEI XML Version (american english): http://nltk.googlecode.com/svn/trunk/nltk_data/index.xml
* Presses Universitaires de Caen (PUC), MRSH de Caen - Revues.org (french): http://www.unicaen.fr/recherche/mrsh/document_numerique/outils ([[http://discours.revues.org?lang=en DISCOURS scientific journal]])
* Frantext - libre (french): http://www.cnrtl.fr/corpus/frantext
* XML-TXM - TXM own pivot format (any language): https://groupes.renater.fr/wiki/txm-info/xml_tei_txm

Experiments with other TEI sources:
* Victorian Women Writers Project (english): http://www.dlib.indiana.edu/collections/vwwp

TEI sources are preprocessed by several XSL stylesheets, one can find in TXM source code.
Some of those stylesheets are available in the online TXM XSL stylesheets library:
http://sourceforge.net/projects/txm/files/library/xsl

== Language(s) ==

=== User Interface Language(s) ===
The user interface is currently available in:
* desktop version:
** English (EN)
** French (FR)
** Russian (RU)
* portal version:
** English (EN)
** French (FR)

=== Documentation Language(s) ===
The documentation is currently available in:
* desktop version:
** English (EN)
** French (FR)
* portal version:
** French (FR) (tutorial - alpha state)

=== Text/Corpus Language(s) ===
TXM works natively with any Unicode-conformant corpus. 
Language support is specific to each NLP tool used (for example, TreeTagger can tag the following languages: BG, DE, EN, ES, ET, FR, FRO, GL, IT, LA, PT, RU, SW, ZH). 
* ZH: best results have been reported by using the ZPar tokenizer & tagger - http://sourceforge.net/projects/zpar

=== Programming Language(s) ===
TXM is written in the following programming languages:
* '''C''' for CQP search engine (independent open source project http://cwb.sourceforge.net)
* '''C''' and '''R''' for statistical packages (independent open source project http://www.r-project.org)
* '''Java''' for the Toolbox and the Applications (driven by an independent open consortium http://jcp.org/en/home/index)
** Eclipse RCP framework used for the desktop version (independent open source project http://wiki.eclipse.org/index.php/Rich_Client_Platform)
** GWT framework used for the web portal version (independent open source project http://code.google.com/intl/fr/webtoolkit)
* '''Groovy''' for the import modules and command scripts (independent open source project http://groovy.codehaus.org)

== Documentation ==

* TXM manual (in French) http://perso.ens-lyon.fr/serge.heiden/txm/files/software/TXM/0.7.7/Manuel%20de%20TXM%200.7%20FR.pdf
* TXM user community wiki (in French) at https://listes.cru.fr/wiki/txm-users (includes a FAQ)
* TXM developers wiki (in French) https://groupes.renater.fr/wiki/txm-info
* All published documentation (for users and for developers) published on Sourceforge: http://sourceforge.net/projects/txm/files/documentation

== Tech support ==

Tech support is community based.

Feedbacks and bug reports:
# Check if your feedback is not already reported in the [http://forge.cbp.ens-lyon.fr/redmine/projects/txm/issues?query_id=31 TXM platform bug tracker]
# If not, send your feedback either:
#* in the [https://lists.sourceforge.net/lists/listinfo/txm-open txm-open mailing list]
#* by directly editing the [https://groupes.renater.fr/wiki/txm-users/public/retours_de_bugs_logiciel/txm_0.7.7 txm-users wiki]
#* by chating directly with the developers on the #txm IRC channel of the 'irc.freenode.net' server ([http://webchat.freenode.net/?channels=txm web access])
#* by contacting the TXM team at the 'textometrie AT ens-lyon.fr' address

== User community ==

TXM community uses two mailing lists and a wiki:
* International mailing list : txm-open AT lists.sourceforge.net (very low activity for the moment)
** See archives at http://sourceforge.net/mailarchive/forum.php?forum_name=txm-open
* The mostly French-speaking mailing list : txm-users AT cru.fr (the most active)
** See archives at https://listes.cru.fr/sympa/arc/txm-users
* TXM user community wiki (in French) at https://listes.cru.fr/wiki/txm-users

Training in the use of TXM is available:
* Monthly in Lyon (France): https://groupes.renater.fr/wiki/txm-users/public/ateliers_txm
* Regularly in workshops: [http://dh2015.org/workshops Sydney 2015], [http://www.germanistik.uni-wuerzburg.de/lehrstuehle/computerphilologie/aktuelles/veranstaltungen/workshop_introduction_to_the_txm_content_analysis_platform Wurzburg 2014]
* and Summer schools: MISAT 2011, [http://www.iqla.org/IQLA-GIAT%20Summer%20School%202013.pdf Padova 2013]

The JADT biennal international conference (http://jadt.org) is the main meeting place for the TXM user community.

== Sample implementations ==
The desktop version of TXM is delivered with several sample corpora included, which can be directly analyzed from within TXM after installation.

The portal version of TXM has a demo running online at http://portal.textometrie.org/demo/?locale=en.

== Current version number and date of release ==
* 0.8.0 (2019-05-29)

== History of versions ==
See software development project report page: http://forge.cbp.ens-lyon.fr/redmine/projects/txm/issues/report.

== How to download or buy ==
http://textometrie.ens-lyon.fr/spip.php?rubrique61

== Additional notes ==
For publications related to TXM, please visit the Textométrie project web site at http://textometrie.ens-lyon.fr/spip.php?article82&lang=en:
* See for example: Heiden, S. (2010b). The TXM Platform: Building Open-Source Textual Analysis Software Compatible with the TEI Encoding Scheme. In K. I. Ryo Otoguro (Ed.), 24th Pacific Asia Conference on Language, Information and Computation - [http://www.compling.jp/paclic24 PACLIC24] (p. 389-398). Institute for Digital Enhancement of Cognitive Development, Waseda University, Sendai, Japan. [http://halshs.archives-ouvertes.fr/halshs-00549764/en Online].

Sponsors & Contributors:
* Initial design and development of TXM (jan 2007- dec 2011) supported by French ANR grant #ANR-06-CORP-029
* Currently the platform continues its development through various contracts:
** ENS-LYON contract jun-aug 2009 (Rhône-Alpes region Cluster 13 grant): Queste del saint Graal web prototype
** ENS-LYON contract sept 2009 - jul 2010 (ANR CORPTEF Research Project funding): portal development
** Lyon 3 University contract jan-mar 2011: XML-Transcriber import, R GUI
** CNRS contract 2011 (DGLFLF grant): GGHF corpus processing
** Paris 1 University contract jan 2012 - dec 2014 (Matrice Equipex): TXM development and infrastructure for historians
* Other independent projects also improve TXM (community of developers):
** LASLA project 2011: import of ancient latin and greek corpora
** GREYC-PUC project may-jul 2011: PUC corpora import, improvement of portal, test on Glassfish
** PhD thesis on micro-finance 2011-: Factiva and Calibre import
** ANR-DFG SRCMF contract jun-jul 2012 : Tiger Search module, import & syntactic concordances

== Notes ==

<references/>

OXygen

2019-05-25T18:18:53Z

Kshawkin: /* Current version number and date of release */

[[Category:Tools]]

[[Category:All-in-one Tools]]
[[Category:Development tools]]
[[Category:Editing tools]]
[[Category:Conversion and preprocessing tools]]

== Synopsis ==
<oXygen/> is a high-powered, cross-platform, graphical XML editor with built-in support for TEI.

== Features ==
Supports most features typical of a high-end XML editor, including:
* syntax coloring
* context-sensitive content assistant
* built-in validation and well-formedness checking
* built-in XSLT engines
* Unicode support
* formatting and indentation
* folding
* outline view (shows document structure)
* model view (shows element content model)
* XPath support
* XSLT debugger
* DTD/schema editor
* Text, Grid, and Author (tagless) editing modes

See also http://www.oxygenxml.com/features.html .

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

I have found this program to be affordable, easy to use, and pre-loaded with TEI capabilities. Also, the platform gets upgraded on a regular basis. -- Greg Moses (Austin, TeiXas!)

== System requirements ==
Runs under Windows, Linux, and Mac operating systems. Requires a Java VM (virtual machine).

(One of the download options for Windows users is an installer that includes the Java VM, eliminating the need to download and install Java separately.)

For detailed requirements, see http://www.oxygenxml.com/download.html .

== Source code and licensing ==
Closed source. Academic licenses available for $48 per person, allowing you to install for your own use on many computers and use with the current major version number. A discount is available for TEI subscribers and individuals from TEI member institutions; the discount code may be found by logging in to [http://members.tei-c.org/MemberInfo http://members.tei-c.org/MemberInfo]. Free 30-day trial license available.

== Support for TEI ==

===The TEI Framework in <oXygen>===

As of Version 9.0 build 2007110615, <oXygen> has TEI P5 schemas, templates and the TEI XSL stylesheets included as an officially-supported framework.

If you are not using the <code>tei-oxygen</code> [[TEIDebian|Debian package]] (for which a package manager will provide automatic updates for new versions of the stylesheet library), you can upgrade your copy of the stylesheet library without needing to download a new version of <oXygen/> doing doing either of the following:

* With version 15.2 or later of <oXygen/>, "subscribe" to the regularly-updated TEI distribution of the framework according to the instructions in this blog post: https://faqingperplxd.wordpress.com/2014/04/02/auto-update-your-tei-framework-in-oxygen/ .

* Use [http://sourceforge.net/projects/tei/files/oxygen-tei/ oxygen-tei], the open-source TEI framework built into <oXygen/>. To install this, look in your Oxygen folder for a "frameworks" directory that contains a directory called "tei". That's where the contents of the zip would go, replacing the old contents of that directory. ''Note that this is not the same thing as the <code>tei-oxygen</code> [[TEIDebian|Debian package]]!'' You can also build this framework for yourself if you are interested in doing so; the [https://github.com/TEIC/oxygen-tei project code is available on GitHub].

=== Other TEI-related Plugins ===

<oXygen/> allows third-party plugins and frameworks. The following are of possible interest to TEI users:

====HisTEI====

If you work with historical documents, you might use [https://github.com/odaata/HisTEI HisTEI], a framework designed to make historical documents easier to transcribe in <<oXygen/>'s XML Author mode.<ref>http://www.oxygenxml.com/pipermail/oxygen-sdk/2014-November/000182.html</ref>

==== Severin ====

[http://code.google.com/p/severin-image-viewer/ Severin] is an image viewer plugin, by Kilian Schmidtner and Stefan Krause, that can be used to see images as you browse though documents. It is an open source project (MIT license), and on the project page you can find a video presentation that uses a TEI document as example.

==== TEI-Facsimile-Plugin ====

[https://github.com/oxygenxml/TEI-Facsimile-Plugin TEI-Facsimile-Plugin] "provides support for working with Digital Facsimiles in Text Encoding Initiative (TEI) vocabulary. The plugin contributes a new View in which the user can load an image and draw shapes. These shapes are then converted into TEI "zone" elements. All the existing "zone" elements from the document are also rendered over the image."<ref>https://github.com/oxygenxml/TEI-Facsimile-Plugin</ref> This plugin requires oXygen version 15 or later.

==== dbTagger ====

https://github.com/aerhard/dbTagger

==== ediarum ====

[[Ediarum]]

==== TEI Completer ====

https://github.com/BCDH/TEI-Completer

==== oXygen-XML-editor-attribute-editor ====

* [https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;7d49b3c3.1612 announcement]
* https://github.com/AlexJitianu/oXygen-XML-editor-attribute-editor

== Language(s) ==
Interface available in English, French, German, Italian, Japanese and Dutch.

Documentation available in English.

== Documentation ==
http://www.oxygenxml.com/documentation.html

== Tech support ==
http://www.oxygenxml.com/techSupport.html

Can buy maintenance and support pack, providing free upgrades and tech support.

== User community ==
* http://www.oxygenxml.com/mailman/listinfo/oxygen-user/
* http://www.oxygenxml.com/forum/

== Current version number and date of release ==
21.1 (2019-05-23)

== History of versions ==
See http://www.oxygenxml.com/software_archive.html .

== How to download or buy ==
http://www.oxygenxml.com/download.html

If you use Debian or Ubuntu, you should instead install the <tt>tei-oxygen</tt> package at http://tei.oucs.ox.ac.uk/teideb/ . (More information below.)

== Additional notes ==

David Sewell wrote:

<blockquote>
Because the schema files distributed with oXygen sometimes lag behind
the latest TEI releases, kind souls like Syd Bauman have from time to
time packaged new schema files so that they can be unpacked to replace
part of the oXygen frameworks hierarchy. You could also go to

http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/

and grab the files there to replace the ones in a local oXygen
directory.
<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;8d5b98b2.0804</ref>
</blockquote>

Sebastian Rahtz added that if you use Debian or Ubuntu, you should instead install the <code>tei-oxygen</code> package. He explained that "this replaces the oXygen TEI package with a link to one installed by the tei-p5-schema package, which is kept up to date. This means you have only one set of TEI files on your machine." It's available at http://tei.oucs.ox.ac.uk/teideb/ .

Marcus Bingenheimer:
If you edit ODD files you need to validate the ODD against tei_odds. tei_all will not catch all mistakes and gives and error whenever elements in the RNG or other namespaces are used within <datatype>.
As usual you can associate the tei_odds with a oxygen specific processing command similar to this:
<code><?oxygen RNGSchema="{your oxygen folder}/frameworks/tei/xml/tei/custom/schema/relaxng/tei_odds.rng" type="xml"?></code>

== References ==
<references/>

Textgrid

2019-03-03T21:20:56Z

Kshawkin: added Category:Tools

TextGrid is a project funded by the German Federal Ministry of
Education and Research (BMBF) as part of the ongoing global movement towards
grid infrastructures and the convergence of e-Science technologies in general. Project
partners include both, technologists and domain experts from six German higher
education institutions and two commercial partners.

'''Project homepage:''' http://www.textgrid.de/

[[Category:Projects]]
[[Category:Tools]]

Transkribus

2019-03-03T01:08:03Z

Kshawkin: Created page with "Category:Tools Category:All-in-one Tools == Synopsis == "Transkribus is a comprehensive platform for the automated recognition, transcription and searching of histori..."

[[Category:Tools]]
[[Category:All-in-one Tools]]

== Synopsis ==
"Transkribus is a comprehensive platform for the automated recognition, transcription and searching of historical documents."<ref>https://transkribus.eu/wiki/index.php/Main_Page</ref> "Transkribus can be used for several purposes. The most important are:
"i. Transcribe documents for a scholarly edition
"ii. Create training data to feed the Handwritten Text Recognition (HTR) system so it can learn to decipher your historical documents.
"iii. Run HTR on your documents and receive automatically generated transcripts.
"iv. Search for distinct words in your document collections with Keyword Spotting which is much more powerful than standard full-text search.
"v. The platform lives from the community. The more data uploaded to Transkribus, the more efficient the program and especially the Handwritten Text Recognition will get."<ref>https://transkribus.eu/wiki/images/7/77/How_to_use_TRANSKRIBUS_-_10_steps.pdf</ref>

== Features ==
* first feature
* second feature
* third feature

== User commentary ==
'''Please sign all comments.'''
(please leave the above note about signing comments, and add signed comments here below it)

== System requirements ==
(type in that information here)

== Source code and licensing ==
(Is it open-source? If so, what license type?)
(For non-open source software, What does a license cost?)
(Is there any technical support fee? How often do you have to pay it?)
(Is there any discount for academic institutions?)
(Is there a discount for TEI members?)

== Support for TEI ==
(Does it support TEI or TEI Lite "out of the box"?)
(How easily can TEI be implemented?)
(Are there customized versions of the tool created for the TEI community, perhaps even by those not affiliated with the tool's creators?)

== Language(s) ==
(What computer language is the tool written in?)
(What language(s) are used in the interface?)
(What language(s) are used in the documentation?)

== Documentation ==
(link to or information about documentation available)

== Tech support ==
(What technical support is provided by the creators of the tool?)

== User community ==
(Are there any communities of users?)

== Sample implementations ==
(links to demo sites running the tool or successful implementations of it)

== Current version number and date of release ==
(type in that information here)

== History of versions ==
(type in that information here)

== How to download or buy ==
https://transkribus.eu/

== Additional notes ==
(type in that information here)

== References ==
<references/>

OXygen

2019-02-28T14:54:35Z

Kshawkin: /* Current version number and date of release */

[[Category:Tools]]

[[Category:All-in-one Tools]]
[[Category:Development tools]]
[[Category:Editing tools]]
[[Category:Conversion and preprocessing tools]]

== Synopsis ==
<oXygen/> is a high-powered, cross-platform, graphical XML editor with built-in support for TEI.

== Features ==
Supports most features typical of a high-end XML editor, including:
* syntax coloring
* context-sensitive content assistant
* built-in validation and well-formedness checking
* built-in XSLT engines
* Unicode support
* formatting and indentation
* folding
* outline view (shows document structure)
* model view (shows element content model)
* XPath support
* XSLT debugger
* DTD/schema editor
* Text, Grid, and Author (tagless) editing modes

See also http://www.oxygenxml.com/features.html .

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

I have found this program to be affordable, easy to use, and pre-loaded with TEI capabilities. Also, the platform gets upgraded on a regular basis. -- Greg Moses (Austin, TeiXas!)

== System requirements ==
Runs under Windows, Linux, and Mac operating systems. Requires a Java VM (virtual machine).

(One of the download options for Windows users is an installer that includes the Java VM, eliminating the need to download and install Java separately.)

For detailed requirements, see http://www.oxygenxml.com/download.html .

== Source code and licensing ==
Closed source. Academic licenses available for $48 per person, allowing you to install for your own use on many computers and use with the current major version number. A discount is available for TEI subscribers and individuals from TEI member institutions; the discount code may be found by logging in to [http://members.tei-c.org/MemberInfo http://members.tei-c.org/MemberInfo]. Free 30-day trial license available.

== Support for TEI ==

===The TEI Framework in <oXygen>===

As of Version 9.0 build 2007110615, <oXygen> has TEI P5 schemas, templates and the TEI XSL stylesheets included as an officially-supported framework.

If you are not using the <code>tei-oxygen</code> [[TEIDebian|Debian package]] (for which a package manager will provide automatic updates for new versions of the stylesheet library), you can upgrade your copy of the stylesheet library without needing to download a new version of <oXygen/> doing doing either of the following:

* With version 15.2 or later of <oXygen/>, "subscribe" to the regularly-updated TEI distribution of the framework according to the instructions in this blog post: https://faqingperplxd.wordpress.com/2014/04/02/auto-update-your-tei-framework-in-oxygen/ .

* Use [http://sourceforge.net/projects/tei/files/oxygen-tei/ oxygen-tei], the open-source TEI framework built into <oXygen/>. To install this, look in your Oxygen folder for a "frameworks" directory that contains a directory called "tei". That's where the contents of the zip would go, replacing the old contents of that directory. ''Note that this is not the same thing as the <code>tei-oxygen</code> [[TEIDebian|Debian package]]!'' You can also build this framework for yourself if you are interested in doing so; the [https://github.com/TEIC/oxygen-tei project code is available on GitHub].

=== Other TEI-related Plugins ===

<oXygen/> allows third-party plugins and frameworks. The following are of possible interest to TEI users:

====HisTEI====

If you work with historical documents, you might use [https://github.com/odaata/HisTEI HisTEI], a framework designed to make historical documents easier to transcribe in <<oXygen/>'s XML Author mode.<ref>http://www.oxygenxml.com/pipermail/oxygen-sdk/2014-November/000182.html</ref>

==== Severin ====

[http://code.google.com/p/severin-image-viewer/ Severin] is an image viewer plugin, by Kilian Schmidtner and Stefan Krause, that can be used to see images as you browse though documents. It is an open source project (MIT license), and on the project page you can find a video presentation that uses a TEI document as example.

==== TEI-Facsimile-Plugin ====

[https://github.com/oxygenxml/TEI-Facsimile-Plugin TEI-Facsimile-Plugin] "provides support for working with Digital Facsimiles in Text Encoding Initiative (TEI) vocabulary. The plugin contributes a new View in which the user can load an image and draw shapes. These shapes are then converted into TEI "zone" elements. All the existing "zone" elements from the document are also rendered over the image."<ref>https://github.com/oxygenxml/TEI-Facsimile-Plugin</ref> This plugin requires oXygen version 15 or later.

==== dbTagger ====

https://github.com/aerhard/dbTagger

==== ediarum ====

[[Ediarum]]

==== TEI Completer ====

https://github.com/BCDH/TEI-Completer

==== oXygen-XML-editor-attribute-editor ====

* [https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;7d49b3c3.1612 announcement]
* https://github.com/AlexJitianu/oXygen-XML-editor-attribute-editor

== Language(s) ==
Interface available in English, French, German, Italian, Japanese and Dutch.

Documentation available in English.

== Documentation ==
http://www.oxygenxml.com/documentation.html

== Tech support ==
http://www.oxygenxml.com/techSupport.html

Can buy maintenance and support pack, providing free upgrades and tech support.

== User community ==
* http://www.oxygenxml.com/mailman/listinfo/oxygen-user/
* http://www.oxygenxml.com/forum/

== Current version number and date of release ==
21.0 (2019-02-22)

== History of versions ==
See http://www.oxygenxml.com/software_archive.html .

== How to download or buy ==
http://www.oxygenxml.com/download.html

If you use Debian or Ubuntu, you should instead install the <tt>tei-oxygen</tt> package at http://tei.oucs.ox.ac.uk/teideb/ . (More information below.)

== Additional notes ==

David Sewell wrote:

<blockquote>
Because the schema files distributed with oXygen sometimes lag behind
the latest TEI releases, kind souls like Syd Bauman have from time to
time packaged new schema files so that they can be unpacked to replace
part of the oXygen frameworks hierarchy. You could also go to

http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/

and grab the files there to replace the ones in a local oXygen
directory.
<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;8d5b98b2.0804</ref>
</blockquote>

Sebastian Rahtz added that if you use Debian or Ubuntu, you should instead install the <code>tei-oxygen</code> package. He explained that "this replaces the oXygen TEI package with a link to one installed by the tei-p5-schema package, which is kept up to date. This means you have only one set of TEI files on your machine." It's available at http://tei.oucs.ox.ac.uk/teideb/ .

Marcus Bingenheimer:
If you edit ODD files you need to validate the ODD against tei_odds. tei_all will not catch all mistakes and gives and error whenever elements in the RNG or other namespaces are used within <datatype>.
As usual you can associate the tei_odds with a oxygen specific processing command similar to this:
<code><?oxygen RNGSchema="{your oxygen folder}/frameworks/tei/xml/tei/custom/schema/relaxng/tei_odds.rng" type="xml"?></code>

== References ==
<references/>

TEI Publisher

2019-02-25T02:57:31Z

Kshawkin: /* Current version number and date of release */

'''Not to be confused with [[TeiPublisher|teiPublisher]]'''.

[[Category:Tools]]

[[Category:Publishing and delivery tools]]

== Synopsis ==
"The instant publishing toolbox"<ref>http://teipublisher.com/</ref>

== Features ==
* High quality editions: Publish your digital edition without writing code. Using the TEI Processing Model, customising the appearance of the text is all done in XML.
* Cross media & multidevice: TEI Publisher generates applications which work well across devices and include features like page by page browsing, search and cross-media export.
* Single source publishing: Create HTML, ePUBs or PDFs from a single document and its associated processing model. No media specific stylesheets required.
* Lean code: For developers, TEI Publisher heavily reduces the amount of custom code required by typical digital edition projects. Save thousands of lines on handwritten transformations and rely on maintained code libraries instead.<ref>http://teipublisher.com/</ref>

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

== System requirements ==
[[Exist]] 4.x.x for version 4.0<ref>https://teipublisher.com/exist/apps/tei-publisher/doc/blog/tei-publisher-40.xml</ref>

== Source code and licensing ==

== Support for TEI ==

== Language(s) ==

== Documentation ==
http://teipublisher.com/exist/apps/tei-publisher/doc/documentation.xml

== Tech support ==

== User community ==

== Sample implementations ==
http://teipublisher.com/index.html#tp-showcases

== Current version number and date of release ==

4.1 (2019-02-22)

== History of versions ==

== How to download or buy ==
https://gitlab.existsolutions.com/tei-publisher

== Additional notes ==

== References ==
<references/>

Tei-xsl

2019-01-30T14:43:57Z

Kshawkin: /* Current version number and date of release */

[[Category:Tools]]

[[Category:Conversion and preprocessing tools]]
[[Category:Publishing and delivery tools]]
[[Category:XSLT]]

== Synopsis ==
This is a family of XSLT 2.0 stylesheets to transform TEI XML documents to various formats, including XHTML, LaTeX, XSL Formatting Objects, ePub, plain text, RDF, JSON; and to/from Word OOXML (docx) and OpenOfice (odt). They concentrate on the core TEI modules which are used for simple transcription and "born digital" writing. It is important to understand that they do '''not'''
* cover ''all'' TEI elements and possible attribute values
* attempt to define a standard TEI processing or rendering model
They should not be treated as the definitive view of the TEI Consortium about rendering TEI documents.

== Features ==

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

== System requirements ==
"The XSL FO style sheets were developed for use with PassiveTeX (http://projects.oucs.ox.ac.uk/passivetex/), a system using XSL formatting objects to render XML to PDF via LaTeX. They have not been extensively tested with the other XSL FO implementations."<ref>http://www.tei-c.org/release/doc/tei-xsl/</ref>

Software dependencies:

* Saxon 9.2 or later. If using Debian or Ubuntu, you can get it from http://tei.oucs.ox.ac.uk/teideb/ .
* ant and ant-contrib. Note that as of 2011-11-30, ant-contrib is not availabe as as RedHat package.

== Source code and licensing ==
This software is dual-licensed:

1. Distributed under a Creative Commons Attribution-ShareAlike 3.0
Unported License http://creativecommons.org/licenses/by-sa/3.0/

2. http://www.opensource.org/licenses/BSD-2-Clause

== Support for TEI ==

The stylesheets render TEI XML documents to various formats, with the constraint that they do not offer an implementation of all tags,
and only support a limited range of values for the @rend attribute.

== Language(s) ==
Documentation is in English.

== Documentation ==
http://www.tei-c.org/release/doc/tei-xsl/

Among the components of this package of stylesheets not documented are the following:

* <code>tools/oddbyexample.xsl</code> – generates a list of all the attribute values used in the directory of texts you apply it to, in the form of an [[ODD]] file, from which you can in turn generate documentation and schemas using Roma
* <code>tools/odd2nuodd.xsl</code> – switches from a traditional ODD-by-exclusion to a newer form ODD-by-inclusion

See also this guide by Laura Mandell, which contains some documentation and some videos: http://idhmc.tamu.edu/chat/xslt/modifyTEI.html
However, be aware that this covers an earlier release, and things may have changed

=== Creating a custom profile ===

To create a profile for converting to/from a format and TEI XML, create either or both as needed:

<code>profiles/$PROFILENAME/$FORMAT/to.xsl</code>

<code>profiles/$PROFILENAME/$FORMAT/from.xsl</code>

Start by copying the files in <code>profiles/default/$FORMAT/</code> and then adding your own overrides and/or additional templates. See [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1303&L=TEI-L&F=&S=&P=99998 this brief example of additional templates].

Note that if your <code>$FORMAT</code> is docx, this directory must contain a file <code>template.docx</code> which is used to create .docx files from. See the sample in the default profile.

=== Converting from DOCX format ===

"The TEI conversions from docx are better in many ways than the conversions from other the wordprocessing formats. There are also small tricks like having docx styles of 'tei_elementName' to get certain phrase-level elements converted."<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;1123776a.1605</ref>

== Tech support ==
Bugs and feature requests should be made in GitHub: https://github.com/TEIC/Stylesheets/issues

== User community ==

== Sample implementations ==

The package includes a number of profiles in the <code>profiles/</code> directory.

== Current version number and date of release ==

7.47.0 (2019-01-29)

== History of versions ==

See detailed changelog at https://github.com/TEIC/Stylesheets and automatically generated commit log at https://github.com/TEIC/Stylesheets/commits/master . Past versions can be downloaded at https://sourceforge.net/projects/tei/files/Stylesheets/ .

== How to download or buy ==

If you use [[Oxygen]], the easiest thing to do might be to download as part of [http://code.google.com/p/oxygen-tei/ oxygen-tei], the open-source TEI framework built into <oXygen/>. Otherwise, there are '''three options''':

=== a) Download zip file ===
Download the latest zip file (below all of the folders) from https://sourceforge.net/projects/tei/files/Stylesheets/ .

=== b) Install the Debian package ===

Install the <code>tei-xsl</code> Debian package from the [http://tei.oucs.ox.ac.uk/teideb/ list of Debian packages].

=== c) Get from Github ===

<code>
git clone git@github.com:TEIC/Stylesheets.git /path/to/local/directory/Stylesheets
</code>

Then, if you want to add these to <code>/usr/</code> (which you will need to do in order to use the command-line shell scripts), you can do the following:

<code>
cd /path/to/local/directory/Stylesheets/
</code>

<code>
make install
</code>

but note the following:

* You will need to run <code>make install</code> as a user with write permission to <code>/usr/</code> . So if using Ubuntu, for example, you will need to instead do <code>sudo make install</code> .

== Additional notes ==
The XSLT 1.0 version of this stylesheet family, which is no longer actively maintained, can be found on Github at https://github.com/sebastianrahtz/TEIXSL-v1.git

== Notes ==

<references/>

Samples of TEI texts

2019-01-25T14:53:21Z

Kshawkin: /* Texts */ added Van Gogh letters

[[Category: Markup]] [[Category: TEI:P4]] [[Category: TEI:P5]] __NOTOC__
The availability of texts enables others to learn by example; fosters similar approaches to solving the same problems across the entire community of practice; and gives developers of TEI-based tools a broader sample of texts to test against. The fact a text is listed here should not be taken as a licence to redistribute the text, please check with text owners should they wish to make any more in-depth use of these materials.

== Explicitly Pedagogical Samples ==

* [http://teibyexample.org TEI By Example] is a set of examples design to teach the basics of TEI. Includes TEI P3 (SGML) and P5 examples. [http://creativecommons.org/licenses/by-sa/3.0/ CC licensed].

== Texts ==

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

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

* [https://github.com/StanfordUniversityLibraries/ap_tei '''FRDA'''] (French Revolution Digital Archive) TEI of full text for 82 volumes of French Revolution parliamentary debates from 1787 to 1794

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

* [https://github.com/CopticScriptorium/corpora Coptic SCRIPTORIUM corpora] for the [http://copticscriptorium.org/ Coptic SCRIPTORIUM]

* [http://www.deutschestextarchiv.de/download '''DTA'''] Deutsches Textarchiv (2435 texts as of 2016-12-21)

* [http://dramacode.github.io Dramacode], French classical plays (Corneille, Molière, Racine, etc.)

* [https://github.com/textcreationpartnership '''EEBO'''] collection Phase 1 TEI P5 XML versions of texts (Text Creation Partnership's Early English Books Online) ([https://raw.githubusercontent.com/textcreationpartnership/Texts/master/TCP.csv CSV file listing all the texts]) (32853 texts as of 2015-01-01)

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

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

* [http://www.folgerdigitaltexts.org/ '''Folger Digital Texts''']: From the Folger Shakespeare Library, "Each play in Folger Digital Texts is rigorously encoded: every word, every punctuation mark, every space, within a sophisticated, TEI-compliant XML structure."

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

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

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

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

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

* The University of [http://www.ota.ox.ac.uk/ '''Oxford Text Archive'''] (OTA) is home to some 2685 TEI P5 texts, including all of the ECCO texts which are in the public domain, all available under CC licences, plus some TEI P5 linguistic corpora, and others following older editions of the guidelines, with legacy licences. The OTA exists as a community resource, and projects and people are encouraged to offer texts for deposit in the archive.

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

* The [http://buddhistinformatics.ddbc.edu.tw/BZA/bzaComCatWeb.html '''Samyukta Agama''' Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. Markup documentation, schemas and stylesheets are available as a zip archive at the website.

* The [http://buddhistinformatics.ddbc.edu.tw/biographies/gis/ '''Chinese Buddhist Bibliographies''' Project] at Dharma Drum Buddhist College provides access to different collections with more than 1000 biographies marked up in TEI for place and person names as well as dates. The archives contain basic documentation, schema etc. The data is in Chinese, linked to authority databases and available through three different interfaces visualizing it as GIS light, social network and on a timeline. All the data is published under a CC licence.

* The [http://buddhistinformatics.ddbc.edu.tw/fosizhi/ '''Chinese Buddhist Temple Gazetteers''' Project] at Dharma Drum Buddhist College provides access to topographical descriptions of Buddhist temple marked up for place and person names as well as dates. All together there are 237 gazetteers, 13 of which are available with TEI markup and new punctuation. The archives contain the TEI, image files referenced in the TEI, schema, METS wrapper etc. The data is linked to authority databases and available through an interface that displays the marked-up edition next to the images. The data is published under a CC licence.

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

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

* [https://github.com/iulibdcs/tei_text TEI and Plain Text from Digital Collections Services, Indiana University Libraries]

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

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

* [http://txm.bfm-corpus.org/?command=documentation&path=/GRAAL '''La Queste del Saint Graal'''] (The Quest of the Holy Grail) online interactive edition offers a parallel multi-level (normalized, diplomatic and imitative) transcription of the Lyon MN PA 77 manuscript along with manuscript images and a translation in modern French, powered by TXM text search and statistical analysis platform. The complete source XML-TEI P5 encoded with Menota extensions manuscript transcriptions and an ODD customization file, as well as the stylesheets used to produce HTML editions and a PDF printable version are freely available for [http://txm.bfm-corpus.org/txm/images/graal_src.zip download] under a CC BY-NC-SA 3.0 license.

* [http://docsouth.unc.edu/southlit/poe/menu.html "Tales" by Edgar Allan Poe] at University of North Carolina at Chapel Hill. Uses mnemonic entity references for non-ASCII characters.

* [https://github.com/TEI-examples/tei-examples tei-examples] -- Examples of TEI documents dealing with different use-cases.

* [https://textgrid.de/digitale-bibliothek '''TextGrid''' Digital Library] conversion from Zeno-XML-Markup to XML-TEI and additional markup

* [https://github.com/stuartyeates/sampler URLs to diverse TEI files] in terms of language, structure, linguistics, coding, tools in use, hosting method, etc.

* [http://vangoghletters.org/vg/ Vincent Van Gogh: The Letters] -- See [http://vangoghletters.org/vg/about_6.html "About this edition"].

* [https://github.com/oeuvres Works in French and TEI] (Baudelaire, Hugo, Rimbaud, Verlaine, Balzac, Descartes, La Fayette, Sade, Saint-Simon, etc.)

== Dictionaries ==
* [[FreeDict]] is a repository of various TEI-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Most of the dictionaries have been converted from TEI P4 to TEI P5, but not all of the changes can be found in the official releases yet. Visiting [http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/ the SVN repository] directly may be the better way out.
* [http://ducange.enc.sorbonne.fr/ Du Cange] is a medieval latin dictionary (mostly written during XVIIe XVIIIe). The printed text is encoded in TEI-P5, freely available at http://svn.code.sf.net/p/ducange/code/xml/ as an [http://sourceforge.net/p/ducange/wiki/Home/ open source project]. The TEI choices are [http://svn.code.sf.net/p/ducange/code/xml/ducange.html documented (in french)].
* [http://algone.net/littre/ Littré] a classical French dictionary, encoded in TEI-P5, freely available at https://svn.code.sf.net/p/javacrim/code/littre/xml/, [https://svn.code.sf.net/p/javacrim/code/littre/xml/schema.html documented in French with the words of Littré himself]

TEI Publisher

2018-12-23T17:34:11Z

Kshawkin: /* Current version number and date of release */

'''Not to be confused with [[TeiPublisher|teiPublisher]]'''.

[[Category:Tools]]

[[Category:Publishing and delivery tools]]

== Synopsis ==
"The instant publishing toolbox"<ref>http://teipublisher.com/</ref>

== Features ==
* High quality editions: Publish your digital edition without writing code. Using the TEI Processing Model, customising the appearance of the text is all done in XML.
* Cross media & multidevice: TEI Publisher generates applications which work well across devices and include features like page by page browsing, search and cross-media export.
* Single source publishing: Create HTML, ePUBs or PDFs from a single document and its associated processing model. No media specific stylesheets required.
* Lean code: For developers, TEI Publisher heavily reduces the amount of custom code required by typical digital edition projects. Save thousands of lines on handwritten transformations and rely on maintained code libraries instead.<ref>http://teipublisher.com/</ref>

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

== System requirements ==
[[Exist]] 4.x.x for version 4.0<ref>https://teipublisher.com/exist/apps/tei-publisher/doc/blog/tei-publisher-40.xml</ref>

== Source code and licensing ==

== Support for TEI ==

== Language(s) ==

== Documentation ==
http://teipublisher.com/exist/apps/tei-publisher/doc/documentation.xml

== Tech support ==

== User community ==

== Sample implementations ==
http://teipublisher.com/index.html#tp-showcases

== Current version number and date of release ==

4.0 (2018-12-20)

== History of versions ==

== How to download or buy ==
https://gitlab.existsolutions.com/tei-publisher

== Additional notes ==

== References ==
<references/>

TEI Publisher

2018-12-23T17:33:59Z

Kshawkin: /* System requirements */

'''Not to be confused with [[TeiPublisher|teiPublisher]]'''.

[[Category:Tools]]

[[Category:Publishing and delivery tools]]

== Synopsis ==
"The instant publishing toolbox"<ref>http://teipublisher.com/</ref>

== Features ==
* High quality editions: Publish your digital edition without writing code. Using the TEI Processing Model, customising the appearance of the text is all done in XML.
* Cross media & multidevice: TEI Publisher generates applications which work well across devices and include features like page by page browsing, search and cross-media export.
* Single source publishing: Create HTML, ePUBs or PDFs from a single document and its associated processing model. No media specific stylesheets required.
* Lean code: For developers, TEI Publisher heavily reduces the amount of custom code required by typical digital edition projects. Save thousands of lines on handwritten transformations and rely on maintained code libraries instead.<ref>http://teipublisher.com/</ref>

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

== System requirements ==
[[Exist]] 4.x.x for version 4.0<ref>https://teipublisher.com/exist/apps/tei-publisher/doc/blog/tei-publisher-40.xml</ref>

== Source code and licensing ==

== Support for TEI ==

== Language(s) ==

== Documentation ==
http://teipublisher.com/exist/apps/tei-publisher/doc/documentation.xml

== Tech support ==

== User community ==

== Sample implementations ==
http://teipublisher.com/index.html#tp-showcases

== Current version number and date of release ==

4.0 (2018-12-21)

== History of versions ==

== How to download or buy ==
https://gitlab.existsolutions.com/tei-publisher

== Additional notes ==

== References ==
<references/>

TEI Publisher

2018-12-23T17:32:54Z

Kshawkin: /* Current version number and date of release */

'''Not to be confused with [[TeiPublisher|teiPublisher]]'''.

[[Category:Tools]]

[[Category:Publishing and delivery tools]]

== Synopsis ==
"The instant publishing toolbox"<ref>http://teipublisher.com/</ref>

== Features ==
* High quality editions: Publish your digital edition without writing code. Using the TEI Processing Model, customising the appearance of the text is all done in XML.
* Cross media & multidevice: TEI Publisher generates applications which work well across devices and include features like page by page browsing, search and cross-media export.
* Single source publishing: Create HTML, ePUBs or PDFs from a single document and its associated processing model. No media specific stylesheets required.
* Lean code: For developers, TEI Publisher heavily reduces the amount of custom code required by typical digital edition projects. Save thousands of lines on handwritten transformations and rely on maintained code libraries instead.<ref>http://teipublisher.com/</ref>

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

== System requirements ==
[[Exist]] 3.6.0 or later for version 3.0<ref>http://teipublisher.com/exist/apps/tei-publisher-home/index.html</ref>

== Source code and licensing ==

== Support for TEI ==

== Language(s) ==

== Documentation ==
http://teipublisher.com/exist/apps/tei-publisher/doc/documentation.xml

== Tech support ==

== User community ==

== Sample implementations ==
http://teipublisher.com/index.html#tp-showcases

== Current version number and date of release ==

4.0 (2018-12-21)

== History of versions ==

== How to download or buy ==
https://gitlab.existsolutions.com/tei-publisher

== Additional notes ==

== References ==
<references/>

TEITOK

2018-12-06T01:43:12Z

Kshawkin: /* Additional notes */ alternative path to website

[[Category:Tools]]

[[Category:Conversion and preprocessing tools]]
[[Category:Publishing and delivery tools]]
[[Category:Querying tools]]

== Synopsis ==

TEITOK - the Tokenized TEI Environment, a web-based platform for viewing, creating, and editing corpora with both rich textual mark-up and linguistic annotation pereferably in TEI annotation. It is developed at the Centro de Linguística da Universidade de Lisboa.

== Features ==

* Build a corpus where each text consists of a TEI/XML file
* Annotate and edit each text in the corpus
** Use a variety of scripts to provide automatic annotations
** Use an easy GUI to edit manually
* Search the corpus using [http://cwb.sourceforge.net CQP]
** Search results give XML fragments rather than raw CQP results
** Statistical data about the results can be rendered as graphs
** Edit XML documents directly from the CQP results
* Visualize each TEI/XML file individually
** Various visualization options depending on the content of the file
* Plot the XML documents on the world map (OpenStreetMap)
** Provide search results direclty on the map
* Align the XML transcription with a facsimile image
** Visualize each manuscript line above its transription
** Get facsimile images of words from a CQP search
** Transcribe directly from the facsimile image to TEI/XML
* Work with dependency relations in TEI/XML
** Searchable using a modified version of CQP (TT-CQP)
** Create word sketches from the corpus
* Align the XML transcription with an audio file
** Get audio fragments direclty from a CQP search
** Visualize the audio as a waveform
** Transcribe directly from the audio file to TEI/XML
* Use stand-off annotation alongside the TEI/XML files
** Visualization and editing of the stand-off inspired by Brat
** Search the stand-off annotations direclty in CQP
* Work with interlinear glossed texts

== User commentary ==

== System requirements ==

Server based software that runs on most Linux servers

== Source code and licensing ==

The source code is available from GitLab, and can be used free of charge

== Support for TEI ==

In principle, TEITOK works with generic XML files, and can hence handle most flavours of TEI/XML. For more advanced features, it assumes the XML to be in TEI/XML P5.

== Language(s) ==

* Interface written in PHP and Javascript
* Scripts written in Perl and C++
* Multilingual interface with customizable internationalization
* Documentation in English

== Documentation ==

[http://www.teitok.org/index.php?action=about]
[http://www.teitok.org/index.php?action=help]

Publications: [http://www.teitok.org/index.php?action=publications]

== Tech support ==

For tech support, there is both a [https://groups.google.com/forum/#!forum/teitok Google group mailing list] and a [https://www.facebook.com/maartenes Facebook page] for TEITOK.

== User community ==

== Sample implementations ==

Examples of projects using TEITOK can be found on the project website: http://www.teitok.org/. Here are some highlighted projects:

* [http://ps.clul.ul.pt Postscriptum] - a corpus of handwritten letter in Portuguese and Spanish
* [http://corpora.ugr.es/ode ODE] - a historic corpus of mediaeval Spanish
* [http://cards-fly.clul.ul.pt/teitok/madison MADISON] - a dialectal corpus of Portuguese
* [http://teitok.iltec.pt/croltec/ CroLTeC] - a learner corpus of Croatian

== Current version number and date of release ==

Frequent updates, current version is 2.3 (August 2018)

== History of versions ==

A complete version changelog can be found on [https://gitlab.com/maartenes/TEITOK/blob/master/CHANGELOG.md GitLab]

== How to download or buy ==

TEITOK is currently a private project on GitLab. Anybody interested in using TEITOK, please create an account on GitLab and contact the author with your account details to add you as a user to the project: Maarten Janssen.

== Additional notes ==
If the teitok.org domain name is not resolving, try accessing the website through http://beta.clul.ul.pt/teitok/site/index.php?action=home .

Editors

2018-11-23T17:44:39Z

Kshawkin: /* Table of Editors */ link to TEI-L discussion about Atom

Periodically the question of which editor to use for TEI tasks arises on the TEI mailing list. There is no single answer to this question, but this page attempts to help you frame the question correctly.

Before thinking about an editor, you should think about who is going to be using it, how often, for what and where.

Those from a technical background are already likely to have a preferred programmable editor. Those from a non-technical background are likely to be more interested in ease of use. Occasional or temporary users are going to what a program that works as similarly as possible to the other applications they use, whereas full-time permanent users are more likely to get a benefit from more powerful editor, even if it has a learning curve. Projects which use large XML files need to be aware that some editors struggle with large XML files. The sed editor (see below) is a special case, allowing for truly arbitrary sizes. Users who need to edit files directly on remote servers may need vt100-capable editors (emacs, vi, sed, etc).

'''If you are a teacher looking for an editor suitable for TEI instruction, have a look at the list of features that are seen as the minimal set needed for a [[Editor for teaching TEI - features|"student version" of a commercial editor]]. This feature set is under discussion and you are welcome to take part in it.'''

The following table an be sorted by several keys. You can accomplish that by clicking on the symbol in the relevant table header cell. Javascript needs to be enabled for the dynamic sorting to work. You can sort by a secondary key with the Shift key pressed.

== Table of Editors ==

{| class="wikitable sortable" border="1"
|+Editors for TEI
|-
! Name !! Operating Systems or Environments !! [http://en.wikipedia.org/wiki/FLOSS FLOSS]? !! Explicit support for XML !! Explicit support for TEI !! class="unsortable"|URL !!Projects Using !! Beginner-friendliness (scale 1-10, 1=hard) !! [http://en.wikipedia.org/wiki/Right-to-left RTL] support !! Notes
|-
| Ace|| Web-based || Yes || Yes, but primitive and buggy || No || [http://ace.ajax.org/] || [[ANGLES]] || 2 || ||
|-
| [[ANGLES]]|| Web-based || Yes || In-progress || ? || [http://umd-mith.github.com/angles/] || || || || The [https://securegrants.neh.gov/publicquery/Download.aspx?data=EbwGdSyLkD7zoB3W75cvd%2bXST%2bWypC%2blxN287EYCLJwL%2fBHyeaDHU3RDLrfbJLx%2b1ItCBTsjaJWE63FMYJfoM3kRWI6WIx3tbxFY0YxJWCwUaJYoXKOUXjj912Gj3rBbZPl64VCB8sIYhhUUUvZJSw%3d%3d white paper] released as part of the NEH grant which funded ANGLES' development indicates that development has ceased. This editor is based on the [http://ace.ajax.org/ Ace] editor.
|-
| Atom || Win, Linux, MacOS || Yes || Yes || No || [https://atom.io/] || [[ATOM]] || 2 || || Needs the package [https://atom.io/packages/linter-autocomplete-jing] to validate with a declared schema. See [https://listserv.brown.edu/cgi-bin/wa?A2=TEI-L;b3a054c.1811 more discussion on TEI-L].
|-
| CodeMirror|| Web-based || Yes || Yes, but primitive and buggy || No || [http://codemirror.net/] || XET || 2 || || Cannot support namespaces without an architectural change due to the absence of lookahead for modes.
|-
| Emeditor || Win || No|| No || No || [http://www.emeditor.com] ||[http://www.lib.umich.edu/tcp/ TCP]|| 9 || || PRO: large-file support, utf-8 support, diff.
|-
| [[Editix]]|| Win, Linux, MacOS || No || Yes || No || [http://www.editix.com/] || || || || A free Lite version exists.
|-
| EditPad Pro || Win ||No || No || No || [http://www.editpadpro.com] ||[http://www.lib.umich.edu/tcp/ TCP]|| 8 || || PRO: UTF-8 support, excellent character-encoding conversions, syntax coloring, regex search/replace, XML 'content folding', handles large files well. CON: no search-in-files, sort, uniq, or diff.
|-
| EditTEI|| all (Java) || No || No || No || [http://www.digiscrib.com/Fra/Edittei.html] || || || || Claiming many features, accessible after registration.
|-
| [[Emacs]] || Mac, Win, Linux, Solaris || Yes || Yes || No || [http://savannah.gnu.org/projects/emacs/] || [http://www.nzetc.org/ NZETC] [http://www.wwp.brown.edu/ WWP]|| 3 || || (See also [[TEIEmacs]]) Best mode for TEI XML is nXML, using RELAX NG compact schemas. For Mac look for Aquamacs package
|-
| epcEdit || Win, Linux, Solaris || No || Yes || No || [http://www.epcedit.com] ||[http://www.lib.umich.edu/tcp/ TCP]|| 7 || || Free; also supports SGML; feels a bit like XMetaL
|-
| Essential XML Editor (formerly Open XML Editor) || Win || Yes || Yes || No || [http://www.philo.de/xmledit/] || || 8 || || Text-based editing, DTD validation, various input encodings but output only in UTF-8, plugin of Saxon XSLT processor and hex editor possible; plugin of Jing, Libxml2 and MSV (W3C-schema, RelaxNG validation) possible only in purchased version
|-
| [[Exchanger XML Editor]]||all (Java) || || || No || [http://www.exchangerxml.com/editor/] || || || || Heavily obsolete (as of Feb'15), won't run on a new Java installation
|-
| [[FontoXML]] || Web-based || No || Yes || Yes || [http://www.FontoXML.com]|| || 9 || 2014 || Web-based XML editor, including a TEI-edition. FontoXML integrates seamlessly into most web content management systems and workflow software.
|-
| [[Geany]] || all || Yes || Yes || No || [http://www.geany.org] || || || || Geany is a cross-platform IDE suitable for XML and HTML, C, Java, PHP, HTML, Python, Perl and Pascal.
|-
| [[jEdit]] || all (Java) || Yes || Yes || Yes || [http://www.jedit.org/] || [http://www.nzetc.org/ NZETC] || 7 || || XML use requires plugins, and only supports DTDs
|-
| Liquid XML Editor|| Win || No || Yes || No || [http://www.liquid-technologies.com/xml-editor.aspx/] || || || || Features of the XML Editor include Validation, XML Syntax Highlighting and Multi-step undo/redo.
|-
| [[Notepad++]]|| Win || Yes || Yes || No || [http://notepad-plus.sourceforge.net/] || [http://www.lib.umich.edu/tcp/ TCP] || 9 || || Freeware. XML support via XMLTools plugin. Basic editor made more versatile by plugin system (eg. Base64 encode-decode, hex editor, etc)
|-
| Office suite + OxGarage || All || ?|| Yes || Yes || [http://www.oucs.ox.ac.uk/oxgarage/]|| || 9 || || Users edit using standard office suite and documents converted to TEI via webservice
|-
| [[oXygen]] || all (Java) || No || Yes || Yes || [http://www.oxygenxml.com/] ||[http://www.wwp.brown.edu/ WWP] [http://www.digitalhumanities.org/dhq/ DHQ] || 8 || in Editor, possibly in Author || Can validate using DTD, W3C schema, RELAX NG, and Schematron; can run XSL transformations on file; WYSIWYG mode using CSS; support for TEI ODD files (editing and schema generation)
|-
| [[Sacodeyl Annotator]]|| all (Java) || || || || [http://www.um.es/sacodeyl/en/pages/software.htm#annotator] || || || ||
|-
| sed || Mac, Win, Linux, Solaris || Yes || No || No || [http://www.grymoire.com/Unix/Sed.html] || || -1 || || Handles with ease files a order of magnitude larger than the system RAM
|-
| [[Serna]]|| || No || Yes || unknown || [http://www.serna-xmleditor.com/] || || || yes || Part of Corena studio now.
|-
| [[Serna|Serna Free]]|| || Yes || Yes || Yes || [https://sourceforge.net/projects/sernafree/] || || || yes || [http://en.wikipedia.org/wiki/Syntext_Serna Wikipedia] reports that the free version of Serna is no longer "distributed." This probably means that the parent company no longer expends any resources on it. The source code of the free version is still available under a GPL license, hosted on Sourceforge.
|-
| [[TextMate]]|| MacOS || No || || No || [http://macromates.com/] || || || || An extension is needed for XML editing
|-
| TextPad || Win || No || No || No || [http://www.textpad.com] ||[http://www.lib.umich.edu/tcp/ TCP]|| 9 || || PRO: simple interface, powerful regex/multi-file replace, search-in-files, primary and secondary sort, uniq, diff, hotlinked search results, syntax coloring. CON: no utf-8 support.
|-
| UltraEdit || Win, Linux || No || Yes || No || [http://www.ultraedit.com/] || || 9 || || customizable for TEI-support; can handle extremely large files; powerful regex/multi-file replace; macro recording
|-
| vi || Mac, Win, Linux, Solaris || Yes || No || No || [http://www.vim.org/] || || 1 || || Ships on all POSIX systems (linux, solaris, BSD, etc) as standard, thus the lowest common denominator editor for server configuration
|-
| [[Wed]] || Web-based || Yes || Yes || Yes || [http://mangalam-research.github.io/wed/] || [https://btw.mangalamresearch.org/ BTW] || 7 || Not as of version 0.20.0 || Provides validation and guided editing. Understands RNG. Can be customized for specific projects. Can show XML structures in a way that mirrors the XML (labels showing location of open and close tags) or stylistically (e.g. headings in bold) in a single view.
|-
| [[XML Copy Editor]] || Win, Ubuntu || Yes || Yes || Yes || [http://xml-copy-editor.sourceforge.net/] ||[http://www.lib.umich.edu/tcp/ TCP]|| 7 || || Free; validates to DTD, XSD, Relax.ng
|-
| XMLBlueprint|| Win || || || || [http://www.xmlblueprint.com/] || || || ||
|-
| XMLMax || Win || No || Yes || No || [http://www.xponentsoftware.com/] || || 8 || || Unlimited XML file size support with low memory requirement. XML parsing with error reporting and fixing. Collapsable treeview, DTD and XML schema validation. XPATH and XSLT.
|-
| [[XMLmind]]|| all (Java) || No || Yes || No || [http://www.xmlmind.com/xmleditor/] || || || no || An evaluation version can be used for 30 days. The last free version is/was the 5.4.0 personal edition.
|-
| XPontus || all (Java) || Yes || Yes || No || [http://xpontus.sourceforge.net] || || || || XPontus XML Editor is a simple XML Editor oriented towards text editing. It can perform validation(DTD, XML Schema, Relax NG, Batch XML validation), XSL transformations(HTML, XML, PDF, SVG), schema/DTD generation, XML/DTD/HTML/XSL code completion, code formatting and much more. Plugin based.
|-
| [[XMLSpy]]|| all (Java) || No || Yes || No || [http://www.altova.com/xml-editor/] || || || yes || Fully functional free 30-day trial versions are offered.
|-
| XMLwriter|| Win || || || || [http://xmlwriter.net/] || || || ||
|-
|}

== Humour ==

Tension between emacs and vi users is longstanding and well summarised on the [http://en.wikipedia.org/wiki/Editor_war Editor war] Wikipedia page. vi was included in the [http://en.wikipedia.org/wiki/POSIX POSIX] standard, whereas emacs was not, perhaps because vi was historically available in multiple implementations from multiple vendors. The following cartoon illustrates the commonly-held assumptions that emacs and vi are very powerful but obscure while their competitors make users do all the work.

[[Image:0xbabaf000l.png|Copyright (c) 2007 Laurent Gregoire http://tnerual.eriogerg.free.fr/0xBABAF000L/10_en.html]]

[[Category:Tools]]
[[Category:Editing tools| ]]

OXygen

2018-10-23T18:38:47Z

Kshawkin: /* Current version number and date of release */

[[Category:Tools]]

[[Category:All-in-one Tools]]
[[Category:Development tools]]
[[Category:Editing tools]]
[[Category:Conversion and preprocessing tools]]

== Synopsis ==
<oXygen/> is a high-powered, cross-platform, graphical XML editor with built-in support for TEI.

== Features ==
Supports most features typical of a high-end XML editor, including:
* syntax coloring
* context-sensitive content assistant
* built-in validation and well-formedness checking
* built-in XSLT engines
* Unicode support
* formatting and indentation
* folding
* outline view (shows document structure)
* model view (shows element content model)
* XPath support
* XSLT debugger
* DTD/schema editor
* Text, Grid, and Author (tagless) editing modes

See also http://www.oxygenxml.com/features.html .

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

I have found this program to be affordable, easy to use, and pre-loaded with TEI capabilities. Also, the platform gets upgraded on a regular basis. -- Greg Moses (Austin, TeiXas!)

== System requirements ==
Runs under Windows, Linux, and Mac operating systems. Requires a Java VM (virtual machine).

(One of the download options for Windows users is an installer that includes the Java VM, eliminating the need to download and install Java separately.)

For detailed requirements, see http://www.oxygenxml.com/download.html .

== Source code and licensing ==
Closed source. Academic licenses available for $48 per person, allowing you to install for your own use on many computers and use with the current major version number. A discount is available for TEI subscribers and individuals from TEI member institutions; the discount code may be found by logging in to [http://members.tei-c.org/MemberInfo http://members.tei-c.org/MemberInfo]. Free 30-day trial license available.

== Support for TEI ==

===The TEI Framework in <oXygen>===

As of Version 9.0 build 2007110615, <oXygen> has TEI P5 schemas, templates and the TEI XSL stylesheets included as an officially-supported framework.

If you are not using the <code>tei-oxygen</code> [[TEIDebian|Debian package]] (for which a package manager will provide automatic updates for new versions of the stylesheet library), you can upgrade your copy of the stylesheet library without needing to download a new version of <oXygen/> doing doing either of the following:

* With version 15.2 or later of <oXygen/>, "subscribe" to the regularly-updated TEI distribution of the framework according to the instructions in this blog post: https://faqingperplxd.wordpress.com/2014/04/02/auto-update-your-tei-framework-in-oxygen/ .

* Use [http://sourceforge.net/projects/tei/files/oxygen-tei/ oxygen-tei], the open-source TEI framework built into <oXygen/>. To install this, look in your Oxygen folder for a "frameworks" directory that contains a directory called "tei". That's where the contents of the zip would go, replacing the old contents of that directory. ''Note that this is not the same thing as the <code>tei-oxygen</code> [[TEIDebian|Debian package]]!'' You can also build this framework for yourself if you are interested in doing so; the [https://github.com/TEIC/oxygen-tei project code is available on GitHub].

=== Other TEI-related Plugins ===

<oXygen/> allows third-party plugins and frameworks. The following are of possible interest to TEI users:

====HisTEI====

If you work with historical documents, you might use [https://github.com/odaata/HisTEI HisTEI], a framework designed to make historical documents easier to transcribe in <<oXygen/>'s XML Author mode.<ref>http://www.oxygenxml.com/pipermail/oxygen-sdk/2014-November/000182.html</ref>

==== Severin ====

[http://code.google.com/p/severin-image-viewer/ Severin] is an image viewer plugin, by Kilian Schmidtner and Stefan Krause, that can be used to see images as you browse though documents. It is an open source project (MIT license), and on the project page you can find a video presentation that uses a TEI document as example.

==== TEI-Facsimile-Plugin ====

[https://github.com/oxygenxml/TEI-Facsimile-Plugin TEI-Facsimile-Plugin] "provides support for working with Digital Facsimiles in Text Encoding Initiative (TEI) vocabulary. The plugin contributes a new View in which the user can load an image and draw shapes. These shapes are then converted into TEI "zone" elements. All the existing "zone" elements from the document are also rendered over the image."<ref>https://github.com/oxygenxml/TEI-Facsimile-Plugin</ref> This plugin requires oXygen version 15 or later.

==== dbTagger ====

https://github.com/aerhard/dbTagger

==== ediarum ====

[[Ediarum]]

==== TEI Completer ====

https://github.com/BCDH/TEI-Completer

==== oXygen-XML-editor-attribute-editor ====

* [https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;7d49b3c3.1612 announcement]
* https://github.com/AlexJitianu/oXygen-XML-editor-attribute-editor

== Language(s) ==
Interface available in English, French, German, Italian, Japanese and Dutch.

Documentation available in English.

== Documentation ==
http://www.oxygenxml.com/documentation.html

== Tech support ==
http://www.oxygenxml.com/techSupport.html

Can buy maintenance and support pack, providing free upgrades and tech support.

== User community ==
* http://www.oxygenxml.com/mailman/listinfo/oxygen-user/
* http://www.oxygenxml.com/forum/

== Current version number and date of release ==
20.1 build ID 2018101517 (2018-10-23)

== History of versions ==
See http://www.oxygenxml.com/software_archive.html .

== How to download or buy ==
http://www.oxygenxml.com/download.html

If you use Debian or Ubuntu, you should instead install the <tt>tei-oxygen</tt> package at http://tei.oucs.ox.ac.uk/teideb/ . (More information below.)

== Additional notes ==

David Sewell wrote:

<blockquote>
Because the schema files distributed with oXygen sometimes lag behind
the latest TEI releases, kind souls like Syd Bauman have from time to
time packaged new schema files so that they can be unpacked to replace
part of the oXygen frameworks hierarchy. You could also go to

http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/

and grab the files there to replace the ones in a local oXygen
directory.
<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;8d5b98b2.0804</ref>
</blockquote>

Sebastian Rahtz added that if you use Debian or Ubuntu, you should instead install the <code>tei-oxygen</code> package. He explained that "this replaces the oXygen TEI package with a link to one installed by the tei-p5-schema package, which is kept up to date. This means you have only one set of TEI files on your machine." It's available at http://tei.oucs.ox.ac.uk/teideb/ .

Marcus Bingenheimer:
If you edit ODD files you need to validate the ODD against tei_odds. tei_all will not catch all mistakes and gives and error whenever elements in the RNG or other namespaces are used within <datatype>.
As usual you can associate the tei_odds with a oxygen specific processing command similar to this:
<code><?oxygen RNGSchema="{your oxygen folder}/frameworks/tei/xml/tei/custom/schema/relaxng/tei_odds.rng" type="xml"?></code>

== References ==
<references/>

Tei-xsl

2018-10-06T12:53:43Z

Kshawkin: /* Current version number and date of release */

[[Category:Tools]]

[[Category:Conversion and preprocessing tools]]
[[Category:Publishing and delivery tools]]
[[Category:XSLT]]

== Synopsis ==
This is a family of XSLT 2.0 stylesheets to transform TEI XML documents to various formats, including XHTML, LaTeX, XSL Formatting Objects, ePub, plain text, RDF, JSON; and to/from Word OOXML (docx) and OpenOfice (odt). They concentrate on the core TEI modules which are used for simple transcription and "born digital" writing. It is important to understand that they do '''not'''
* cover ''all'' TEI elements and possible attribute values
* attempt to define a standard TEI processing or rendering model
They should not be treated as the definitive view of the TEI Consortium about rendering TEI documents.

== Features ==

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

== System requirements ==
"The XSL FO style sheets were developed for use with PassiveTeX (http://projects.oucs.ox.ac.uk/passivetex/), a system using XSL formatting objects to render XML to PDF via LaTeX. They have not been extensively tested with the other XSL FO implementations."<ref>http://www.tei-c.org/release/doc/tei-xsl/</ref>

Software dependencies:

* Saxon 9.2 or later. If using Debian or Ubuntu, you can get it from http://tei.oucs.ox.ac.uk/teideb/ .
* ant and ant-contrib. Note that as of 2011-11-30, ant-contrib is not availabe as as RedHat package.

== Source code and licensing ==
This software is dual-licensed:

1. Distributed under a Creative Commons Attribution-ShareAlike 3.0
Unported License http://creativecommons.org/licenses/by-sa/3.0/

2. http://www.opensource.org/licenses/BSD-2-Clause

== Support for TEI ==

The stylesheets render TEI XML documents to various formats, with the constraint that they do not offer an implementation of all tags,
and only support a limited range of values for the @rend attribute.

== Language(s) ==
Documentation is in English.

== Documentation ==
http://www.tei-c.org/release/doc/tei-xsl/

Among the components of this package of stylesheets not documented are the following:

* <code>tools/oddbyexample.xsl</code> – generates a list of all the attribute values used in the directory of texts you apply it to, in the form of an [[ODD]] file, from which you can in turn generate documentation and schemas using Roma
* <code>tools/odd2nuodd.xsl</code> – switches from a traditional ODD-by-exclusion to a newer form ODD-by-inclusion

See also this guide by Laura Mandell, which contains some documentation and some videos: http://idhmc.tamu.edu/chat/xslt/modifyTEI.html
However, be aware that this covers an earlier release, and things may have changed

=== Creating a custom profile ===

To create a profile for converting to/from a format and TEI XML, create either or both as needed:

<code>profiles/$PROFILENAME/$FORMAT/to.xsl</code>

<code>profiles/$PROFILENAME/$FORMAT/from.xsl</code>

Start by copying the files in <code>profiles/default/$FORMAT/</code> and then adding your own overrides and/or additional templates. See [http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1303&L=TEI-L&F=&S=&P=99998 this brief example of additional templates].

Note that if your <code>$FORMAT</code> is docx, this directory must contain a file <code>template.docx</code> which is used to create .docx files from. See the sample in the default profile.

=== Converting from DOCX format ===

"The TEI conversions from docx are better in many ways than the conversions from other the wordprocessing formats. There are also small tricks like having docx styles of 'tei_elementName' to get certain phrase-level elements converted."<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;1123776a.1605</ref>

== Tech support ==
Bugs and feature requests should be made in GitHub: https://github.com/TEIC/Stylesheets/issues

== User community ==

== Sample implementations ==

The package includes a number of profiles in the <code>profiles/</code> directory.

== Current version number and date of release ==

7.46.0 (2018-10-05)

== History of versions ==

See detailed changelog at https://github.com/TEIC/Stylesheets and automatically generated commit log at https://github.com/TEIC/Stylesheets/commits/master . Past versions can be downloaded at https://sourceforge.net/projects/tei/files/Stylesheets/ .

== How to download or buy ==

If you use [[Oxygen]], the easiest thing to do might be to download as part of [http://code.google.com/p/oxygen-tei/ oxygen-tei], the open-source TEI framework built into <oXygen/>. Otherwise, there are '''three options''':

=== a) Download zip file ===
Download the latest zip file (below all of the folders) from https://sourceforge.net/projects/tei/files/Stylesheets/ .

=== b) Install the Debian package ===

Install the <code>tei-xsl</code> Debian package from the [http://tei.oucs.ox.ac.uk/teideb/ list of Debian packages].

=== c) Get from Github ===

<code>
git clone git@github.com:TEIC/Stylesheets.git /path/to/local/directory/Stylesheets
</code>

Then, if you want to add these to <code>/usr/</code> (which you will need to do in order to use the command-line shell scripts), you can do the following:

<code>
cd /path/to/local/directory/Stylesheets/
</code>

<code>
make install
</code>

but note the following:

* You will need to run <code>make install</code> as a user with write permission to <code>/usr/</code> . So if using Ubuntu, for example, you will need to instead do <code>sudo make install</code> .

== Additional notes ==
The XSLT 1.0 version of this stylesheet family, which is no longer actively maintained, can be found on Github at https://github.com/sebastianrahtz/TEIXSL-v1.git

== Notes ==

<references/>

Workgroup to revise the Best Practices for TEI in Libraries

2018-09-10T16:00:41Z

Kshawkin: /* Meeting minutes */

== Background ==

[https://list.indiana.edu/sympa/arc/teilib-l/2015-11/msg00006.html Invitation to participate] in revision of ''[http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]''

== Logistics ==

First Monday of each month

9–10 a.m. Eastern Time in North America (14:00–15:00 UTC in winter in North America, 13:00–14:00 UTC at other times of the year)

People with email addresses listed below will have hangout link sent to them for each meeting. We can do up to 10 people with a regular hangout. If we get more people, we'll find someone with a Google Apps for Education account who can support up to 15(?).

: Actually, you can only invite up to 5 people to a Hangout. Beyond that, you need to just share a link. We'll plan to share the link on teilib-l shortly before each meeting.

If you can't make it, follow along by reviewing minutes (linked below) and/or watching [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues issues on GitHub] (click "watch" after logging in) and adding comments there.

== Resources ==

* [https://drive.google.com/open?id=0B13gonNAATNSSmtJMk14VHpzazQ Our Google Drive folder]
* [http://paramedic.wwp.northeastern.edu/~syd/temp/BPTL/ latest development snapshot]

== Members ==
* Kevin Hawkins (kevin.s.hawkins@gmail)
* stuart yeates ()
* stefanie gehrke (stefanie.gehrke9@gmail.com)
* Elli Mylonas (elli_mylonas@brown.edu)
* James Griffin (griffinj@lafayette.edu [or jrgriffiniii@gmail.com])
* Lisa McAulay ()
* Martin Mueller (martinmueller@northwestern.edu)
* Michelle Dalmau ()
* Antonio Rojas ()
* Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu])
* Peter Gorman (peter.gorman@wisc.edu)
* Andrew Rouner (andrew.rouner@gmail.com)
* Syd Bauman (s.bauman@northeastern.edu)

== Suggested meeting procedure ==

# Appoint notetaker, creating a new Google Docs file in our Google Drive folder.
# Resume discussions postponed from last meeting.
# Go through issues not yet discussed in order of [[BP revision ticket triage]]. For each issue, someone volunteers to summarize the issue:
## If the issue is straightforward and there's immediate consensus, ask for volunteer to record consensus as a comment on the issue, wait 7 days for objections, and then implement*.
## If issue is complicated, ask for volunteer to examine issue more closely after the meeting to propose a solution (either rejecting suggestion or changing prose and/or schema to implement*). Volunteer will post proposed solution as comment on the issue at least 7 days before our next meeting and lead discussion at next meeting.
### If there is consensus, volunteer implements* after the meeting.
### If there are any adjustments to proposal at that time, volunteer records in a comment on the issue and waits another 7 days for objections before implementing*.
# After meeting, those present review the minutes in the next 48 hours. Notetaker then announces minutes on TEILIB-L.

<nowiki>*</nowiki> Change may be implemented either by committing to the master branch or making pull requests. The advantage of a pull request is that it forces a second set of eyes to review changes. This is especially important for changes to content models in the ODD (rather than simply to prose).

== Meeting minutes ==

* [[Minutes for February 1, 2016|February 1, 2016]]
* [[March 7, 2016]]
* [[April 4, 2016]]
* [[May 2, 2016]]
* [[June 6, 2016]]
* [[July 11, 2016]]
* [[August 1, 2016]]
* [[September 12, 2016]]
* [[October 10, 2016]]
* [[November 14, 2016]]
* [[December 12, 2016]]
* [[January 9, 2017]]
* [[February 13, 2017]]
* [[March 6, 2017]]
* [[April 3, 2017]]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/blob/master/2017-05-08_notes.xml May 8, 2017]
* June 19, 2017 (decisions recorded only in GitHub issues)
* July 18, 2017 (decisions recorded only in GitHub issues)
* August 14, 2017 (decisions recorded only in GitHub issues)
* August 28, 2017
* September 11, 2017
* January 23, 2018 (decisions recorded only in GitHub issues)
* February 13, 2018 (decisions recorded only in GitHub issues)
* March 13, 2018 (decisions recorded only in GitHub issues)
* April 11, 2018 (decisions recorded only in GitHub issues)
* May 2, 2018 (decisions recorded only in GitHub issues)
* May 29, 2018 (decisions recorded only in GitHub issues)
* July 10, 2018 (decisions recorded only in GitHub issues)
* August 14, 2018 (decisions recorded only in GitHub issues)
* August 23, 2018 (decisions recorded only in GitHub issues)
* August 30, 2018 (decisions recorded only in GitHub issues)
[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]

Workgroup to revise the Best Practices for TEI in Libraries

2018-08-30T21:47:34Z

Kshawkin: /* Meeting minutes */ added 2018-08-30 meeting

== Background ==

[https://list.indiana.edu/sympa/arc/teilib-l/2015-11/msg00006.html Invitation to participate] in revision of ''[http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]''

== Logistics ==

First Monday of each month

9–10 a.m. Eastern Time in North America (14:00–15:00 UTC in winter in North America, 13:00–14:00 UTC at other times of the year)

People with email addresses listed below will have hangout link sent to them for each meeting. We can do up to 10 people with a regular hangout. If we get more people, we'll find someone with a Google Apps for Education account who can support up to 15(?).

: Actually, you can only invite up to 5 people to a Hangout. Beyond that, you need to just share a link. We'll plan to share the link on teilib-l shortly before each meeting.

If you can't make it, follow along by reviewing minutes (linked below) and/or watching [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues issues on GitHub] (click "watch" after logging in) and adding comments there.

== Resources ==

* [https://drive.google.com/open?id=0B13gonNAATNSSmtJMk14VHpzazQ Our Google Drive folder]
* [http://paramedic.wwp.northeastern.edu/~syd/temp/BPTL/ latest development snapshot]

== Members ==
* Kevin Hawkins (kevin.s.hawkins@gmail)
* stuart yeates ()
* stefanie gehrke (stefanie.gehrke9@gmail.com)
* Elli Mylonas (elli_mylonas@brown.edu)
* James Griffin (griffinj@lafayette.edu [or jrgriffiniii@gmail.com])
* Lisa McAulay ()
* Martin Mueller (martinmueller@northwestern.edu)
* Michelle Dalmau ()
* Antonio Rojas ()
* Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu])
* Peter Gorman (peter.gorman@wisc.edu)
* Andrew Rouner (andrew.rouner@gmail.com)
* Syd Bauman (s.bauman@northeastern.edu)

== Suggested meeting procedure ==

# Appoint notetaker, creating a new Google Docs file in our Google Drive folder.
# Resume discussions postponed from last meeting.
# Go through issues not yet discussed in order of [[BP revision ticket triage]]. For each issue, someone volunteers to summarize the issue:
## If the issue is straightforward and there's immediate consensus, ask for volunteer to record consensus as a comment on the issue, wait 7 days for objections, and then implement*.
## If issue is complicated, ask for volunteer to examine issue more closely after the meeting to propose a solution (either rejecting suggestion or changing prose and/or schema to implement*). Volunteer will post proposed solution as comment on the issue at least 7 days before our next meeting and lead discussion at next meeting.
### If there is consensus, volunteer implements* after the meeting.
### If there are any adjustments to proposal at that time, volunteer records in a comment on the issue and waits another 7 days for objections before implementing*.
# After meeting, those present review the minutes in the next 48 hours. Notetaker then announces minutes on TEILIB-L.

<nowiki>*</nowiki> Change may be implemented either by committing to the master branch or making pull requests. The advantage of a pull request is that it forces a second set of eyes to review changes. This is especially important for changes to content models in the ODD (rather than simply to prose).

== Meeting minutes ==

* [[Minutes for February 1, 2016|February 1, 2016]]
* [[March 7, 2016]]
* [[April 4, 2016]]
* [[May 2, 2016]]
* [[June 6, 2016]]
* [[July 11, 2016]]
* [[August 1, 2016]]
* [[September 12, 2016]]
* [[October 10, 2016]]
* [[November 14, 2016]]
* [[December 12, 2016]]
* [[January 9, 2017]]
* [[February 13, 2017]]
* [[March 6, 2017]]
* [[April 3, 2017]]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/blob/master/2017-05-08_notes.xml May 8, 2017]
* June 19, 2017 (decisions recorded only in GitHub issues)
* July 18, 2017 (decisions recorded only in GitHub issues)
* August 14, 2017 (decisions recorded only in GitHub issues)
* August 28, 2017
* September 11, 2017
* January 23, 2018 (decisions recorded only in GitHub issues)
* February 13, 2018 (decisions recorded only in GitHub issues)
* March 13, 2018 (decisions recorded only in GitHub issues)
* April 11, 2018 (decisions recorded only in GitHub issues)
* May 2, 2018 (decisions recorded only in GitHub issues)
* May 29, 2018 (decisions recorded only in GitHub issues)
* July 10, 2018 (decisions recorded only in GitHub issues)
* August 14, 2018 (decisions recorded only in GitHub issues)
* August 23, 2018
* August 30, 2018
[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]

Upconversion

2018-08-26T16:39:51Z

Kshawkin: /* Identifying named entities */ added HIRMEOS workshop on entity-fishing

== Introduction: on automating tagging ==

When you begin learning text encoding, you might think that people transcribe a source document and then add all the tags into the document by hand.

Then you learn how to use an [[:Category:Editing tools|XML editor]] to not only validate your XML but also save keystrokes on entering elements.

And then you learn about [[Digitization tools|OCR software]], which can save you effort in transcribing a source document, leaving you just to correct OCR errors.

And then you learn that there are vendors that will do some combination of scanning, OCR, and encoding documents (often through "double keyboarding" according to a vendor spec such as [[TEI Tite]], which guarantees verity high accuracy in transcription and encoding). While vendors are generally not expected to add markup requiring specialized knowledge (this might be left to project staff), it is also not a good use of resources to expect a vendor to perform basic structural tagging if this can be easily deduced from OCR output or from page images. ''Upconversion'' from a less structured format to a more structured one can sometimes be performed through rules-based techniques (like XSLT), but the data is usually inconsistent enough that there may be competing sets of rules. Basic ''heuristic techniques'' that choose between competing rules can be used to make judgments about features on the page and derive markup from these. They are never perfect, but neither are human encoders.

Furthermore, more advanced heuristics and information retrieval (IR) techniques can be used to identify named entities, topics, sentiment, tone, and complexity of a text, and IR techniques are frequently used for authorship attribution.

Below are resources that might be helpful for those looking to use heuristic and IR techniques to add markup to an XML document.

== Adding structural markup ==

* [[GROBID]]
* [http://bilbo.hypotheses.org/ BILBO]
* [http://wing.comp.nus.edu.sg/parsCit/ ParsCit]
* [https://sourceforge.net/projects/pdf2xml/ pdf2xml]
* various projects coming out of [http://lamp.cfar.umd.edu/ LAMP]
* [http://pdfx.cs.man.ac.uk/ pdfx]
* [https://code.google.com/p/lapdftext/ LA-PDFText] (turns PDF into some sort of XML)
* [http://www.shabash.net/merops/default.html Merops]
* [https://github.com/scrapy/scrapely scrapely] -- HTML to JSON
* [https://github.com/coolwanglu/pdf2htmlEX pdf2htmlEX]
* see “Ideas” section of [http://web.archive.org/web/20130921075854/http://scholrev.org/hackathon http://scholrev.org/hackathon/]
* see [https://listserv.nd.edu/cgi-bin/wa?A2=ind1506&L=CODE4LIB&F=&S=&P=134330 discussion of structuring OCRd text on CODE4LIB]
* Open Typesetting Stack (formerly the PKP XML Parsing Service): ([https://github.com/pkp/ots sourcecode], [http://pkp-udev.lib.sfu.ca/ beta site]) -- discerns structure to create various output formats

== Identifying named entities ==

* [http://bilbo.hypotheses.org/ BILBO]
* [http://www.opencalais.com/ Calais]
* [http://seasr.org/ SEASR]
* [http://semlab.io/DADAlytics_ner_demo/ NER toolchain from Semantic Lab]
* [http://www.hirmeos.eu/2018/08/21/hirmeos-workshop-entity-fishing-for-digital-humanities-and-scholarly-publishing/ HIRMEOS Workshop: Entity-Fishing for Digital Humanities and Scholarly Publishing HIRMEOS Workshop: Entity-Fishing for Digital Humanities and Scholarly Publishing]

== Identifying topics, sentiment, tone, and complexity ==

* [http://www.opencalais.com/ Calais]

[[Category:Tools]]

Workgroup to revise the Best Practices for TEI in Libraries

2018-08-23T17:07:13Z

Kshawkin: /* Meeting minutes */ added August meetings

== Background ==

[https://list.indiana.edu/sympa/arc/teilib-l/2015-11/msg00006.html Invitation to participate] in revision of ''[http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]''

== Logistics ==

First Monday of each month

9–10 a.m. Eastern Time in North America (14:00–15:00 UTC in winter in North America, 13:00–14:00 UTC at other times of the year)

People with email addresses listed below will have hangout link sent to them for each meeting. We can do up to 10 people with a regular hangout. If we get more people, we'll find someone with a Google Apps for Education account who can support up to 15(?).

: Actually, you can only invite up to 5 people to a Hangout. Beyond that, you need to just share a link. We'll plan to share the link on teilib-l shortly before each meeting.

If you can't make it, follow along by reviewing minutes (linked below) and/or watching [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues issues on GitHub] (click "watch" after logging in) and adding comments there.

== Resources ==

* [https://drive.google.com/open?id=0B13gonNAATNSSmtJMk14VHpzazQ Our Google Drive folder]
* [http://paramedic.wwp.northeastern.edu/~syd/temp/BPTL/ latest development snapshot]

== Members ==
* Kevin Hawkins (kevin.s.hawkins@gmail)
* stuart yeates ()
* stefanie gehrke (stefanie.gehrke9@gmail.com)
* Elli Mylonas (elli_mylonas@brown.edu)
* James Griffin (griffinj@lafayette.edu [or jrgriffiniii@gmail.com])
* Lisa McAulay ()
* Martin Mueller (martinmueller@northwestern.edu)
* Michelle Dalmau ()
* Antonio Rojas ()
* Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu])
* Peter Gorman (peter.gorman@wisc.edu)
* Andrew Rouner (andrew.rouner@gmail.com)
* Syd Bauman (s.bauman@northeastern.edu)

== Suggested meeting procedure ==

# Appoint notetaker, creating a new Google Docs file in our Google Drive folder.
# Resume discussions postponed from last meeting.
# Go through issues not yet discussed in order of [[BP revision ticket triage]]. For each issue, someone volunteers to summarize the issue:
## If the issue is straightforward and there's immediate consensus, ask for volunteer to record consensus as a comment on the issue, wait 7 days for objections, and then implement*.
## If issue is complicated, ask for volunteer to examine issue more closely after the meeting to propose a solution (either rejecting suggestion or changing prose and/or schema to implement*). Volunteer will post proposed solution as comment on the issue at least 7 days before our next meeting and lead discussion at next meeting.
### If there is consensus, volunteer implements* after the meeting.
### If there are any adjustments to proposal at that time, volunteer records in a comment on the issue and waits another 7 days for objections before implementing*.
# After meeting, those present review the minutes in the next 48 hours. Notetaker then announces minutes on TEILIB-L.

<nowiki>*</nowiki> Change may be implemented either by committing to the master branch or making pull requests. The advantage of a pull request is that it forces a second set of eyes to review changes. This is especially important for changes to content models in the ODD (rather than simply to prose).

== Meeting minutes ==

* [[Minutes for February 1, 2016|February 1, 2016]]
* [[March 7, 2016]]
* [[April 4, 2016]]
* [[May 2, 2016]]
* [[June 6, 2016]]
* [[July 11, 2016]]
* [[August 1, 2016]]
* [[September 12, 2016]]
* [[October 10, 2016]]
* [[November 14, 2016]]
* [[December 12, 2016]]
* [[January 9, 2017]]
* [[February 13, 2017]]
* [[March 6, 2017]]
* [[April 3, 2017]]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/blob/master/2017-05-08_notes.xml May 8, 2017]
* June 19, 2017 (decisions recorded only in GitHub issues)
* July 18, 2017 (decisions recorded only in GitHub issues)
* August 14, 2017 (decisions recorded only in GitHub issues)
* August 28, 2017
* September 11, 2017
* January 23, 2018 (decisions recorded only in GitHub issues)
* February 13, 2018 (decisions recorded only in GitHub issues)
* March 13, 2018 (decisions recorded only in GitHub issues)
* April 11, 2018 (decisions recorded only in GitHub issues)
* May 2, 2018 (decisions recorded only in GitHub issues)
* May 29, 2018 (decisions recorded only in GitHub issues)
* July 10, 2018 (decisions recorded only in GitHub issues)
* August 14, 2018 (decisions recorded only in GitHub issues)
* August 23, 2018
[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]

ODD

2018-08-20T13:51:07Z

Kshawkin: /* Presentations */ added http://tei.it.ox.ac.uk/Talks/2014-10-odds/

'''ODD''' stands for "One Document Does it all". It is a TEI XML-conformant specification format that allows one to customize TEI P5 in a [[Wikipedia:literate programming|literate programming]] fashion. It uses elements from the new [http://www.tei-c.org/P5/Guidelines/TD.html Documentation Elements] module and is designed for processing in a pipeline as in [http://tei.it.ox.ac.uk/Talks/2014-10-odds/oddity.png this diagram].

== Description ==
The TEI Guidelines, its DTD, and its schema fragments, are all produced from a single XML resource containing:

# Descriptive prose (lots of it)
# Examples of usage (plenty)
# Formal declarations for components of the TEI Abstract Model:
## elements and attributes
## modules
## classes and macros

We call this resource an ODD (One Document Does it all), although the master source is instantiated as a gazillion XML mini-documents.

A system of XSLT stylesheets called [[Roma]] has been created for the purpose of easy manipulation of ODD files.

== Example ==
The TEI scheme can only be used by customizing it. Customizations are also expressed in the ODD language. For example:

<pre>
<schemaSpec ident="myTEIlite">
<desc>This is TEI Lite with simplified heads</desc>
<moduleRef key="tei"/>
<moduleRef key="textstructure"/>
<moduleRef key="linking"/>
<moduleRef key="core"/>
<moduleRef key="header"/>
<elementSpec ident="head" mode="change">
<content><textNode/></content>
</elementSpec>
</schemaSpec>
</pre>

produces a schema a bit like TEI Lite, with a slight change : the element <head> now can contain only text nodes.

== Uses besides the TEI Guidelines and various customizations ==

* [http://www.w3.org/TR/its/ Internationalization Tag Set (ITS)]
* various standards proposal designed within ISO committee TC 37 have been totally or partially written in TEI/ODD: MLIF, MAF, ISO 16642 rev., ISOTimeML

== "Pure ODD" ==

Over the years ODD has evolved in response to the needs of the TEI community, both as the core specification language for the TEI guidelines, and also as a generic customization language. Since 2004, much
effort has been put into making it less of a hybrid language, combining its own vocabulary with RelaxNG fragments and Schematron rules. Versions of TEI P5 later than 2.5 contain elements which can be used to express content models directly in the TEI ODD language, rather than in RELAXNG. ODD is thus an entirely self-contained generic specification language, independent
of other existing grammars, and hence known as Pure ODD. The proposals for Pure ODD were included in the Guidelines during January 2016, and are included as part of the 3.0.0 release

If your existing TEI schema was developed prior to this release, you should probably read up on [http://teic.github.io/TCW/purifyDoc.html How to Update your ODD]

== See also ==
*[http://en.wikipedia.org/wiki/ODD_%28Text_Encoding_Initiative%29 ODD (Text Encoding Initiative)] in Wikipedia
*[[ODD-dev]] Not updated since 2012
*[[ODD chaining]] Not updated since 2012
=== Documentation ===
* [http://www.tei-c.org/Guidelines/Customization/odds.xml Getting Started with P5 ODDs]
* [http://teic.github.io/TCW/howtoGenerate.html How to Make an ODD Automagically]
* [http://teic.github.io/TCW/howtoChain.html ODD chaining for Beginners]
* [http://teic.github.io/TCW/purifyDoc.html How to Update your ODD] (from a pre 3.0 version)
* [http://www.w3.org/TR/xml-i18n-bp/#tei-modularization A fragment of W3C's Best Practices for XML Internationalization concerning ODD customization for the Internationalization Tag Set (ITS).]
* [[Mapping ODD processing]]

=== Presentations ===
*[http://tei.oucs.ox.ac.uk/Oxford/2007-02-13-oucs/talk-odds.xml A talk about the ODD system], given on 13 Feb 2007 by Lou Burnard and Sebastian Rahtz at the OUCS ''Encoding Digital Texts'' workshop
*[http://tei.oucs.ox.ac.uk/Oxford/2006-09-methNet/Talks/RomaJourney.ppt A PowerPoint presentation on TEI/ODD] by Laurent Romary; OUCS, September 2006
*[http://www.balisage.net/Proceedings/vol7/html/Banski01/BalisageVol7-Banski01.html Literate serialization of linguistic metamodels] by Piotr Bański, Balisage-2011
*[http://tei.it.ox.ac.uk/Talks/2014-10-odds/ ODD workshop (October 2014)]

=== Articles ===
* [http://jtei.revues.org/842 Resolving the Durand Conundrum], by Lou Burnard
* [http://conferences.idealliance.org/extreme/html/2004/Bauman01/EML2004Bauman01.html Odd Customizations], by Syd Bauman and Julia Flanders.
* [http://conferences.idealliance.org/extreme/html/2004/Burnard01/EML2004Burnard01.html RelaxNG with Son of ODD], by Lou Burnard and Sebastian Rahtz.
* [http://www.balisage.net/Proceedings/vol1/html/Bauman01/BalisageVol1-Bauman01.html Freedom to Constrain] by Syd Bauman

[[Category:Customization|!]]

ODD

2018-08-20T13:49:50Z

Kshawkin: link to diagram of ODD processing pipeline

'''ODD''' stands for "One Document Does it all". It is a TEI XML-conformant specification format that allows one to customize TEI P5 in a [[Wikipedia:literate programming|literate programming]] fashion. It uses elements from the new [http://www.tei-c.org/P5/Guidelines/TD.html Documentation Elements] module and is designed for processing in a pipeline as in [http://tei.it.ox.ac.uk/Talks/2014-10-odds/oddity.png this diagram].

== Description ==
The TEI Guidelines, its DTD, and its schema fragments, are all produced from a single XML resource containing:

# Descriptive prose (lots of it)
# Examples of usage (plenty)
# Formal declarations for components of the TEI Abstract Model:
## elements and attributes
## modules
## classes and macros

We call this resource an ODD (One Document Does it all), although the master source is instantiated as a gazillion XML mini-documents.

A system of XSLT stylesheets called [[Roma]] has been created for the purpose of easy manipulation of ODD files.

== Example ==
The TEI scheme can only be used by customizing it. Customizations are also expressed in the ODD language. For example:

<pre>
<schemaSpec ident="myTEIlite">
<desc>This is TEI Lite with simplified heads</desc>
<moduleRef key="tei"/>
<moduleRef key="textstructure"/>
<moduleRef key="linking"/>
<moduleRef key="core"/>
<moduleRef key="header"/>
<elementSpec ident="head" mode="change">
<content><textNode/></content>
</elementSpec>
</schemaSpec>
</pre>

produces a schema a bit like TEI Lite, with a slight change : the element <head> now can contain only text nodes.

== Uses besides the TEI Guidelines and various customizations ==

* [http://www.w3.org/TR/its/ Internationalization Tag Set (ITS)]
* various standards proposal designed within ISO committee TC 37 have been totally or partially written in TEI/ODD: MLIF, MAF, ISO 16642 rev., ISOTimeML

== "Pure ODD" ==

Over the years ODD has evolved in response to the needs of the TEI community, both as the core specification language for the TEI guidelines, and also as a generic customization language. Since 2004, much
effort has been put into making it less of a hybrid language, combining its own vocabulary with RelaxNG fragments and Schematron rules. Versions of TEI P5 later than 2.5 contain elements which can be used to express content models directly in the TEI ODD language, rather than in RELAXNG. ODD is thus an entirely self-contained generic specification language, independent
of other existing grammars, and hence known as Pure ODD. The proposals for Pure ODD were included in the Guidelines during January 2016, and are included as part of the 3.0.0 release

If your existing TEI schema was developed prior to this release, you should probably read up on [http://teic.github.io/TCW/purifyDoc.html How to Update your ODD]

== See also ==
*[http://en.wikipedia.org/wiki/ODD_%28Text_Encoding_Initiative%29 ODD (Text Encoding Initiative)] in Wikipedia
*[[ODD-dev]] Not updated since 2012
*[[ODD chaining]] Not updated since 2012
=== Documentation ===
* [http://www.tei-c.org/Guidelines/Customization/odds.xml Getting Started with P5 ODDs]
* [http://teic.github.io/TCW/howtoGenerate.html How to Make an ODD Automagically]
* [http://teic.github.io/TCW/howtoChain.html ODD chaining for Beginners]
* [http://teic.github.io/TCW/purifyDoc.html How to Update your ODD] (from a pre 3.0 version)
* [http://www.w3.org/TR/xml-i18n-bp/#tei-modularization A fragment of W3C's Best Practices for XML Internationalization concerning ODD customization for the Internationalization Tag Set (ITS).]
* [[Mapping ODD processing]]

=== Presentations ===
*[http://tei.oucs.ox.ac.uk/Oxford/2007-02-13-oucs/talk-odds.xml A talk about the ODD system], given on 13 Feb 2007 by Lou Burnard and Sebastian Rahtz at the OUCS ''Encoding Digital Texts'' workshop
*[http://tei.oucs.ox.ac.uk/Oxford/2006-09-methNet/Talks/RomaJourney.ppt A PowerPoint presentation on TEI/ODD] by Laurent Romary; OUCS, September 2006
*[http://www.balisage.net/Proceedings/vol7/html/Banski01/BalisageVol7-Banski01.html Literate serialization of linguistic metamodels] by Piotr Bański, Balisage-2011

=== Articles ===
* [http://jtei.revues.org/842 Resolving the Durand Conundrum], by Lou Burnard
* [http://conferences.idealliance.org/extreme/html/2004/Bauman01/EML2004Bauman01.html Odd Customizations], by Syd Bauman and Julia Flanders.
* [http://conferences.idealliance.org/extreme/html/2004/Burnard01/EML2004Burnard01.html RelaxNG with Son of ODD], by Lou Burnard and Sebastian Rahtz.
* [http://www.balisage.net/Proceedings/vol1/html/Bauman01/BalisageVol1-Bauman01.html Freedom to Constrain] by Syd Bauman

[[Category:Customization|!]]

User talk:Maarten Janssen

2018-08-17T14:22:36Z

Kshawkin: Welcome!

'''Welcome to ''TEIWiki''!'''
We hope you will contribute much and well.
You will probably want to read the [[Help:Contents|help pages]].
Again, welcome and have fun! [[User:Kshawkin|Kshawkin]] 14:22, 17 August 2018 (UTC)

User:Maarten Janssen

2018-08-17T14:22:35Z

Kshawkin: Creating user page with biography of new user.

Developer of the TEITOK system for building TEI/XML based corpora - working at the CELGA-ILTEC institute of the University of Coimbra.

[[Category:Users]]

TEI Transviewer

2018-08-03T14:09:24Z

Kshawkin: /* How to download or buy */ added link

[[Category:Tools]]
[[Category:Publishing and delivery tools]]

== Synopsis ==
TEI Transviewer is "a tool for the transformation of XML-TEI documents so that they can be viewed in the browser. It is intended to facilitate the exploration of historical documents through side-by-side and single view of transcription and digital facsimile, synchronised scrolling and zooming, page and structural navigation, linear and diplomatic transcription view, free text search and search by categories of named entities (persons, organisations, places, dates), etc."<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;424fc759.1707</ref>

== Features ==

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

== System requirements ==

== Source code and licensing ==
"If this type of tool may be of interest for some of you, an open source release will be made available soon."<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;424fc759.1707</ref>

== Support for TEI ==

== Language(s) ==
"The TEI Transviewer is based on Java server-side XSLT transformation, Javascript and CSS."<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;424fc759.1707</ref>

== Documentation ==

== Tech support ==

== User community ==

== Sample implementations ==
https://www.cvce.eu/search?q=*&format=tei%2Bxml

== Current version number and date of release ==

== History of versions ==

== How to download or buy ==
https://github.com/C2DH/open-tei-transviewer

== Additional notes ==

== References ==
<references/>

TEI Transviewer

2018-08-03T14:06:56Z

Kshawkin: removed leftovers from wiki template

[[Category:Tools]]
[[Category:Publishing and delivery tools]]

== Synopsis ==
TEI Transviewer is "a tool for the transformation of XML-TEI documents so that they can be viewed in the browser. It is intended to facilitate the exploration of historical documents through side-by-side and single view of transcription and digital facsimile, synchronised scrolling and zooming, page and structural navigation, linear and diplomatic transcription view, free text search and search by categories of named entities (persons, organisations, places, dates), etc."<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;424fc759.1707</ref>

== Features ==

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

== System requirements ==

== Source code and licensing ==
"If this type of tool may be of interest for some of you, an open source release will be made available soon."<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;424fc759.1707</ref>

== Support for TEI ==

== Language(s) ==
"The TEI Transviewer is based on Java server-side XSLT transformation, Javascript and CSS."<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;424fc759.1707</ref>

== Documentation ==

== Tech support ==

== User community ==

== Sample implementations ==
https://www.cvce.eu/search?q=*&format=tei%2Bxml

== Current version number and date of release ==

== History of versions ==

== How to download or buy ==

== Additional notes ==

== References ==
<references/>

Workgroup to revise the Best Practices for TEI in Libraries

2018-07-18T00:46:59Z

Kshawkin: /* Meeting minutes */ added last few meetings

== Background ==

[https://list.indiana.edu/sympa/arc/teilib-l/2015-11/msg00006.html Invitation to participate] in revision of ''[http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]''

== Logistics ==

First Monday of each month

9–10 a.m. Eastern Time in North America (14:00–15:00 UTC in winter in North America, 13:00–14:00 UTC at other times of the year)

People with email addresses listed below will have hangout link sent to them for each meeting. We can do up to 10 people with a regular hangout. If we get more people, we'll find someone with a Google Apps for Education account who can support up to 15(?).

: Actually, you can only invite up to 5 people to a Hangout. Beyond that, you need to just share a link. We'll plan to share the link on teilib-l shortly before each meeting.

If you can't make it, follow along by reviewing minutes (linked below) and/or watching [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues issues on GitHub] (click "watch" after logging in) and adding comments there.

== Resources ==

* [https://drive.google.com/open?id=0B13gonNAATNSSmtJMk14VHpzazQ Our Google Drive folder]
* [http://paramedic.wwp.northeastern.edu/~syd/temp/BPTL/ latest development snapshot]

== Members ==
* Kevin Hawkins (kevin.s.hawkins@gmail)
* stuart yeates ()
* stefanie gehrke (stefanie.gehrke9@gmail.com)
* Elli Mylonas (elli_mylonas@brown.edu)
* James Griffin (griffinj@lafayette.edu [or jrgriffiniii@gmail.com])
* Lisa McAulay ()
* Martin Mueller (martinmueller@northwestern.edu)
* Michelle Dalmau ()
* Antonio Rojas ()
* Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu])
* Peter Gorman (peter.gorman@wisc.edu)
* Andrew Rouner (andrew.rouner@gmail.com)
* Syd Bauman (s.bauman@northeastern.edu)

== Suggested meeting procedure ==

# Appoint notetaker, creating a new Google Docs file in our Google Drive folder.
# Resume discussions postponed from last meeting.
# Go through issues not yet discussed in order of [[BP revision ticket triage]]. For each issue, someone volunteers to summarize the issue:
## If the issue is straightforward and there's immediate consensus, ask for volunteer to record consensus as a comment on the issue, wait 7 days for objections, and then implement*.
## If issue is complicated, ask for volunteer to examine issue more closely after the meeting to propose a solution (either rejecting suggestion or changing prose and/or schema to implement*). Volunteer will post proposed solution as comment on the issue at least 7 days before our next meeting and lead discussion at next meeting.
### If there is consensus, volunteer implements* after the meeting.
### If there are any adjustments to proposal at that time, volunteer records in a comment on the issue and waits another 7 days for objections before implementing*.
# After meeting, those present review the minutes in the next 48 hours. Notetaker then announces minutes on TEILIB-L.

<nowiki>*</nowiki> Change may be implemented either by committing to the master branch or making pull requests. The advantage of a pull request is that it forces a second set of eyes to review changes. This is especially important for changes to content models in the ODD (rather than simply to prose).

== Meeting minutes ==

* [[Minutes for February 1, 2016|February 1, 2016]]
* [[March 7, 2016]]
* [[April 4, 2016]]
* [[May 2, 2016]]
* [[June 6, 2016]]
* [[July 11, 2016]]
* [[August 1, 2016]]
* [[September 12, 2016]]
* [[October 10, 2016]]
* [[November 14, 2016]]
* [[December 12, 2016]]
* [[January 9, 2017]]
* [[February 13, 2017]]
* [[March 6, 2017]]
* [[April 3, 2017]]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/blob/master/2017-05-08_notes.xml May 8, 2017]
* June 19, 2017 (decisions recorded only in GitHub issues)
* July 18, 2017 (decisions recorded only in GitHub issues)
* August 14, 2017 (decisions recorded only in GitHub issues)
* August 28, 2017
* September 11, 2017
* January 23, 2018 (decisions recorded only in GitHub issues)
* February 13, 2018 (decisions recorded only in GitHub issues)
* March 13, 2018 (decisions recorded only in GitHub issues)
* April 11, 2018 (decisions recorded only in GitHub issues)
* May 2, 2018 (decisions recorded only in GitHub issues)
* May 29, 2018 (decisions recorded only in GitHub issues)
* July 10, 2018 (decisions recorded only in GitHub issues)
[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]

SIG:MSS

2018-07-02T23:37:58Z

Kshawkin: /* Manuscript Description */ new link for msw05

<big>'''TEI Special Interest Group on Manuscripts (TEI MS SIG)'''</big>

== Introduction ==
The goal of the TEI Special Interest Group on Manuscripts is to bring together users of the TEI who wish to improve the encoding strategies for marking up transcriptions and editions of manuscript materials. The SIG was originally setup by Elena Pierazzo, Susan Schreibman, and Edward Vanhoutte. It is currently convened by Gerrit Brüning and Stephen McCormick.

The SIG runs a mailing list. To join visit http://listserv.brown.edu/tei-ms-sig.html.

==Achievements==
The SIG’s most important achievements were in the field of the representation of primary sources, resulting in the proposals of the working group on [[Genetic Editions]] which were submitted as “[http://www.tei-c.org/Activities/Council/Working/tcw19.html An Encoding Model for Genetic Editions]” and largely incorporated in the TEI Guidelines.

Important work was done towards a revision of the chapter on critical apparatus, see working group on [[Critical_Apparatus_Workgroup|Critical Apparatus]] / [[Textual Variance]].

== Agenda of this SIG ==
Revision of the chapter on critical apparatus; issues of variation; clarify the role of using the critical apparatus tagset in manuscript transcription (which is dependent on whether one is encoding an edition or encoding a manuscript transcription). See
*[[Critical_Apparatus_Workgroup|Critical Apparatus]]
*[[Physical_Collation|Physical Collation]]
and the following threads on sourceforge, TEI-L, and SIG-L:
*http://sourceforge.net/p/tei/bugs/357/
*http://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;bfa42e32.1310
*http://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-MS-SIG;ad41772a.1401
*“[http://listserv.brown.edu/archives/cgi-bin/wa?A1=ind1401&L=TEI-MS-SIG#3 App. Crit. state of play and questions]” and related threads on SIG-L from January 2014.
*“[https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;7d23da20.1407 <rdg>s that go on and on]“ (July 2014)
*http://sourceforge.net/p/tei/feature-requests/521/

Revision of the chapter on manuscript description; see working group on [[msDesc enhancement|MSS Description]].

Continuing and extending the work on the chapter on the representation of primary sources, see [[Sandbox for Genetic Editing]].

Further issues:
* how to encode fragments
* how to record codicology (the substance of the medium, ink stints, etc); Robinson noted that the TEI already has mechanisms to record this, but it needs to be better documented

== Past Meetings ==
* The SIG met at the Third Annual TEI Members' Meeting in Nancy, France on 08 November 2003. The report can be found [http://www.tei-c.org/Activities/SIG/Manuscript/mssigr01.xml here].
* The second meeting of the SIG was held at the Fourth Annual TEI Members' Meeting at Johns Hopkins University, Baltimore, USA, 23 October 2004. The report can be found [http://www.tei-c.org/Activities/SIG/Manuscript/mssigr02.xml here].
* The third meeting of the SIG was held at Seventh Annual TEI Member's Meeting at University of Maryland, College Park, 3nd of November 2007. The agenda of the meeting can be found [[MS SIG Agenda 2007|here]]; the report can be found [[MS SIG Report 07|here]]. During the meeting several task forces were created to deal with specific problems: the task forces main page can be found [[MS task forces|here]].
* [[SIGMS_Agenda_20081108|Agenda SIG meeting, London 8 November 2008]]
* [[SIGMS_Minutes_20091114|Minutes SIG meeting, Ann Arbor 14 November 2009]]
* [[SIGMS_Minutes_20101112|Minutes SIG meeting, Zadar 12 November 2010]]
* [[SIGMS_Minutes_20111014|Minutes SIG meeting, Würzburg 14 October 2011]]
* [[MS_SIG_meeting,_Rome,_3_October_2013|Minutes SIG meeting, Rome, 3 October 2013]]

== Links ==
=== Lists ===
*List of “institutions using TEI to encode and digitize manuscripts,” compiled by Tucker Hannah (https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-MS-SIG;e8b927bf.1304) Google spreadsheet https://docs.google.com/document/d/1Wv5Xn4aUW8uNUv1c-B5KNyzRx_TmWOKYEZylv5znPzc/edit
*“A Catalog of Digital Scholarly Editions” by Patrick Sahle http://www.digitale-edition.de./
*“A Catalogue of Digital Editions” by Greta Franzini https://sites.google.com/site/digitaleds/home Google spreadsheet “Digital Editions Catalogue” https://docs.google.com/spreadsheet/ccc?key=0Ag9fg4mfdAuPdHF2Y0twOVpaYS1MbjVWY25UNFZYWFE#gid=0
*“Editionen-Datenbank” (Editions Database) of the Deutsches Literaturarchiv Marbach (DLA) http://www.dla-marbach.de/?id=60340

=== Manuscript Description ===

Projects, resources, guidelines concerning MS description.

* [http://enrich.manuscriptorium.com ENRICH project] - standardising and aggregating medieval manuscript descriptions. See also [http://tei.oucs.ox.ac.uk/ENRICH/ OUCS ENRICH Website] containing ENRICH Schemas, ODD, Documentation and Training Materials.
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/description_dtd.html DESCRIPTION DTD] page).
* [http://www.hab.de/forschung/projekte/master-e.htm MASTER - Interface format for the description of medieval manuscripts]
* [http://www.tei-c.org/Vault/Workgroups/MS/msw05.html Reviews of the manuscript description chapter: A summary]

=== Manuscript Editions ===
* [http://bdinski.obdurodon.org/ Bdinski sbornik: Manuscript and text]
* Carolingian Canon Law http://ccl.rch.uky.edu/
* Codex Sinaiticus http://www.codexsinaiticus.org/en/
* [http://www.kantl.be/ctb/project/dalf/ DALF: Digital Archive of Letters in Flanders]
* Queste del saint Graal http://txm.ish-lyon.cnrs.fr/bfm/?command=documentation&path=/GRAAL
* Hendrik Ibsens skrifter http://www.ibsen.uio.no/forside.xhtml
* [http://web.uvic.ca/hrd/lydgate/pilot.htm Partial Transcription of John Lydgate's "Fall of Princes"]
* [http://www.digitalmishnah.umd.edu/ Digital Mishnah Project], http://www.digitalmishnah.org/
* [http://digitalmitford.org Digital Mitford: The Mary Russell Mitford Archive]
* New Testament Transcripts http://nttranscripts.uni-muenster.de/
* New Testament Virtual Manuscript Room http://ntvmr.uni-muenster.de/
* [http://www.newtonproject.ic.ac.uk/prism.php?id=1 The Newton Project]
* [http://webapp1.dlib.indiana.edu/newton/index.jsp The Chymistry of Isaac Newton]
* [http://elec.enc.sorbonne.fr/chroniqueslatines/ Chroniques latines de Saint-Denis] : critical edition using TEI P4 (but we hope to migrate in P5 this year) : [http://elec.enc.sorbonne.fr/chroniqueslatines/xml/chroniquesstdenis.xml XML Files]
* [http://www.marktwainproject.org/homepage.html Mark Twain Project Online]
* Scholarly Digital Editions http://www.sd-editions.com/
* Les manuscrits de Stendhal en ligne http://stendhal.msh-alpes.fr/manuscrits/index.php
* [http://vbd.humnet.unipi.it/ Digital Vercelli Book]
* [http://www.desgodets.net Les Cours d'Antoine Desgodets]
* [http://tei.ibi.hu-berlin.de/berliner-intellektuelle/?en Letters and Texts. Intellectual Berlin around 1800]

=== Manuscript Transcription ===
Projects, resources, guidelines concerning MS transcription.
* [http://www.cdlib.org/inside/diglib/stwg/ms/ CDL Encoding Guidelines for Manuscripts and Rare Books]
* [http://www.scriptorium.columbia.edu/ Digital Scriptorium] (see especially the [https://www1.columbia.edu/sec/cu/libraries/bts/digital_scriptorium/technical/ds-xml/transcription_dtd/index.html TRANSCRIPTION DTD] and [https://www1.columbia.edu/sec/cu/libraries/bts/digital_scriptorium/technical/ds-xml/description_dtd/index.html DESCRIPTION DTD] pages).
* [[EpiDoc]], guidelines for transcribing ancient texts
* [http://skaldic.arts.usyd.edu.au/docs/guidelines/guide.html Guidelines for the electronic edition of the skaldic corpus]
* [http://gandalf.aksis.uib.no/menota/guidelines/ The Menota handbook]
*[http://ahds.ac.uk/creating/case-studies/newton/index.htm The Newton Project: Implementing and Exploiting XML]
* [http://www.whitmanarchive.org/guidelines/ The Walt Whitman Archive Encoding Guidelines for Poetry Manuscripts]
* [http://jefferson.village.virginia.edu/seenet/piers/protocoltran.html Transcriptional Protocols: Piers Plowman Electronic Archive and SEENET]
* [http://lemo.irht.cnrs.fr/43/43-12.htm Réflexions sur l'utilisation de la TEI pour encoder les sources diplomatiques] and [http://elec.enc.sorbonne.fr/cartulaireblanc/guidebalisage/ Guide du balisage du Cartulaire blanc] : two resources in French
* [http://ccfm.ens-lsh.fr/IMG/pdf/BFM-Mss_Encodage-XML.pdf Base de Français Médiéval - MSS Encoding Guidelines (in French)]
* [http://marjorie.burghart.online.fr/?q=en/content/tei-critical-apparatus-cheatsheet TEI: Critical Apparatus Cheatsheet]
* Guidelines for Using TEI for the Carolingian Canon Law Project http://ccl.rch.uky.edu/using-TEI

===Projects using the new genetic or documentary markup===
*'''[http://www.lokalbericht.ch Digital edition of Hermann Burger's Lokalbericht]'''; genetic markup, from which textual markup is derived; source files will be available in July 2017.
*“Diachronic Markup and Presentation Practices for Text Editions in Digital Research Environments“ http://www.ehumanities.uni-passau.de/projekte/diachronic-markup/
* '''[http://www.uni-goettingen.de/en/303691.html Genetic-critical and annotated hybrid-edition of Theodor Fontane’s notebooks based on a virtual research environment]''': The TEI code (not published yet) is based on a <sourceDoc>/<zone>/<line> structure.
* '''[http://shelleygodwinarchive.org/ The Shelley-Godwin Archive]''' employs an encoding based on <sourceDoc>/<zone>/<line> and making use of <milestone> (e.g. <milestone unit="tei:p"/>) and <anchor> elements. The archive distinguishes two stages of transcriptions (basic and fully vetted) and the TEI encodings are directly accessible through the browser.
*Edition of Goethe’s Faust https://faustedition.uni-wuerzburg.de/dev/project/about
*Transcription of the [http://en.wikipedia.org/wiki/Holy_Trinity_Church,_Long_Melford#Clopton_Chantry_Chapel John Lydgate verses at Holy Trinity, Long Melford], see Matthew Davis’ post on TEI-L: http://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;34ca5119.1311
*Representation of the papers of Fernando Pessoa, see http://listserv.brown.edu/archives/cgi-bin/wa?A2=tei-l;50923a39.1402
* Proust Prototype http://research.cch.kcl.ac.uk/proust_prototype/ (see http://markmail.org/message/vtuwcuckf4ukxqfk)

[[Category:SIG|MSS]]
[[Category:SIG:Manuscripts]]

Textual Communities

2018-06-29T21:31:21Z

Kshawkin: Created page with "Category:Tools Category:Editing tools Category:Conversion and preprocessing tools Category:Publishing and delivery tools Category:Interfaces == Synopsis == ..."

[[Category:Tools]]

[[Category:Editing tools]]
[[Category:Conversion and preprocessing tools]]
[[Category:Publishing and delivery tools]]
[[Category:Interfaces]]

== Synopsis ==
"Textual Communities is an environment for the collaborative online creation of scholarly editions."<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;9bdf9845.1806</ref>

== Features ==
* It is not an adaptation of any other system, but is built anew from the ground up;
* It understands text as a collection of leaves distributed across a document tree and an entity tree. Accordingly, it can both present text page by page (or line by line), as parts of a document tree, and it can present text entity by entity, as a hierarchy of acts of eommunication (hence, line 1 of the General Prologue of the Canterbury Tales), as parts of an entity tree;
* It offers powerful collation tools, CollateX and the Collation Editor, permitting precise tailoring of the collation of any entity in muliple documents;
* It includes tools for managing collaboration: to invite, supervise and monitor multiple collaborators;
* It includes an IIIF image server, and can create editiable documents from IIIF manifests;
* It provides an API giving access to all materials through URI resource descriptors.

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

== System requirements ==

== Source code and licensing ==

== Support for TEI ==

== Language(s) ==

== Documentation ==
https://wiki.usask.ca/display/TC/Textual+Communities

== Tech support ==

== User community ==

== Sample implementations ==
* The production version: https://textualcommunities.org/
* The sandbox version: https://textualcommunitiessandbox.org/

== Current version number and date of release ==

== History of versions ==

== How to download or buy ==

== Additional notes ==

== References ==
<references/>

Apache Cocoon

2018-06-21T16:10:14Z

Kshawkin: added <references/>

[[Category:Tools]]
[[Category:Publishing and delivery tools]]

= Summary =

Apache Cocoon is a web development framework built around the concepts of separation of concerns and component-based web development. The TEI consortium website is dynamically produced from TEI XML using Cocoon.

Note that ''Cocoon is no longer being updated''.<ref>https://cdrhdev.unl.edu/log/2018/api/</ref>

= Description =

Apache Cocoon is a web development framework built around the concepts of separation of concerns (making sure people can interact and collaborate on a project, without stepping on each other toes) and component-based web development.

Cocoon implements these concepts around the notion of "component pipelines", each component on the pipeline specializing on a particular operation. This makes it possible to use a "building block" approach for web solutions, hooking together components into pipelines without any required programming.

Cocoon is "web glue for your web application development needs". It is a glue that keeps concerns separate and allows parallel evolution of the two sides, improving development pace and reducing the chance of conflicts.

Cocoon has been designed to coexist and interoperate side-by-side with your existing J2EE solutions or to give them new functionality without requiring any change in the existing infrastructure.

Cocoon interacts with many data sources, including filesystems, RDBMS, LDAP, native XML databases, SAP® systems and network-based data sources. It adapts content delivery to the capabilities of different devices like HTML, WML, PDF, SVG, and RTF, to name just a few. You can run Cocoon as a Servlet as well as through a powerful, commandline interface. The deliberate design of its abstract environment gives you the freedom to extend its functionality to meet your special needs in a highly modular fashion.

= Installation Notes =

There are many different ways to install Cocoon, and so it is probably best that you look at the [http://cocoon.apache.org/2.1/installing/index.html Cocoon installation instructions]. Those using debian-compatible systems can install a packaged version of cocoon provided by the late Sebastian Rahtz: see http://tei.oucs.ox.ac.uk/teideb/ .

Cocoon is also distributed with the [http://exist.sourceforge.net/ eXist] XML database already built into it (Cocoon built with eXist as a "block") by the eXist project. If you are likely to want both eXist and Cocoon, this is a very handy package. [http://hcmc.uvic.ca/blogs/index.php?blog=11&p=2595&more=1&c=1&tb=1&pb=1 This blog entry] gives is a step-by-step guide used by staff at the UVic HCMC when they deploy a new Cocoon+eXist instance under the Tomcat servlet container.

= Configuration =

[[Serving "application/tei+xml" from Cocoon]]

= External Links =

* http://cocoon.apache.org/
* http://cocoon.apache.org/2.1/installing/index.html
* http://cocoon.apache.org/2.1/introduction.html
* http://tei.oucs.ox.ac.uk/teideb/
* http://en.wikipedia.org/wiki/Apache_Cocoon

= References =
<references/>

Apache Cocoon

2018-06-21T16:09:49Z

Kshawkin: /* Summary */ Cocoon no longer being updated.

Apache Cocoon

2018-06-21T16:08:20Z

Kshawkin: /* Installation Notes */ copyediting

[[Category:Tools]]
[[Category:Publishing and delivery tools]]

= Summary =

Apache Cocoon is a web development framework built around the concepts of separation of concerns and component-based web development. The TEI consortium website is dynamically produced from TEI XML using Cocoon.

= Description =

Apache Cocoon is a web development framework built around the concepts of separation of concerns (making sure people can interact and collaborate on a project, without stepping on each other toes) and component-based web development.

Cocoon implements these concepts around the notion of "component pipelines", each component on the pipeline specializing on a particular operation. This makes it possible to use a "building block" approach for web solutions, hooking together components into pipelines without any required programming.

Cocoon is "web glue for your web application development needs". It is a glue that keeps concerns separate and allows parallel evolution of the two sides, improving development pace and reducing the chance of conflicts.

Cocoon has been designed to coexist and interoperate side-by-side with your existing J2EE solutions or to give them new functionality without requiring any change in the existing infrastructure.

Cocoon interacts with many data sources, including filesystems, RDBMS, LDAP, native XML databases, SAP® systems and network-based data sources. It adapts content delivery to the capabilities of different devices like HTML, WML, PDF, SVG, and RTF, to name just a few. You can run Cocoon as a Servlet as well as through a powerful, commandline interface. The deliberate design of its abstract environment gives you the freedom to extend its functionality to meet your special needs in a highly modular fashion.

= Installation Notes =

There are many different ways to install Cocoon, and so it is probably best that you look at the [http://cocoon.apache.org/2.1/installing/index.html Cocoon installation instructions]. Those using debian-compatible systems can install a packaged version of cocoon provided by the late Sebastian Rahtz: see http://tei.oucs.ox.ac.uk/teideb/ .

Cocoon is also distributed with the [http://exist.sourceforge.net/ eXist] XML database already built into it (Cocoon built with eXist as a "block") by the eXist project. If you are likely to want both eXist and Cocoon, this is a very handy package. [http://hcmc.uvic.ca/blogs/index.php?blog=11&p=2595&more=1&c=1&tb=1&pb=1 This blog entry] gives is a step-by-step guide used by staff at the UVic HCMC when they deploy a new Cocoon+eXist instance under the Tomcat servlet container.

= Configuration =

[[Serving "application/tei+xml" from Cocoon]]

= External Links =

* http://cocoon.apache.org/
* http://cocoon.apache.org/2.1/installing/index.html
* http://cocoon.apache.org/2.1/introduction.html
* http://tei.oucs.ox.ac.uk/teideb/
* http://en.wikipedia.org/wiki/Apache_Cocoon

OXygen

2018-06-16T01:08:31Z

Kshawkin: /* Current version number and date of release */

[[Category:Tools]]

[[Category:All-in-one Tools]]
[[Category:Development tools]]
[[Category:Editing tools]]
[[Category:Conversion and preprocessing tools]]

== Synopsis ==
<oXygen/> is a high-powered, cross-platform, graphical XML editor with built-in support for TEI.

== Features ==
Supports most features typical of a high-end XML editor, including:
* syntax coloring
* context-sensitive content assistant
* built-in validation and well-formedness checking
* built-in XSLT engines
* Unicode support
* formatting and indentation
* folding
* outline view (shows document structure)
* model view (shows element content model)
* XPath support
* XSLT debugger
* DTD/schema editor
* Text, Grid, and Author (tagless) editing modes

See also http://www.oxygenxml.com/features.html .

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

I have found this program to be affordable, easy to use, and pre-loaded with TEI capabilities. Also, the platform gets upgraded on a regular basis. -- Greg Moses (Austin, TeiXas!)

== System requirements ==
Runs under Windows, Linux, and Mac operating systems. Requires a Java VM (virtual machine).

(One of the download options for Windows users is an installer that includes the Java VM, eliminating the need to download and install Java separately.)

For detailed requirements, see http://www.oxygenxml.com/download.html .

== Source code and licensing ==
Closed source. Academic licenses available for $48 per person, allowing you to install for your own use on many computers and use with the current major version number. A discount is available for TEI subscribers and individuals from TEI member institutions; the discount code may be found by logging in to [http://members.tei-c.org/MemberInfo http://members.tei-c.org/MemberInfo]. Free 30-day trial license available.

== Support for TEI ==

===The TEI Framework in <oXygen>===

As of Version 9.0 build 2007110615, <oXygen> has TEI P5 schemas, templates and the TEI XSL stylesheets included as an officially-supported framework.

If you are not using the <code>tei-oxygen</code> [[TEIDebian|Debian package]] (for which a package manager will provide automatic updates for new versions of the stylesheet library), you can upgrade your copy of the stylesheet library without needing to download a new version of <oXygen/> doing doing either of the following:

* With version 15.2 or later of <oXygen/>, "subscribe" to the regularly-updated TEI distribution of the framework according to the instructions in this blog post: https://faqingperplxd.wordpress.com/2014/04/02/auto-update-your-tei-framework-in-oxygen/ .

* Use [http://sourceforge.net/projects/tei/files/oxygen-tei/ oxygen-tei], the open-source TEI framework built into <oXygen/>. To install this, look in your Oxygen folder for a "frameworks" directory that contains a directory called "tei". That's where the contents of the zip would go, replacing the old contents of that directory. ''Note that this is not the same thing as the <code>tei-oxygen</code> [[TEIDebian|Debian package]]!'' You can also build this framework for yourself if you are interested in doing so; the [https://github.com/TEIC/oxygen-tei project code is available on GitHub].

=== Other TEI-related Plugins ===

<oXygen/> allows third-party plugins and frameworks. The following are of possible interest to TEI users:

====HisTEI====

If you work with historical documents, you might use [https://github.com/odaata/HisTEI HisTEI], a framework designed to make historical documents easier to transcribe in <<oXygen/>'s XML Author mode.<ref>http://www.oxygenxml.com/pipermail/oxygen-sdk/2014-November/000182.html</ref>

==== Severin ====

[http://code.google.com/p/severin-image-viewer/ Severin] is an image viewer plugin, by Kilian Schmidtner and Stefan Krause, that can be used to see images as you browse though documents. It is an open source project (MIT license), and on the project page you can find a video presentation that uses a TEI document as example.

==== TEI-Facsimile-Plugin ====

[https://github.com/oxygenxml/TEI-Facsimile-Plugin TEI-Facsimile-Plugin] "provides support for working with Digital Facsimiles in Text Encoding Initiative (TEI) vocabulary. The plugin contributes a new View in which the user can load an image and draw shapes. These shapes are then converted into TEI "zone" elements. All the existing "zone" elements from the document are also rendered over the image."<ref>https://github.com/oxygenxml/TEI-Facsimile-Plugin</ref> This plugin requires oXygen version 15 or later.

==== dbTagger ====

https://github.com/aerhard/dbTagger

==== ediarum ====

[[Ediarum]]

==== TEI Completer ====

https://github.com/BCDH/TEI-Completer

==== oXygen-XML-editor-attribute-editor ====

* [https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;7d49b3c3.1612 announcement]
* https://github.com/AlexJitianu/oXygen-XML-editor-attribute-editor

== Language(s) ==
Interface available in English, French, German, Italian, Japanese and Dutch.

Documentation available in English.

== Documentation ==
http://www.oxygenxml.com/documentation.html

== Tech support ==
http://www.oxygenxml.com/techSupport.html

Can buy maintenance and support pack, providing free upgrades and tech support.

== User community ==
* http://www.oxygenxml.com/mailman/listinfo/oxygen-user/
* http://www.oxygenxml.com/forum/

== Current version number and date of release ==
20.1 (2018-06-15)

== History of versions ==
See http://www.oxygenxml.com/software_archive.html .

== How to download or buy ==
http://www.oxygenxml.com/download.html

If you use Debian or Ubuntu, you should instead install the <tt>tei-oxygen</tt> package at http://tei.oucs.ox.ac.uk/teideb/ . (More information below.)

== Additional notes ==

David Sewell wrote:

<blockquote>
Because the schema files distributed with oXygen sometimes lag behind
the latest TEI releases, kind souls like Syd Bauman have from time to
time packaged new schema files so that they can be unpacked to replace
part of the oXygen frameworks hierarchy. You could also go to

http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/

and grab the files there to replace the ones in a local oXygen
directory.
<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;8d5b98b2.0804</ref>
</blockquote>

Sebastian Rahtz added that if you use Debian or Ubuntu, you should instead install the <code>tei-oxygen</code> package. He explained that "this replaces the oXygen TEI package with a link to one installed by the tei-p5-schema package, which is kept up to date. This means you have only one set of TEI files on your machine." It's available at http://tei.oucs.ox.ac.uk/teideb/ .

Marcus Bingenheimer:
If you edit ODD files you need to validate the ODD against tei_odds. tei_all will not catch all mistakes and gives and error whenever elements in the RNG or other namespaces are used within <datatype>.
As usual you can associate the tei_odds with a oxygen specific processing command similar to this:
<code><?oxygen RNGSchema="{your oxygen folder}/frameworks/tei/xml/tei/custom/schema/relaxng/tei_odds.rng" type="xml"?></code>

== References ==
<references/>

OxGarage

2018-05-19T16:19:20Z

Kshawkin: /* Sample implementations */ added oxgarage-paderborn.tei-c.org

[[Category:Tools]]

[[Category:Conversion and preprocessing tools]]

== Synopsis ==
[http://www.tei-c.org/oxgarage/ OxGarage] is a web, and RESTful, service to manage the transformation of documents between a variety of formats. The majority of transformations use the Text Encoding Initiative format as a pivot format. It is a good tool for conversion from TEI to Word (.docx), or Word (.docx) to TEI, but also does many other formats.

There is a [http://htmlpreview.github.io/?https://github.com/TEIC/oxgarage/blob/master/doc/matrix.html list of formats for conversion to and from] which OxGarage supports.
Some of these use [[Tei-xsl|XSLT-based transformations]] and others are provided by [http://www.artofsolving.com/opensource/jodconverter JODConverter].

== Features ==

OxGarage can be used to
* Convert TEI documents to HTML, LaTeX, Word, OpenOffice, and ePub
* Process TEI ODD documents to make schemas or documentation
* Convert Word documents to TEI
* Transform some common XML formats (NLM, P4, Docbook) to or from TEI
* Manage any of the document conversions supported by OpenOffice

A user uploads a document, chooses the target format, OxGarage works out the pipeline of required transformation steps, performs them, and returns the resulting new document. For example, an ODD document can be turned into ePub by

# expanding the ODD file by merging with the TEI P5 source
# converting the resulting XML to TEI Lite for formatting
# transforming TEI Lite XML to HTML and packaging as ePub

OxGarage takes care of all three stages, the user does not need to know about the middle stage. All transformations using TEI are
performed with XSLT 2.0 stylesheets, some other transformations use JODConverter and a headless OpenOffice instance.

The results for some transformations can be tweaked by choosing different output profiles. These are defined on the OxGarage server.

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

== System requirements ==
A standard modern web browser is all that is required to make use of the Web Client. If you want to deploy the underlying system yourself you need Sun/Oracle Java 6 JRE, Tomcat, OpenOffice, etc. To build it you also need Maven and various java libraries, and a Debian setup is provided. For more information see https://github.com/TEIC/oxgarage

== Source code and licensing ==
OxGarage source code is hosted on Github, at https://github.com/TEIC/oxgarage;
is is a fork and extension of the EGE project (on Sourceforge: http://enrich-ege.sourceforge.net/)
and is licensed under the GPL.

== Support for TEI ==
The basic stylesheets provided with OxGarage (and ENRICH-EGE) use TEI as an output and pivot format.

== Language(s) ==
The Web Client and Documentation is only provided in English

== Documentation ==
See doc directory at https://github.com/TEIC/oxgarage

== Tech support ==

Create an issue in GitHub ( https://github.com/TEIC/oxgarage/issues ) for best-effort support concerning the OxGarage customisation.

== User community ==

== Sample implementations ==

* Production version: http://www.tei-c.org/oxgarage/
* Possibly outdated copy: http://oxgarage.oucs.ox.ac.uk:8080/ege-webclient/
* Development version: https://oxgarage-paderborn.tei-c.org/

== Current version number and date of release ==

Version 2.3.3 March 2014

== History of versions ==

== How to download or buy ==

Download either:
* from Github (https://github.com/TEIC/oxgarage)
* as a Debian package from http://tei.oucs.ox.ac.uk/teideb/

== Additional notes ==

== References ==

<references/>

OxGarage

2018-05-19T16:18:36Z

Kshawkin: /* Tech support */ now use GitHub instead of email

[[Category:Tools]]

[[Category:Conversion and preprocessing tools]]

== Synopsis ==
[http://www.tei-c.org/oxgarage/ OxGarage] is a web, and RESTful, service to manage the transformation of documents between a variety of formats. The majority of transformations use the Text Encoding Initiative format as a pivot format. It is a good tool for conversion from TEI to Word (.docx), or Word (.docx) to TEI, but also does many other formats.

There is a [http://htmlpreview.github.io/?https://github.com/TEIC/oxgarage/blob/master/doc/matrix.html list of formats for conversion to and from] which OxGarage supports.
Some of these use [[Tei-xsl|XSLT-based transformations]] and others are provided by [http://www.artofsolving.com/opensource/jodconverter JODConverter].

== Features ==

OxGarage can be used to
* Convert TEI documents to HTML, LaTeX, Word, OpenOffice, and ePub
* Process TEI ODD documents to make schemas or documentation
* Convert Word documents to TEI
* Transform some common XML formats (NLM, P4, Docbook) to or from TEI
* Manage any of the document conversions supported by OpenOffice

A user uploads a document, chooses the target format, OxGarage works out the pipeline of required transformation steps, performs them, and returns the resulting new document. For example, an ODD document can be turned into ePub by

# expanding the ODD file by merging with the TEI P5 source
# converting the resulting XML to TEI Lite for formatting
# transforming TEI Lite XML to HTML and packaging as ePub

OxGarage takes care of all three stages, the user does not need to know about the middle stage. All transformations using TEI are
performed with XSLT 2.0 stylesheets, some other transformations use JODConverter and a headless OpenOffice instance.

The results for some transformations can be tweaked by choosing different output profiles. These are defined on the OxGarage server.

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

== System requirements ==
A standard modern web browser is all that is required to make use of the Web Client. If you want to deploy the underlying system yourself you need Sun/Oracle Java 6 JRE, Tomcat, OpenOffice, etc. To build it you also need Maven and various java libraries, and a Debian setup is provided. For more information see https://github.com/TEIC/oxgarage

== Source code and licensing ==
OxGarage source code is hosted on Github, at https://github.com/TEIC/oxgarage;
is is a fork and extension of the EGE project (on Sourceforge: http://enrich-ege.sourceforge.net/)
and is licensed under the GPL.

== Support for TEI ==
The basic stylesheets provided with OxGarage (and ENRICH-EGE) use TEI as an output and pivot format.

== Language(s) ==
The Web Client and Documentation is only provided in English

== Documentation ==
See doc directory at https://github.com/TEIC/oxgarage

== Tech support ==

Create an issue in GitHub ( https://github.com/TEIC/oxgarage/issues ) for best-effort support concerning the OxGarage customisation.

== User community ==

== Sample implementations ==

* Production version: http://www.tei-c.org/oxgarage/
* Possibly outdated copy: http://oxgarage.oucs.ox.ac.uk:8080/ege-webclient/

== Current version number and date of release ==

Version 2.3.3 March 2014

== History of versions ==

== How to download or buy ==

Download either:
* from Github (https://github.com/TEIC/oxgarage)
* as a Debian package from http://tei.oucs.ox.ac.uk/teideb/

== Additional notes ==

== References ==

<references/>

TEI Publisher

2018-05-19T16:15:13Z

Kshawkin: /* How to download or buy */ new URL

'''Not to be confused with [[TeiPublisher|teiPublisher]]'''.

[[Category:Tools]]

[[Category:Publishing and delivery tools]]

== Synopsis ==
"The instant publishing toolbox"<ref>http://teipublisher.com/</ref>

== Features ==
* High quality editions: Publish your digital edition without writing code. Using the TEI Processing Model, customising the appearance of the text is all done in XML.
* Cross media & multidevice: TEI Publisher generates applications which work well across devices and include features like page by page browsing, search and cross-media export.
* Single source publishing: Create HTML, ePUBs or PDFs from a single document and its associated processing model. No media specific stylesheets required.
* Lean code: For developers, TEI Publisher heavily reduces the amount of custom code required by typical digital edition projects. Save thousands of lines on handwritten transformations and rely on maintained code libraries instead.<ref>http://teipublisher.com/</ref>

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

== System requirements ==
[[Exist]] 3.6.0 or later for version 3.0<ref>http://teipublisher.com/exist/apps/tei-publisher-home/index.html</ref>

== Source code and licensing ==

== Support for TEI ==

== Language(s) ==

== Documentation ==
http://teipublisher.com/exist/apps/tei-publisher/doc/documentation.xml

== Tech support ==

== User community ==

== Sample implementations ==
http://teipublisher.com/index.html#tp-showcases

== Current version number and date of release ==

3.0 (2017-12-19)

== History of versions ==

== How to download or buy ==
https://gitlab.existsolutions.com/tei-publisher

== Additional notes ==

== References ==
<references/>

TEI Publisher

2018-05-19T16:14:15Z

Kshawkin: /* Features */ explanations for each bullet point

'''Not to be confused with [[TeiPublisher|teiPublisher]]'''.

[[Category:Tools]]

[[Category:Publishing and delivery tools]]

== Synopsis ==
"The instant publishing toolbox"<ref>http://teipublisher.com/</ref>

== Features ==
* High quality editions: Publish your digital edition without writing code. Using the TEI Processing Model, customising the appearance of the text is all done in XML.
* Cross media & multidevice: TEI Publisher generates applications which work well across devices and include features like page by page browsing, search and cross-media export.
* Single source publishing: Create HTML, ePUBs or PDFs from a single document and its associated processing model. No media specific stylesheets required.
* Lean code: For developers, TEI Publisher heavily reduces the amount of custom code required by typical digital edition projects. Save thousands of lines on handwritten transformations and rely on maintained code libraries instead.<ref>http://teipublisher.com/</ref>

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

== System requirements ==
[[Exist]] 3.6.0 or later for version 3.0<ref>http://teipublisher.com/exist/apps/tei-publisher-home/index.html</ref>

== Source code and licensing ==

== Support for TEI ==

== Language(s) ==

== Documentation ==
http://teipublisher.com/exist/apps/tei-publisher/doc/documentation.xml

== Tech support ==

== User community ==

== Sample implementations ==
http://teipublisher.com/index.html#tp-showcases

== Current version number and date of release ==

3.0 (2017-12-19)

== History of versions ==

== How to download or buy ==
http://gitlab.exist-db.org/tei-publisher/

== Additional notes ==

== References ==
<references/>

OXygen

2018-05-14T13:23:11Z

Kshawkin: /* The TEI Framework in <oXygen> */ new URL for James's blog

[[Category:Tools]]

[[Category:All-in-one Tools]]
[[Category:Development tools]]
[[Category:Editing tools]]
[[Category:Conversion and preprocessing tools]]

== Synopsis ==
<oXygen/> is a high-powered, cross-platform, graphical XML editor with built-in support for TEI.

== Features ==
Supports most features typical of a high-end XML editor, including:
* syntax coloring
* context-sensitive content assistant
* built-in validation and well-formedness checking
* built-in XSLT engines
* Unicode support
* formatting and indentation
* folding
* outline view (shows document structure)
* model view (shows element content model)
* XPath support
* XSLT debugger
* DTD/schema editor
* Text, Grid, and Author (tagless) editing modes

See also http://www.oxygenxml.com/features.html .

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

I have found this program to be affordable, easy to use, and pre-loaded with TEI capabilities. Also, the platform gets upgraded on a regular basis. -- Greg Moses (Austin, TeiXas!)

== System requirements ==
Runs under Windows, Linux, and Mac operating systems. Requires a Java VM (virtual machine).

(One of the download options for Windows users is an installer that includes the Java VM, eliminating the need to download and install Java separately.)

For detailed requirements, see http://www.oxygenxml.com/download.html .

== Source code and licensing ==
Closed source. Academic licenses available for $48 per person, allowing you to install for your own use on many computers and use with the current major version number. A discount is available for TEI subscribers and individuals from TEI member institutions; the discount code may be found by logging in to [http://members.tei-c.org/MemberInfo http://members.tei-c.org/MemberInfo]. Free 30-day trial license available.

== Support for TEI ==

===The TEI Framework in <oXygen>===

As of Version 9.0 build 2007110615, <oXygen> has TEI P5 schemas, templates and the TEI XSL stylesheets included as an officially-supported framework.

If you are not using the <code>tei-oxygen</code> [[TEIDebian|Debian package]] (for which a package manager will provide automatic updates for new versions of the stylesheet library), you can upgrade your copy of the stylesheet library without needing to download a new version of <oXygen/> doing doing either of the following:

* With version 15.2 or later of <oXygen/>, "subscribe" to the regularly-updated TEI distribution of the framework according to the instructions in this blog post: https://faqingperplxd.wordpress.com/2014/04/02/auto-update-your-tei-framework-in-oxygen/ .

* Use [http://sourceforge.net/projects/tei/files/oxygen-tei/ oxygen-tei], the open-source TEI framework built into <oXygen/>. To install this, look in your Oxygen folder for a "frameworks" directory that contains a directory called "tei". That's where the contents of the zip would go, replacing the old contents of that directory. ''Note that this is not the same thing as the <code>tei-oxygen</code> [[TEIDebian|Debian package]]!'' You can also build this framework for yourself if you are interested in doing so; the [https://github.com/TEIC/oxygen-tei project code is available on GitHub].

=== Other TEI-related Plugins ===

<oXygen/> allows third-party plugins and frameworks. The following are of possible interest to TEI users:

====HisTEI====

If you work with historical documents, you might use [https://github.com/odaata/HisTEI HisTEI], a framework designed to make historical documents easier to transcribe in <<oXygen/>'s XML Author mode.<ref>http://www.oxygenxml.com/pipermail/oxygen-sdk/2014-November/000182.html</ref>

==== Severin ====

[http://code.google.com/p/severin-image-viewer/ Severin] is an image viewer plugin, by Kilian Schmidtner and Stefan Krause, that can be used to see images as you browse though documents. It is an open source project (MIT license), and on the project page you can find a video presentation that uses a TEI document as example.

==== TEI-Facsimile-Plugin ====

[https://github.com/oxygenxml/TEI-Facsimile-Plugin TEI-Facsimile-Plugin] "provides support for working with Digital Facsimiles in Text Encoding Initiative (TEI) vocabulary. The plugin contributes a new View in which the user can load an image and draw shapes. These shapes are then converted into TEI "zone" elements. All the existing "zone" elements from the document are also rendered over the image."<ref>https://github.com/oxygenxml/TEI-Facsimile-Plugin</ref> This plugin requires oXygen version 15 or later.

==== dbTagger ====

https://github.com/aerhard/dbTagger

==== ediarum ====

[[Ediarum]]

==== TEI Completer ====

https://github.com/BCDH/TEI-Completer

==== oXygen-XML-editor-attribute-editor ====

* [https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;7d49b3c3.1612 announcement]
* https://github.com/AlexJitianu/oXygen-XML-editor-attribute-editor

== Language(s) ==
Interface available in English, French, German, Italian, Japanese and Dutch.

Documentation available in English.

== Documentation ==
http://www.oxygenxml.com/documentation.html

== Tech support ==
http://www.oxygenxml.com/techSupport.html

Can buy maintenance and support pack, providing free upgrades and tech support.

== User community ==
* http://www.oxygenxml.com/mailman/listinfo/oxygen-user/
* http://www.oxygenxml.com/forum/

== Current version number and date of release ==
20.0 (2018-03-16)

== History of versions ==
See http://www.oxygenxml.com/software_archive.html .

== How to download or buy ==
http://www.oxygenxml.com/download.html

If you use Debian or Ubuntu, you should instead install the <tt>tei-oxygen</tt> package at http://tei.oucs.ox.ac.uk/teideb/ . (More information below.)

== Additional notes ==

David Sewell wrote:

<blockquote>
Because the schema files distributed with oXygen sometimes lag behind
the latest TEI releases, kind souls like Syd Bauman have from time to
time packaged new schema files so that they can be unpacked to replace
part of the oXygen frameworks hierarchy. You could also go to

http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/

and grab the files there to replace the ones in a local oXygen
directory.
<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;8d5b98b2.0804</ref>
</blockquote>

Sebastian Rahtz added that if you use Debian or Ubuntu, you should instead install the <code>tei-oxygen</code> package. He explained that "this replaces the oXygen TEI package with a link to one installed by the tei-p5-schema package, which is kept up to date. This means you have only one set of TEI files on your machine." It's available at http://tei.oucs.ox.ac.uk/teideb/ .

Marcus Bingenheimer:
If you edit ODD files you need to validate the ODD against tei_odds. tei_all will not catch all mistakes and gives and error whenever elements in the RNG or other namespaces are used within <datatype>.
As usual you can associate the tei_odds with a oxygen specific processing command similar to this:
<code><?oxygen RNGSchema="{your oxygen folder}/frameworks/tei/xml/tei/custom/schema/relaxng/tei_odds.rng" type="xml"?></code>

== References ==
<references/>

Upconversion

2018-05-03T13:53:04Z

Kshawkin: /* Adding structural markup */ missing square bracket

== Introduction: on automating tagging ==

When you begin learning text encoding, you might think that people transcribe a source document and then add all the tags into the document by hand.

Then you learn how to use an [[:Category:Editing tools|XML editor]] to not only validate your XML but also save keystrokes on entering elements.

And then you learn about [[Digitization tools|OCR software]], which can save you effort in transcribing a source document, leaving you just to correct OCR errors.

And then you learn that there are vendors that will do some combination of scanning, OCR, and encoding documents (often through "double keyboarding" according to a vendor spec such as [[TEI Tite]], which guarantees verity high accuracy in transcription and encoding). While vendors are generally not expected to add markup requiring specialized knowledge (this might be left to project staff), it is also not a good use of resources to expect a vendor to perform basic structural tagging if this can be easily deduced from OCR output or from page images. ''Upconversion'' from a less structured format to a more structured one can sometimes be performed through rules-based techniques (like XSLT), but the data is usually inconsistent enough that there may be competing sets of rules. Basic ''heuristic techniques'' that choose between competing rules can be used to make judgments about features on the page and derive markup from these. They are never perfect, but neither are human encoders.

Furthermore, more advanced heuristics and information retrieval (IR) techniques can be used to identify named entities, topics, sentiment, tone, and complexity of a text, and IR techniques are frequently used for authorship attribution.

Below are resources that might be helpful for those looking to use heuristic and IR techniques to add markup to an XML document.

== Adding structural markup ==

* [[GROBID]]
* [http://bilbo.hypotheses.org/ BILBO]
* [http://wing.comp.nus.edu.sg/parsCit/ ParsCit]
* [https://sourceforge.net/projects/pdf2xml/ pdf2xml]
* various projects coming out of [http://lamp.cfar.umd.edu/ LAMP]
* [http://pdfx.cs.man.ac.uk/ pdfx]
* [https://code.google.com/p/lapdftext/ LA-PDFText] (turns PDF into some sort of XML)
* [http://www.shabash.net/merops/default.html Merops]
* [https://github.com/scrapy/scrapely scrapely] -- HTML to JSON
* [https://github.com/coolwanglu/pdf2htmlEX pdf2htmlEX]
* see “Ideas” section of [http://web.archive.org/web/20130921075854/http://scholrev.org/hackathon http://scholrev.org/hackathon/]
* see [https://listserv.nd.edu/cgi-bin/wa?A2=ind1506&L=CODE4LIB&F=&S=&P=134330 discussion of structuring OCRd text on CODE4LIB]
* Open Typesetting Stack (formerly the PKP XML Parsing Service): ([https://github.com/pkp/ots sourcecode], [http://pkp-udev.lib.sfu.ca/ beta site]) -- discerns structure to create various output formats

== Identifying named entities ==

* [http://bilbo.hypotheses.org/ BILBO]
* [http://www.opencalais.com/ Calais]
* [http://seasr.org/ SEASR]
* [http://semlab.io/DADAlytics_ner_demo/ NER toolchain from Semantic Lab]

== Identifying topics, sentiment, tone, and complexity ==

* [http://www.opencalais.com/ Calais]

[[Category:Tools]]

Upconversion

2018-05-03T13:51:53Z

Kshawkin: /* Adding structural markup */ new link for sourcecode for Open Typesetting Stack

== Introduction: on automating tagging ==

When you begin learning text encoding, you might think that people transcribe a source document and then add all the tags into the document by hand.

Then you learn how to use an [[:Category:Editing tools|XML editor]] to not only validate your XML but also save keystrokes on entering elements.

And then you learn about [[Digitization tools|OCR software]], which can save you effort in transcribing a source document, leaving you just to correct OCR errors.

And then you learn that there are vendors that will do some combination of scanning, OCR, and encoding documents (often through "double keyboarding" according to a vendor spec such as [[TEI Tite]], which guarantees verity high accuracy in transcription and encoding). While vendors are generally not expected to add markup requiring specialized knowledge (this might be left to project staff), it is also not a good use of resources to expect a vendor to perform basic structural tagging if this can be easily deduced from OCR output or from page images. ''Upconversion'' from a less structured format to a more structured one can sometimes be performed through rules-based techniques (like XSLT), but the data is usually inconsistent enough that there may be competing sets of rules. Basic ''heuristic techniques'' that choose between competing rules can be used to make judgments about features on the page and derive markup from these. They are never perfect, but neither are human encoders.

Furthermore, more advanced heuristics and information retrieval (IR) techniques can be used to identify named entities, topics, sentiment, tone, and complexity of a text, and IR techniques are frequently used for authorship attribution.

Below are resources that might be helpful for those looking to use heuristic and IR techniques to add markup to an XML document.

== Adding structural markup ==

* [[GROBID]]
* [http://bilbo.hypotheses.org/ BILBO]
* [http://wing.comp.nus.edu.sg/parsCit/ ParsCit]
* [https://sourceforge.net/projects/pdf2xml/ pdf2xml]
* various projects coming out of [http://lamp.cfar.umd.edu/ LAMP]
* [http://pdfx.cs.man.ac.uk/ pdfx]
* [https://code.google.com/p/lapdftext/ LA-PDFText] (turns PDF into some sort of XML)
* [http://www.shabash.net/merops/default.html Merops]
* [https://github.com/scrapy/scrapely scrapely] -- HTML to JSON
* [https://github.com/coolwanglu/pdf2htmlEX pdf2htmlEX]
* see “Ideas” section of [http://web.archive.org/web/20130921075854/http://scholrev.org/hackathon http://scholrev.org/hackathon/]
* see [https://listserv.nd.edu/cgi-bin/wa?A2=ind1506&L=CODE4LIB&F=&S=&P=134330 discussion of structuring OCRd text on CODE4LIB]
* Open Typesetting Stack (formerly the PKP XML Parsing Service): (https://github.com/pkp/ots sourcecode], [http://pkp-udev.lib.sfu.ca/ beta site]) -- discerns structure to create various output formats

== Identifying named entities ==

* [http://bilbo.hypotheses.org/ BILBO]
* [http://www.opencalais.com/ Calais]
* [http://seasr.org/ SEASR]
* [http://semlab.io/DADAlytics_ner_demo/ NER toolchain from Semantic Lab]

== Identifying topics, sentiment, tone, and complexity ==

* [http://www.opencalais.com/ Calais]

[[Category:Tools]]

Upconversion

2018-05-03T13:51:02Z

Kshawkin: /* Identifying named entities */ added http://semlab.io/DADAlytics_ner_demo/

== Introduction: on automating tagging ==

When you begin learning text encoding, you might think that people transcribe a source document and then add all the tags into the document by hand.

Then you learn how to use an [[:Category:Editing tools|XML editor]] to not only validate your XML but also save keystrokes on entering elements.

And then you learn about [[Digitization tools|OCR software]], which can save you effort in transcribing a source document, leaving you just to correct OCR errors.

And then you learn that there are vendors that will do some combination of scanning, OCR, and encoding documents (often through "double keyboarding" according to a vendor spec such as [[TEI Tite]], which guarantees verity high accuracy in transcription and encoding). While vendors are generally not expected to add markup requiring specialized knowledge (this might be left to project staff), it is also not a good use of resources to expect a vendor to perform basic structural tagging if this can be easily deduced from OCR output or from page images. ''Upconversion'' from a less structured format to a more structured one can sometimes be performed through rules-based techniques (like XSLT), but the data is usually inconsistent enough that there may be competing sets of rules. Basic ''heuristic techniques'' that choose between competing rules can be used to make judgments about features on the page and derive markup from these. They are never perfect, but neither are human encoders.

Furthermore, more advanced heuristics and information retrieval (IR) techniques can be used to identify named entities, topics, sentiment, tone, and complexity of a text, and IR techniques are frequently used for authorship attribution.

Below are resources that might be helpful for those looking to use heuristic and IR techniques to add markup to an XML document.

== Adding structural markup ==

* [[GROBID]]
* [http://bilbo.hypotheses.org/ BILBO]
* [http://wing.comp.nus.edu.sg/parsCit/ ParsCit]
* [https://sourceforge.net/projects/pdf2xml/ pdf2xml]
* various projects coming out of [http://lamp.cfar.umd.edu/ LAMP]
* [http://pdfx.cs.man.ac.uk/ pdfx]
* [https://code.google.com/p/lapdftext/ LA-PDFText] (turns PDF into some sort of XML)
* [http://www.shabash.net/merops/default.html Merops]
* [https://github.com/scrapy/scrapely scrapely] -- HTML to JSON
* [https://github.com/coolwanglu/pdf2htmlEX pdf2htmlEX]
* see “Ideas” section of [http://web.archive.org/web/20130921075854/http://scholrev.org/hackathon http://scholrev.org/hackathon/]
* see [https://listserv.nd.edu/cgi-bin/wa?A2=ind1506&L=CODE4LIB&F=&S=&P=134330 discussion of structuring OCRd text on CODE4LIB]
* Open Typesetting Stack (formerly the PKP XML Parsing Service): ([https://github.com/pkp/xmlps sourcecode], [http://pkp-udev.lib.sfu.ca/ beta site]) -- discerns structure to create various output formats

== Identifying named entities ==

* [http://bilbo.hypotheses.org/ BILBO]
* [http://www.opencalais.com/ Calais]
* [http://seasr.org/ SEASR]
* [http://semlab.io/DADAlytics_ner_demo/ NER toolchain from Semantic Lab]

== Identifying topics, sentiment, tone, and complexity ==

* [http://www.opencalais.com/ Calais]

[[Category:Tools]]

Council-licensing

2018-04-21T18:49:44Z

Kshawkin: /* Not Software */ also added boilerplate to each page generated by OpenCMS

[[Category:Council]]
[[Council]] is looking at regularising/standardising the licences it uses for various bits of output of the TEI-C. Eventually it recommended to the [[Board]] that it dual license everything with [http://www.opensource.org/licenses/BSD-2-Clause BSD 2-Clause] and [http://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution CC+BY 3.0]. Users can choose which license is most appropriate in their situation/use of materials, and use that. In both cases it is Attribution of materials used that is asked.

== Software ==
{| border="1" align="center" style="text-align:center;" cellpadding="10px;"
|- style="background-color:#AAF; font-weight:bold"
|Object
|'''Previous Licence'''
|'''Proposed Licence'''
|'''To be updated? By whom? Status?'''
|-
|Stylesheets
|[http://www.gnu.org/licenses/lgpl-2.1.html GNU LGPL 2.1]
|[http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|dual CC / BSD. Sebastian Rahtz. Done on 2011-11-05. Let him know if any are missing the new licenses.
|-
|Roma
| GPL
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|dual CC / BSD. Sebastian Rahtz. Done on 2011-11-05. Let him know if any are missing the new licenses.
|-
|Exemplars
| misc
|[http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|dual CC / BSD. Sebastian Rahtz. Done on 2011-11-05. Let him know if any are missing the new licenses.
|-
| TEIOO
| [http://www.gnu.org/licenses/lgpl-2.1.html GNU LGPL 2.1] (though LICENSE file has [http://www.gnu.org/licenses/gpl-2.0.html GNU GPL 2.0])
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|
|-
| Vesta
| GPL
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|
|-
| PassiveTeX (SR/Oxford) (Should probably be removed from TEI-C repository?)
| 'Free' in LICENSE but 'COPYING' file has [http://www.gnu.org/licenses/gpl-2.0.html GNU GPL 2.0]
| ??
|
|}

== Not Software ==
{| border="1" align="center" style="text-align:center;" cellpadding="10px;"
|- style="background-color:#AAF; font-weight:bold"
|Object
|'''Previous Licence'''
|'''Proposed Licence'''
|'''To be updated? By whom? Status?'''
|-
|Guidelines (ODD source)
|[http://www.gnu.org/licenses/gpl-2.0.html GNU GPL 2.0]
|[http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|
|-
|Guidelines (official HTML release)
|[http://www.gnu.org/licenses/gpl-2.0.html GNU GPL 2.0]
|[http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|
|-
|Sample ODDs
| 'free' (mostly but some GPL exceptions like teilite and tei_enrich, and tei_tite is unlicensed)
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|
|-
|Pre-generated Schemas
| 'free' (mostly)
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|
|-
|Roma-generated Schemas
| Content of <availability>
| Content of <availability>
|
|-
|Wiki
|[http://www.gnu.org/licenses/fdl-1.2.html GNU FDL 1.2]
|[http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|[[User:James | James]] will update LocalSettings.php to point to http://www.tei-c.org/Guidelines/access.xml#body.1_div.2 which will be changed to reflect new dual-license.
|-
| TEI-C Website (other than Guidelines)
| Varies by page, but many unlicensed
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
| [[User:James | James]] will update http://www.tei-c.org/Guidelines/access.xml#body.1_div.2 to reflect new dual-license. This now says "most materials", so if any page has other terms, those would take precedence. Update by [[User:Kshawkin|Kshawkin]] 04:37, 18 April 2018 (CEST): also revised http://www.tei-c.org/About/website.xml . Another update by [[User:Kshawkin|Kshawkin]] 20:49, 21 April 2018 (CEST): also added boilerplate text to bottom of each page generated by OpenCMS.
|-
| TEI CSS
| none
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/BSD-2-Clause BSD 2-Clause]
|
|-
| TEI-ISO Feature Structure Representation (ch. 18)
| [http://www.gnu.org/licenses/gpl-2.0.html GNU GPL 2.0]
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|
|}

== Not under consideration ==
{| border="1" align="center" style="text-align:center;" cellpadding="10px;"
|- style="background-color:#AAF; font-weight:bold"
|Object
|'''Current Licence'''
|'''Proposed Licence'''
|-
| jTEI
| [http://creativecommons.org/licenses/by-nd/3.0/ CC+by+nd 3.0]
| [http://creativecommons.org/licenses/by-nd/3.0/ CC+by+nd 3.0]
|}

Council-licensing

2018-04-18T02:37:52Z

Kshawkin: /* Not Software */ noted update to http://www.tei-c.org/About/website.xml as well

[[Category:Council]]
[[Council]] is looking at regularising/standardising the licences it uses for various bits of output of the TEI-C. Eventually it recommended to the [[Board]] that it dual license everything with [http://www.opensource.org/licenses/BSD-2-Clause BSD 2-Clause] and [http://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution CC+BY 3.0]. Users can choose which license is most appropriate in their situation/use of materials, and use that. In both cases it is Attribution of materials used that is asked.

== Software ==
{| border="1" align="center" style="text-align:center;" cellpadding="10px;"
|- style="background-color:#AAF; font-weight:bold"
|Object
|'''Previous Licence'''
|'''Proposed Licence'''
|'''To be updated? By whom? Status?'''
|-
|Stylesheets
|[http://www.gnu.org/licenses/lgpl-2.1.html GNU LGPL 2.1]
|[http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|dual CC / BSD. Sebastian Rahtz. Done on 2011-11-05. Let him know if any are missing the new licenses.
|-
|Roma
| GPL
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|dual CC / BSD. Sebastian Rahtz. Done on 2011-11-05. Let him know if any are missing the new licenses.
|-
|Exemplars
| misc
|[http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|dual CC / BSD. Sebastian Rahtz. Done on 2011-11-05. Let him know if any are missing the new licenses.
|-
| TEIOO
| [http://www.gnu.org/licenses/lgpl-2.1.html GNU LGPL 2.1] (though LICENSE file has [http://www.gnu.org/licenses/gpl-2.0.html GNU GPL 2.0])
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|
|-
| Vesta
| GPL
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|
|-
| PassiveTeX (SR/Oxford) (Should probably be removed from TEI-C repository?)
| 'Free' in LICENSE but 'COPYING' file has [http://www.gnu.org/licenses/gpl-2.0.html GNU GPL 2.0]
| ??
|
|}

== Not Software ==
{| border="1" align="center" style="text-align:center;" cellpadding="10px;"
|- style="background-color:#AAF; font-weight:bold"
|Object
|'''Previous Licence'''
|'''Proposed Licence'''
|'''To be updated? By whom? Status?'''
|-
|Guidelines (ODD source)
|[http://www.gnu.org/licenses/gpl-2.0.html GNU GPL 2.0]
|[http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|
|-
|Guidelines (official HTML release)
|[http://www.gnu.org/licenses/gpl-2.0.html GNU GPL 2.0]
|[http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|
|-
|Sample ODDs
| 'free' (mostly but some GPL exceptions like teilite and tei_enrich, and tei_tite is unlicensed)
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|
|-
|Pre-generated Schemas
| 'free' (mostly)
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|
|-
|Roma-generated Schemas
| Content of <availability>
| Content of <availability>
|
|-
|Wiki
|[http://www.gnu.org/licenses/fdl-1.2.html GNU FDL 1.2]
|[http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|[[User:James | James]] will update LocalSettings.php to point to http://www.tei-c.org/Guidelines/access.xml#body.1_div.2 which will be changed to reflect new dual-license.
|-
| TEI-C Website (other than Guidelines)
| Varies by page, but many unlicensed
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
| [[User:James | James]] will update http://www.tei-c.org/Guidelines/access.xml#body.1_div.2 to reflect new dual-license. This now says "most materials", so if any page has other terms, those would take precedence. Update by [[User:Kshawkin|Kshawkin]] 04:37, 18 April 2018 (CEST): also revised http://www.tei-c.org/About/website.xml .
|-
| TEI CSS
| none
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/BSD-2-Clause BSD 2-Clause]
|
|-
| TEI-ISO Feature Structure Representation (ch. 18)
| [http://www.gnu.org/licenses/gpl-2.0.html GNU GPL 2.0]
| [http://creativecommons.org/licenses/by/3.0/ CC+BY 3.0] and [http://www.opensource.org/licenses/bsd-license.php BSD 2-Clause]
|
|}

== Not under consideration ==
{| border="1" align="center" style="text-align:center;" cellpadding="10px;"
|- style="background-color:#AAF; font-weight:bold"
|Object
|'''Current Licence'''
|'''Proposed Licence'''
|-
| jTEI
| [http://creativecommons.org/licenses/by-nd/3.0/ CC+by+nd 3.0]
| [http://creativecommons.org/licenses/by-nd/3.0/ CC+by+nd 3.0]
|}

DHConvalidator

2018-03-23T15:37:14Z

Kshawkin: Created page with "Category:Tools Category:Conversion and preprocessing tools == Synopsis == This tool integrates with [http://www.conftool.net/ ConfTool] and OxGarage to create conver..."

[[Category:Tools]]
[[Category:Conversion and preprocessing tools]]

== Synopsis ==
This tool integrates with [http://www.conftool.net/ ConfTool] and [[OxGarage]] to create convert a DOCX or ODT file to TEI and create a package including the original file and the converted file.

== Features ==

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

== System requirements ==
Requires access to an instance of [[OxGarage]]

== Source code and licensing ==
GNU GPL v3.0

== Support for TEI ==

== Language(s) ==

== Documentation ==

== Tech support ==

== User community ==

== Sample implementations ==

== Current version number and date of release ==

== History of versions ==

== How to download or buy ==
https://github.com/ADHO/dhconvalidator

== Additional notes ==

Crosswalks

2018-03-21T13:47:39Z

Kshawkin: /* From TEI to other formats */ new section: TEI to ESE and EDM

[[Category:SIG:Libraries]]

This page is a central location to gather ''schema crosswalks'' (''mappings'') from TEI headers to other data formats and from other data formats to TEI headers, and to mention tools that implement these mappings.

If you have a mapping that you'd like to share but don't have a place to put it, consider adding it directly to the wiki as its own page!

== From TEI to other formats ==

=== TEI to MARC ===

[http://www.tei-c.org/SIG/Libraries/teiinlibraries/main-driver.html#index.xml-body.1_div.4_div.1_div.6 Section 4.1.6] of [http://purl.oclc.org/NET/teiinlibraries <cite>Best Practices for TEI in Libraries</cite> (version 3.0)] provides a mapping.

=== TEI to MODS ===

[https://github.com/sarahjeansweeney/TEI2MODS TEI2MODS]

=== TEI to Dublin Core ===

?

=== TEI to RIS ===

[[BiblStruct-to-RIS]]

=== TEI to ESE and EDM ===

https://sourceforge.net/projects/eregia2eseedm/

== From other formats to TEI ==

=== MARC to TEI ===

[http://www.tei-c.org/SIG/Libraries/teiinlibraries/main-driver.html#index.xml-body.1_div.4_div.1_div.6 Section 4.1.6] of [http://purl.oclc.org/NET/teiinlibraries <cite>Best Practices for TEI in Libraries</cite> (version 3.0)] provides a mapping. Conversion from MARCXML to TEI has been implemented in [[Thutmose_II]].

=== TextGrid to TEI ===

There is a "Copy TEI Header" button in the metadata forms in TextGridLab. Maybe this crosswalk is documented somewhere?

OXygen

2018-03-16T15:18:46Z

Kshawkin: /* Current version number and date of release */

[[Category:Tools]]

[[Category:All-in-one Tools]]
[[Category:Development tools]]
[[Category:Editing tools]]
[[Category:Conversion and preprocessing tools]]

== Synopsis ==
<oXygen/> is a high-powered, cross-platform, graphical XML editor with built-in support for TEI.

== Features ==
Supports most features typical of a high-end XML editor, including:
* syntax coloring
* context-sensitive content assistant
* built-in validation and well-formedness checking
* built-in XSLT engines
* Unicode support
* formatting and indentation
* folding
* outline view (shows document structure)
* model view (shows element content model)
* XPath support
* XSLT debugger
* DTD/schema editor
* Text, Grid, and Author (tagless) editing modes

See also http://www.oxygenxml.com/features.html .

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

I have found this program to be affordable, easy to use, and pre-loaded with TEI capabilities. Also, the platform gets upgraded on a regular basis. -- Greg Moses (Austin, TeiXas!)

== System requirements ==
Runs under Windows, Linux, and Mac operating systems. Requires a Java VM (virtual machine).

(One of the download options for Windows users is an installer that includes the Java VM, eliminating the need to download and install Java separately.)

For detailed requirements, see http://www.oxygenxml.com/download.html .

== Source code and licensing ==
Closed source. Academic licenses available for $48 per person, allowing you to install for your own use on many computers and use with the current major version number. A discount is available for TEI subscribers and individuals from TEI member institutions; the discount code may be found by logging in to [http://members.tei-c.org/MemberInfo http://members.tei-c.org/MemberInfo]. Free 30-day trial license available.

== Support for TEI ==

===The TEI Framework in <oXygen>===

As of Version 9.0 build 2007110615, <oXygen> has TEI P5 schemas, templates and the TEI XSL stylesheets included as an officially-supported framework.

If you are not using the <code>tei-oxygen</code> [[TEIDebian|Debian package]] (for which a package manager will provide automatic updates for new versions of the stylesheet library), you can upgrade your copy of the stylesheet library without needing to download a new version of <oXygen/> doing doing either of the following:

* With version 15.2 or later of <oXygen/>, "subscribe" to the regularly-updated TEI distribution of the framework according to the instructions in this blog post: [http://blogs.it.ox.ac.uk/jamesc/2014/04/02/auto-update-your-tei-framework-in-oxygen/ http://blogs.it.ox.ac.uk/jamesc/2014/04/02/auto-update-your-tei-framework-in-oxygen/].

* Use [http://sourceforge.net/projects/tei/files/oxygen-tei/ oxygen-tei], the open-source TEI framework built into <oXygen/>. To install this, look in your Oxygen folder for a "frameworks" directory that contains a directory called "tei". That's where the contents of the zip would go, replacing the old contents of that directory. ''Note that this is not the same thing as the <code>tei-oxygen</code> [[TEIDebian|Debian package]]!'' You can also build this framework for yourself if you are interested in doing so; the [https://github.com/TEIC/oxygen-tei project code is available on GitHub].

=== Other TEI-related Plugins ===

<oXygen/> allows third-party plugins and frameworks. The following are of possible interest to TEI users:

====HisTEI====

If you work with historical documents, you might use [https://github.com/odaata/HisTEI HisTEI], a framework designed to make historical documents easier to transcribe in <<oXygen/>'s XML Author mode.<ref>http://www.oxygenxml.com/pipermail/oxygen-sdk/2014-November/000182.html</ref>

==== Severin ====

[http://code.google.com/p/severin-image-viewer/ Severin] is an image viewer plugin, by Kilian Schmidtner and Stefan Krause, that can be used to see images as you browse though documents. It is an open source project (MIT license), and on the project page you can find a video presentation that uses a TEI document as example.

==== TEI-Facsimile-Plugin ====

[https://github.com/oxygenxml/TEI-Facsimile-Plugin TEI-Facsimile-Plugin] "provides support for working with Digital Facsimiles in Text Encoding Initiative (TEI) vocabulary. The plugin contributes a new View in which the user can load an image and draw shapes. These shapes are then converted into TEI "zone" elements. All the existing "zone" elements from the document are also rendered over the image."<ref>https://github.com/oxygenxml/TEI-Facsimile-Plugin</ref> This plugin requires oXygen version 15 or later.

==== dbTagger ====

https://github.com/aerhard/dbTagger

==== ediarum ====

[[Ediarum]]

==== TEI Completer ====

https://github.com/BCDH/TEI-Completer

==== oXygen-XML-editor-attribute-editor ====

* [https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;7d49b3c3.1612 announcement]
* https://github.com/AlexJitianu/oXygen-XML-editor-attribute-editor

== Language(s) ==
Interface available in English, French, German, Italian, Japanese and Dutch.

Documentation available in English.

== Documentation ==
http://www.oxygenxml.com/documentation.html

== Tech support ==
http://www.oxygenxml.com/techSupport.html

Can buy maintenance and support pack, providing free upgrades and tech support.

== User community ==
* http://www.oxygenxml.com/mailman/listinfo/oxygen-user/
* http://www.oxygenxml.com/forum/

== Current version number and date of release ==
20.0 (2018-03-16)

== History of versions ==
See http://www.oxygenxml.com/software_archive.html .

== How to download or buy ==
http://www.oxygenxml.com/download.html

If you use Debian or Ubuntu, you should instead install the <tt>tei-oxygen</tt> package at http://tei.oucs.ox.ac.uk/teideb/ . (More information below.)

== Additional notes ==

David Sewell wrote:

<blockquote>
Because the schema files distributed with oXygen sometimes lag behind
the latest TEI releases, kind souls like Syd Bauman have from time to
time packaged new schema files so that they can be unpacked to replace
part of the oXygen frameworks hierarchy. You could also go to

http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/

and grab the files there to replace the ones in a local oXygen
directory.
<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;8d5b98b2.0804</ref>
</blockquote>

Sebastian Rahtz added that if you use Debian or Ubuntu, you should instead install the <code>tei-oxygen</code> package. He explained that "this replaces the oXygen TEI package with a link to one installed by the tei-p5-schema package, which is kept up to date. This means you have only one set of TEI files on your machine." It's available at http://tei.oucs.ox.ac.uk/teideb/ .

Marcus Bingenheimer:
If you edit ODD files you need to validate the ODD against tei_odds. tei_all will not catch all mistakes and gives and error whenever elements in the RNG or other namespaces are used within <datatype>.
As usual you can associate the tei_odds with a oxygen specific processing command similar to this:
<code><?oxygen RNGSchema="{your oxygen folder}/frameworks/tei/xml/tei/custom/schema/relaxng/tei_odds.rng" type="xml"?></code>

== References ==
<references/>

TEI Critical Apparatus Toolbox

2018-03-09T14:39:03Z

Kshawkin: /* Additional notes */ added link to jTEI article

[[Category:Tools]]

[[Category:Testing and QA tools]]

== Synopsis ==
The TEI Critical Apparatus Toolbox (formerly TEI Critical Edition Toolbox) "is a tool for people preparing a natively digital TEI critical edition.

"The Toolbox lets you:
* Check your encoding: offers facilities to display your edition while it is still in the making, and check the consistency of your encoding
* Display parallel versions: choose the sigla of the witnesses, and the different versions of the text, following each chosen witness, will be displayed in parallel columns."<ref>http://ciham-digital.huma-num.fr/teitoolbox/</ref>

== Features ==

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

== System requirements ==
* Your edition must be encoded in TEI with the Parallel Segmentation method.
* You simply need a recent browser to access the application and upload your XML file (nothing to install).<ref>http://ciham-digital.huma-num.fr/teitoolbox/</ref>

== Source code and licensing ==

== Support for TEI ==
TEI markup must use the parallel segmentation method.

== Language(s) ==
Interface is in English.

== Documentation ==
http://ciham-digital.huma-num.fr/teitoolbox/help.php

== Tech support ==

== User community ==

== Sample implementations ==
* http://ciham-digital.huma-num.fr/teitoolbox/check.php
* http://ciham-digital.huma-num.fr/teitoolbox/witnesses.php

== Current version number and date of release ==

== History of versions ==

== How to download or buy ==
available soon at http://ciham-digital.huma-num.fr/teitoolbox/download.php

== Additional notes ==
"For a presentation of the Toolbox, see this article in the Journal of the Text Encoding Initiative:
The TEI Critical Apparatus Toolbox: Empowering Textual Scholars through Display, Control, and Comparison Features
http://journals.openedition.org/jtei/1520"<ref>https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;ec22af28.1803</ref>

== References ==
<references/>

SIG:Newspapers&Periodicals

2018-03-02T02:52:12Z

Kshawkin: Created page with "SIG convener: Dario Kampkaspar Pulbications with any kind af regular publication cycle, from several times a day to cycles of several years, arguably form the majority of (print..."

SIG convener: Dario Kampkaspar

Pulbications with any kind af regular publication cycle, from several times a day to cycles of several years, arguably form the majority of (printed) texts nowadays. They span from newspapers via almanacs to comics and many others.

While these different types all have their own needs, their periodicity means that there are special questions to keep in mind when systematically encoding them.

The SIG Periodicals and Newspapers will focus on aspects that are common to all these kinds of periodicals:

* how to encode this periodicity with its aspects in a concise and machine readable way;
* how to deal with parts of periodicals that have their own periodicity (e.g. weekly, monthly etc. additions);
* how to deal with texts continued over several issues of a perdiodical;
* how to encode the title of e.g. a newspaper (which usually do not cover an entire page).

Additionally, the SIG will focus on methods and workflows for preparing full texts of periodicals by means of OCR and related technologies.

[[Category:SIG]]

User talk:Andreas Nolda

2018-01-26T16:30:48Z

Kshawkin: Welcome!

User:Andreas Nolda

2018-01-26T16:30:47Z

Kshawkin: Creating user page with biography of new user.

I am a linguist working with, and programming for, TEI since the SGML days in the 1990's.

In 2004/05 I was involved in submitting a proposal for a revised bibliographic markup scheme in TEI, eventually leading to the creation of the <relatedItem> element and, later on, to a recursive re-definition of the content model of <bibl>.

I am using TEI in particular for my 'born digital' documents, for which I have created the TEI2X package (http://andreas.nolda.org/software.html#tei2x). This package provides XSLT stylesheets for the generation of TeX files, DOCX files, and HTML files from TEI source files.

[[Category:Users]]

Workgroup to revise the Best Practices for TEI in Libraries

2018-01-24T01:51:32Z

Kshawkin: /* Meeting minutes */ added 2018-01-23 meeting for the record

== Background ==

[https://list.indiana.edu/sympa/arc/teilib-l/2015-11/msg00006.html Invitation to participate] in revision of ''[http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]''

== Logistics ==

First Monday of each month

9–10 a.m. Eastern Time in North America (14:00–15:00 UTC in winter in North America, 13:00–14:00 UTC at other times of the year)

People with email addresses listed below will have hangout link sent to them for each meeting. We can do up to 10 people with a regular hangout. If we get more people, we'll find someone with a Google Apps for Education account who can support up to 15(?).

: Actually, you can only invite up to 5 people to a Hangout. Beyond that, you need to just share a link. We'll plan to share the link on teilib-l shortly before each meeting.

If you can't make it, follow along by reviewing minutes (linked below) and/or watching [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues issues on GitHub] (click "watch" after logging in) and adding comments there.

== Resources ==

* [https://drive.google.com/open?id=0B13gonNAATNSSmtJMk14VHpzazQ Our Google Drive folder]
* [http://paramedic.wwp.northeastern.edu/~syd/temp/BPTL/ latest development snapshot]

== Members ==
* Kevin Hawkins (kevin.s.hawkins@gmail)
* stuart yeates ()
* stefanie gehrke (stefanie.gehrke9@gmail.com)
* Elli Mylonas (elli_mylonas@brown.edu)
* James Griffin (griffinj@lafayette.edu [or jrgriffiniii@gmail.com])
* Lisa McAulay ()
* Martin Mueller (martinmueller@northwestern.edu)
* Michelle Dalmau ()
* Antonio Rojas ()
* Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu])
* Peter Gorman (peter.gorman@wisc.edu)
* Andrew Rouner (andrew.rouner@gmail.com)
* Syd Bauman (s.bauman@northeastern.edu)

== Suggested meeting procedure ==

# Appoint notetaker, creating a new Google Docs file in our Google Drive folder.
# Resume discussions postponed from last meeting.
# Go through issues not yet discussed in order of [[BP revision ticket triage]]. For each issue, someone volunteers to summarize the issue:
## If the issue is straightforward and there's immediate consensus, ask for volunteer to record consensus as a comment on the issue, wait 7 days for objections, and then implement*.
## If issue is complicated, ask for volunteer to examine issue more closely after the meeting to propose a solution (either rejecting suggestion or changing prose and/or schema to implement*). Volunteer will post proposed solution as comment on the issue at least 7 days before our next meeting and lead discussion at next meeting.
### If there is consensus, volunteer implements* after the meeting.
### If there are any adjustments to proposal at that time, volunteer records in a comment on the issue and waits another 7 days for objections before implementing*.
# After meeting, those present review the minutes in the next 48 hours. Notetaker then announces minutes on TEILIB-L.

<nowiki>*</nowiki> Change may be implemented either by committing to the master branch or making pull requests. The advantage of a pull request is that it forces a second set of eyes to review changes. This is especially important for changes to content models in the ODD (rather than simply to prose).

== Meeting minutes ==

* [[Minutes for February 1, 2016|February 1, 2016]]
* [[March 7, 2016]]
* [[April 4, 2016]]
* [[May 2, 2016]]
* [[June 6, 2016]]
* [[July 11, 2016]]
* [[August 1, 2016]]
* [[September 12, 2016]]
* [[October 10, 2016]]
* [[November 14, 2016]]
* [[December 12, 2016]]
* [[January 9, 2017]]
* [[February 13, 2017]]
* [[March 6, 2017]]
* [[April 3, 2017]]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/blob/master/2017-05-08_notes.xml May 8, 2017]
* June 19, 2017 (decisions recorded only in GitHub issues)
* July 18, 2017 (decisions recorded only in GitHub issues)
* August 14, 2017 (decisions recorded only in GitHub issues)
* August 28, 2017
* September 11, 2017
* January 23, 2018 (decisions recorded only in GitHub issues)

[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]