diff --git a/data/JTEI/10_2016-19/jtei-10-burghart-source.xml b/data/JTEI/10_2016-19/jtei-10-burghart-source.xml index d63aec0..3aab424 100644 --- a/data/JTEI/10_2016-19/jtei-10-burghart-source.xml +++ b/data/JTEI/10_2016-19/jtei-10-burghart-source.xml @@ -49,6 +49,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/10_2016-19/jtei-10-dumont-source.xml b/data/JTEI/10_2016-19/jtei-10-dumont-source.xml index 472fe05..c161c2a 100644 --- a/data/JTEI/10_2016-19/jtei-10-dumont-source.xml +++ b/data/JTEI/10_2016-19/jtei-10-dumont-source.xml @@ -47,6 +47,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/10_2016-19/jtei-10-emsley-source.xml b/data/JTEI/10_2016-19/jtei-10-emsley-source.xml index f4a3696..11bc189 100644 --- a/data/JTEI/10_2016-19/jtei-10-emsley-source.xml +++ b/data/JTEI/10_2016-19/jtei-10-emsley-source.xml @@ -59,6 +59,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/10_2016-19/jtei-10-haaf-source.xml b/data/JTEI/10_2016-19/jtei-10-haaf-source.xml index 6aa8cc7..8de991a 100644 --- a/data/JTEI/10_2016-19/jtei-10-haaf-source.xml +++ b/data/JTEI/10_2016-19/jtei-10-haaf-source.xml @@ -69,6 +69,19 @@ text-decoration:line-through; vertical-align: super;font-size:0.83em; + + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -211,15 +224,16 @@ target="http://www.deutschestextarchiv.de/doku/software#cab"/>. as well as collaborative text correction and annotationSee <ptr type="software" xml:id="R3" - target="#dtaq"/><rs type="soft.name" ref="#R3">DTAQ: Kollaborative Qualitätssicherung im Deutschen Textarchiv</rs> - (Collaborative Quality Assurance within the DTA), accessed January 28, 2017, . On the process of - quality assurance in the DTA, see, for example, Haaf, - Wiegand, and Geyken 2013.) is a matter of supporting scholarly projects - in their usage of the DTA infrastructure, which is part of the DTA’s mission. Second, - while the DTA corpus is fairly diverse with regard to (printed) text types and - disciplines, the absence of manuscripts causes certain core text + level="a">DTAQ: Kollaborative Qualitätssicherung im Deutschen + Textarchiv (Collaborative Quality Assurance within the DTA), accessed + January 28, 2017, . On the + process of quality assurance in the DTA, see, for example, Haaf, Wiegand, and Geyken 2013.) is a matter of supporting + scholarly projects in their usage of the DTA infrastructure, which is part of the DTA’s + mission. Second, while the DTA corpus is fairly diverse with regard to (printed) text + types and disciplines, the absence of manuscripts causes certain core text typesSee Gansel 2011, 53, for a reflection on the term Kerntextsorte (i.e., core text type). of writing to be underrepresented within the corpus (e.g., private @@ -274,14 +288,14 @@ Since June 2014, nine complete volumes with a total of more than 3,500 manuscript pages have been manually transcribed, annotated in TEI XML, and published via the DTA infrastructure. Most of these manuscripts were keyed manually by a vendor and published at - an early stage in the web-based quality assurance platform DTAQ. There, the transcription - as well as the annotation of each document was checked and corrected, if necessary; DTAQ - also provided the means to add additional markup, such as the tagging of person names - (persName), directly at page level. After the process of quality control has - been completed, the manuscripts were released on the DTA website.For the ongoing - publication of the Hidden Kosmos subcorpus, see the DTA search page, AvHKV subcorpus, - accessed July 13, 2017, DTAQ. There, the + transcription as well as the annotation of each document was checked and corrected, if + necessary; DTAQ also provided the means to add additional markup, such as the tagging of + person names (persName), directly at page level. After the process of quality + control has been completed, the manuscripts were released on the DTA website.For the + ongoing publication of the Hidden Kosmos subcorpus, see the DTA search page, AvHKV + subcorpus, accessed July 13, 2017, . While the Hidden Kosmos project is now complete, development of the DTABf-M continues through work on other manuscripts.

diff --git a/data/JTEI/10_2016-19/jtei-10-homenda-source.xml b/data/JTEI/10_2016-19/jtei-10-homenda-source.xml index 6b98500..60af5b3 100644 --- a/data/JTEI/10_2016-19/jtei-10-homenda-source.xml +++ b/data/JTEI/10_2016-19/jtei-10-homenda-source.xml @@ -62,6 +62,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/10_2016-19/jtei-10-romary-source.xml b/data/JTEI/10_2016-19/jtei-10-romary-source.xml index 5999044..7409708 100644 --- a/data/JTEI/10_2016-19/jtei-10-romary-source.xml +++ b/data/JTEI/10_2016-19/jtei-10-romary-source.xml @@ -85,6 +85,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -645,15 +658,14 @@ available at . In our proposal, the etym element has to be made recursive in order to allow the fine-grained representations we propose here. The corresponding ODD customization, together with - reference examples, is available on GitHub.
and the - fact that a change occurred within the contemporary lexicon (as opposed to its parent - language) is indicated by means of xml:lang on the source form.There - may also be cases in which it is unknown whether a given etymological process occurred - within the contemporary language or parent system; in such cases the encoder can just - use the main language tag for both the diachronic and synchronic portions of the entry - as a default (see, for instance, ).

+ reference examples, is available on GitHub. and the fact that a change + occurred within the contemporary lexicon (as opposed to its parent language) is + indicated by means of xml:lang on the source form.There may also be + cases in which it is unknown whether a given etymological process occurred within the + contemporary language or parent system; in such cases the encoder can just use the + main language tag for both the diachronic and synchronic portions of the entry as a + default (see, for instance, ).

In the TEI encoding, the former two can be respectively labeled as: and The interested reader may ponder here the possibility to also encode scripts by means of the notation attribute instead of using a cluttering of language subtags on xml:lang. For more on this issue, see the proposal in - the TEI GitHub (). This is why we have extended the notation attribute to orth in order to allow for better representation of both language @@ -1486,23 +1498,23 @@ extent of knowledge that is truly necessary to create an accurate model of metaphorical processes. In order to do this, it is necessary to make use of one or more ontologies, which could be locally defined within a project, and of external linked open data sources - such as DBpedia and Wikidata, or some combination thereof. Within - TEI dictionary markup, URIs for existing ontological entries can be referenced in the - sense, usg, and ref elements as the value of the attribute - corresp.

+ such as DBpedia and Wikidata, or some combination + thereof. Within TEI dictionary markup, URIs for existing ontological entries can be + referenced in the sense, usg, and ref elements as the value of + the attribute corresp.

Within the etymon, the oRef and/or pRef can be included with a pointer to the source form using the corresp attribute, the value of which is a reference to the source entry’s unique identifier (if such an entry exists within the dataset). In such cases, the etymon pointing to the source entry can be assumed to inherit the source’s domain and sense information, and this information can be automatically - extracted with a fairly simple XSLT program; thus the encoders may choose to leave some or - all of this information out of the etymon section. However, in the case that the dataset - does not actually have entries for the source terms, or the encoder wants to be explicit - in all aspects of the etymology, as mentioned above, the source domain and the + extracted with a fairly simple XSLT program; thus the encoders may choose to leave some + or all of this information out of the etymon section. However, in the case that the + dataset does not actually have entries for the source terms, or the encoder wants to be + explicit in all aspects of the etymology, as mentioned above, the source domain and the ontologically based sense of an etymon can be encoded within cit as ref and usg respectively.

@@ -1560,8 +1572,8 @@ URI is referenced in oRef and pRef as the value of corresp (@corresp="#animal").

In sense, the URI corresponding to the DBpedia entry for horse is the - value for the attribute corresp. Additionally, the date + target="#dbpedia"/>DBpedia entry for horse is + the value for the attribute corresp. Additionally, the date notBefore="…" element–attribute pairing is used to specify that the term has only been used for the horse since 1517 at maximum (corresponding to the first Spanish expedition into Mexico). Within the actual document, the contents of note discuss diff --git a/data/JTEI/10_2016-19/jtei-10-viglianti-source.xml b/data/JTEI/10_2016-19/jtei-10-viglianti-source.xml index 8a48419..274d931 100644 --- a/data/JTEI/10_2016-19/jtei-10-viglianti-source.xml +++ b/data/JTEI/10_2016-19/jtei-10-viglianti-source.xml @@ -51,6 +51,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/11_2019-20/jtei-11-intro-source.xml b/data/JTEI/11_2019-20/jtei-11-intro-source.xml index 869a261..f61d488 100644 --- a/data/JTEI/11_2019-20/jtei-11-intro-source.xml +++ b/data/JTEI/11_2019-20/jtei-11-intro-source.xml @@ -90,6 +90,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/11_2019-20/jtei-cc-pn-dalmau-139-source.xml b/data/JTEI/11_2019-20/jtei-cc-pn-dalmau-139-source.xml index 6c13928..564f047 100644 --- a/data/JTEI/11_2019-20/jtei-cc-pn-dalmau-139-source.xml +++ b/data/JTEI/11_2019-20/jtei-cc-pn-dalmau-139-source.xml @@ -152,6 +152,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/11_2019-20/jtei-cc-pn-geissler-138-source.xml b/data/JTEI/11_2019-20/jtei-cc-pn-geissler-138-source.xml index c894ac6..e7c91b5 100644 --- a/data/JTEI/11_2019-20/jtei-cc-pn-geissler-138-source.xml +++ b/data/JTEI/11_2019-20/jtei-cc-pn-geissler-138-source.xml @@ -64,6 +64,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/11_2019-20/jtei-cc-pn-morgenstern-135-source.xml b/data/JTEI/11_2019-20/jtei-cc-pn-morgenstern-135-source.xml index 4799395..ed79551 100644 --- a/data/JTEI/11_2019-20/jtei-cc-pn-morgenstern-135-source.xml +++ b/data/JTEI/11_2019-20/jtei-cc-pn-morgenstern-135-source.xml @@ -65,6 +65,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/11_2019-20/jtei-cc-pn-resch-142-source.xml b/data/JTEI/11_2019-20/jtei-cc-pn-resch-142-source.xml index 7b6325f..478d3e3 100644 --- a/data/JTEI/11_2019-20/jtei-cc-pn-resch-142-source.xml +++ b/data/JTEI/11_2019-20/jtei-cc-pn-resch-142-source.xml @@ -98,6 +98,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/11_2019-20/jtei-cc-ra-bermudez-sabel-137-source.xml b/data/JTEI/11_2019-20/jtei-cc-ra-bermudez-sabel-137-source.xml index c83a09b..6553385 100644 --- a/data/JTEI/11_2019-20/jtei-cc-ra-bermudez-sabel-137-source.xml +++ b/data/JTEI/11_2019-20/jtei-cc-ra-bermudez-sabel-137-source.xml @@ -53,6 +53,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -110,11 +123,11 @@ ways in which the variant taxonomy may be linked to the body of the edition.

Although this paper is TEI-centered, other XML technologies will be mentioned. includes a brief commentary on using XSLT - to transform a TEI-conformant definition of constraints into schema rules. However, the + type="software" xml:id="R1" target="#xslt"/>XSLT to + transform a TEI-conformant definition of constraints into schema rules. However, the greatest attention to an additional technology is in , which discusses the use of XQuery to retrieve particular + target="#xquery"/>XQuery to retrieve particular loci critici and to deploy quantitative analyses.

@@ -212,16 +225,16 @@ neutralized.This statement is especially significant when dealing with corpora that have been compiled over a long period of time. As is clearly explained in the introduction to the Helsinki Corpus that Irma Taavitsainen and Päivi Pahta prepared for - the Corpus Resource Database (CoRD) (Placing the Helsinki Corpus Middle English + Section Introduction into Context, Corpus Resource Database (CoRD) (Placing the Helsinki Corpus Middle English Section Introduction into - Context, ): The idea of basing corpus texts directly on - manuscript sources has been presented more recently The principles of preparing - manuscript texts for print have undergone changes during the history of + />): The idea of basing corpus texts directly + on manuscript sources has been presented more recently The principles of + preparing manuscript texts for print have undergone changes during the history of editing.

Depending on the historical period to which a tradition belongs, even graphic variants, often dismissed as nonsignificant variation because they may not be textually @@ -544,17 +557,17 @@ >parallel segmentation method (TEI Consortium 2016, 12.2.3) seems to be a popular encoding technique for multi-witness editions, in terms of both the specific tools that have been created for this method and the number - of projects that apply it.Tools include Versioning Machine, CollateX (both - the Java and Python versions), and Juxta. For - representative projects using the parallel segmentation method see Tools include Versioning Machine, CollateX (both the Java and Python versions), and Juxta. For representative projects using the parallel segmentation + method see Satire in Circulation: James editions Russell Lowell’s Letter from a volunteer in Saltillo, Walden: A diff --git a/data/JTEI/11_2019-20/jtei-cc-ra-hannessschlaeger-164-source.xml b/data/JTEI/11_2019-20/jtei-cc-ra-hannessschlaeger-164-source.xml index 3f1483c..9a46a09 100644 --- a/data/JTEI/11_2019-20/jtei-cc-ra-hannessschlaeger-164-source.xml +++ b/data/JTEI/11_2019-20/jtei-cc-ra-hannessschlaeger-164-source.xml @@ -57,6 +57,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -120,12 +133,12 @@ example, which is as TEI-specific as it can get: I will describe the history of the TEI Conference 2016 abstracts, which have, since the conference, been transformed into a TEI data set that has been published not only on GitHub, but also in an - eXistdb-powered web application. This is by any standard a wonderful development for a - collection of textual data—and one that would not have been possible had the abstracts not - been published under an open license, especially since their authors come from fourteen - different countries.

+ target="#github"/>GitHub, but also in an eXistdb-powered web application. This is by any standard a wonderful development + for a collection of textual data—and one that would not have been possible had the + abstracts not been published under an open license, especially since their authors come + from fourteen different countries.

Why Nation Matters, Why It Shouldn’t: National Laws vs. WIPO @@ -445,23 +458,23 @@ explain how licensing played a vital role in enabling this transformation.

Submission of the Abstracts and the joys of ConfTool -

As it is every year, the conference management software As it is every year, the conference management software ConfTool ProConfTool Conference - Management Software, ConfTool GmbH, accessed August 23, 2019, . was used for the submission of the - abstracts of the 2016 TEI conference. When the Vienna team received access to the - ConfTool system, the instance for the 2016 conference had been equipped with default - settings based on previous TEI conference settings. As ConfTool is not the most - intuitive system to handle for a first-time administrator,The chair of the 2017 - TEI conference program committee Kathryn Tomasek has described the rather tricky - structure of the system as the joys of ConfTool (email message to author, April - 11, 2017). one aspect was overlooked when setting up the system for the 2016 - conference: the Copyright Transfer Terms and Licensing Policy that - contributors had to agree to when submitting an abstract remained unchanged. It was - phrased as follows:

+ Management Software, ConfTool GmbH, accessed August 23, 2019, . was used for the + submission of the abstracts of the 2016 TEI conference. When the Vienna team received + access to the ConfTool system, the instance for the 2016 conference had been equipped + with default settings based on previous TEI conference settings. As ConfTool is not + the most intuitive system to handle for a first-time administrator,The chair of + the 2017 TEI conference program committee Kathryn Tomasek has described the rather + tricky structure of the system as the joys of ConfTool (email + message to author, April 11, 2017). one aspect was overlooked when setting up + the system for the 2016 conference: the Copyright Transfer Terms and Licensing + Policy that contributors had to agree to when submitting an abstract + remained unchanged. It was phrased as follows:

The undersigned hereby assigns the organizers of the TEI Conference and Members’ Meeting 2016 all rights under copyright that may exist in and to the above work, including the rights to use, distribute, publish, record, broadcast, reproduce and @@ -531,26 +544,26 @@ Hannesschläger, and Wissik 2016a). Subsequently, the PDF of this printed book was made available via the conference website under the same license (Resch, Hannesschläger, and Wissik 2016b).

-

The page proofs that were transformed into this PDF had been created with Adobe +

The page proofs that were transformed into this PDF had been created with Adobe InDesign. The real fun started when the InDesign file was exported to XML and - transformed back into single files (one file per abstract). These files were edited with - the Oxygen XML editor to become proper TEI files with extensive headers. Finally, they - were published as a repository together with the TEI schema on GitHub (Hannesschläger and Schopper 2017), again - under the same license. This allowed Martin Sievers, one of the abstract authors, to - immediately correct a typing error in his abstract that the editors had overlooked (see - history of Hannesschläger and Schopper - 2017 on InDesign file was exported to + XML and transformed back into single files (one file per abstract). These files were + edited with the Oxygen XML editor to become proper TEI files with extensive headers. + Finally, they were published as a repository together with the TEI schema on GitHub (Hannesschläger and Schopper + 2017), again under the same license. This allowed Martin Sievers, one of the + abstract authors, to immediately correct a typing error in his abstract that the editors + had overlooked (see history of Hannesschläger + and Schopper 2017 on GitHub).

But the story did not end there. The freely available and processable collection of abstracts inspired Peter Andorfer, a colleague of the editors at the Austrian Centre for Digital Humanities, to use this text collection to built an eXistdb-powered web - application (Andorfer and Hannesschläger - 2017). In the context of licensing issues, it is important to mention that + application (Andorfer and Hannesschläger + 2017). In the context of licensing issues, it is important to mention that Andorfer was never approached by the editors or explicitly asked to process the TEI files, and he only informed the editors about the web application that he was building when it was already available online (as a work in progress, but diff --git a/data/JTEI/12_2019-20/jtei-12-intro-source.xml b/data/JTEI/12_2019-20/jtei-12-intro-source.xml index d6d92f2..17e84f1 100644 --- a/data/JTEI/12_2019-20/jtei-12-intro-source.xml +++ b/data/JTEI/12_2019-20/jtei-12-intro-source.xml @@ -64,6 +64,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/12_2019-20/jtei-cc-pn-arneil-159-source.xml b/data/JTEI/12_2019-20/jtei-cc-pn-arneil-159-source.xml index 971c985..bffdd99 100644 --- a/data/JTEI/12_2019-20/jtei-cc-pn-arneil-159-source.xml +++ b/data/JTEI/12_2019-20/jtei-cc-pn-arneil-159-source.xml @@ -52,6 +52,19 @@

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+ + +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+ diff --git a/data/JTEI/12_2019-20/jtei-cc-pn-hechtl-166-source.xml b/data/JTEI/12_2019-20/jtei-cc-pn-hechtl-166-source.xml index 528bee7..978c83d 100644 --- a/data/JTEI/12_2019-20/jtei-cc-pn-hechtl-166-source.xml +++ b/data/JTEI/12_2019-20/jtei-cc-pn-hechtl-166-source.xml @@ -78,6 +78,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/12_2019-20/jtei-cc-ra-alles-169-source.xml b/data/JTEI/12_2019-20/jtei-cc-ra-alles-169-source.xml index 4dafe7b..4619888 100644 --- a/data/JTEI/12_2019-20/jtei-cc-ra-alles-169-source.xml +++ b/data/JTEI/12_2019-20/jtei-cc-ra-alles-169-source.xml @@ -66,6 +66,19 @@

TEI 2017 Conference Abstracts.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/12_2019-20/jtei-cc-ra-bauman-170-source.xml b/data/JTEI/12_2019-20/jtei-cc-ra-bauman-170-source.xml index e9be8fe..decf682 100644 --- a/data/JTEI/12_2019-20/jtei-cc-ra-bauman-170-source.xml +++ b/data/JTEI/12_2019-20/jtei-cc-ra-bauman-170-source.xml @@ -52,6 +52,19 @@

TEI 2017 Conference Abstracts.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -440,8 +453,8 @@ differentiate it from the main title. She plans to use TEI P5, so her first thought is Does the TEI title element have a type attribute? So she switches into oXygen, creates a new - tei_all document, puts her cursor immediately before the + target="#oxygen"/>oXygen, creates a + new tei_all document, puts her cursor immediately before the closing angle bracket of the title start-tag

The TAGC in SGML nomenclature.

and types a space. The result () immediately tells her that yes, the @@ -450,13 +463,13 @@ the TEI suggested values.
Choosing the type attribute from a - drop-down in oXygen + drop-down in oXygen
In this fictional—but completely believable—example the encoder - has used the schema (tei_all) through a tool (oXygen) as a - way of finding out about the markup language (TEI). Yes, she could just as - well have read the tei_all) through a tool (oXygen) as a way of finding out about the markup language + (TEI). Yes, she could just as well have read the documentation and obtained the same information, but she didn’t have to; she used the schema as an investigative tool to help her learn @@ -468,15 +481,16 @@ help us write our documents. Editing software can read the schema and restrict the markup or even text that can be entered based on the rules in the schema and the position of the cursor. demonstrates oXygen helping an encoder. Here oXygen is - not just answering a common question: is the TEI element for a notes - statement notesStmt or noteStmt? It is also requiring that - the user enter only one of three elements allowed by the schema (or a - comment, etc.).
+ type="crossref"/> demonstrates oXygen helping an encoder. Here oXygen is not just answering a common question: is the TEI + element for a notes statement notesStmt or noteStmt? It is + also requiring that the user enter only one of three elements allowed by the + schema (or a comment, etc.).
- Inserting an element in oXygen + Inserting an element in oXygen
By using an editor that understands the schema, an encoder can avoid making common mistakes (like misspelling an element name) at the time of the original encoding. This is extremely helpful in constraining one’s @@ -798,10 +812,10 @@

Either way, in order to avoid this potential maintenance nightmare, tei_customization.odd is not a static file, but rather is generated by running an XSLT program that reads as its input the - source to TEI P5

Remember, the TEI Guidelines are written in TEI. The - source to all of P5 is a single TEI document, although for convenience it is - split into well over 850 separate files.

and writes + type="soft.name" ref="#R2">XSLT program that reads as its input the source + to TEI P5

Remember, the TEI Guidelines are written in TEI. The source to + all of P5 is a single TEI document, although for convenience it is split + into well over 850 separate files.

and writes tei_customization.odd as its output. Running this program is one of the steps in the build process for creating a new set of TEI P5 generated outputs.

These outputs include schemas in RELAX NG and @@ -895,8 +909,8 @@ ref="#R3">XSLT program used to generate tei_customization.odd can be found in the TEI GitHub repository. It is currently called + type="software" xml:id="R4" target="#github"/>GitHub repository. It is currently called TEI-to-tei_customization.xslt. The generated tei_customization ODD file and the schemas generated from it can be found in each release of the TEI from 3.3.0 on.

For example, the @@ -907,14 +921,15 @@ target="http://www.tei-c.org/Vault/P5/3.3.0/xml/tei/custom/schema/relaxng/tei_customization.rnc" />.

Furthermore, the current version of tei_customization is available - from within oXygen as part of the TEI oXygen framework. However, the RELAX NG - schema (tei_customization.rng or tei_customization.rnc) has the behavior discussed - in . While this is not a bug or broken - in any way, it is likely to be confusing and problematic for most users of oXygen. - The TEI_Council is interested in finding a way around this difficulty.

+ from within oXygen as part of the TEI + oXygen framework. However, the RELAX NG schema (tei_customization.rng or + tei_customization.rnc) has the behavior discussed in . While this is not a bug or broken in any way, it is likely + to be confusing and problematic for most users of oXygen. The + TEI_Council is interested in finding a way around this difficulty.

@@ -1152,12 +1167,12 @@ customization that she has to do this. The consequences of failing to turn it off are severe, though: although completion pop-up boxes still work, validation (both automatic validation as you type and static validation, for example ⌘-⇧-V) completely - stops working. Furthermore, oXygen leaves this feature on by default for a reason. - Even though ID/IDREF checking itself is of almost no use to a user working with TEI - P5 documents,

Because P5 does not use the ID/IDREF mechanism, the only one of - the three added constraints that is useful is (2), that the value of - xml:id is unique. This can easily be tested by other means. For + stops working. Furthermore, oXygen leaves this feature on by default for a + reason. Even though ID/IDREF checking itself is of almost no use to a user working + with TEI P5 documents,

Because P5 does not use the ID/IDREF mechanism, the + only one of the three added constraints that is useful is (2), that the value + of xml:id is unique. This can easily be tested by other means. For proof-of-concept tests in Schematron, see Xmlid uniqueness.sch on the TEI wiki.

use of this @@ -1167,8 +1182,8 @@ several possible solutions to this problem, each of which has its drawbacks. The TEI Council will hopefully implement one of them soon, making use of tei_customization from the oXygen framework much less - problematic.

+ target="#teioxygenframework"/>oXygen + framework much less problematic.

diff --git a/data/JTEI/12_2019-20/jtei-cc-ra-burnard-149-source.xml b/data/JTEI/12_2019-20/jtei-cc-ra-burnard-149-source.xml index fd16c80..6b1be63 100644 --- a/data/JTEI/12_2019-20/jtei-cc-ra-burnard-149-source.xml +++ b/data/JTEI/12_2019-20/jtei-cc-ra-burnard-149-source.xml @@ -52,6 +52,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/12_2019-20/jtei-cc-ra-flanders-176-source.xml b/data/JTEI/12_2019-20/jtei-cc-ra-flanders-176-source.xml index 60de149..5bd9b90 100644 --- a/data/JTEI/12_2019-20/jtei-cc-ra-flanders-176-source.xml +++ b/data/JTEI/12_2019-20/jtei-cc-ra-flanders-176-source.xml @@ -119,6 +119,19 @@

TEI 2017 Conference Abstracts

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -146,51 +159,56 @@
-

This paper focuses on recent work by the TEI Archiving, Preservation, and Access Service +

This paper focuses on recent work by the TEI Archiving, Preservation, and Access Service (TAPAS) on pedagogy with TEI, and specifically on a recent initiative called - TAPAS Classroom focused on exploring pedagogical uses of TEI. We - provide some background on TAPAS, describe several case studies involving pedagogical - partners who used TAPAS in teaching, and finally describe the TAPAS Classroom initiative - and its outcomes.

+ TAPAS Classroom focused on exploring pedagogical uses of + TEI. We provide some background on TAPAS, describe several case studies involving + pedagogical partners who used TAPAS in teaching, and finally describe the TAPAS + Classroom initiative and its outcomes.

Introduction and Background

TAPAS

.

originated with the needs of - humanities scholars and specifically with the rise (in the first decade of the - twenty-first century) of scholarly interest in text encoding as a core humanities method. - With expertise supported by the proliferation of text encoding workshops aimed at - humanists, such scholars were typically not affiliated with large established projects but - were often working independently on small, monograph- or article-scale projects, such as - an edition of a single text, a small collection of manuscripts, or a small run of a local - periodical. As already noted in a previous article (Flanders and Hamlin 2013), infrastructure for TEI publication was at - that time (and still remains to some extent) challenging for individual scholars and small - projects, because of the costs and logistics of maintaining servers, developing and - supporting XSLT stylesheets, and maintaining technical expertise for - troubleshooting and longer term support. TAPAS was developed to provide an alternative in - the form of a web-based service for publishing TEI data. It offers a growing - infrastructure of TEI publishing tools, a publishing venue that highlights the value of - using TEI, and a long-term guarantee of visibility and access to the TEI data. TAPAS was - originally hosted at Brown University and is now hosted at Northeastern University, which - also provides a guarantee of long-term repository support for TAPAS data. TAPAS has been - generously funded by the TEI Consortium and by an initial planning grant from the - Institute for Museum and Library Services, a digital humanities startup grant from the - NEH, a research and development grant from the NEH, and most recently a digital humanities - advancement grant which has supported TAPAS Classroom.

+ target="#tapas"/>TAPAS

.

originated with the needs of humanities scholars and specifically + with the rise (in the first decade of the twenty-first century) of scholarly interest in + text encoding as a core humanities method. With expertise supported by the proliferation + of text encoding workshops aimed at humanists, such scholars were typically not affiliated + with large established projects but were often working independently on small, monograph- + or article-scale projects, such as an edition of a single text, a small collection of + manuscripts, or a small run of a local periodical. As already noted in a previous article + (Flanders and Hamlin 2013), infrastructure + for TEI publication was at that time (and still remains to some extent) challenging for + individual scholars and small projects, because of the costs and logistics of maintaining + servers, developing and supporting XSLT stylesheets, and maintaining technical expertise + for troubleshooting and longer term support. TAPAS was developed to provide an + alternative in the form of a web-based service for publishing TEI data. It offers a + growing infrastructure of TEI publishing tools, a publishing venue that highlights the + value of using TEI, and a long-term guarantee of visibility and access to the TEI data. + TAPAS was originally hosted at Brown University and is now hosted at Northeastern + University, which also provides a guarantee of long-term repository support for TAPAS + data. TAPAS has been generously funded by the TEI Consortium and by an initial planning + grant from the Institute for Museum and Library Services, a digital humanities startup + grant from the NEH, a research and development grant from the NEH, and most recently a + digital humanities advancement grant which has supported TAPAS Classroom.

- TAPAS Classroom and TEI Pedagogy + TAPAS Classroom and TEI Pedagogy

What do we envision when we think of TEI in the classroom? Three scenarios are particularly prominent. The first involves students contributing to TEI projects. Many faculty who lead TEI projects seek to involve students in @@ -245,33 +263,39 @@ Maybe Maybe - During the development of TAPAS Classroom, several scholars were already - experimenting with using TAPAS pedagogically. The following case studies describe how - these different scenarios played out in practice.

+ During the development of TAPAS Classroom, several scholars were already + experimenting with using TAPAS pedagogically. The following case studies + describe how these different scenarios played out in practice.

Scenario 1: A Course Designed Around Student Participation in a Faculty Research Project.

Karen Bourrier, Digital Dinah Craik ()

-

Karen Bourrier is a faculty member at the University of Calgary and has been using - TAPAS for her project, Digital Dinah Craik; a presentation at - TEI 2017 by her research assistant and project editor Kailey Fukushima described the - project’s work in detail. This project includes close to four hundred TEI files - organized into six distinct collections. The project team includes a rotating group of - undergraduate and graduate students who typically have no TEI experience when they start - work, and who transcribe, encode, and add enhanced markup to each text as it proceeds - through the project’s workflow. They are trained to encode in TEI/XML (using the Oxygen - XML editor) and to use TAPAS once a completed text is ready to publish. Professor - Bourrier’s pedagogical objectives for the course include professionalization of students - through involvement in long-term digital projects, and engaging students in - collaborative relationships with faculty and scholars in their field. (Kailey Fukushima - reported that TAPAS publication constituted a useful addition to students’ CVs.) - Practically speaking, because of the students’ lack of prior experience with TEI, it was - important to have easy-to-use tools so that students could focus on concepts and gain - fluency, thereby streamlining the process of training students to work on the - project.

-

Professor Bourrier’s pedagogical experimentation with TAPAS yielded several specific +

Karen Bourrier is a faculty member at the University of Calgary and has been using TAPAS for her project, Digital Dinah Craik; a + presentation at TEI 2017 by her research assistant and project editor Kailey Fukushima + described the project’s work in detail. This project includes close to four hundred TEI + files organized into six distinct collections. The project team includes a rotating + group of undergraduate and graduate students who typically have no TEI experience when + they start work, and who transcribe, encode, and add enhanced markup to each text as it + proceeds through the project’s workflow. They are trained to encode in TEI/XML (using + the Oxygen XML editor) and to use TAPAS once a completed text is ready to + publish. Professor Bourrier’s pedagogical objectives for the course include + professionalization of students through involvement in long-term digital projects, and + engaging students in collaborative relationships with faculty and scholars in their + field. (Kailey Fukushima reported that TAPAS publication constituted a useful addition + to students’ CVs.) Practically speaking, because of the students’ lack of prior + experience with TEI, it was important to have easy-to-use tools so that students could + focus on concepts and gain fluency, thereby streamlining the process of training + students to work on the project.

+

Professor Bourrier’s pedagogical experimentation with TAPAS yielded several specific design considerations. First, a close linkage between process and outcome is valuable in motivating students and focusing their effort, so a workflow that permits immediate publication (and in which the concept of publication and the @@ -292,15 +316,16 @@ target="http://www.tapasproject.org/dh-190-scholarly-text-encoding-w16"/> with schedule at )

Mackenzie Brooks is an assistant professor and digital humanities librarian at - Washington and Lee University, who used TAPAS in two iterations of a one-credit - lab course on scholarly text encoding with TEI, accompanying a - course in French literature taught by Professor Stephen P. McCormick. The course covered - the origins and theoretical orientations of text markup, document analysis, schema - creation, encoding, and publication, and also provided students with a grounding in the - technical skills necessary to create a digital edition as part of the work they were - doing in the accompanying literature class. Working in groups, students created simple - digital editions focused on a specific text drawn from the university’s rare book and - manuscript collection.

+ Washington and Lee University, who used TAPAS in two iterations of a + one-credit lab course on scholarly text encoding with TEI, + accompanying a course in French literature taught by Professor Stephen P. McCormick. The + course covered the origins and theoretical orientations of text markup, document + analysis, schema creation, encoding, and publication, and also provided students with a + grounding in the technical skills necessary to create a digital edition as part of the + work they were doing in the accompanying literature class. Working in groups, students + created simple digital editions focused on a specific text drawn from the university’s + rare book and manuscript collection.

As Brooks reported in a paper that described this course in detail (Brooks 2017), digital humanities at Washington and Lee University has a strongly pedagogical focus, and this course was an experimental @@ -308,10 +333,11 @@ look like. Framing the digital component as a one-credit lab course, taught by library faculty, offered a way to integrate digital approaches more flexibly into the curriculum without creating a burden for disciplinary faculty. In this - context, a platform like TAPAS enables the instructors to focus on the challenges of - teaching text encoding and to reduce the technical overhead for both students and - instructors so that questions relating to editorial theory and practice and literary - interpretation can come to the fore.

+ context, a platform like TAPAS enables the instructors to focus on the + challenges of teaching text encoding and to reduce the technical overhead for both + students and instructors so that questions relating to editorial theory and practice and + literary interpretation can come to the fore.

Constance Crompton and Michelle Levy, Simon Fraser University (Lyrical Ballads, ).

Connie Crompton is a faculty member at the University of Ottawa (at the time of the @@ -342,10 +368,11 @@

Mary Isbell is a faculty member at the University of New Haven, where she has been experimenting with building a program of digital humanities pedagogy using TEI. In spring 2016 she taught a course on Digital Editing, in which her ten undergraduate - students created individual digital TEI editions which were published in TAPAS as a - private collection visible only to members of the project. The course was aimed at - English majors with no encoding background, with a central learning goal of developing - students’ skill in XML and TEI. It also attracted students from History and + students created individual digital TEI editions which were published in TAPAS as a private collection visible only to members of the project. The course + was aimed at English majors with no encoding background, with a central learning goal of + developing students’ skill in XML and TEI. It also attracted students from History and Communications. Here, as with Brooks’s course described above, having students create individual editions of their own design was an important focus and was closely aligned with the technical and conceptual skill of modeling textual data through text encoding. @@ -356,10 +383,11 @@ 2017), and also serves to empower students as both tool-users and creators of cultural meaning. Isbell noted that the ability to see their work realized as a readable edition was a crucial motivator for students in pushing through the process of learning - and debugging their TEI/XML encoding. Because TAPAS was in beta when Isbell ran the - course, she resourcefully integrated bug discovery and reporting explicitly into the - course, so that students had some exposure to the processes of digital humanities tool - development and had a sense of participation in that process—an unintended but very + and debugging their TEI/XML encoding. Because TAPAS was in beta when Isbell + ran the course, she resourcefully integrated bug discovery and reporting explicitly into + the course, so that students had some exposure to the processes of digital humanities + tool development and had a sense of participation in that process—an unintended but very positive outcome.

@@ -373,35 +401,44 @@ thesis project undertaken by Doyle Calhoun with support from Anna Kijas, the Senior Digital Scholarship Librarian at Boston College. For this project, Calhoun encoded a proof-of-concept segment of a nineteenth-century dictionary, together with - proof-of-concept authority lists for persons, organizations, and historical places. - TAPAS served as the data repository for the encoded files, which were also published - through a project web site that included an interactive map using CartoDB.

For a - more detailed account of the project, see Kijas - (2016).

In addition to the outcomes for Calhoun’s own degree - program and professional development, Kijas had some larger pedagogical objectives from - the perspective of her digital humanities center: to involve non-faculty (library and DH - center staff) in student teaching and student research, at both undergraduate and - graduate level, and to introduce and support TEI as part of an institution-level - initiative.

-

Although supporting student-led research was not on the TAPAS project’s radar as a very - likely usage scenario during the initial planning and design process for TAPAS - Classroom, it is an important outcome that underscores the potential benefits of having - access to TAPAS at the institutional level (i.e., as a benefit of TEI institutional - membership). From the perspective of the library, one important feature of the TAPAS - service is that it provides a low-cost but durable infrastructure easy for novices to - master. From the perspective of the student researcher, the important features are the - longevity and stability of the data (enabling continuity of the project through - successive institutional moves) as well as ease of use.

+ proof-of-concept authority lists for persons, organizations, and historical places. TAPAS served as the data repository for the encoded files, which were also + published through a project web site that included an interactive map using CartoDB.

For a more detailed account of the project, see Kijas (2016).

In addition to the + outcomes for Calhoun’s own degree program and professional development, Kijas had some + larger pedagogical objectives from the perspective of her digital humanities center: to + involve non-faculty (library and DH center staff) in student teaching and student + research, at both undergraduate and graduate level, and to introduce and support TEI as + part of an institution-level initiative.

+

Although supporting student-led research was not on the TAPAS project’s + radar as a very likely usage scenario during the initial planning and design process for + TAPAS Classroom, it is an important outcome that underscores the potential + benefits of having access to TAPAS at the institutional level (i.e., as a benefit + of TEI institutional membership). From the perspective of the library, one important + feature of the TAPAS service is that it provides a low-cost but durable + infrastructure easy for novices to master. From the perspective of the student + researcher, the important features are the longevity and stability of the data (enabling + continuity of the project through successive institutional moves) as well as ease of + use.

Goals and Desiderata -

Based on these experiments, the TAPAS development team set several important design goals - for the TAPAS Classroom project, in supporting pedagogy with TEI: +

Based on these experiments, the TAPAS development team set several important design + goals for the TAPAS Classroom project, in supporting pedagogy with TEI: Make the process easier: For faculty who teach with TEI (either for its own sake or as part of a larger course in digital humanities or humanities), some - supporting infrastructure is needed. TAPAS can ideally streamline or eliminate the + supporting infrastructure is needed. TAPAS can ideally streamline or eliminate the process of getting access to shared server space, setting up student accounts, and ensuring that data is stored safely and can be accessed after the course is over. These functions are valuable for instructors at all levels of technical expertise but @@ -414,66 +451,79 @@ suggested the value of a publication system that makes it possible to see the publication apparatus as such, and to look under the surface: for instance by offering different stylesheets and viewing options and showing that the formatted display of - TEI is independent of the underlying encoding. TAPAS can offer a multiplicity of - viewing options and an interface that makes it easy to move between them, enabling + TEI is independent of the underlying encoding. TAPAS can offer a multiplicity + of viewing options and an interface that makes it easy to move between them, enabling students to make direct comparisons between different ways of handling the data and offering a clear causal view in which changes to the data have a visible effect on the output (thereby motivating students to experiment with the markup in greater detail). - Support the encoding: In these scenarios, TAPAS was used as an - end-point and a publication venue, but it is clear that there is pedagogical value in - user-friendly TEI tools earlier in the classroom narrative as well. Mary Isbell, for - instance, noted the potential value of student-level error messages, and Karen + Support the encoding: In these scenarios, TAPAS was used as + an end-point and a publication venue, but it is clear that there is pedagogical value + in user-friendly TEI tools earlier in the classroom narrative as well. Mary Isbell, + for instance, noted the potential value of student-level error messages, and Karen Bourrier observed how students learned from their encounter with the workflow - management aspects of TAPAS. Through user-friendly validation, interactive ways to - inspect the TEI encoding, and other ways for students to explore their encoding in - progress from many perspectives, TAPAS has potential value as a source of approachable - information that can inform the encoding process. - Under TAPAS Classroom, several major new pieces of TAPAS were developed that - respond to these desiderata. First, we developed new stylesheets for viewing TEI files, - aimed specifically at pedagogical uses; this grant also gave us an opportunity to develop - a fully modular system for managing these view packages (about which - more below). Second, we re-examined the ways in which validation functions in TAPAS, and - began developing tools that present validation to students in a specifically pedagogical - context rather than as part of TAPAS’s own data management systems. Third, we developed a - set of sample and template files to serve as starting points for students, recognizing - that in short courses where the goal is to get students quickly oriented in a new skill - (as for instance in the Crompton example described above), it could be helpful to have - some pre-established starting points that are well contextualized and self-explanatory. - And finally, we developed a community workshops space within TAPAS - that simplifies the process of setting up a teaching environment, aimed particularly at - instructors teaching shorter workshops that may be repeated over time. In what follows, we - focus on two components in particular: the view packages and our initial forays into - thinking about validation.

+ management aspects of TAPAS. Through user-friendly validation, + interactive ways to inspect the TEI encoding, and other ways for students to explore + their encoding in progress from many perspectives, TAPAS has potential value as a + source of approachable information that can inform the encoding process. + Under TAPAS Classroom, several major new pieces of TAPAS were developed + that respond to these desiderata. First, we developed new stylesheets for viewing TEI + files, aimed specifically at pedagogical uses; this grant also gave us an opportunity to + develop a fully modular system for managing these view packages + (about which more below). Second, we re-examined the ways in which validation functions in + TAPAS, and began developing tools that present validation to students in a + specifically pedagogical context rather than as part of TAPAS’s own data management + systems. Third, we developed a set of sample and template files to serve as starting + points for students, recognizing that in short courses where the goal is to get students + quickly oriented in a new skill (as for instance in the Crompton example described above), + it could be helpful to have some pre-established starting points that are well + contextualized and self-explanatory. And finally, we developed a community + workshops space within TAPAS that simplifies the process of setting up a + teaching environment, aimed particularly at instructors teaching shorter workshops that + may be repeated over time. In what follows, we focus on two components in particular: the + view packages and our initial forays into thinking about validation.

View Packages -

The display of TEI files through the TAPAS interface is handled—as with almost all modern - web display of TEI data—through XSLT stylesheets, and indeed one of TAPAS’s most - important functions is to enable users to transform and view their TEI data without having - to write or run XSLT on their own. TAPAS’s XSLT stylesheets do not operate in - isolation but as part of a more complex view package that includes - several distinct components: - One or more XSLT stylesheets which transform the source TEI - data into another format (typically XHTML but potentially JSON or other formats that - are particularly suited to some viewing application) +

The display of TEI files through the TAPAS interface is handled—as with almost all + modern web display of TEI data—through XSLT stylesheets, and indeed one of TAPAS’s most important functions is to enable users to transform and view their TEI + data without having to write or run XSLT on their own. TAPAS’s XSLT stylesheets do + not operate in isolation but as part of a more complex view package + that includes several distinct components: + One or more XSLT stylesheets which transform the source TEI data into another + format (typically XHTML but potentially JSON or other formats that are particularly + suited to some viewing application) A CSS stylesheet that provides styling information Optional JavaScript code to produce features of user interactivity (such as mouse-overs or selection of specific viewing options) - Optional XProc code which handles the sequential processing of the data by the - individual components of the view package + Optional XProc code which handles the sequential processing of the data by + the individual components of the view package Optional RELAX NG or ISO Schematron files that formalize any specific data constraints required by the view package (for instance, a view package for displaying a bibliography might include a test to ascertain that the file contains a listBibl) - Metadata about the view package that supports its use within the TAPAS - system + Metadata about the view package that supports its use within the TAPAS system Supporting documentation of the view package, including a manifest that describes its components and the expectations concerning the kinds of data for which it is best suited @@ -482,45 +532,56 @@ that are appropriate for that scenario. For instance, a view package might focus on the display of heavily revised manuscripts and might offer readers the ability to view successive revision stages or choose which revisers’ work to make visible. (This interface - is not currently available in TAPAS but would be a great future project.) In this way, - view packages serve as reading environments rather than as individual stylesheets, and - they enable TAPAS to group together multiple viewing options that complement one another - within a specific usage scenario, such as the ability to alternate between a normalized - and a diplomatic view of a manuscript source. All view packages are maintained on GitHub, - and a future goal for TAPAS is to use GitHub as a collaborative tool—enabling community - members to propose and develop new view packages for inclusion in TAPAS.

-

From the user perspective, TAPAS contributors can specify a default view package for a - given record or collection, so that when a reader visits that material their initial view - of the TEI data reflects the contributor’s choice. For instance, the creator of a + is not currently available in TAPAS but would be a great future project.) In this + way, view packages serve as reading environments rather than as individual stylesheets, + and they enable TAPAS to group together multiple viewing options that complement one + another within a specific usage scenario, such as the ability to alternate between a + normalized and a diplomatic view of a manuscript source. All view packages are maintained + on GitHub, and a future goal for TAPAS is to use GitHub as a collaborative + tool—enabling community members to propose and develop new view packages for inclusion in + TAPAS.

+

From the user perspective, TAPAS contributors can specify a default view package + for a given record or collection, so that when a reader visits that material their initial + view of the TEI data reflects the contributor’s choice. For instance, the creator of a collection of historic letters (such as the <ref target="https://digitalmitford.org/">Digital Mitford</ref> project) might choose a view package that handles manuscript features well, while the creator of a teaching collection aimed at sparking discussion of XML visualization might instead choose the Hieractivity view package (described below) as the default. However, whatever the - default setting is, TAPAS readers can select any view package option in the reading - interface (even if it goes against the grain of the data), and this may offer readers - additional insight into the TEI data that is shared via TAPAS.

+ default setting is, TAPAS readers can select any view package option in the + reading interface (even if it goes against the grain of the data), and this may offer + readers additional insight into the TEI data that is shared via TAPAS.

- TAPAS Generic View Package -

The basic goal of the TAPAS Generic view package is to handle almost any TEI markup in - a moderately functional way. It is not intended as a high-function or specialized - display; the term generic signals the fact that it displays TEI - data in a general-purpose manner and can serve as the default stylesheet for almost any - kind of data for which no more specialized viewing option has been provided. It offers a - good basic reading interface, with a table of contents for navigation and the ability to - shift between diplomatic and normalized views. For pedagogical purposes, it has the - virtue that it is very forgiving: it does not require or assume adherence to any - specific TEI schema or encoding protocol, and it produces a visible outcome from a wide - variety of encoding features (so that any class involving TEI is likely to generate - something that will get results). Its display options give emphasis to the areas of TEI - encoding that see most frequent pedagogical use: personography and contextual - information, transcription of primary source documents, and basic display of prose - narratives such as fiction, life writing, and letters. It also supports renditional - encoding (on rend or style) so that student encoders can exert - some influence on the output. Instructors have also noted that it works well as a - proofreading display to reveal both encoding errors and transcription errors.

+ TAPAS Generic View Package +

The basic goal of the TAPAS Generic view package is to handle almost any + TEI markup in a moderately functional way. It is not intended as a high-function or + specialized display; the term generic signals the fact that it + displays TEI data in a general-purpose manner and can serve as the default stylesheet + for almost any kind of data for which no more specialized viewing option has been + provided. It offers a good basic reading interface, with a table of contents for + navigation and the ability to shift between diplomatic and normalized views. For + pedagogical purposes, it has the virtue that it is very forgiving: it does not require + or assume adherence to any specific TEI schema or encoding protocol, and it produces a + visible outcome from a wide variety of encoding features (so that any class involving + TEI is likely to generate something that will get results). Its display options give + emphasis to the areas of TEI encoding that see most frequent pedagogical use: + personography and contextual information, transcription of primary source documents, and + basic display of prose narratives such as fiction, life writing, and letters. It also + supports renditional encoding (on rend or style) so that student + encoders can exert some influence on the output. Instructors have also noted that it + works well as a proofreading display to reveal both encoding errors and transcription + errors.

Hieractivity View Package @@ -547,50 +608,63 @@
Other View Packages -

TAPAS currently also offers two other view packages: an XML view package which shows - the XML code and a view that uses the open-source TEI Boilerplate +

TAPAS currently also offers two other view packages: an XML view package which + shows the XML code and a view that uses the open-source TEI Boilerplate stylesheets.

TEI Boilerplate: . See Walsh and Simpson (2013).

The XML - view is not remarkable in itself, but it is pedagogically useful within the overall - ecology of the view packages because it allows students to see the direct connection - between the markup and the different outcomes in the other view packages. It is also - helpful for troubleshooting and for comparing results with other students. The TEI - Boilerplate view package was originally included because it offered an easy-to-install - viewing option early in the TAPAS development process, but it has shown its value in - other ways as well: it offers several proof-of-concept viewing options that help - demonstrate the versatility of display through simple changes in CSS, and in the future - it might offer a way for TAPAS to accommodate user-contributed CSS and control over - document display by that means. It also connects TAPAS to other strands of research and - development for TEI publication.

+ target="http://dcl.ils.indiana.edu/teibp/index.html"/>. See Walsh and + Simpson (2013).

The XML view is not remarkable in itself, + but it is pedagogically useful within the overall ecology of the view packages because + it allows students to see the direct connection between the markup and the different + outcomes in the other view packages. It is also helpful for troubleshooting and for + comparing results with other students. The TEI Boilerplate view + package was originally included because it offered an easy-to-install viewing option + early in the TAPAS development process, but it has shown its value in other ways as + well: it offers several proof-of-concept viewing options that help demonstrate the + versatility of display through simple changes in CSS, and in the future it might offer a + way for TAPAS to accommodate user-contributed CSS and control over document + display by that means. It also connects TAPAS to other strands of + research and development for TEI publication.

Validation -

Validation was a key outcome for TAPAS Classroom and proved more challenging than we - anticipated, for reasons that have to do with the way TAPAS data is ingested into the - Fedora repository component and how it is handled once ingested. There are three basic - functions validation can potentially play in TAPAS: +

Validation was a key outcome for TAPAS Classroom and proved more challenging than we + anticipated, for reasons that have to do with the way TAPAS data is ingested into the + Fedora repository component and how it is handled once ingested. There are three + basic functions validation can potentially play in TAPAS: To test files upon ingestion to ensure they are XML documents, and specifically, - TEI; this is a gatekeeping function with a simple yes or no answer. TAPAS currently - uses validation in this way. - To provide users with a more detailed profile of their data once it gets into - TAPAS. This function would go beyond the simple gatekeeping function to give users - information about where their TEI data matches or fails to match a given schema. The - first step in this detailed profiling would be to provide a more detailed validation - report based on validation against the TAPAS schema (currently - tei_all), but a further (and extremely valuable) step would be to + TEI; this is a gatekeeping function with a simple yes or no answer. TAPAS currently uses validation in this way. + To provide users with a more detailed profile of their data once it gets into TAPAS. This function would go beyond the simple gatekeeping function to give + users information about where their TEI data matches or fails to match a given schema. + The first step in this detailed profiling would be to provide a more detailed + validation report based on validation against the TAPAS schema (currently + tei_all), but a further (and extremely valuable) step would be to support this with more detailed validation reporting against user-supplied schemas. - TAPAS is currently developing a validation reporting feature, described in more detail - below. + TAPAS is currently developing a validation reporting feature, described in + more detail below. To test a given file or set of files against a specific functional scenario. For - instance, in the context of TAPAS view packages, validation could be used to discover - and report on whether a given TEI file will work appropriately within a given view - package, and if not, what is missing from the encoding. + instance, in the context of TAPAS view packages, validation could be used to + discover and report on whether a given TEI file will work appropriately within a given + view package, and if not, what is missing from the encoding. For pedagogical purposes, validation serves a very specific set of needs. First, it can give students information about their own encoding (for example in the context of an assignment prompt) and can reinforce what students are learning about TEI by providing @@ -605,26 +679,28 @@ settings, the schema may be accorded the status of a standard to be achieved, while in others it may function in more complex and dialogic ways as a hypothesis about texts to be tested and revised.

-

To support these pedagogical functions, TAPAS plans to treat validation in a somewhat +

To support these pedagogical functions, TAPAS plans to treat validation in a somewhat novel way, using the view package technology to situate validation as a view of the document itself through the lens of a schema. Technically, the process involves: - running a validation process in XProc + running a validation process in XProc running an XSLT stylesheet that integrates the validation output with the TEI document running an XSLT stylesheet that transforms the whole thing into HTML for display (with JavaScript as needed to support interaction - such as navigation between the error report and the document itself). + type="soft.name" ref="#R79">JavaScript as needed to support interaction such as + navigation between the error report and the document itself). Along the way, the process substitutes error messages that are more intelligible to novices and also more reassuring and detailed, and collapses multiple occurrences of a given error message into a single instance. The result is to position the validation view less as an authoritative and fearsome report of failure and more as an informational report that describes the relationship between the document and the schema that has been - invoked. An initial version of the validation view package was developed for TAPAS + invoked. An initial version of the validation view package was developed for TAPAS Classroom and is scheduled for release in 2020.

@@ -633,16 +709,20 @@ TEI plays in a particular classroom setting. In some cases, the goal may be to learn TEI and to excite students about its potential as a digital humanities tool. In other cases, the goal may be to use TEI as a way of framing a conversation about digital editing, data - modeling, or data visualization. TAPAS (and the features developed through the TAPAS + modeling, or data visualization. TAPAS (and the features developed through the TAPAS Classroom project) offers a platform for TEI display and publication that allows the complexities of TEI encoding to take a back seat—through encoding templates and a simple upload and publication workflow—in cases where expertise in TEI is not the main goal of the class. But at the same time, it offers the ability to look beneath the surface of those systems at any time, to gain greater insight into the encoding, and to explore what - happens if the code or the display choices are changed. TAPAS also supports varied roles + happens if the code or the display choices are changed. TAPAS also supports varied roles for students that give them different forms of scaffolded authority: as contributors to real-world publications, as creators of their own projects, as collaborators and - experimenters in public spaces. TAPAS thus supports a vision of digital humanities + experimenters in public spaces. TAPAS thus supports a vision of digital humanities pedagogy that is experiential, experimental, and collaborative.

@@ -655,14 +735,14 @@ 24: 467–481. ; . - Flanders, Julia, and Scott - Hamlin. 2013. <rs type="soft.name" ref="#R86">TAPAS</rs>: Building a TEI Publishing - and Repository Service. Journal of the Text Encoding - Initiative - 5. ; DOI: 10.4000/jtei.788. + Flanders, Julia, and Scott + Hamlin. 2013. <rs type="soft.name" ref="#R86" + >TAPAS</rs>: Building a TEI Publishing and Repository Service. Journal of the Text Encoding Initiative + 5. ; DOI: 10.4000/jtei.788. Hswe, Patricia, et al. 2017. A Tale of Two Internships: Developing Digital Skills Through Engaged Scholarship. Digital Humanities Quarterly @@ -673,13 +753,14 @@ travaux linguistiques des missionnaires. Boston College Libraries Newsletter. . - - Walsh, John, and Grant Leyton - Simpson. 2013. <rs type="soft.name" ref="#R85">TEI Boilerplate</rs>. Journal of Digital Humanities - 2 (3). . + + Walsh, John, and Grant Leyton + Simpson. 2013. <rs type="soft.name" + ref="#R85">TEI Boilerplate</rs>. Journal of Digital + Humanities + 2 (3). . diff --git a/data/JTEI/12_2019-20/jtei-cc-ra-fukushima-162-source.xml b/data/JTEI/12_2019-20/jtei-cc-ra-fukushima-162-source.xml index a823217..5482650 100644 --- a/data/JTEI/12_2019-20/jtei-cc-ra-fukushima-162-source.xml +++ b/data/JTEI/12_2019-20/jtei-cc-ra-fukushima-162-source.xml @@ -73,6 +73,19 @@

TEI 2017 Conference Abstracts.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/12_2019-20/jtei-cc-ra-kaethler-168-source.xml b/data/JTEI/12_2019-20/jtei-cc-ra-kaethler-168-source.xml index d73911d..17a7032 100644 --- a/data/JTEI/12_2019-20/jtei-cc-ra-kaethler-168-source.xml +++ b/data/JTEI/12_2019-20/jtei-cc-ra-kaethler-168-source.xml @@ -55,6 +55,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/12_2019-20/jtei-cc-ra-scholger-173-source.xml b/data/JTEI/12_2019-20/jtei-cc-ra-scholger-173-source.xml index ed16087..c0ab731 100644 --- a/data/JTEI/12_2019-20/jtei-cc-ra-scholger-173-source.xml +++ b/data/JTEI/12_2019-20/jtei-cc-ra-scholger-173-source.xml @@ -56,6 +56,19 @@

TEI 2017 Conference Abstracts.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/12_2019-20/jtei-kokaze-177-source.xml b/data/JTEI/12_2019-20/jtei-kokaze-177-source.xml index 71c51fa..1b7ff93 100644 --- a/data/JTEI/12_2019-20/jtei-kokaze-177-source.xml +++ b/data/JTEI/12_2019-20/jtei-kokaze-177-source.xml @@ -134,6 +134,19 @@

TEI 2017 Conference Abstracts.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/12_2019-20/jtei-mholmes-158-source.xml b/data/JTEI/12_2019-20/jtei-mholmes-158-source.xml index 00c4499..9dcc9c1 100644 --- a/data/JTEI/12_2019-20/jtei-mholmes-158-source.xml +++ b/data/JTEI/12_2019-20/jtei-mholmes-158-source.xml @@ -49,6 +49,19 @@

TEI 2017 Conference Abstracts

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/13_2020-22/jtei-cc-pn-kuhry-188-source.xml b/data/JTEI/13_2020-22/jtei-cc-pn-kuhry-188-source.xml index 37d3ffd..52ba5f2 100644 --- a/data/JTEI/13_2020-22/jtei-cc-pn-kuhry-188-source.xml +++ b/data/JTEI/13_2020-22/jtei-cc-pn-kuhry-188-source.xml @@ -48,6 +48,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -374,46 +387,53 @@ the apparatus, ability to display different versions of the work-in-progress edition (corresponding to the text of different manuscripts), and handling of editions encoded with rdg or lem elements in the apparatus. Those needs are met by the - TEI Critical Apparatus Toolbox, which she created.Marjorie - Burkhart et al., TEI Critical Apparatus Toolbox, - accessed June 3, 2021, . I - would add another prior and very basic need: finding help to encode the edition. Indeed, - the task of encoding is described as the main difficulty confronted by TEI users, partly - because of the lack of user-friendly tools (Burghart and Rehbein 2012). One can find tools to annotate images and - transcribe sources,Such tools include Transkribus (from READ-COOP SCE, accessed - June 3, 2021, ) and Archetype - (previously called the DigiPal framework, now supported by King’s Digital Laboratory, - King’s College London, accessed June 3, 2021, ). but these tools do not enable the scholar to encode variants and the - critical apparatus as specified in the TEI Guidelines. They are therefore purely - document-centered tools, and we have seen above (see ) that there is a general demand for text-oriented digital scholarly - editions designed to be critical. Collation of several manuscripts can also produce an - automatically encoded critical apparatus using the TEI parallel segmentation method, by - means of CollateX or Juxta software, provided one already has the separate - transcriptions at one’s disposal.Interedition Development Group, CollateX – - Software for Collating Textual Sources, accessed June 4, 2021, . For a history of collation tools and especially of - the developments leading to CollateX, see Nury and Spadini (2020). Juxta is no longer maintained; it has been replaced by two - programs both developed by Performant Software Solutions: Faircopy (accessed June 4, - 2021, ), a transcription interface - producing TEI encoding, and TextLab (accessed June 4, 2021, ), which seems to be more focused on genetic - editing. However, a legacy version of Juxta, accessed June 4, 2021, can be found at - . Roeder (TEI + Critical Apparatus Toolbox, which she created.Marjorie Burkhart et al., TEI Critical Apparatus Toolbox, accessed June 3, 2021, . I would add another prior and + very basic need: finding help to encode the edition. Indeed, the task of encoding is + described as the main difficulty confronted by TEI users, partly because of the lack of + user-friendly tools (Burghart and Rehbein + 2012). One can find tools to annotate images and transcribe sources,Such + tools include Transkribus (from READ-COOP SCE, accessed June 3, 2021, ) and Archetype + (previously called the DigiPal framework, now supported by King’s Digital Laboratory, King’s College London, + accessed June 3, 2021, ). but these tools do not enable the + scholar to encode variants and the critical apparatus as specified in the TEI + Guidelines. They are therefore purely document-centered tools, and we have seen above + (see ) that there is a general demand for + text-oriented digital scholarly editions designed to be critical. Collation of several + manuscripts can also produce an automatically encoded critical apparatus using the TEI + parallel segmentation method, by means of CollateX or Juxta software, provided one already has the separate transcriptions at one’s + disposal.Interedition Development Group, + CollateX – Software for Collating Textual Sources, accessed June 4, 2021, . For a history + of collation tools and especially of the developments leading to CollateX, see + Nury and Spadini (2020). Juxta is no + longer maintained; it has been replaced by two programs both developed by Performant Software Solutions: Faircopy (accessed June 4, 2021, ), a transcription interface producing + TEI encoding, and TextLab (accessed June 4, 2021, ), which seems to be more + focused on genetic editing. However, a legacy version of Juxta, accessed + June 4, 2021, can be found at . Roeder (2020) provides a survey of three web-based tools offering automated collation. As such, the result is not a proper critical edition, as no selection of variants has been made to produce a critical text @@ -425,26 +445,29 @@ encoding. So the second part of the project consists in creating a panel of tools for the encoding of ancient textual sources in TEI XML. These tools will enhance existing software, and not create it from scratch.

-

The tools include XSLT stylesheets that convert styled Word or - LibreOffice documents to TEI XML.Sample transformations can already be made using - OxGarage (accessed June 4, 2021, ), and - XSLT stylesheets can be found in the TEI Consortium’s GitHub repository, - accessed June 4, 2021,. - Pre-encoding a text in a word processor can be useful, but frequently a deeper level of - encoding is needed, which is difficult to reach working only on the text document. So a - second category of tools is a series of frameworks or encoding environments made through - customization of two widely used XML editors: - XMLmind XML Editor - (XXE),Accessed June 4, 2021, . Customization of this editor is a - central part of the work of the Document numérique team of Maison de la Recherche - en Sciences Humaines (MRSH) de Caen (see the Métopes workflow, accessed August 14, - 2021, ). The tools include XSLT stylesheets that convert styled Word or LibreOffice documents to + TEI XML.Sample transformations can already be made using OxGarage + (accessed June 4, 2021, ), and XSLT stylesheets can + be found in the TEI Consortium’s GitHub repository, accessed June 4, 2021,. Pre-encoding a text in + a word processor can be useful, but frequently a deeper level of encoding is needed, + which is difficult to reach working only on the text document. So a second category of + tools is a series of frameworks or encoding environments made through customization of + two widely used XML editors: + XMLmind XML + Editor (XXE),Accessed June 4, 2021, . + Customization of this editor is a central part of the work of the Document + numérique team of Maison de la Recherche en Sciences Humaines (MRSH) de Caen (see + the Métopes workflow, accessed August 14, 2021, ). XMLmind XML Editor was used in the team’s collaboration with the Biblissima Equipex (Equipment of Excellence project funded by the French National Research Agency – ANR), for which @@ -457,21 +480,23 @@ stylesheets, and to automate and speed up the encoding tasks with custom commands. Oxygen XML Editor,Accessed - June 4, 2021, . which supports - right-to-left scripts, unlike the current version of XXE (however, recent steps have - been made in this direction by the developers of XXE). A framework similar to XXE’s - was developed for Oxygen’s Author mode, to be used by projects focusing on Hebrew or + target="#oxygen"/>Oxygen XML + Editor,Accessed June 4, 2021, . which supports + right-to-left scripts, unlike the current version of XXE (however, + recent steps have been made in this direction by the developers of XXE). A framework similar to XXE’s was developed for + Oxygen’s Author mode, to be used by projects focusing on Hebrew or Arabic sources.Since version 15.1, Oxygen has handled RTL scripts quite - effectively in author mode (but not text mode). See discussions about this issue - on the Epidoc and TEI listservs: Hugh Cayless, RTL texts, MARKUP mailing list archives, February 13, - 2020, Oxygen has handled RTL + scripts quite effectively in author mode (but not text mode). See discussions + about this issue on the Epidoc and TEI listservs: Hugh + Cayless, RTL texts, MARKUP mailing list + archives, February 13, 2020, , and David J. Birnbaum, Editing Arabic TEI, TEI-L mailing list archives, February 2, 2017, Oxygen or to - the tree view in Oxygen or to the tree view in XXE.

@@ -525,19 +550,21 @@ In the encodingDesc element of the teiHeader, defining a list of values for the place attribute of the note - element (Oxygen framework). + element (Oxygen framework).

-

In the Oxygen framework, inside the text element, the insertion of tags for - which the typology of attribute values has been described in the teiHeader (and - registered as available in drop-down menus) generates a drop-down menu listing these - values, thanks to the use of XPath.

+

In the Oxygen framework, inside the text element, the insertion of + tags for which the typology of attribute values has been described in the + teiHeader (and registered as available in drop-down menus) generates a + drop-down menu listing these values, thanks to the use of XPath.

In the corpus, choosing one of the defined values for the - place attribute of the note element (Oxygen framework). + place attribute of the note element (Oxygen + framework).

The same principle is used for references to witnesses in the critical apparatus, by @@ -555,29 +582,31 @@

The challenge in developing encoding frameworks is not so much technical, as they use features available in each application. Frameworks consist of command configuration and CSS files, sometimes XSLT files. They provide an economic, versatile way - to provide scholars with customized tools for digital scholarly editing.The - Ediarum framework for Oxygen has been developed at the Berlin-Brandenburg Academy of - Sciences and Humanities to help scholars create digital editions of historical - documents in TEI XML. However, this framework does not enable one to encode variant - readings and is therefore not designed for critical editing of medieval sources. See - Mertgens (2019) and the Ediarum website: - . - The Caen team Pôle Document numérique has since published a framework for critical - editing in TEI Parallel Segmentation based on XMLmind XML Editor software: see Éditer des sources avec apparat critique, accessed June 4, 2021, - . The challenge is rather about ontology and modeling.I am taking part - in a collective effort between scholarly editors and scientific publishing services - (in collaboration with IRHT’s publication team, the Caen team, and Ecole nationale des - Chartes) to collect and analyze editorial and encoding practices when it comes to - ancient sources, in order to model a common core of editorial features and to make - encoding and publishing tools more interoperable and complementary.

+ type="soft.name" ref="#R3">XSLT files. They provide an economic, versatile way to + provide scholars with customized tools for digital scholarly editing.The Ediarum framework for Oxygen has been developed at the Berlin-Brandenburg Academy of Sciences and Humanities to help + scholars create digital editions of historical documents in TEI XML. However, this + framework does not enable one to encode variant readings and is therefore not designed + for critical editing of medieval sources. See Mertgens (2019) and the Ediarum website: . The Caen team Pôle Document numérique has since published a framework for critical editing in TEI Parallel Segmentation based on + XMLmind XML Editor software: see Éditer des sources avec + apparat critique, accessed June 4, 2021, . The challenge is rather about ontology and modeling.I am + taking part in a collective effort between scholarly editors and scientific publishing + services (in collaboration with IRHT’s publication team, the Caen team, and Ecole + nationale des Chartes) to collect and analyze editorial and encoding practices when it + comes to ancient sources, in order to model a common core of editorial features and to + make encoding and publishing tools more interoperable and complementary.

Among the difficulties or constraints are thus:

the need to offer tools specialized enough to fill the particular needs of each @@ -611,12 +640,13 @@ whether in print or in digital form, can be supported by existing tools which the scholar can configure.See, for example, the Print an edition tool in the TEI Critical Apparatus Toolbox by M. Burghart, - in which the sample XSLT stylesheet to transform TEI XML into - LaTeX, to produce a printable PDF with a traditional critical apparatus, can be - downloaded and modified: . - Burghart (2016) provides a survey of + target="#teicat"/>TEI Critical Apparatus + Toolbox by M. Burghart, in which the sample XSLT + stylesheet to transform TEI XML into LaTeX, to produce a printable PDF with a + traditional critical apparatus, can be downloaded and modified: . Burghart (2016) provides a survey of transformation and display tools for scholarly editions encoded with TEI. TEI Publisher () and the Max display engine ( The working interface of the XMLmind framework. The central pane - shows the CSS-customized view of the file containing the central text. The left pane - shows the—almost—raw code of the same file. The + command designed in - the CSS to be available on the lemma (element term type="lemme") opens a - transformed version of the glosses’ thesaurus and allows one to choose the - appropriate gloss archetype toward which the target attribute must point - (XMLmind framework. The + central pane shows the CSS-customized view of the file containing the central text. + The left pane shows the—almost—raw code of the same file. The + + command designed in the CSS to be available on the lemma (element term + type="lemme") opens a transformed version of the glosses’ thesaurus and + allows one to choose the appropriate gloss archetype toward which the + target attribute must point (XMLmind framework).

@@ -742,8 +772,9 @@
- Display of the glosses’ thesaurus (XMLmind framework). + Display of the glosses’ thesaurus (XMLmind + framework).
lem elements are not used because there is no putative original text. @@ -769,10 +800,10 @@
Display Possibilities

A publication prototype has been created using XSLT stylesheets and Javascript - to produce interactive HTML pages. The current version allows one to + target="#xslt"/>XSLT stylesheets and Javascript to produce interactive HTML pages. The current version allows one to + read the reconstructed text of each manuscript; open each gloss in a pop-up with a click on the lemma (each pop-up can be moved where one likes); diff --git a/data/JTEI/13_2020-22/jtei-cc-ra-barney-187-source.xml b/data/JTEI/13_2020-22/jtei-cc-ra-barney-187-source.xml index e339a1c..21dafba 100644 --- a/data/JTEI/13_2020-22/jtei-cc-ra-barney-187-source.xml +++ b/data/JTEI/13_2020-22/jtei-cc-ra-barney-187-source.xml @@ -58,6 +58,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/13_2020-22/jtei-cc-ra-holmes-181-source.xml b/data/JTEI/13_2020-22/jtei-cc-ra-holmes-181-source.xml index d0aab3b..a191866 100644 --- a/data/JTEI/13_2020-22/jtei-cc-ra-holmes-181-source.xml +++ b/data/JTEI/13_2020-22/jtei-cc-ra-holmes-181-source.xml @@ -50,6 +50,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/13_2020-22/jtei-cc-ra-parisse-182-source.xml b/data/JTEI/13_2020-22/jtei-cc-ra-parisse-182-source.xml index 5d1c588..abcc3ae 100644 --- a/data/JTEI/13_2020-22/jtei-cc-ra-parisse-182-source.xml +++ b/data/JTEI/13_2020-22/jtei-cc-ra-parisse-182-source.xml @@ -63,6 +63,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -234,10 +247,10 @@

Many software packages dedicated to editing spoken language transcription contain utilities that can convert many formats: for example, - EXMARaLDA ( Schmidt 2004 - ; see ), + EXMARaLDA ( Schmidt 2004 + ; see ), + Anvil ( Kipp 2001; see ), and EXMARaLDA and FOLKER (Schmidt and Schütte - 2010; see ; see ), but this was only because the conversion tools from and to EXMARaLDA, EXMARaLDA and FOLKER software fit within the process chain of - TEICORPO. This demonstrates the usefulness of a well-known and - efficient format such as TEI.

+ + TEICORPO. This demonstrates the usefulness of a well-known and efficient format + such as TEI.

There are, however, differences between the two projects that make them nonredundant but complementary, each project having specificities that can be useful or damaging depending on the user’s needs. One minor difference is that the - .

+ .

Conversion to and from TEI @@ -1009,8 +1023,8 @@ target="#letrameur"/> Le Trameur (Fleury and Zimina 2014; see ), - and + type="soft.url" ref="#R119">), and Iramuteq (see and de Souza et al. 2018), providing a @@ -1150,13 +1164,13 @@ syntactic model. For French data, we used the PERCEO model (Benzitoun, Fort, and Sagot 2012).

The command line to be used is: - java -cp java -cp TEICORPO.jar fr.ortolang. - TEICORPO. - Tei TreeTagger filenames... - with additional parameters:

+ TEICORPO. Tei TreeTagger + filenames... with additional parameters:

-syntaxformat @@ -1332,10 +1346,12 @@ parameters can be used in a similar way to specify the grammatical model to be used and the output format. A command line example is:

- java -cp " - teicorpo.jar:directory_for_SNLP/*" fr.ortolang. - teicorpo.TeiSNLP - -syntaxformat svalue -model filename.tei_corpo.xml

+ java -cp " + teicorpo.jar:directory_for_SNLP/*" + fr.ortolang. + teicorpo.TeiSNLP -syntaxformat svalue -model + filename.tei_corpo.xml

The directory_for_SNLP is the name of the location on a computer where all the CoreNLP JAR files can be found. Note that using @@ -1397,8 +1413,8 @@

Export can be done from TEI into a format used by textometric software (see ). This is the case for TXM, -

See the Textométrie website, last updated June 29, 2020, .

+

See the Textométrie website, last updated June 29, 2020, .

a textometric software application. In this case, instead of using a partition representation, the information from the grammatical analysis is inserted at the word level in an XML structure. For example, in the case below, the , Alex Klassmann, and Han Sloetjes. 2006. <rs type="soft.name - " - ref="#R235">ELAN</rs>: A Professional Framework for Multimodality - Research. In Proceedings of LREC 2006, Fifth International Conference on - Language Resources and Evaluation, 1556–59. N.p.: - European Language Resources Association (ELRA). ELAN: A Professional Framework for + Multimodality Research. In Proceedings of LREC 2006, Fifth International + Conference on Language Resources and Evaluation, 1556–59. N.p.: European Language Resources Association (ELRA). . diff --git a/data/JTEI/13_2020-22/jtei-cc-ra-winslow-186-source.xml b/data/JTEI/13_2020-22/jtei-cc-ra-winslow-186-source.xml index 4540e0e..8a7c47a 100644 --- a/data/JTEI/13_2020-22/jtei-cc-ra-winslow-186-source.xml +++ b/data/JTEI/13_2020-22/jtei-cc-ra-winslow-186-source.xml @@ -48,6 +48,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -576,8 +589,8 @@ proposed vocabulary, provided in SKOS (Simple Knowledge Organization System) format (as part of the project’s - GitHub repository,Accessed July 13, 2021, GitHub repository,Accessed July 13, 2021, . at + + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/13_2020-22/jtei_cc_ra_mcallister_185_source.xml b/data/JTEI/13_2020-22/jtei_cc_ra_mcallister_185_source.xml index 9a06f45..f8283c1 100644 --- a/data/JTEI/13_2020-22/jtei_cc_ra_mcallister_185_source.xml +++ b/data/JTEI/13_2020-22/jtei_cc_ra_mcallister_185_source.xml @@ -52,6 +52,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/14_2021-23/jtei-baillot-giovacchini-191-source.xml b/data/JTEI/14_2021-23/jtei-baillot-giovacchini-191-source.xml index fcb893b..1d8194d 100644 --- a/data/JTEI/14_2021-23/jtei-baillot-giovacchini-191-source.xml +++ b/data/JTEI/14_2021-23/jtei-baillot-giovacchini-191-source.xml @@ -60,6 +60,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/14_2021-23/jtei-barabuccietal-196-source.xml b/data/JTEI/14_2021-23/jtei-barabuccietal-196-source.xml index ee287b0..eb03a71 100644 --- a/data/JTEI/14_2021-23/jtei-barabuccietal-196-source.xml +++ b/data/JTEI/14_2021-23/jtei-barabuccietal-196-source.xml @@ -76,6 +76,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/14_2021-23/jtei-bleeker-et-al-199-source.xml b/data/JTEI/14_2021-23/jtei-bleeker-et-al-199-source.xml index 95892ec..17a217b 100644 --- a/data/JTEI/14_2021-23/jtei-bleeker-et-al-199-source.xml +++ b/data/JTEI/14_2021-23/jtei-bleeker-et-al-199-source.xml @@ -80,6 +80,19 @@ humanities and social sciences, open to quality periodicals seeking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/14_2021-23/jtei-burnard-shoch-odebrecht-194-source.xml b/data/JTEI/14_2021-23/jtei-burnard-shoch-odebrecht-194-source.xml index 3630420..2868bb0 100644 --- a/data/JTEI/14_2021-23/jtei-burnard-shoch-odebrecht-194-source.xml +++ b/data/JTEI/14_2021-23/jtei-burnard-shoch-odebrecht-194-source.xml @@ -54,6 +54,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -655,19 +668,19 @@ components used by any ELTeC schema at any level. This ODD also contains documentation and specifies usage constraints applicable across every schema. This base ODD is then processed using the TEI standard odd2odd stylesheet to produce a - stand-alone set of TEI specifications which we call eltec-library. Three different - ODDs, eltec-0, eltec-1, and eltec-2, then derive specific schemas and documentation - for each of the three ELTeC levels, using this library of specifications as a base - rather than using the whole of the TEI. This enables us to customize the TEI across - the whole project, while at the same time respecting three different views of the - resulting encoding standard. As with other ODDs, we are then able to produce - documentation and formal schemas which reflect exactly the scope of each encoding - level.

+ target="#odd2odd"/>TEI standard odd2odd + stylesheet to produce a stand-alone set of TEI specifications which we call + eltec-library. Three different ODDs, eltec-0, eltec-1, and eltec-2, then derive + specific schemas and documentation for each of the three ELTeC levels, using this + library of specifications as a base rather than using the whole of the TEI. This + enables us to customize the TEI across the whole project, while at the same time + respecting three different views of the resulting encoding standard. As with other + ODDs, we are then able to produce documentation and formal schemas which reflect + exactly the scope of each encoding level.

The ODD sources and their outputs are maintained on GitHub and are also published on Zenodo (published on Zenodo (Odebrecht et al. 2019) along with the ELTeC corpora.The GitHub repository for the ELTeC collection diff --git a/data/JTEI/14_2021-23/jtei-cc-pn-erjavec-195-source.xml b/data/JTEI/14_2021-23/jtei-cc-pn-erjavec-195-source.xml index b302f64..56f3d92 100644 --- a/data/JTEI/14_2021-23/jtei-cc-pn-erjavec-195-source.xml +++ b/data/JTEI/14_2021-23/jtei-cc-pn-erjavec-195-source.xml @@ -68,6 +68,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -804,8 +817,8 @@ Jan Bušta, Miloš Jakubíček, Vojtěch Kovář, Jan Michelfeit, Pavel Rychlý, and Vít Suchomel. 2014. - The Sketch Engine: Ten Years On. + target="#sketchengine"/>2014. The Sketch Engine: Ten Years On. Lexicography: Journal of ASIALEX 1 (1): 7–36. doi: + + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/14_2021-23/jtei-cc-ra-mylonas-202-source.xml b/data/JTEI/14_2021-23/jtei-cc-ra-mylonas-202-source.xml index bac78c5..9de8aef 100644 --- a/data/JTEI/14_2021-23/jtei-cc-ra-mylonas-202-source.xml +++ b/data/JTEI/14_2021-23/jtei-cc-ra-mylonas-202-source.xml @@ -100,6 +100,19 @@ font-weight:bold; + + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/14_2021-23/jtei-cc-ra-okada-200-source.xml b/data/JTEI/14_2021-23/jtei-cc-ra-okada-200-source.xml index 02761c6..5ee049f 100644 --- a/data/JTEI/14_2021-23/jtei-cc-ra-okada-200-source.xml +++ b/data/JTEI/14_2021-23/jtei-cc-ra-okada-200-source.xml @@ -82,6 +82,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/14_2021-23/jtei-cc-ra-wissik-198-source.xml b/data/JTEI/14_2021-23/jtei-cc-ra-wissik-198-source.xml index e625e25..1b9cc64 100644 --- a/data/JTEI/14_2021-23/jtei-cc-ra-wissik-198-source.xml +++ b/data/JTEI/14_2021-23/jtei-cc-ra-wissik-198-source.xml @@ -58,6 +58,19 @@ font-weight: bold; font-style: italic; + + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/14_2021-23/jtei-provideh-201-source.xml b/data/JTEI/14_2021-23/jtei-provideh-201-source.xml index 9be932d..01c20eb 100644 --- a/data/JTEI/14_2021-23/jtei-provideh-201-source.xml +++ b/data/JTEI/14_2021-23/jtei-provideh-201-source.xml @@ -200,6 +200,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/14_2021-23/jtei-truan-203-source.xml b/data/JTEI/14_2021-23/jtei-truan-203-source.xml index bb39b2c..1f4480c 100644 --- a/data/JTEI/14_2021-23/jtei-truan-203-source.xml +++ b/data/JTEI/14_2021-23/jtei-truan-203-source.xml @@ -76,6 +76,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/14_2021-23/jtei-vogeler-introduction-source.xml b/data/JTEI/14_2021-23/jtei-vogeler-introduction-source.xml index 9d5b7ee..72158ef 100644 --- a/data/JTEI/14_2021-23/jtei-vogeler-introduction-source.xml +++ b/data/JTEI/14_2021-23/jtei-vogeler-introduction-source.xml @@ -47,6 +47,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/14_2021-23/jtei_cc_ra_iglesias_192_source.xml b/data/JTEI/14_2021-23/jtei_cc_ra_iglesias_192_source.xml index f0707d1..a7ab3cb 100644 --- a/data/JTEI/14_2021-23/jtei_cc_ra_iglesias_192_source.xml +++ b/data/JTEI/14_2021-23/jtei_cc_ra_iglesias_192_source.xml @@ -109,6 +109,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/16_2023_spa/jtei-calarco-232-source.xml b/data/JTEI/16_2023_spa/jtei-calarco-232-source.xml index e98c6b9..0539a60 100644 --- a/data/JTEI/16_2023_spa/jtei-calarco-232-source.xml +++ b/data/JTEI/16_2023_spa/jtei-calarco-232-source.xml @@ -63,6 +63,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/16_2023_spa/jtei-calvo-235-source.xml b/data/JTEI/16_2023_spa/jtei-calvo-235-source.xml index d4ecd34..f2c18ab 100644 --- a/data/JTEI/16_2023_spa/jtei-calvo-235-source.xml +++ b/data/JTEI/16_2023_spa/jtei-calvo-235-source.xml @@ -80,6 +80,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/16_2023_spa/jtei-lopez-236-source.xml b/data/JTEI/16_2023_spa/jtei-lopez-236-source.xml index cf930bc..a75ddb7 100644 --- a/data/JTEI/16_2023_spa/jtei-lopez-236-source.xml +++ b/data/JTEI/16_2023_spa/jtei-lopez-236-source.xml @@ -54,6 +54,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/16_2023_spa/jtei-mcclarc-238-source.xml b/data/JTEI/16_2023_spa/jtei-mcclarc-238-source.xml index 416ba95..150cb5c 100644 --- a/data/JTEI/16_2023_spa/jtei-mcclarc-238-source.xml +++ b/data/JTEI/16_2023_spa/jtei-mcclarc-238-source.xml @@ -104,6 +104,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/16_2023_spa/jtei-rioriande-torresallen-250-source.xml b/data/JTEI/16_2023_spa/jtei-rioriande-torresallen-250-source.xml index d1bd2d0..b8beb96 100644 --- a/data/JTEI/16_2023_spa/jtei-rioriande-torresallen-250-source.xml +++ b/data/JTEI/16_2023_spa/jtei-rioriande-torresallen-250-source.xml @@ -71,6 +71,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/16_2023_spa/jtei-rojas-233-source.xml b/data/JTEI/16_2023_spa/jtei-rojas-233-source.xml index c9b581f..517b06b 100644 --- a/data/JTEI/16_2023_spa/jtei-rojas-233-source.xml +++ b/data/JTEI/16_2023_spa/jtei-rojas-233-source.xml @@ -120,6 +120,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/16_2023_spa/jtei-spanish-introduction.xml b/data/JTEI/16_2023_spa/jtei-spanish-introduction.xml index 746c7b5..9f96b4c 100644 --- a/data/JTEI/16_2023_spa/jtei-spanish-introduction.xml +++ b/data/JTEI/16_2023_spa/jtei-spanish-introduction.xml @@ -64,6 +64,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/7_2014/jtei-7-carter-source.xml b/data/JTEI/7_2014/jtei-7-carter-source.xml index a19fd08..fffe1af 100644 --- a/data/JTEI/7_2014/jtei-7-carter-source.xml +++ b/data/JTEI/7_2014/jtei-7-carter-source.xml @@ -39,6 +39,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/7_2014/jtei-7-dee-source.xml b/data/JTEI/7_2014/jtei-7-dee-source.xml index b08c1c8..db3ab1d 100644 --- a/data/JTEI/7_2014/jtei-7-dee-source.xml +++ b/data/JTEI/7_2014/jtei-7-dee-source.xml @@ -35,6 +35,19 @@ articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -150,15 +163,15 @@

The survey

This survey was the research for a master’s dissertation at King’s College, London, under the supervision of Dr. Elena Pierazzo.

was titled Learning the TEI. Created using SurveyMonkey - software, and live for approximately a month between late June and late August 2013, it - collected 95 anonymous responses in total. It was offered only in English. As a - consequence, those researchers without professional proficiency in English were probably - excluded. The survey asked a combination of open and closed questions, targeting experts - as well as novices in the field. Designed for gathering insight to help improve task-based - online resources for working with the TEI, I wrote the questions to solicit thickly descriptive feedback wherever possible (Geertz 1973). The survey + xml:id="R1" target="softw:surveymonkey"/>SurveyMonkey software, and live for approximately a month between late June and + late August 2013, it collected 95 anonymous responses in total. It was offered only in + English. As a consequence, those researchers without professional proficiency in English + were probably excluded. The survey asked a combination of open and closed questions, + targeting experts as well as novices in the field. Designed for gathering insight to help + improve task-based online resources for working with the TEI, I wrote the questions to + solicit thickly descriptive feedback wherever possible + (Geertz 1973). The survey included questions focused on acquiring descriptions of the TEI to assess user understanding, technical competency of respondents, and the kinds of textual work currently being undertaken. I hoped that these questions might reach survey respondents diff --git a/data/JTEI/7_2014/jtei-7-pfannenschmidt-source.xml b/data/JTEI/7_2014/jtei-7-pfannenschmidt-source.xml index e7b65ef..c78f09f 100644 --- a/data/JTEI/7_2014/jtei-7-pfannenschmidt-source.xml +++ b/data/JTEI/7_2014/jtei-7-pfannenschmidt-source.xml @@ -44,6 +44,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/7_2014/jtei-7-schmidt-source.xml b/data/JTEI/7_2014/jtei-7-schmidt-source.xml index 0f4b342..ea37512 100644 --- a/data/JTEI/7_2014/jtei-7-schmidt-source.xml +++ b/data/JTEI/7_2014/jtei-7-schmidt-source.xml @@ -36,6 +36,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/7_2014/jtei-7-schreibman-intro-source.xml b/data/JTEI/7_2014/jtei-7-schreibman-intro-source.xml index fa83a67..f620795 100644 --- a/data/JTEI/7_2014/jtei-7-schreibman-intro-source.xml +++ b/data/JTEI/7_2014/jtei-7-schreibman-intro-source.xml @@ -32,6 +32,19 @@ articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/8_2014-15/jtei-8-barbero-source.xml b/data/JTEI/8_2014-15/jtei-8-barbero-source.xml index 10d8224..f197e68 100644 --- a/data/JTEI/8_2014-15/jtei-8-barbero-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-barbero-source.xml @@ -55,6 +55,19 @@ articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/8_2014-15/jtei-8-berti-source.xml b/data/JTEI/8_2014-15/jtei-8-berti-source.xml index 0d767b8..4981c20 100644 --- a/data/JTEI/8_2014-15/jtei-8-berti-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-berti-source.xml @@ -110,6 +110,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/8_2014-15/jtei-8-blanco-source.xml b/data/JTEI/8_2014-15/jtei-8-blanco-source.xml index 95253d9..0bb15ad 100644 --- a/data/JTEI/8_2014-15/jtei-8-blanco-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-blanco-source.xml @@ -69,6 +69,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/8_2014-15/jtei-8-boschetti-source.xml b/data/JTEI/8_2014-15/jtei-8-boschetti-source.xml index 980dc07..4ee11fd 100644 --- a/data/JTEI/8_2014-15/jtei-8-boschetti-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-boschetti-source.xml @@ -63,6 +63,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -240,8 +253,9 @@ . The continuous integration and release are supported by open source Integrated Development Environments (IDEs) like Eclipse or NetBeans and by a software - configuration management tool such as + target="#netbeans"/> + NetBeans and by a software configuration management + tool such as SVN or Git for versioning and revision control.

@@ -276,9 +290,9 @@ objects. The resources are stored and maintained in a native XML database management system (i.e., eXist-db). The APIs and services provided by Lucene, a - software library developed and hosted by the Apache Foundation, have been used for - indexing the textual data.

+ xml:id="R55" target="#lucene"/>Lucene, a software + library developed and hosted by the Apache Foundation, have been used for indexing the + textual data.

For instance, the information conveyed by the following TEI snippet is distributed among the appropriate Java objects that handle the four levels described diff --git a/data/JTEI/8_2014-15/jtei-8-ciotti-source.xml b/data/JTEI/8_2014-15/jtei-8-ciotti-source.xml index e2fda20..6645de9 100644 --- a/data/JTEI/8_2014-15/jtei-8-ciotti-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-ciotti-source.xml @@ -79,6 +79,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/8_2014-15/jtei-8-dalmau-source.xml b/data/JTEI/8_2014-15/jtei-8-dalmau-source.xml index af88e2d..37e9e6c 100644 --- a/data/JTEI/8_2014-15/jtei-8-dalmau-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-dalmau-source.xml @@ -72,6 +72,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/8_2014-15/jtei-8-dumont-source.xml b/data/JTEI/8_2014-15/jtei-8-dumont-source.xml index 36bb3cf..0c99d96 100644 --- a/data/JTEI/8_2014-15/jtei-8-dumont-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-dumont-source.xml @@ -56,6 +56,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -89,7 +102,7 @@ initiative of Berlin-Brandenburg Academy of Sciences and Humanities, is based on three software components: eXistdb, Oxygen XML Author, and Oxygen XML Author, and ConTeXt. These components are combined, supplemented with additional functions, and tailored to fit a project’s needs. After a pilot run, eXistdb and not just externally. + xml:id="R13" target="#oxygenauthor"/> Oxygen XML Author . as the user @@ -260,11 +273,11 @@ edition. Besides the creation of multiple TEI P5–compatible schemata, the functions and toolbar of the Oxygen XML Author were also configured and - supplemented with additional custom functions. XQuery and XSLT scripts were written for the - Web publication and its presentation was designed in HTML and CSS. The automatic - generation of the print edition was programmed with the formatting language XQuery and XSLT scripts were + written for the Web publication and its presentation was designed in HTML and CSS. The + automatic generation of the print edition was programmed with the formatting language ConTeXt.

@@ -281,7 +294,8 @@ conflicts and unintended overwrites.

- A User-Friendly Environment with + A User-Friendly Environment with Oxygen XML Author

@@ -342,8 +356,8 @@ xml:id="R28" target="#java"/> Java operation, we used parameters and not constants in the source code. Thus, the parameter values could be comfortably entered in - Oxygen XML Author and changed if necessary.

+ Oxygen XML Author and changed if necessary.

Customized @@ -354,9 +368,9 @@
Website

In addition to the work environment in Oxygen XML Author , we also - created a website for the project. On this website the researchers can easily browse - through or search the current data collection through a live connection with the + target="#oxygenauthor"/>Oxygen XML Author , we + also created a website for the project. On this website the researchers can easily + browse through or search the current data collection through a live connection with the database. Access to the website can be either limited to the project team or open to the public.

@@ -458,24 +472,23 @@ the launch of the work environment the operability continually improves.

After we published a report about ediarum,Stefan - Dumont and Martin Fechner, Digitale - Arbeitsumgebung für das Editionsvorhaben <q>Schleiermacher in Berlin - 1808–1834</q>, digiversity: Webmagazin für - Informationstechnologie in den Geisteswissenschaften (October 11, - 2012), report about ediarum,Stefan Dumont and + Martin Fechner, Digitale Arbeitsumgebung für das + Editionsvorhaben <q>Schleiermacher in Berlin 1808–1834</q>, digiversity: Webmagazin für Informationstechnologie in den + Geisteswissenschaften (October 11, 2012), . it caught the attention of other research institutions. During this time TELOTA introduced and explained the environment to interested institutions in various presentations. As a result, for example, the Academy of Science and Literature Mainz adopted the concept of ediarum and built their own digital work - environment based on it. Other interested persons can read about the concept in a series - of blog entries that are written as tutorials.Stefan Dumont, - Tutorial: Wie baue ich ein eigenes Framework für Oxygen - XML?, digiversity: Webmagazin für Informationstechnologie - in den Geisteswissenschaften (October 30, 2013), ediarum and built their own digital work environment + based on it. Other interested persons can read about the concept in a series of blog + entries that are written as tutorials.Stefan Dumont, Tutorial: Wie baue ich ein eigenes Framework für Oxygen XML?, + digiversity: Webmagazin für Informationstechnologie in den + Geisteswissenschaften (October 30, 2013), , and Stefan Dumont, Tutorial: Indexfunktionen für <ptr type="software" xml:id="R43" target="#oxygen"/><rs @@ -496,7 +509,7 @@ >Oxygen</rs> Frameworks or, if necessary, changed in accordance with theGNU LGPL (Lesser General Public License).</p> <p>At the end of 2013, TELOTA began implementing <ptr type="software" xml:id="R57" - target="#ediarum"/><rs type="soft.name" ref="#R57">ediarum</rs> for the <ref + target="#ediarum"/><rs type="soft.name" ref="#R57">ediarum</rs> for the <ref target="http://www.gotthelf.unibe.ch/content/index_ger.html">historical-critical edition of Jeremias Gotthelf</ref>.<note><title level="m">Jeremias Gotthelf: Historisch-kritische Gesamtausgabe (HKG), Forschungsstelle Jeremias Gotthelf, @@ -504,13 +517,13 @@ />. In this collaboration with Bern University, new functions are being developed and existing ones improved. For instance, we plan to build a function to allow end users to insert overlapping markup (using, e.g., anchor elements and spanTo) - in Oxygen XML Author .

+ in Oxygen XML Author .

Summary and Prospects

The bottom-up development of ediarum with its strong focus on user-friendliness + type="soft.name" ref="#R58">ediarum with its strong focus on user-friendliness brings with it certain implications.

It has required a lot of work during the initial implementation and customization of the environment, especially to generate the website and print edition. TELOTA is now @@ -518,13 +531,12 @@ needed for programming. The goal, however, will be not to develop a complete plug-and-play solution. That would be impossible, considering the complexity and diversity of critical editions. The aim for a future version of ediarum will be rather to - create a solution for encoding editions in TEI which involves the lowest possible amount - of time and effort for programming while being customized to the specific needs of a - project.

-

The concept of ediarum’s development with its tailored solution - has various advantages: + target="#ediarum"/>ediarum will be rather to create + a solution for encoding editions in TEI which involves the lowest possible amount of time + and effort for programming while being customized to the specific needs of a project.

+

The concept of ediarum’s development with its tailored solution has various advantages: + Time and effort for programming is spared through the consistent use of existing software and the elimination of extraneous functionality not required by a particular project. In this way a functional software solution is reached more quickly and @@ -538,9 +550,9 @@

Thus, through addressing the needs of a specific project, we found a solution that can be - used by many: ediarum helps bridge the gap between hesitant users - and the many possibilities and advantages of TEI encoding.

+ used by many: ediarum helps bridge the gap between hesitant users and the many + possibilities and advantages of TEI encoding.

diff --git a/data/JTEI/8_2014-15/jtei-8-eide-source.xml b/data/JTEI/8_2014-15/jtei-8-eide-source.xml index 3065a61..4e7883b 100644 --- a/data/JTEI/8_2014-15/jtei-8-eide-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-eide-source.xml @@ -46,6 +46,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/8_2014-15/jtei-8-haaf-source.xml b/data/JTEI/8_2014-15/jtei-8-haaf-source.xml index e2578f6..d1ddcb7 100644 --- a/data/JTEI/8_2014-15/jtei-8-haaf-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-haaf-source.xml @@ -65,6 +65,19 @@ text-align:right; + + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/8_2014-15/jtei-8-iglesia-source.xml b/data/JTEI/8_2014-15/jtei-8-iglesia-source.xml index d52f2ca..a1d0c5e 100644 --- a/data/JTEI/8_2014-15/jtei-8-iglesia-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-iglesia-source.xml @@ -65,6 +65,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -675,7 +688,8 @@ type="doi">10.1093/llc/fqr020. Le Boeuf, Patrick, Martin Doerr, Christian Emil Ore, and Stephen Stead. - 2013. Definition of the CIDOC Conceptual Reference Model, version 5.1.2 (October). 2013. Definition of the CIDOC Conceptual Reference + Model, version 5.1.2 (October). . Myers, Victoria, David O’Shaughnessy, and Mark Philp, eds. 2010. diff --git a/data/JTEI/8_2014-15/jtei-8-intro-source.xml b/data/JTEI/8_2014-15/jtei-8-intro-source.xml index 947ba26..6ed117b 100644 --- a/data/JTEI/8_2014-15/jtei-8-intro-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-intro-source.xml @@ -66,6 +66,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -190,12 +203,12 @@ Similarly, Boschetti and Del Grosso describe the design and development of <ptr type="software" xml:id="R3" target="#teicophilib"/><rs type="soft.name" ref="#R3">TeiCoPhiLib</rs>, a library of Java software components devoted - to editing, processing, and visualising TEI documents in the domain of philological - studies. This tool is particularly suited to fostering collaborative philological work. - This cluster is closed by Dalmau and Hawkins’s article, the focus of which is not on - specific tools or platforms, but rather on the impact and adoption of TEI and text - encoding practices in the library community.

+ target="#java"/>Java software components devoted to + editing, processing, and visualising TEI documents in the domain of philological studies. + This tool is particularly suited to fostering collaborative philological work. This + cluster is closed by Dalmau and Hawkins’s article, the focus of which is not on specific + tools or platforms, but rather on the impact and adoption of TEI and text encoding + practices in the library community.

We conclude this introduction with a few words about how this issue fits within the current developments of TEI and of the Digital Humanities community more generally. Every now and then it is healthy to ask where the TEI is going and why we care about it. With diff --git a/data/JTEI/8_2014-15/jtei-8-moerth-source.xml b/data/JTEI/8_2014-15/jtei-8-moerth-source.xml index 08e26d6..268b686 100644 --- a/data/JTEI/8_2014-15/jtei-8-moerth-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-moerth-source.xml @@ -113,6 +113,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/8_2014-15/jtei-8-munoz-source.xml b/data/JTEI/8_2014-15/jtei-8-munoz-source.xml index d3f4d36..379b43d 100644 --- a/data/JTEI/8_2014-15/jtei-8-munoz-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-munoz-source.xml @@ -63,6 +63,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -344,26 +357,26 @@ decreases the reusability of the textual data produced. The project relies on an automatic process to convert the document-focused encoding into a text-focused one. This process consists of - a set of XSLT - transformations authored by Wendell Piez, who - served as a consultant to the S-GA project in 2013. These transformations are structured - as a pipeline—progressively remodeling the document-focused TEI data to a more familiar - text-focused TEI.The automated transformation workflow was originally managed using - XProc to compose the various stylesheets but was converted to an Apache Cocoon block for ease of maintenance by project staff at MITH. - Some of the stages involved in this process include, for example, identifying chapter - boundaries that span across multiple surfaces (which for convenience are - maintained in separate files), and then combining the content of these surfaces into a - single div type="chapter". While some transformations can be handled - heuristically, others require a hint for the processor. To support - this automated conversion, the S-GA team needed to go beyond purpose-built milestone - elements like delSpan and addSpan and, in effect, semantically overload - the general purpose milestone element using attributes. The value of an attribute - on milestone indicates which text-focused element is intended to appear in a - particular location:This solution is loosely analogous to some of the ways custom - data attributes are intended to be used under the HTML5 Specification: a + set of XSLT transformations authored by Wendell Piez, who served as a consultant to the S-GA project in 2013. These + transformations are structured as a pipeline—progressively remodeling the document-focused + TEI data to a more familiar text-focused TEI.The automated transformation workflow + was originally managed using XProc to compose the various stylesheets but was + converted to an Apache Cocoon block for ease of maintenance by project + staff at MITH. Some of the stages involved in this process include, for example, + identifying chapter boundaries that span across multiple surfaces (which for + convenience are maintained in separate files), and then combining the content of these + surfaces into a single div type="chapter". While some transformations can be + handled heuristically, others require a hint for the processor. To + support this automated conversion, the S-GA team needed to go beyond purpose-built + milestone elements like delSpan and addSpan and, in effect, semantically + overload the general purpose milestone element using attributes. The value of an + attribute on milestone indicates which text-focused element is intended to appear + in a particular location:This solution is loosely analogous to some of the ways + custom data attributes are intended to be used under the HTML5 Specification: . diff --git a/data/JTEI/8_2014-15/jtei-8-piez-source.xml b/data/JTEI/8_2014-15/jtei-8-piez-source.xml index 4abe997..5a8de87 100644 --- a/data/JTEI/8_2014-15/jtei-8-piez-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-piez-source.xml @@ -41,6 +41,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/8_2014-15/jtei-8-rosselli-source.xml b/data/JTEI/8_2014-15/jtei-8-rosselli-source.xml index 8e0b59d..ec46578 100644 --- a/data/JTEI/8_2014-15/jtei-8-rosselli-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-rosselli-source.xml @@ -89,6 +89,19 @@ articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -587,10 +600,9 @@ type="software" xml:id="R44" target="#EVT"/> EVT. Some of the planned features will require fundamental changes to the software architecture to be implemented effectively: this is - probably the case for the - Digital Lightbox (see ), which requires a client-server architecture ( + Digital Lightbox (see ), which requires a client-server architecture (), instead of the current client-only model, to perform some of the existing and planned actions. The currently developed search engine () may prove too limited when dealing with larger @@ -635,19 +647,18 @@ felt that it was not sufficiently user-friendly, which is a critical goal of the entire project. In fact, forcing the editor to install and configure specific server software is a cumbersome requirement. Moreover, thanks to its client-only architecture, up to - this point - EVT could work as a desktop application or an off-line web application that - could be accessed anywhere, and possibly distributed in optical formats (CD or DVD). - Forcing the prerequisites of an Internet connection and of dependency on a server-based - XML database would have undermined our original goal. Going the database route was no - longer an option for a client-only + this point + EVT could work as a desktop application or an + off-line web application that could be accessed anywhere, and possibly distributed in + optical formats (CD or DVD). Forcing the prerequisites of an Internet connection and of + dependency on a server-based XML database would have undermined our original goal. Going + the database route was no longer an option for a client-only EVT and we immediately felt the need to go back to our original architecture to meet this standard. This sudden turnaround marked another chapter in the research process and brought us to the current implementation of - EVT - Search.

+ EVT Search.

However, this new vision also had obvious limitations and issues. An XML database could provide us with crucial functionality typical of every information retrieval system: an indexer, a powerful and flexible server-side language (XQuery), and some useful built-in @@ -676,7 +687,8 @@ collections of web pages. It can function both offline and online, and it does not necessarily require a web server or a server-side programming/query language (such as SQL, PHP, or Python) in order to work. While technically a plug-in, its architecture - is quite interesting and versatile: + is quite interesting and versatile: Tipue uses a combination of client-side JavaScript for the actual bulk of the work, and JSON (or Digital Lightbox

A beta version is - available at .

is a - web-based visualization framework which aims to support historians, paleographers, art - historians, and others in analyzing and studying digital reproductions of cultural - heritage objects. The methodology of research inspiring development of this tool is to - study paleographic elements in a qualitative way, helping scholars’ interpretations as - much as possible, and therefore to reject any automatic methods such as pattern - recognition and clustering which are supposed to return quantitative and objective - results. Although ongoing projects making use of these computational methods are very - promising, the results that may be obtained at this time are still significantly less - precise (with regard to specific image features, at least) than those produced through - human interpretation.

+ available at .

is a web-based + visualization framework which aims to support historians, paleographers, art historians, + and others in analyzing and studying digital reproductions of cultural heritage objects. + The methodology of research inspiring development of this tool is to study paleographic + elements in a qualitative way, helping scholars’ interpretations as much as possible, + and therefore to reject any automatic methods such as pattern recognition and clustering + which are supposed to return quantitative and objective results. Although ongoing + projects making use of these computational methods are very promising, the results that + may be obtained at this time are still significantly less precise (with regard to + specific image features, at least) than those produced through human interpretation.

Initially developed exclusively for paleographic research, the Digital Lightbox may be used with any type of image @@ -957,29 +969,30 @@ EVT provides a rich and usable interface to browse and study manuscript texts together with the corresponding images, the tools offered by the - Digital Lightbox allow users to identify, gather, and analyze visual details which - can be found within the images, and which are important for inquiries relating, for - instance, to the style of the handwriting, decorations on manuscript folia, or page - layout.

-

An effort to adapt and integrate the + Digital Lightbox allow users to identify, gather, + and analyze visual details which can be found within the images, and which are important + for inquiries relating, for instance, to the style of the handwriting, decorations on + manuscript folia, or page layout.

+

An effort to adapt and integrate the Digital Lightbox into EVT is already underway, making it available as a - separate, image-centered view, but there is a major hurdle to overcome: some of the - DL - features are only possible within a client-server architecture. Since + separate, image-centered view, but there is a major hurdle to overcome: some of the + DL features are only possible within a + client-server architecture. Since EVT or, more precisely, a separate version of EVT will migrate to this architecture, at some - point in the future it will be possible to integrate a full version of the - DL. Plans for - the current, client-only version envision implementing all those features that do not - depend on server software: even if this means giving up interesting features such as - collaborative work and annotation, we believe that even a subset of the available tools - will be an invaluable help for manuscript image analysis. Furthermore, as noted above, - thanks to HTML5 and CSS3 it will become more and more feasible to implement features in - a client-only mode.

+ point in the future it will be possible to integrate a full version of the + DL. Plans for the current, client-only version + envision implementing all those features that do not depend on server software: even if + this means giving up interesting features such as collaborative work and annotation, we + believe that even a subset of the available tools will be an invaluable help for + manuscript image analysis. Furthermore, as noted above, thanks to HTML5 and CSS3 it will + become more and more feasible to implement features in a client-only mode.

New Architecture @@ -1077,7 +1090,8 @@ Giancarlo Buomprisco

- EVT website:

+ EVT website:

diff --git a/data/JTEI/8_2014-15/jtei-8-silva-source.xml b/data/JTEI/8_2014-15/jtei-8-silva-source.xml index 6edbe02..b2a5429 100644 --- a/data/JTEI/8_2014-15/jtei-8-silva-source.xml +++ b/data/JTEI/8_2014-15/jtei-8-silva-source.xml @@ -64,6 +64,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/9_2016-17/jtei-9-armaselu-source.xml b/data/JTEI/9_2016-17/jtei-9-armaselu-source.xml index 21d9876..2f6cdaf 100644 --- a/data/JTEI/9_2016-17/jtei-9-armaselu-source.xml +++ b/data/JTEI/9_2016-17/jtei-9-armaselu-source.xml @@ -78,6 +78,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/9_2016-17/jtei-9-ciotti-source.xml b/data/JTEI/9_2016-17/jtei-9-ciotti-source.xml index 9c04bdb..da8faea 100644 --- a/data/JTEI/9_2016-17/jtei-9-ciotti-source.xml +++ b/data/JTEI/9_2016-17/jtei-9-ciotti-source.xml @@ -75,6 +75,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/9_2016-17/jtei-9-illetschko-source.xml b/data/JTEI/9_2016-17/jtei-9-illetschko-source.xml index 9ba8d41..bdc1f3e 100644 --- a/data/JTEI/9_2016-17/jtei-9-illetschko-source.xml +++ b/data/JTEI/9_2016-17/jtei-9-illetschko-source.xml @@ -78,6 +78,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/9_2016-17/jtei-9-intro-source.xml b/data/JTEI/9_2016-17/jtei-9-intro-source.xml index 8bfb961..8313014 100644 --- a/data/JTEI/9_2016-17/jtei-9-intro-source.xml +++ b/data/JTEI/9_2016-17/jtei-9-intro-source.xml @@ -46,6 +46,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/9_2016-17/jtei-9-nelson-source.xml b/data/JTEI/9_2016-17/jtei-9-nelson-source.xml index 7e39a24..f322668 100644 --- a/data/JTEI/9_2016-17/jtei-9-nelson-source.xml +++ b/data/JTEI/9_2016-17/jtei-9-nelson-source.xml @@ -47,6 +47,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/9_2016-17/jtei-9-turska-source.xml b/data/JTEI/9_2016-17/jtei-9-turska-source.xml index 8d14bbf..2d93052 100644 --- a/data/JTEI/9_2016-17/jtei-9-turska-source.xml +++ b/data/JTEI/9_2016-17/jtei-9-turska-source.xml @@ -91,6 +91,19 @@ humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/rolling_2019/jtei-oc-ds-schoch-144-source.xml b/data/JTEI/rolling_2019/jtei-oc-ds-schoch-144-source.xml index dba40a4..619601c 100644 --- a/data/JTEI/rolling_2019/jtei-oc-ds-schoch-144-source.xml +++ b/data/JTEI/rolling_2019/jtei-oc-ds-schoch-144-source.xml @@ -97,6 +97,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/rolling_2021/jtei-vagionakis-204-source.xml b/data/JTEI/rolling_2021/jtei-vagionakis-204-source.xml index 1a463de..9b0e388 100644 --- a/data/JTEI/rolling_2021/jtei-vagionakis-204-source.xml +++ b/data/JTEI/rolling_2021/jtei-vagionakis-204-source.xml @@ -45,6 +45,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -271,15 +284,15 @@ also happened in 2017: the appearance of a powerful new tool for digital epigraphy, EpiDoc Front-End Services (EFES).

GitHub repository, accessed July - 21, 2021, .

Although I was already aware of the many benefits - deriving from a semantic markup of the inscriptions,

On which see and .

what really persuaded me to - adopt a TEI-based approach for the creation of my epigraphic editions was actually - the great facilitation that EFES offered in using TEI-EpiDoc, which I will - discuss in the following section.

+ 21, 2021, .

Although I was + already aware of the many benefits deriving from a semantic markup of the + inscriptions,

On which see + and .

what + really persuaded me to adopt a TEI-based approach for the creation of my epigraphic + editions was actually the great facilitation that EFES offered in using + TEI-EpiDoc, which I will discuss in the following section.

The Benefits of Using EpiDoc and EpiDoc Reference XSLT Stylesheets, created for transformation of EpiDoc XML files into HTML,

Accessed July 21, 2021, - .

require relatively advanced knowledge of XSLT to use - them to produce a satisfying HTML edition for online publication or to generate a - printable PDF. Not to mention the creation of a complete searchable database to be - published online, equipped with indexes and appropriate search filters: this is far - beyond the IT skills of the average epigraphist.

+ .

require + relatively advanced knowledge of XSLT to use them to produce a satisfying HTML + edition for online publication or to generate a printable PDF. Not to mention the + creation of a complete searchable database to be published online, equipped with + indexes and appropriate search filters: this is far beyond the IT skills of the + average epigraphist.

The situation is a little better for those who use EpiDoc as a tool for simplifying their research work on a collection of ancient documents, without aiming at the publication of the encoded inscriptions. The querying of a set of EpiDoc inscriptions @@ -360,8 +374,8 @@ Digital Publishing Tool: EpiDoc Front-End Services, September 1, 2017, ; see also the Kiln GitHub repository, accessed July 21, 2021, + />; see also the Kiln GitHub repository, accessed July 21, 2021, .

is a platform that simplifies the creation and management of databases of inscriptions encoded following the EpiDoc Guidelines. More specifically, + + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/rolling_2022/jtei-elagina-215-source.xml b/data/JTEI/rolling_2022/jtei-elagina-215-source.xml index c6b186f..6301b6a 100644 --- a/data/JTEI/rolling_2022/jtei-elagina-215-source.xml +++ b/data/JTEI/rolling_2022/jtei-elagina-215-source.xml @@ -50,6 +50,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/rolling_2022/jtei-hewan-214-source.xml b/data/JTEI/rolling_2022/jtei-hewan-214-source.xml index 21df549..48e9ba6 100644 --- a/data/JTEI/rolling_2022/jtei-hewan-214-source.xml +++ b/data/JTEI/rolling_2022/jtei-hewan-214-source.xml @@ -49,6 +49,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/rolling_2022/jtei-mitiku-212-source.xml b/data/JTEI/rolling_2022/jtei-mitiku-212-source.xml index 291524b..0165ed7 100644 --- a/data/JTEI/rolling_2022/jtei-mitiku-212-source.xml +++ b/data/JTEI/rolling_2022/jtei-mitiku-212-source.xml @@ -47,6 +47,19 @@

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+ + +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+ diff --git a/data/JTEI/rolling_2022/jtei-oc-ra-schwartz-208-source.xml b/data/JTEI/rolling_2022/jtei-oc-ra-schwartz-208-source.xml index 6570e65..8307188 100644 --- a/data/JTEI/rolling_2022/jtei-oc-ra-schwartz-208-source.xml +++ b/data/JTEI/rolling_2022/jtei-oc-ra-schwartz-208-source.xml @@ -93,6 +93,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/rolling_2022/jtei-reule-211-source.xml b/data/JTEI/rolling_2022/jtei-reule-211-source.xml index aae523e..e479c48 100644 --- a/data/JTEI/rolling_2022/jtei-reule-211-source.xml +++ b/data/JTEI/rolling_2022/jtei-reule-211-source.xml @@ -48,6 +48,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/data/JTEI/rolling_2022/jtei-teilex-207-source.xml b/data/JTEI/rolling_2022/jtei-teilex-207-source.xml index 8476c01..1b56f35 100644 --- a/data/JTEI/rolling_2022/jtei-teilex-207-source.xml +++ b/data/JTEI/rolling_2022/jtei-teilex-207-source.xml @@ -110,6 +110,19 @@ journals in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to + software items in the software-list.xml file, which are encoded with item + elements and identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
@@ -183,9 +196,9 @@ 2018), an initiative launched in 2016 under the auspices of the DARIAH Working Group on Lexical Resources, which aims to define a pivot format for the integration and querying of heterogeneous TEI-based lexical resources.See the - project’s GitHub repository, accessed June 17, 2022, - . + project’s GitHub repository, accessed June 17, 2022, .

The scope of our proposal covers the usage of the following concepts central to etymological description:

diff --git a/data/JTEI/rolling_2023/jtei-oc-ra-almas-209-source.xml b/data/JTEI/rolling_2023/jtei-oc-ra-almas-209-source.xml index 4b2fe1f..32026e0 100644 --- a/data/JTEI/rolling_2023/jtei-oc-ra-almas-209-source.xml +++ b/data/JTEI/rolling_2023/jtei-oc-ra-almas-209-source.xml @@ -165,6 +165,19 @@ in the humanities and social sciences, open to quality periodicals looking to publish full-text articles online.

+ + +

In the context of this project, private URIs with the prefix softw point to software + items in the software-list.xml file, which are encoded with item elements and + identified in xml:id.

+
+ +

In the context of this project, private URIs with the prefix cit point to + category elements in the citation-taxonomy.xml file.

+
+
diff --git a/schema/tei_jtei_annotated.odd b/schema/tei_jtei_annotated.odd index c8dc596..a44d7d0 100644 --- a/schema/tei_jtei_annotated.odd +++ b/schema/tei_jtei_annotated.odd @@ -2047,7 +2047,7 @@ + include="appInfo application availability catRef change classCode edition encodingDesc fileDesc idno keywords langUsage language licence listChange profileDesc projectDesc publicationStmt rendition revisionDesc seriesStmt sourceDesc tagsDecl teiHeader textClass titleStmt listPrefixDef prefixDef"/> @@ -2603,10 +2603,10 @@ - + mode="delete"/>--> diff --git a/schema/tei_jtei_annotated.rng b/schema/tei_jtei_annotated.rng index 1932d96..81c67bb 100644 --- a/schema/tei_jtei_annotated.rng +++ b/schema/tei_jtei_annotated.rng @@ -5,7 +5,7 @@ xmlns="http://relaxng.org/ns/structure/1.0" datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes" ns="http://www.tei-c.org/ns/1.0">