Recent changes to Software

Software modified by Pietro Maria Liuzzo

Pietro Maria Liuzzo — Wed, 05 Dec 2018 09:25:44 -0000

--- v10
+++ v11
@@ -35,6 +35,7 @@
 These scripts are designed to import translations and minimal data to the [Eagle MediaWiki](eagle-network.eu/wiki/index.php/Main_Page) and might be useful if  you want to contribute translations (please email [Pietro](pietro.liuzzo@uni-hamburg.de) for further info) 
 * [Online Epidoc Converter](http://epidoc.dainst.org/)
 * [Exist-db Test App](https://github.com/EpiDoc/OEDUc) this app which can be installed via the package manager in exist db includes a series of lightly documented features which could be reused by projects working with this framework. Features are described in the wiki and in the index page of the app.
+* [XTriples](http://xtriples.spatialhumanities.de/index.html) allows to extract RDF defined in a simple configuration file from XML data. It has been tested on EpiDoc data as you can see  [in this presentation](https://digicademy.github.io/DARIAH-GT/)  and [in this presentation](https://digicademy.github.io/dariah-workshop2016-xtriples-cidoc/).
 * Oxygen Frameworks
 * Crosswalks
 * Transcoder

Software modified by Pietro Maria Liuzzo

Pietro Maria Liuzzo — Wed, 05 Dec 2018 09:07:52 -0000

--- v9
+++ v10
@@ -4,9 +4,15 @@
 Help with XML Editing Software
 ----

-EpiDoc files can be created and edited using any available XML editing software (several of which are listed at the [TEI wiki](http://wiki.tei-c.org/index.php/Category:Editing_tools) or [Wikipedia](http://en.wikipedia.org/wiki/List_of_XML_editors)); basic training in the use of such tools is usually included in both EpiDoc and TEI training events, or any XML tutorial.
+EpiDoc files can be created and edited using any available XML editing software (several of which are listed at the [TEI wiki](http://wiki.tei-c.org/index.php/Category:Editing_tools), [TEI wiki Editors page](https://wiki.tei-c.org/index.php/Editors) or [Wikipedia](http://en.wikipedia.org/wiki/List_of_XML_editors)); basic training in the use of such tools is usually included in both EpiDoc and TEI training events, or any XML tutorial.

 The Oxygen XML Editor is one such option, and is available for Linux, Mac OS X and Windows.  Oxygen XML Editor can be downloaded [here](http://www.oxygenxml.com/download_oxygenxml_editor.html) and can be trialled for 30 days for free; an academic license is only $99 thereafter.
+
+[Atom](https://atom.io/) is another option for editing and validating XML, as well as interacting with data in GitHub. It is free. To validate your files, you can add [this package](https://atom.io/packages/linter-autocomplete-jing). Eventually this can also be connected to [eXist-db](http://exist-db.org) with a [further package](https://atom.io/packages/existdb) and serve also querying and transformations in there. 
+
+[eXist-db](http://exist-db.org) ships also with a free XML editor called eXide which has a lot of support for encoding XML. Validation and transformations need to be run as queries with the relevant functions.
+
+

 Other Tools for Working with XML and EpiDoc
 ----

Software modified by Pietro Maria Liuzzo

Pietro Maria Liuzzo — Thu, 07 Sep 2017 06:21:43 -0000

--- v8
+++ v9
@@ -28,6 +28,7 @@
 * [Epidoc to Wikibase](https://github.com/pietrodn/eagle)
 These scripts are designed to import translations and minimal data to the [Eagle MediaWiki](eagle-network.eu/wiki/index.php/Main_Page) and might be useful if  you want to contribute translations (please email [Pietro](pietro.liuzzo@uni-hamburg.de) for further info) 
 * [Online Epidoc Converter](http://epidoc.dainst.org/)
+* [Exist-db Test App](https://github.com/EpiDoc/OEDUc) this app which can be installed via the package manager in exist db includes a series of lightly documented features which could be reused by projects working with this framework. Features are described in the wiki and in the index page of the app.
 * Oxygen Frameworks
 * Crosswalks
 * Transcoder

Software modified by Pietro Maria Liuzzo

Pietro Maria Liuzzo — Fri, 15 Apr 2016 13:52:24 -0000

--- v7
+++ v8
@@ -26,7 +26,8 @@
 * [HTML table to EpiDoc](https://github.com/PietroLiuzzo/epidocupconversion/blob/master/allinone/htmltable-epidoc.xsl)
 This is a template to take data from a table in html and create a series of template EpiDoc. It should be useful if you begin your work from this kind of data (any table which you can save in html). The order of the columns depend from your input. A lot of post process editing will be needed any way. Much more editing will be required if EDH conventions are not followed for the text.
 * [Epidoc to Wikibase](https://github.com/pietrodn/eagle)
-These scripts are designed to import translations and minimal data to the [Eagle MediaWiki](eagle-network.eu/wiki/index.php/Main_Page) and might be useful if  you want to contribute translations (please email [Pietro](pietro.liuzzo@zaw.uni-heidelberg.de) for further info) 
+These scripts are designed to import translations and minimal data to the [Eagle MediaWiki](eagle-network.eu/wiki/index.php/Main_Page) and might be useful if  you want to contribute translations (please email [Pietro](pietro.liuzzo@uni-hamburg.de) for further info) 
+* [Online Epidoc Converter](http://epidoc.dainst.org/)
 * Oxygen Frameworks
 * Crosswalks
 * Transcoder

Software modified by BODARD Gabriel

BODARD Gabriel — Mon, 24 Nov 2014 16:24:38 -0000

--- v6
+++ v7
@@ -15,17 +15,16 @@

 Tools Created by Members of the EpiDoc Community
 ----
-* [EpiDoc upconversion](https://github.com/PietroLiuzzo/epidocupconversion)
-This is a series of xsl transformation in continuous development that can convert string to xml markup. It was designed to meet the needs of [EAGLE project members](http://www.eagle-network.eu/about/partners/). These XSL also insert in your EpiDoc template structure links to the [Eagle Vocabularies](http://www.eagle-network.eu/about/reserved-area/eagle-vocabulary/), if you use terms which are there (and you can always ask to add them: email [Pietro](pietro.liuzzo@zaw.uni-heidelberg.de)).
-* [HTML table to EpiDoc](https://github.com/PietroLiuzzo/epidocupconversion/blob/master/allinone/htmltable-epidoc.xsl)
-This is a template to take data from a table in html and create a series of template EpiDoc. It should be useful if you begin your work from this kind of data (any table which you can save in html). The order of the columns depend from your input. A lot of post process editing will be needed any way. Much more editing will be required if EDH conventions are not followed for the text.
 * [(London) P5 Conversion](https://svn.code.sf.net/p/epidoc/code/trunk/P5 conversion)
 A set of XSLT scripts for converting an EpiDoc project in TEI P4 to match the guidelines for EpiDoc in TEI P5. The scripts are customized to specific projects (DDbDP, InsAph, IRT, etc.) and probably need customization for more general use.
 * [(EAGLE) EpiDoc P4-P5](https://github.com/PietroLiuzzo/EpidocP4toP5-EAGLE)
 Based on IRT for [EAGLE](http://www.eagle-network.eu/) crosswalk, this xsl takes EpiDoc p4 and transforms it in p5 adding EAGLE vocabularies where possible and IPR statements according to EAGLE requirements.  
 * [Crosswalking EpiDoc to EDH with EDH validation schema](https://github.com/PietroLiuzzo/Epidoc2EDH)
-Based on RIB to EDH crosswalk, this XSL takes a list of files in EpiDoc XML, matched with existing HD numbers and TM ids in an html table and converts structured information to a flat xml file with values with strict conventions (e.g. An.Ep.2009: 45 --> AE 2009, 0045.). To be reused this needs to be widely customized according to the input EpiDoc, as many of the transformation match string patterns and non structured data.
-The results should validate to the EDH schema.
+Based on RIB to EDH crosswalk, this XSL takes a list of files in EpiDoc XML, matched with existing HD numbers and TM ids in an html table and converts structured information to a flat xml file with values with strict conventions (e.g. An.Ep.2009: 45 --> AE 2009, 0045.). To be reused this needs to be widely customized according to the input EpiDoc, as many of the transformation match string patterns and non structured data. The results should validate to the EDH schema.
+* [EpiDoc upconversion](https://github.com/PietroLiuzzo/epidocupconversion)
+This is a series of xsl transformation in continuous development that can convert string to xml markup. It was designed to meet the needs of [EAGLE project members](http://www.eagle-network.eu/about/partners/). These XSL also insert in your EpiDoc template structure links to the [Eagle Vocabularies](http://www.eagle-network.eu/about/reserved-area/eagle-vocabulary/), if you use terms which are there (and you can always ask to add them: email [Pietro](pietro.liuzzo@zaw.uni-heidelberg.de)).
+* [HTML table to EpiDoc](https://github.com/PietroLiuzzo/epidocupconversion/blob/master/allinone/htmltable-epidoc.xsl)
+This is a template to take data from a table in html and create a series of template EpiDoc. It should be useful if you begin your work from this kind of data (any table which you can save in html). The order of the columns depend from your input. A lot of post process editing will be needed any way. Much more editing will be required if EDH conventions are not followed for the text.
 * [Epidoc to Wikibase](https://github.com/pietrodn/eagle)
 These scripts are designed to import translations and minimal data to the [Eagle MediaWiki](eagle-network.eu/wiki/index.php/Main_Page) and might be useful if  you want to contribute translations (please email [Pietro](pietro.liuzzo@zaw.uni-heidelberg.de) for further info) 
 * Oxygen Frameworks

Software modified by BODARD Gabriel

BODARD Gabriel — Mon, 24 Nov 2014 16:23:51 -0000

--- v5
+++ v6
@@ -18,8 +18,10 @@
 * [EpiDoc upconversion](https://github.com/PietroLiuzzo/epidocupconversion)
 This is a series of xsl transformation in continuous development that can convert string to xml markup. It was designed to meet the needs of [EAGLE project members](http://www.eagle-network.eu/about/partners/). These XSL also insert in your EpiDoc template structure links to the [Eagle Vocabularies](http://www.eagle-network.eu/about/reserved-area/eagle-vocabulary/), if you use terms which are there (and you can always ask to add them: email [Pietro](pietro.liuzzo@zaw.uni-heidelberg.de)).
 * [HTML table to EpiDoc](https://github.com/PietroLiuzzo/epidocupconversion/blob/master/allinone/htmltable-epidoc.xsl)
-This is a template to take data from a table in html and create a series of template EpiDoc. It should be useful if you begin your work from this kind of data (any table which you can save in html). The order of the columns depend from your input. A lot of post process editing will be needed any way. Much more editing will be required if EDH conventions are not followed for the text. 
-* [EAGLE EpiDoc P4-P5](https://github.com/PietroLiuzzo/EpidocP4toP5-EAGLE)
+This is a template to take data from a table in html and create a series of template EpiDoc. It should be useful if you begin your work from this kind of data (any table which you can save in html). The order of the columns depend from your input. A lot of post process editing will be needed any way. Much more editing will be required if EDH conventions are not followed for the text.
+* [(London) P5 Conversion](https://svn.code.sf.net/p/epidoc/code/trunk/P5 conversion)
+A set of XSLT scripts for converting an EpiDoc project in TEI P4 to match the guidelines for EpiDoc in TEI P5. The scripts are customized to specific projects (DDbDP, InsAph, IRT, etc.) and probably need customization for more general use.
+* [(EAGLE) EpiDoc P4-P5](https://github.com/PietroLiuzzo/EpidocP4toP5-EAGLE)
 Based on IRT for [EAGLE](http://www.eagle-network.eu/) crosswalk, this xsl takes EpiDoc p4 and transforms it in p5 adding EAGLE vocabularies where possible and IPR statements according to EAGLE requirements.  
 * [Crosswalking EpiDoc to EDH with EDH validation schema](https://github.com/PietroLiuzzo/Epidoc2EDH)
 Based on RIB to EDH crosswalk, this XSL takes a list of files in EpiDoc XML, matched with existing HD numbers and TM ids in an html table and converts structured information to a flat xml file with values with strict conventions (e.g. An.Ep.2009: 45 --> AE 2009, 0045.). To be reused this needs to be widely customized according to the input EpiDoc, as many of the transformation match string patterns and non structured data.

Software modified by BODARD Gabriel

BODARD Gabriel — Mon, 24 Nov 2014 16:20:44 -0000

--- v4
+++ v5
@@ -19,14 +19,13 @@
 This is a series of xsl transformation in continuous development that can convert string to xml markup. It was designed to meet the needs of [EAGLE project members](http://www.eagle-network.eu/about/partners/). These XSL also insert in your EpiDoc template structure links to the [Eagle Vocabularies](http://www.eagle-network.eu/about/reserved-area/eagle-vocabulary/), if you use terms which are there (and you can always ask to add them: email [Pietro](pietro.liuzzo@zaw.uni-heidelberg.de)).
 * [HTML table to EpiDoc](https://github.com/PietroLiuzzo/epidocupconversion/blob/master/allinone/htmltable-epidoc.xsl)
 This is a template to take data from a table in html and create a series of template EpiDoc. It should be useful if you begin your work from this kind of data (any table which you can save in html). The order of the columns depend from your input. A lot of post process editing will be needed any way. Much more editing will be required if EDH conventions are not followed for the text. 
-* [EpiDoc P4-P5](https://github.com/PietroLiuzzo/EpidocP4toP5-EAGLE)
+* [EAGLE EpiDoc P4-P5](https://github.com/PietroLiuzzo/EpidocP4toP5-EAGLE)
 Based on IRT for [EAGLE](http://www.eagle-network.eu/) crosswalk, this xsl takes EpiDoc p4 and transforms it in p5 adding EAGLE vocabularies where possible and IPR statements according to EAGLE requirements.  
 * [Crosswalking EpiDoc to EDH with EDH validation schema](https://github.com/PietroLiuzzo/Epidoc2EDH)
 Based on RIB to EDH crosswalk, this XSL takes a list of files in EpiDoc XML, matched with existing HD numbers and TM ids in an html table and converts structured information to a flat xml file with values with strict conventions (e.g. An.Ep.2009: 45 --> AE 2009, 0045.). To be reused this needs to be widely customized according to the input EpiDoc, as many of the transformation match string patterns and non structured data.
 The results should validate to the EDH schema.
 * [Epidoc to Wikibase](https://github.com/pietrodn/eagle)
-These scripts are designed to import translations and minimal data to the [Eagle MediaWiki](eagle-network.eu/wiki/index.php/Main_Page) and might be useful if  you want to contribute translations (please, just email [Pietro](pietro.liuzzo@zaw.uni-heidelberg.de) for further info) 
+These scripts are designed to import translations and minimal data to the [Eagle MediaWiki](eagle-network.eu/wiki/index.php/Main_Page) and might be useful if  you want to contribute translations (please email [Pietro](pietro.liuzzo@zaw.uni-heidelberg.de) for further info) 
 * Oxygen Frameworks
-* Crosswalkers
+* Crosswalks
 * Transcoder
-* ???

Software modified by Pietro Maria Liuzzo

Pietro Maria Liuzzo — Fri, 25 Apr 2014 13:38:59 -0000

--- v3
+++ v4
@@ -15,22 +15,17 @@

 Tools Created by Members of the EpiDoc Community
 ----
-*[EpiDoc upconversion](https://github.com/PietroLiuzzo/epidocupconversion)
+* [EpiDoc upconversion](https://github.com/PietroLiuzzo/epidocupconversion)
 This is a series of xsl transformation in continuous development that can convert string to xml markup. It was designed to meet the needs of [EAGLE project members](http://www.eagle-network.eu/about/partners/). These XSL also insert in your EpiDoc template structure links to the [Eagle Vocabularies](http://www.eagle-network.eu/about/reserved-area/eagle-vocabulary/), if you use terms which are there (and you can always ask to add them: email [Pietro](pietro.liuzzo@zaw.uni-heidelberg.de)).
-
-*[HTML table to EpiDoc](https://github.com/PietroLiuzzo/epidocupconversion/blob/master/allinone/htmltable-epidoc.xsl)
+* [HTML table to EpiDoc](https://github.com/PietroLiuzzo/epidocupconversion/blob/master/allinone/htmltable-epidoc.xsl)
 This is a template to take data from a table in html and create a series of template EpiDoc. It should be useful if you begin your work from this kind of data (any table which you can save in html). The order of the columns depend from your input. A lot of post process editing will be needed any way. Much more editing will be required if EDH conventions are not followed for the text. 
-
-*[EpiDoc P4-P5](https://github.com/PietroLiuzzo/EpidocP4toP5-EAGLE)
+* [EpiDoc P4-P5](https://github.com/PietroLiuzzo/EpidocP4toP5-EAGLE)
 Based on IRT for [EAGLE](http://www.eagle-network.eu/) crosswalk, this xsl takes EpiDoc p4 and transforms it in p5 adding EAGLE vocabularies where possible and IPR statements according to EAGLE requirements.  
-
-*[Crosswalking EpiDoc to EDH with EDH validation schema](https://github.com/PietroLiuzzo/Epidoc2EDH)
+* [Crosswalking EpiDoc to EDH with EDH validation schema](https://github.com/PietroLiuzzo/Epidoc2EDH)
 Based on RIB to EDH crosswalk, this XSL takes a list of files in EpiDoc XML, matched with existing HD numbers and TM ids in an html table and converts structured information to a flat xml file with values with strict conventions (e.g. An.Ep.2009: 45 --> AE 2009, 0045.). To be reused this needs to be widely customized according to the input EpiDoc, as many of the transformation match string patterns and non structured data.
 The results should validate to the EDH schema.
-
-*[Epidoc to Wikibase](https://github.com/pietrodn/eagle)
+* [Epidoc to Wikibase](https://github.com/pietrodn/eagle)
 These scripts are designed to import translations and minimal data to the [Eagle MediaWiki](eagle-network.eu/wiki/index.php/Main_Page) and might be useful if  you want to contribute translations (please, just email [Pietro](pietro.liuzzo@zaw.uni-heidelberg.de) for further info) 
-
 * Oxygen Frameworks
 * Crosswalkers
 * Transcoder

Software modified by Pietro Maria Liuzzo

Pietro Maria Liuzzo — Fri, 25 Apr 2014 13:38:21 -0000

--- v2
+++ v3
@@ -15,6 +15,21 @@

 Tools Created by Members of the EpiDoc Community
 ----
+*[EpiDoc upconversion](https://github.com/PietroLiuzzo/epidocupconversion)
+This is a series of xsl transformation in continuous development that can convert string to xml markup. It was designed to meet the needs of [EAGLE project members](http://www.eagle-network.eu/about/partners/). These XSL also insert in your EpiDoc template structure links to the [Eagle Vocabularies](http://www.eagle-network.eu/about/reserved-area/eagle-vocabulary/), if you use terms which are there (and you can always ask to add them: email [Pietro](pietro.liuzzo@zaw.uni-heidelberg.de)).
+
+*[HTML table to EpiDoc](https://github.com/PietroLiuzzo/epidocupconversion/blob/master/allinone/htmltable-epidoc.xsl)
+This is a template to take data from a table in html and create a series of template EpiDoc. It should be useful if you begin your work from this kind of data (any table which you can save in html). The order of the columns depend from your input. A lot of post process editing will be needed any way. Much more editing will be required if EDH conventions are not followed for the text. 
+
+*[EpiDoc P4-P5](https://github.com/PietroLiuzzo/EpidocP4toP5-EAGLE)
+Based on IRT for [EAGLE](http://www.eagle-network.eu/) crosswalk, this xsl takes EpiDoc p4 and transforms it in p5 adding EAGLE vocabularies where possible and IPR statements according to EAGLE requirements.  
+
+*[Crosswalking EpiDoc to EDH with EDH validation schema](https://github.com/PietroLiuzzo/Epidoc2EDH)
+Based on RIB to EDH crosswalk, this XSL takes a list of files in EpiDoc XML, matched with existing HD numbers and TM ids in an html table and converts structured information to a flat xml file with values with strict conventions (e.g. An.Ep.2009: 45 --> AE 2009, 0045.). To be reused this needs to be widely customized according to the input EpiDoc, as many of the transformation match string patterns and non structured data.
+The results should validate to the EDH schema.
+
+*[Epidoc to Wikibase](https://github.com/pietrodn/eagle)
+These scripts are designed to import translations and minimal data to the [Eagle MediaWiki](eagle-network.eu/wiki/index.php/Main_Page) and might be useful if  you want to contribute translations (please, just email [Pietro](pietro.liuzzo@zaw.uni-heidelberg.de) for further info) 

 * Oxygen Frameworks
 * Crosswalkers

Software modified by Tom Elliott

Tom Elliott — Thu, 24 Apr 2014 15:27:53 -0000

--- v1
+++ v2
@@ -12,3 +12,11 @@
 ----

 Tools for publishing, searching and otherwise processing EpiDoc and TEI files include the XML transformation languages [XSLT](http://www.w3schools.com/xsl/xsl_intro.asp) and [XQuery](http://www.w3schools.com/xquery/default.asp), general searching platforms such as [Solr](http://lucene.apache.org/solr/), and TEI specific open source tools like [Kiln](https://github.com/kcl-ddh/kiln) and the [Papyrological Navigator](https://github.com/papyri/navigator). Support and advice on these tools may be available at the repositories or documentation sites for each.
+
+Tools Created by Members of the EpiDoc Community
+----
+
+* Oxygen Frameworks
+* Crosswalkers
+* Transcoder
+* ???