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 9b9e126..c18fe38 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
@@ -200,15 +200,17 @@
projects, though the TEI Consortium website has for many years offered a platform
for one: Projects Using the TEI, accessed May 17, 2021,
. More recently, the
- TEIhub project lists more than 12,500 GitHub-hosted TEI
- projects (last updated May 11, 2021, );
- an associated bot called TEI Pelican provides a daily twitter feed of new GitHub repositories containing a TEI header. We are unaware
- of any systematic analysis of the application types indicated by these data
- sources, but a glance gives the impression that traditional editorial and
- resource-building projects predominate.
+ TEIhub project lists more than 12,500 GitHub-hosted TEI
+ projects (last updated May 11, 2021, ); an associated bot called TEI Pelican provides a daily twitter feed of new
+ GitHub repositories containing a TEI header. We are unaware of
+ any systematic analysis of the application types indicated by these data sources,
+ but a glance gives the impression that traditional editorial and resource-building
+ projects predominate.
The work of the ActionFurther information about the Action is available from
its website at . For information
@@ -228,9 +230,8 @@
issues of sampling and balance were prepared for discussion and approval by the
members of WG1, and remain available from the Working Group’s website. These
and other documents are available from the Action’s GitHub page, accessed May 17, 2021, .
+ xml:id="R3" target="#GitHub"/>GitHub page,
+ accessed May 17, 2021, .
@@ -653,7 +654,8 @@
In the ELTeC project, we begin by defining an ODD which selects from TEI all the
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
+ 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
@@ -662,13 +664,14 @@
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
- (Odebrecht et al. 2019) along with
- the ELTeC corpora.The GitHub repository for the ELTeC
- collection (last updated May 17, 2021) is found at The ODD sources and their outputs are maintained on GitHub and are also published on Zenodo (Odebrecht et al. 2019) along with the
+ ELTeC corpora.The GitHub repository for the ELTeC collection
+ (last updated May 17, 2021) is found at ; the Zenodo community within which it
is being published (last updated April 11, 2021) lives at .
@@ -689,8 +692,8 @@
development and are expected to become available during the coming year. As noted
above, up-to-date information about the current state of all corpora is publicly
visible at , which includes
- links to the individual GitHub repositories for each corpus.
+ links to the individual GitHub repositories for each corpus.
As well as continuing to expand the collection, and continuing to fine-tune its
composition, we hope to improve the consistency and reliability of the metadata
associated with each text, as far as possible automatically. For example, we have
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 0152101..4236f95 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
@@ -207,10 +207,11 @@
The Parla-CLARIN Schema
Parla-CLARIN is written as a TEI ODD document, consisting of the prose guidelines and
- the schema specification, on the basis of which it is possible, using the standard TEI
- XSLT stylesheets, to derive an XML schema expressed either as a RelaxNG schema, a DTD,
- or a W3C schema, which is then used for formal validations of a Parla-CLARIN
- parliamentary corpus.
+ the schema specification, on the basis of which it is possible, using the standard TEI XSLT stylesheets, to derive an XML schema expressed either as a
+ RelaxNG schema, a DTD, or a W3C schema, which is then used for formal validations of a
+ Parla-CLARIN parliamentary corpus.
While the proposal tries to cater for many encoding needs, it is possible that new
users will have to use TEI elements or attributes that are not discussed in the prose
guidelines. Since the recommendations are still under development, the formal schema
@@ -324,20 +325,22 @@
Presentation of Parla-CLARIN
Like the TEI Guidelines, the Parla-CLARIN recommendations are available on GitHub, as a projectTomaž Erjavec and Andrej Pančur, Parla-CLARIN
- project GitHub site, last updated March 17, 2021, . of the CLARIN ERIC
- collection. The project contains a folder for the schema (i.e., the Parla-CLARIN ODD
- document and XML schemas derived from it), a folder for the programs that convert the
- ODD into the XML schemas and to the HTML of the prose and schema definitions, and a
- folder for examples, which contains an artificial but fully worked out example of a
- Parla-CLARIN document and subfolders with various example resources, where each should
- contain:
+ target="https://github.com/clarin-eric/parla-clarin/">GitHub, as a
+ projectTomaž Erjavec and Andrej Pančur, Parla-CLARIN project GitHub site, last updated March 17, 2021, . of the CLARIN
+ ERIC collection. The project contains a folder for the schema (i.e., the Parla-CLARIN
+ ODD document and XML schemas derived from it), a folder for the programs that convert the ODD into the XML schemas and to the HTML of the
+ prose and schema definitions, and a folder for examples, which contains an
+ artificial but fully worked out example of a Parla-CLARIN document and subfolders with
+ various example resources, where each should contain: a sample of a corpus in its source encoding;
- XSLT script to convert it into Parla-CLARIN; and
+ XSLT script to convert it into Parla-CLARIN;
+ andthe output of the conversion.
@@ -495,12 +498,15 @@
Nevertheless, AKN is an important schema for modeling parliamentary proceedings,
especially as the primary encoding standard used by various legislative bodies, so some
of AKN’s solutions were used in developing the Parla-CLARIN proposal, in particular the
- typology of divisions of a document. Also developed was a partial, but non-trivial,
- conversion from AKN to Parla-CLARIN, which covers several AKN example documents. As
- mentioned in , the example documents and
- conversion script can be found in the Examples folder of the Parla-CLARIN
- Git repository. The akn2tei.xsl script attempts to preserve the IDs of
- the source AKN document, converts the AKN addressee, role, and questions and answers to
+ typology of divisions of a document. Also developed was a partial, but non-trivial, conversion from AKN to Parla-CLARIN, which covers several AKN example
+ documents. As mentioned in , the example
+ documents and conversion script can be found in the Examples folder of
+ the Parla-CLARIN Git repository. The akn2tei.xsl script attempts to preserve the IDs of the source
+ AKN document, converts the AKN addressee, role, and questions and answers to
Parla-CLARIN, and maps FRBR data (which distinguishes a work from
its expression and its expression from its
manifestation) to the appropriate TEI elements and attributes.
@@ -572,9 +578,10 @@
parliamentary proceedings meant for scholarly investigations. This scheme is currently a
straightforward customization of the TEI Guidelines, with the majority of the effort
having gone into the writing of the prose guidelines of the Parla-CLARIN recommendations
- and into developing the conversion from Akoma Ntoso to Parla-CLARIN. We have not included
- examples of the encoding, as these are readily available on the GitHub
+ and into developing the conversion from Akoma Ntoso to Parla-CLARIN. We
+ have not included examples of the encoding, as these are readily available on the GitHub
documentation page of the project, and large Parla-CLARIN encoded corpora are openly
available.
Apart from the siParl 2.0 corpus mentioned above (As we wanted to have corpora that are not only interchangeable but interoperable as well,
we created a bespoke ParlaMint XML schema directly in RelaxNG – the schema is compatible
with Parla-CLARIN as it validates a subset of documents that would be validated against
- Parla-CLARIN. We produced common scripts that can convert any of the four corpora to plain
- text, to CoNLL-U format as used by the Universal Dependencies project, and to vertical
- format as used by the CWBThe IMS
- Open Corpus Workbench (CWB), last modified March 30, 2021, . and Sketch EngineAccessed January 13, 2022,
- . (Kilgarriff et al. 2014) concordancers, as well as to
- extract complete speech metadata into TSV files.
+ Parla-CLARIN. We produced common scripts that can convert any of the four corpora
+ to plain text, to CoNLL-U format as used by the Universal Dependencies project, and to
+ vertical format as used by the CWBThe IMS Open Corpus Workbench
+ (CWB), last modified March 30, 2021, . and Sketch
+ EngineAccessed January 13, 2022, . (Kilgarriff et al.
+ 2014) concordancers, as well as to extract complete speech metadata into
+ TSV files.
In order for Parla-CLARIN to achieve its goal of becoming a widely recognized encoding
format for corpora of parliamentary proceedings, significant work remains to be done. On
the basis of the lessons learned in creating ParlaMint, we plan to revise the prose
@@ -619,10 +632,10 @@
specification from the default ones in the TEI Guidelines to ones taken or adapted from
the collected parliamentary corpora.
Second, as we have already done for ParlaMint, we plan to add to the GitHub
- Parla-CLARIN project more down-conversion scripts with which we would increase the
- usability of the Parla-CLARIN corpora. As mentioned, work also needs to be done to develop
- a conversion to RDF.
+ xml:id="R4" target="#GitHub"/>GitHub Parla-CLARIN
+ project more down-conversion scripts with which we would increase the usability of the
+ Parla-CLARIN corpora. As mentioned, work also needs to be done to develop a conversion to
+ RDF.
Last, but not least, one of the great benefits of Git is the ability to support
collaborative work, be it through posting issues, or through using pull requests to
incorporate changes. While the community has not so far made use of these options, we hope
@@ -790,8 +803,8 @@
Kilgarriff, Adam, Vít Baisa,
Jan Bušta, Miloš Jakubíček, Vojtěch
Kovář, Jan Michelfeit, Pavel Rychlý, and
- Vít Suchomel. 2014. The Sketch Engine:
- Ten Years On.
+ Vít Suchomel. 2014.
+ The Sketch Engine: Ten Years On.Lexicography: Journal of ASIALEX1 (1):
7–36. doi:TranslateTEI,TranslateTEI ha sido
desarrollada por Hugh Cayless (Duke
University) y está disponible en: fecha de consulta 16 de julio de 2023, para mejorar la experiencia de usuario al colaborar con traducciones
multilingües de las especificaciones de la TEI;Las especificaciones de la TEI
@@ -241,7 +241,7 @@
El software utilizado para crear y distribuir la encuesta fue Qualtrics,Qualtrics, fecha de
- consulta 16 de julio de 2023, y la licencia de uso fue
proporcionada por la Universidad de Miami. 135 participantes iniciaron la encuesta,
aunque sólo 107 respondieron a todas las secciones y preguntas. 77 de estas 107
@@ -485,17 +485,17 @@
abierto como eXist.Exist Database, fecha de consulta 16 de julio de 2023,
+ type="soft.url" ref="#R7">
En lo que respecta a la transformación y renderizado de XML, el lenguaje más
utilizado parece seguir siendo el ya veterano XSLT (29),XSLT, fecha de consulta 16 de julio de 2023,
- . mientras que las transformaciones XQuery
(11)XQuery, fecha de consulta 16
- de julio de 2023, . se utilizan menos.
Esto no parece coincidir del todo con la pregunta anterior sobre el uso de bases
de datos XML, ya que la mayoría de las bases de datos XML nativas utilizan Jekyll, Gatsby, etc.), 3. Boilerplate, 4. eXist; 5. TEI Publisher, 6. CETEIcean, 7.
- Edition Visualization Technology, y añadimos una opción 8. Otros.
+ ref="#R19">Boilerplate, 4. eXist; 5. TEI Publisher, 6. CETEIcean, 7. Edition Visualization Technology, y añadimos una opción 8. Otros.
No es sorprendente que la puntuación más alta correspondiera a las
infraestructuras creadas ad hoc (43). Así pues, la gran
mayoría siente la necesidad de construir su propia infraestructura en términos de
diseño web, funcionalidades, motor de búsqueda, presentación de las
características del texto y publicación. La relevancia de estos datos radica en la
escasez de plataformas que respondan a las necesidades de los profesionales. Sin
- embargo, entre las plataformas más utilizadas, los participantes eligen TEI
- Publisher (14),TEI Publisher, fecha de consulta 16 de julio de 2023, una herramienta
- diseñada en 2004 para crear repositorios basados en XML a través de una base de
- datos XML nativa con eXist que emplea además una biblioteca de motor de búsqueda
- de texto llamada Lucene.Exist Database, fecha de consulta 16 de julio de
- 2023, . De hecho, los proyectos que
- se apoyan en la solución de base de datos eXist (9) se encuentran entre las
- primeras posiciones. A continuación, los generadores web estáticos aparecen como
- una opción viable y en alza, como Jekyll o Gatsby (11).Para más información
- véase sobre Jekyll, fecha de consulta 16 de julio de 2023, y Gatsby, fecha de consulta 16 de julio de
- 2023, . El hecho de que los
- generadores web estáticos formen parte de las opciones mejor rankeadas responde
- probablemente a dos hechos: primero, el auge de la computación mínima que permite
- la creación de infraestructuras sin necesidad de servidores comerciales o
- institucionales (por ejemplo, los sitios estáticos pueden vivir en servicios
- gratuitos como GitHub y GitHub Pages)GitHub Pages, fecha de consulta 16
- de julio de 2023, . y segundo,
- la falta de acceso a infraestructuras digitales especialmente en América
+ embargo, entre las plataformas más utilizadas, los participantes eligen TEI Publisher (14),TEI
+ Publisher, fecha de consulta 16 de julio de 2023,
+ una herramienta diseñada en 2004 para crear repositorios basados en XML a través
+ de una base de datos XML nativa con eXist que emplea además
+ una biblioteca de motor de búsqueda de texto llamada Lucene.Exist Database,
+ fecha de consulta 16 de julio de 2023, . De hecho, los proyectos que
+ se apoyan en la solución de base de datos eXist (9) se encuentran
+ entre las primeras posiciones. A continuación, los generadores web estáticos
+ aparecen como una opción viable y en alza, como Jekyll o Gatsby (11).Para más información véase sobre Jekyll, fecha de consulta 16 de julio de 2023, y Gatsby, fecha de consulta 16 de julio de
+ 2023, . El hecho de que los generadores web estáticos formen parte
+ de las opciones mejor rankeadas responde probablemente a dos hechos: primero, el
+ auge de la computación mínima que permite la creación de infraestructuras sin
+ necesidad de servidores comerciales o institucionales (por ejemplo, los sitios
+ estáticos pueden vivir en servicios gratuitos como GitHub y
+ GitHub Pages)GitHub
+ Pages, fecha de consulta 16 de julio de 2023, . y
+ segundo, la falta de acceso a infraestructuras digitales especialmente en América
Latina.Para más información sobre el movimiento de la computación mínima,
véase la página del grupo Minimal Computing, fecha de consulta 16 de julio de
2023, . Además,
entre las otras plataformas para publicar archivos TEI algunos participantes
- respondieron estar usando CETEIcean (6),CETEIcean, fecha de consulta 16 de
- julio de 2023, .
- Edition Visualization Technology (5),EVT, fecha de consulta 16 de julio de
- 2023, . mientras que sólo uno
- marcó la hoy bastante anticuada Boilerplate (1).TEI Boilerplate, fecha de
- consulta 16 de julio de 2023, . Entre los que respondieron con la opción Otros, los
- participantes añadieron que reconocen su falta de conocimientos acerca de las
- tecnologías de transformación y publicación de archivos TEI (4), mientras que
- otros mencionaron estar utilizando otras opciones como Kiln,Kiln, fecha de
- consulta 16 de julio de 2023, .
- TEITOK,TEITOK, fecha de consulta 16 de julio de 2023, . R scripts,R Scripts,
- fecha de consulta 16 de julio de 2023, . o tener en mente para el futuro el uso de Textual
- CommunitiesTextual Communities, fecha de consulta 16 de julio de 2023,
- . o TEI
- Publisher.
+ respondieron estar usando CETEIcean (6),CETEIcean, fecha de
+ consulta 16 de julio de 2023, .
+ Edition Visualization Technology (5),EVT, fecha de consulta 16 de julio de 2023, . mientras que sólo uno marcó la hoy bastante anticuada Boilerplate (1).TEI
+ Boilerplate, fecha de consulta 16 de julio de 2023, .
+ Entre los que respondieron con la opción Otros, los participantes
+ añadieron que reconocen su falta de conocimientos acerca de las tecnologías de
+ transformación y publicación de archivos TEI (4), mientras que otros mencionaron
+ estar utilizando otras opciones como Kiln,Kiln, fecha de consulta 16 de julio de
+ 2023, .
+ TEITOK,TEITOK, fecha
+ de consulta 16 de julio de 2023, .
+ R scripts,R Scripts, fecha de
+ consulta 16 de julio de 2023, . o tener en mente para el futuro el uso de Textual CommunitiesTextual Communities, fecha de consulta 16 de julio de 2023, . o TEI Publisher.
Plataformas y herramientas para transformar y/o publicar
@@ -701,8 +733,8 @@
mejorar la enseñanza y el aprendizaje de la TEI? Algunos de los
participantes insistieron en la necesidad de recursos y materiales de formación a
todos los niveles y en español, incluyendo además temas específicos (por ejemplo,
- transformaciones con XSLT), así como otros tipos de recursos, como
+ transformaciones con XSLT), así como otros tipos de recursos, como
referencias bibliográficas. La necesidad de formación formal e informal dentro y
fuera del mundo académico surge también como otra preocupación legítima. Entre las
demandas de formación aflora el desconocimiento de las etapas finales del proceso
@@ -735,8 +767,8 @@
instrucciones generales para marcar textos de modo que puedan ser procesados por
ordenador. El consorcio de la TEI está insuflado de un espíritu de apertura y
colaboración que hace que los propios usuarios puedan proponer mejoras y
- modificaciones a través de su repositorio en GitHub. Este espíritu de
+ modificaciones a través de su repositorio en GitHub. Este espíritu de
colaboración y difusión se manifiesta también a través de un diálogo continuo
mediante una lista de discusión en línea y la organización anual de un congreso
internacional. Por último, el consorcio es un gran paraguas que da lugar a diferentes
@@ -796,22 +828,26 @@
programación y la alfabetización digital en general. Además, diríamos que han surgido
de forma audible otras dos preocupaciones, en primer lugar, la necesidad de
materiales de formación para todo el proceso de labor editorial, con especial
- insistencia en la transformación del XML-TEI (XSLT, XQuery) y publicación
- de los archivos TEI. Esto significa que la comunidad ya ha superado las fases
- iniciales de familiarización con la TEI, y que ahora urgen temas más avanzados. En
- segundo lugar, han aparecido varias voces que defienden la necesidad de contar con
+ insistencia en la transformación del XML-TEI (XSLT, XQuery) y
+ publicación de los archivos TEI. Esto significa que la comunidad ya ha superado las
+ fases iniciales de familiarización con la TEI, y que ahora urgen temas más avanzados.
+ En segundo lugar, han aparecido varias voces que defienden la necesidad de contar con
editores XML gratuitos. El hecho de que el software más popular sea propietario
desanima a algunos usuarios. Ni que decir tiene que ya se han dado algunos pasos para
- adaptar software de código abierto para trabajar con archivos TEI, como Visual Studio
- Code, que se ha beneficiado del desarrollo del plugin Scholarly
- XML, que permite una codificación básica pero rigurosa en
- XML-TEI.Este trabajo se debe a Raffaele Viglianti (Maryland Institute for
- Technology in the Humanities) y el plugin puede descargarse en línea en: fecha de
- consulta 16 de julio de 2023, .
+ adaptar software de código abierto para trabajar con archivos TEI, como Visual Studio Code, que se ha beneficiado del desarrollo del
+ plugin Scholarly
+ XML, que permite una codificación básica pero rigurosa
+ en XML-TEI.Este trabajo se debe a Raffaele
+ Viglianti (Maryland Institute for Technology in the Humanities) y el
+ plugin puede descargarse en línea en: fecha de consulta 16 de julio de 2023, .
En resumen, la encuesta nos permitió comprender mejor no sólo a la comunidad
hispanohablante que utiliza XML-TEI, sino también pensar en estrategias que puedan
diff --git a/data/JTEI/7_2014/jtei-7-dee-source.xml b/data/JTEI/7_2014/jtei-7-dee-source.xml
index 8066f09..030fa69 100644
--- a/data/JTEI/7_2014/jtei-7-dee-source.xml
+++ b/data/JTEI/7_2014/jtei-7-dee-source.xml
@@ -149,23 +149,24 @@
Learning the TEI Survey
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 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 who had never heard of the TEI but who were
- working intensively with texts. Because of this, nearly all questions were optional, so
- that those who had never heard of the technologies and communities mentioned were still
- able to respond. As a consequence, most of the survey results are not of statistical
- significance, and I would caution against understanding the results in a quantitative
- light.
+ 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
+ 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
+ who had never heard of the TEI but who were working intensively with texts. Because of
+ this, nearly all questions were optional, so that those who had never heard of the
+ technologies and communities mentioned were still able to respond. As a consequence, most
+ of the survey results are not of statistical significance, and I would caution against
+ understanding the results in a quantitative light.
This section is divided into four subsections, broadly categorized according to the
different subjects about which the survey addressed. provides an overview of the respondents—how they were reached, who
@@ -354,8 +355,9 @@
presentations/talks; various digital editions; digital editions,
mostly; Creating digital editions Creating digital collections
sic. Sixty-two percent intended to transform their data
- with an independently-developed stylesheet, 24% with a TEI stylesheet, and only 10% plan
- to leave them as TEI XML.
+ with an independently-developed stylesheet, 24% with a TEI stylesheet, and only
+ 10% plan to leave them as TEI XML.
The respondents from the mailing list gave less consistent answers than the expert
users, yet still appeared to be using the TEI primarily in service of interoperability
and the construction of digital editions. When asked, What do you hope to achieve
@@ -464,8 +466,9 @@
developed by Mandell and Chesley; the latter the need for TEI XML introductory
resources to be coupled with transformation technologies such as XSLT in the manner of
Bridget Almas’s NEH Tutorial. As will be discussed later in this subsection, certain
- users find that the absence of integrated XSLT resources on the TEI
- by Example site falls short of their needs.
+ users find that the absence of integrated XSLT resources on the TEI by Example site falls short of their needs.
The Learners’ Perspective
@@ -474,12 +477,14 @@
list. Two had reached out to a member of the community for guidance, and both had met
their mentors in person, one through a summer school TEI training and one through a
university course. Five had used the TEI website; two had not. Online tools they
- claimed to have used included OxGarage, Roma, TEI by Example,
- and the TEI Guidelines, as well as the university-hosted resources published by the
- Brown University Women Writers Project (Bauman and
- Flanders 2013) and Humboldt University in Berlin. Within the resources, these
- respondents mostly reported problems with seeking and finding the information that
- they need for their particular project.
+ claimed to have used included OxGarage, Roma, TEI by
+ Example, and the TEI Guidelines, as well as the university-hosted resources
+ published by the Brown University Women Writers Project (Bauman and Flanders 2013) and Humboldt University in
+ Berlin. Within the resources, these respondents mostly reported problems with seeking
+ and finding the information that they need for their particular project.
Of the four respondents who declared their affiliation with an academic and/or
research institution, all said that their institution did not offer
instruction in the TEI. In response to the question, How easily would you be able
@@ -544,24 +549,25 @@
by linking to examples, failed by not simplifying the reference for beginners.
Very detailed, there’s a lot to read>too time-consuming Important
features clearly marked>very helpful. TEI by example very useful for
- thinking about which tags we need for our project. The XSLT resources are pretty
- unhelpful, though; The TEI Guidelines are very comprehensive and provide good
- examples—but no best practices in areas where there is more
- than one solution. Unfortunately TEI By Example did not
- deliver any better in that respect; Not enough variety of examples, case
- studies—I have sought out examples of projects that use TEI but it can be difficult
- to identify. Or maybe my problem is that I don’t know how to identify if a project
- uses TEI or not; Useful as a reference resource. Learnt mostly by induction
- from examples; The modular approach TEI takes to including/not including
- elements is very confusing to the novice or person who’s familiar with working with
- smaller XML schemas that don’t take a modular approach. The guidelines and the wiki
- don’t make this clear once you’re deep in the documentation; they assume you already
- understand this. All of the above comments which state or imply the need for
- expert guidance might reflect the absence of the respondents from the TEI-L mailing
- list, where these kinds of best practices are continuously
- discussed, and perhaps suggest a future need for the TEI-L mailing list
- archives to be re-formatted for greater accessibility.
+ thinking about which tags we need for our project. The XSLT resources are
+ pretty unhelpful, though; The TEI Guidelines are very comprehensive and
+ provide good examples—but no best practices in areas where
+ there is more than one solution. Unfortunately TEI By
+ Example did not deliver any better in that respect; Not enough
+ variety of examples, case studies—I have sought out examples of projects that use
+ TEI but it can be difficult to identify. Or maybe my problem is that I don’t know
+ how to identify if a project uses TEI or not; Useful as a reference resource.
+ Learnt mostly by induction from examples; The modular approach TEI takes to
+ including/not including elements is very confusing to the novice or person who’s
+ familiar with working with smaller XML schemas that don’t take a modular approach.
+ The guidelines and the wiki don’t make this clear once you’re deep in the
+ documentation; they assume you already understand this. All of the above
+ comments which state or imply the need for expert guidance might reflect the absence
+ of the respondents from the TEI-L mailing list, where these kinds of best
+ practices are continuously discussed, and perhaps suggest a future need
+ for the TEI-L
+ mailing list archives to be re-formatted for greater accessibility.
@@ -732,24 +738,27 @@
Integrated Resources
-
While initiatives such as TAPAS, TEICHI, and CWRC-WriterWelcome to CWRC Writer,
- CWRC-Writer Help, accessed September 7,
- 2013, .
have
- begun to address to different aspects of these needs (Flanders and Hamlin 2013; Pape, Schöch, and Wegner 2013; Crane
- 2010), there has yet to be a deeply comprehensive resource intimately linked to
- the TEI Guidelines themselves. New technical infrastructure should support workflows
- that allow users to enter the genre with which they are working in a search engine
- connected to the TEI Guidelines (e.g., poetry), find a list of relevant
- tags with explanations of their functions, and from those tags find projects and files
- that make use of those tags; for example, a search that retrieves all TEI-conformant
- files using an l tag, and allows the user to search the projects that created
- these files.
+
While initiatives such as TAPAS, TEICHI, and CWRC-WriterWelcome to <rs
+ type="soft.name" ref="#R9">CWRC Writer</rs>, CWRC-Writer Help, accessed September 7, 2013, .
have begun to address to different aspects of these needs (Flanders and
+ Hamlin 2013; Pape, Schöch, and Wegner 2013; Crane 2010), there has yet to be a deeply comprehensive
+ resource intimately linked to the TEI Guidelines themselves. New technical
+ infrastructure should support workflows that allow users to enter the genre with which
+ they are working in a search engine connected to the TEI Guidelines (e.g.,
+ poetry), find a list of relevant tags with explanations of their
+ functions, and from those tags find projects and files that make use of those tags; for
+ example, a search that retrieves all TEI-conformant files using an l tag, and
+ allows the user to search the projects that created these files.
This vision may be a long way off, and should certainly be modified by community
expertise, changing needs, and computational realities. However, this is the kind of
organized, integrated, and open plan that the TEI community, both present and potential,
@@ -793,12 +802,14 @@
level="a">Give us Editors! Re-inventing the Edition and Re-thinking the
Humanities. OpenStax CNX, May 13. .
- Flanders, Julia, and Scott
- Hamlin. 2013. TAPAS: 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="#R10">TAPAS</rs>: Building a TEI Publishing and Repository Service.
+ Journal of the Text Encoding Initiative
+ 5. .
+ doi:10.4000/jtei.788.Geertz, Clifford. 1973. The Interpretation of Cultures: Selected Essays. New York,
NY: Perseus Books Group.
@@ -825,12 +836,16 @@
level="m">Introduction to Digital Textual Editing: An UNOFFICIAL Guide to the Value of
TEI. Slidecast posted June 30, 2013. .
- Pape, Sebastian, Christof Schöch,
- and Lutz Wegner. 2012. TEICHI and the
- Tools Paradox: Developing a Publishing Framework for Digital Editions. Journal of the Text Encoding Initiative
- 2. .
- doi:10.4000/jtei.432.
+ Pape,
+ Sebastian, Christof
+ Schöch, and Lutz
+ Wegner. 2012. <rs type="soft.name"
+ ref="#R11">TEICHI</rs> and the Tools Paradox: Developing a Publishing Framework
+ for Digital Editions. Journal of the Text Encoding
+ Initiative
+ 2. .
+ doi:10.4000/jtei.432.Roueché, Charlotte, and Julia
Flanders. 2014. Introduction for
Epigraphers. EpiDoc Guidelines: Ancient Documents in TEI
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 0269c87..529f58b 100644
--- a/data/JTEI/8_2014-15/jtei-8-berti-source.xml
+++ b/data/JTEI/8_2014-15/jtei-8-berti-source.xml
@@ -143,9 +143,10 @@
</list>. The ultimate goals are the creation of open, linked, machine-actionable texts for
the study and advancement of the field of Classical textual fragmentary heritage and the
development of a collaborative environment for crowdsourced annotations. These goals are
- being achieved by implementing the Perseids Platform and by encoding the <title level="m"
- >Fragmenta Historicorum Graecorum, one of the most important and comprehensive
- collections of fragmentary authors.
+ being achieved by implementing the Perseids Platform and by
+ encoding the Fragmenta Historicorum Graecorum, one of the most
+ important and comprehensive collections of fragmentary authors.
@@ -202,11 +203,14 @@
to digitize paper editions of fragmentary works and link them to source texts,
andto produce born-digital editions of fragmentary works
- . In order to achieve these goals, LOFTS is implementing a Fragmentary Texts Editor
- within the Perseids PlatformFor a prototype interface, see . (Almas and Berti 2013) and is producing a digital edition of the
- Fragmenta Historicorum Graecorum edited by Karl Müller in the
+ . In order to achieve these goals, LOFTS is implementing a Fragmentary
+ Texts Editor within the Perseids PlatformFor a prototype interface,
+ see . (Almas and Berti 2013) and is producing a digital edition of the Fragmenta Historicorum Graecorum edited by Karl Müller in the
nineteenth century (Müller 1878–85; DFHG
Project).On this project, see below, .
Alongside the DFHG project, LOFTS is working on two other subprojects: Berti and Stoyanova 2014).
+
The present paper is divided into two parts. The first part () describes the implementation of a fragmentary texts editor within
Perseids, the editorial platform developed by the Perseus Project for collaborative
@@ -875,15 +880,17 @@
28(4):
493–503. doi:10.1093/llc/fqt046.
- Almas, Bridget, and Monica
- Berti. 2013. Perseids Collaborative Platform for
- Annotating Text Re-uses of Fragmentary Authors. In DH-Case
- 2013. Proceedings of the 1st International Workshop on Collaborative Annotations in
- Shared Environments: Metadata, Vocabularies and Techniques in the Digital
- Humanities, edited by Francesca Tomasi and Fabio
- Vitali, article no. 7. New York, NY: ACM
- Digital Library. doi:10.1145/2517978.2517986.
+ Almas,
+ Bridget, and Monica
+ Berti. 2013. Perseids Collaborative
+ Platform for Annotating Text Re-uses of Fragmentary Authors. In DH-Case 2013. Proceedings of the 1st International Workshop on
+ Collaborative Annotations in Shared Environments: Metadata, Vocabularies and
+ Techniques in the Digital Humanities, edited by Francesca
+ Tomasi and Fabio Vitali, article no. 7. New
+ York, NY: ACM Digital Library. doi:10.1145/2517978.2517986.Almas, Bridget, Monica Berti,
Sayeed Choudhury, David Dubin, Megan
Senseney, and Karen M. Wickett. 2013. EVT could go beyond being a project-specific tool. The inspiration for these
changes came from work done in similar projects developed within the TEI community,
- namely
+ namely TEI Boilerplate,