<?xml version="1.0" encoding="UTF-8"?>
<?xml-model https://raw.githubusercontent.com/i-d-e/ride/master/schema/ride.rng application/xml http://relaxng.org/ns/structure/1.0?>
<?xml-model https://raw.githubusercontent.com/i-d-e/ride/master/schema/ride.rng application/xml http://purl.oclc.org/dsdl/schematron?>
<TEI xmlns="http://www.tei-c.org/ns/1.0" xml:id="ride.19.4">
   <teiHeader>
      <fileDesc>
         <titleStmt>
            <title>ChatGPT as an Assistant for Digital Scholarly Editing</title>
            <author ref="https://orcid.org/0000-0003-1438-3236">
               <name>
                  <forename>Martina</forename>
                  <surname>Scholger</surname>
               </name>
               <affiliation>
                  <orgName>University of Graz</orgName>
                  <placeName>Graz, Austria</placeName>
               </affiliation>
               <email>martina.scholger@uni-graz.at</email>
            </author>
            <author ref="https://orcid.org/0000-0003-4674-1042">
               <name>
                  <forename>Roman</forename>
                  <surname>Bleier</surname>
               </name>
               <affiliation>
                  <orgName>University of Graz</orgName>
                  <placeName>Graz, Austria</placeName>
               </affiliation>
               <email>roman.bleier@uni-graz.at</email>
            </author>
         </titleStmt>
         <publicationStmt>
            <publisher>Institut für Dokumentologie und Editorik e.V.</publisher>
            <date when="2026-03">March 2026</date>
            <idno type="URI">http://ride.i-d-e.de/issues/issue-19/chatgpt</idno>
            <idno type="DOI">10.18716/ride.a.19.4</idno>
            <idno type="archive"
               >https://github.com/i-d-e/ride/raw/master/issues/issue19/chatgpt/chatgpt.pdf</idno>
            <availability>
               <licence target="http://creativecommons.org/licenses/by/4.0/"/>
            </availability>
         </publicationStmt>
         <seriesStmt>
            <title level="j">RIDE - A review journal for digital editions and resources</title>
            <editor ref="https://orcid.org/0000-0003-4674-1042">Roman Bleier</editor>
            <editor ref="https://orcid.org/0000-0002-6923-0950">Stefan Dumont</editor>
            <editor ref="https://orcid.org/0000-0003-2852-065X" role="managing">Ulrike
               Henny-Krahmer</editor>
            <editor ref="https://orcid.org/0000-0003-1438-3236" role="managing">Martina
               Scholger</editor>
            <biblScope unit="issue" n="19">Tools and Environments</biblScope>
            <idno type="URI">http://ride.i-d-e.de/issues/issue-19</idno>
            <idno type="DOI">10.18716/ride.a.19</idno>
         </seriesStmt>
         <notesStmt>
            <relatedItem type="reviewed_resource">
               <bibl>
                  <title>ChatGPT</title>
                  <editor>OpenAI</editor>
                  <date type="publication">2022</date>
                  <idno type="URI">https://openai.com/</idno>
                  <date type="accessed">2026-02-01</date>
               </bibl>
            </relatedItem>
            <relatedItem type="reviewing_criteria">
               <bibl>
                  <ref
                     target="https://www.i-d-e.de/publikationen/weitereschriften/criteria-tools-version-1/"
                     >Criteria for Reviewing Tools and Environments for Digital Scholarly
                     Editing</ref>
               </bibl>
            </relatedItem>
         </notesStmt>
         <sourceDesc>
            <p>born digital</p>
         </sourceDesc>
      </fileDesc>
      <encodingDesc>
         <classDecl>
            <taxonomy
               xml:base="https://www.i-d-e.de/publikationen/weitereschriften/criteria-tools-version-1/">
               <category>
                  <catDesc>General information</catDesc>
                  <category xml:id="te001">
                     <catDesc>Software type <ref target="#K0.1.1">cf. Catalogue 0.1.1</ref>
                     </catDesc>
                     <catDesc>What type of software is it?</catDesc>
                     <category xml:id="te002">
                        <catDesc>Software tool</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te003">
                        <catDesc>Virtual Reseaerch Environment (VRE)</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te004">
                     <catDesc>Identification of the environment <ref target="#K1.4">cf. Catalogue
                           1.4</ref>
                     </catDesc>
                     <catDesc>On which platform runs the tool?</catDesc>
                     <category xml:id="te005">
                        <catDesc>Operating system</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te006">
                        <catDesc>Web browser</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te007">
                        <catDesc>Another application</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te008">
                     <catDesc>Purpose <ref target="#K1.5">cf. Catalogue 1.5</ref>
                     </catDesc>
                     <catDesc>For what purpose was the tool developed?</catDesc>
                     <category xml:id="te009">
                        <catDesc>developed to accomplish a general task</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te010">
                        <catDesc>developed for a specific project or materials</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te011">
                     <catDesc>Funding <ref target="#K1.6">cf. Catalogue 1.6</ref>
                     </catDesc>
                     <catDesc>Which is the financial model of the tool?</catDesc>
                     <category xml:id="te012">
                        <catDesc>Free/open</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te013">
                        <catDesc>Support-based</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te014">
                        <catDesc>Behind a paywall</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te015">
                     <catDesc>Maturity <ref target="#K1.5">cf. Catalogue 1.5</ref>
                     </catDesc>
                     <catDesc>What is the development stage of the tool?</catDesc>
                     <category xml:id="te016">
                        <catDesc>Release</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te017">
                        <catDesc>Beta</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te018">
                        <catDesc>Alpha</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
               </category>
               <category>
                  <catDesc>Methods and implementation</catDesc>
                  <category xml:id="te019">
                     <catDesc>Programming Language <ref target="#K2.3">cf. Catalogue 2.3</ref>
                     </catDesc>
                     <catDesc>Which programming languages and technologies are used?</catDesc>
                     <category xml:id="te020">
                        <catDesc>C family</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te021">
                        <catDesc>Java</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te022">
                        <catDesc>Python</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te023">
                        <catDesc>PHP</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te024">
                        <catDesc>R</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te025">
                        <catDesc>Ruby</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te026">
                        <catDesc>XSLT</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te027">
                        <catDesc>Unknown</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te028">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                        <catDesc>
                           <gloss>large language model</gloss>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te029">
                     <catDesc>Reuse <ref target="#K3.1.6">cf. Catalogue 2.3</ref>
                     </catDesc>
                     <catDesc>Does the tool reuse portions of other existing software?</catDesc>
                     <category xml:id="te030">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te031">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te032">
                     <catDesc>Input format <ref target="#K2.3">cf. Catalogue 2.4</ref>
                     </catDesc>
                     <catDesc>Which input formats are supported?</catDesc>
                     <category xml:id="te033">
                        <catDesc>.xml</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te034">
                        <catDesc>.xml/tei</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te035">
                        <catDesc>.txt</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te036">
                        <catDesc>.pdf</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te037">
                        <catDesc>.csv</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te038">
                        <catDesc>.html</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te039">
                        <catDesc>.json</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te040">
                        <catDesc>.rdf</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te041">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te042">
                     <catDesc>Output format <ref target="#K2.3">cf. Catalogue 2.4</ref>
                     </catDesc>
                     <catDesc>Which output formats are supported?</catDesc>
                     <category xml:id="te043">
                        <catDesc>.xml</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te044">
                        <catDesc>.xml/tei</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te045">
                        <catDesc>.txt</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te046">
                        <catDesc>.pdf</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te047">
                        <catDesc>.csv</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te048">
                        <catDesc>.html</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te049">
                        <catDesc>.json</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te050">
                        <catDesc>.rdf</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te051">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te052">
                     <catDesc>Encoding <ref target="#K2.3">cf. Catalogue 2.4</ref>
                     </catDesc>
                     <catDesc>Which character encoding formats are supported?</catDesc>
                     <category xml:id="te053">
                        <catDesc>latin-1</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te054">
                        <catDesc>utf-8</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te055">
                        <catDesc>utf-16</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te056">
                        <catDesc>Unknown</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te057">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te058">
                     <catDesc>Encoding preprocessing</catDesc>
                     <catDesc>Is a pre-processing conversion included?</catDesc>
                     <category xml:id="te059">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te060">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te061">
                     <catDesc>Dependencies <ref target="#K3.2">cf. Catalogue 3.2</ref>
                     </catDesc>
                     <catDesc>Does the documentation list dependencies on other software, libraries
                        or hardware?</catDesc>
                     <category xml:id="te062">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te063">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te064">
                        <catDesc>Not applicable (no documentation provided)</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te065">
                     <catDesc>Dependencies installation</catDesc>
                     <catDesc>If yes, is the software handling the installation of dependencies
                        during the general installation process (you don't have to install them
                        manually before the installation)?</catDesc>
                     <category xml:id="te066">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te067">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te068">
                        <catDesc>Not applicable (no documentation provided)</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
               </category>
               <category>
                  <catDesc>Documentation and support</catDesc>
                  <category xml:id="te069">
                     <catDesc>Documentation <ref target="#K3.4">cf. Catalogue 3.4</ref>
                     </catDesc>
                     <catDesc>Is documentation and/or a manual available? (tool website, wiki, blog,
                        documentation, or tutorial)</catDesc>
                     <category xml:id="te070">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te071">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te072">
                     <catDesc>Documentation format <ref target="#K3.3">cf. Catalogue 3.3</ref>
                     </catDesc>
                     <catDesc>Which format has the documentation?</catDesc>
                     <category xml:id="te073">
                        <catDesc>readme</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te074">
                        <catDesc>.txt</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te075">
                        <catDesc>.html</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te076">
                        <catDesc>.pdf</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te077">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te078">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te079">
                     <catDesc>Documentation parts <ref target="#K3.3">cf. Catalogue 3.3</ref>
                     </catDesc>
                     <catDesc>Which of the following sections does the documentation
                        contain?</catDesc>
                     <category xml:id="te080">
                        <catDesc>‘Getting Started’ section (installation and
                           configuration)</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te081">
                        <catDesc>Step-by-step instructions</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te082">
                        <catDesc>Examples</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te083">
                        <catDesc>Troubleshooting (a selection of possible error messages and related
                           solutions)</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te084">
                        <catDesc>FAQ</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te085">
                        <catDesc>Support</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te086">
                        <catDesc>API documentation (if relevant)</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te087">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te088">
                     <catDesc>Documentation language <ref target="#K3.3">cf. Catalogue 3.3</ref>
                     </catDesc>
                     <catDesc>In what languages is the documentation available?</catDesc>
                     <category xml:id="te089">
                        <catDesc>Arabic</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te090">
                        <catDesc>Chinese</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te091">
                        <catDesc>Danish</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te092">
                        <catDesc>English</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te093">
                        <catDesc>Finnish</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te094">
                        <catDesc>French</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te095">
                        <catDesc>German</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te096">
                        <catDesc>Greek</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te097">
                        <catDesc>Hebrew</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te098">
                        <catDesc>Hindi</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te099">
                        <catDesc>Italian</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te100">
                        <catDesc>Japanese</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te101">
                        <catDesc>Latin</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te102">
                        <catDesc>Norwegian</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te103">
                        <catDesc>Polish</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te104">
                        <catDesc>Portuguese</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te105">
                        <catDesc>Russian</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te106">
                        <catDesc>Spanish</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te107">
                        <catDesc>Swedish</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te108">
                        <catDesc>Turkish</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te109">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te110">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te111">
                     <catDesc>Support <ref target="#K3.4">cf. Catalogue 3.4</ref>
                     </catDesc>
                     <catDesc>Is there a method to get active support from the developer(s) or from
                        the community?</catDesc>
                     <category xml:id="te112">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te113">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te114">
                     <catDesc>From of support <ref target="#K3.4">cf. Catalogue 3.4</ref>
                     </catDesc>
                     <catDesc>Which form of support is offered?</catDesc>
                     <category xml:id="te115">
                        <catDesc>Help desk</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te116">
                        <catDesc>Forum</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te117">
                        <catDesc>Mailing-list</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te118">
                        <catDesc>Not applicable (if no support is given)</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te119">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                        <catDesc>
                           <gloss>e-learning and online training</gloss>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te120">
                     <catDesc>Issue tracker <ref target="#K3.4">cf. Catalogue 3.4</ref>
                     </catDesc>
                     <catDesc>Is it possible to post bugs or issue using issue tracker
                        mechanisms?</catDesc>
                     <category xml:id="te121">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te122">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
               </category>
               <category>
                  <catDesc>Usability and sustainability</catDesc>
                  <category xml:id="te123">
                     <catDesc>Build and install <ref target="#K3.6">cf. Catalogue 3.6</ref>
                     </catDesc>
                     <catDesc>Grade how straightforward it is to build or install the tool on a
                        supported platform:</catDesc>
                     <category xml:id="te124">
                        <catDesc>straightforward</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te125">
                        <catDesc>normal</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te126">
                        <catDesc>tricky</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te127">
                     <catDesc>Tests <ref target="#K3.7">cf. Catalogue 3.7</ref>
                     </catDesc>
                     <catDesc>Is there a test suite, covering the core functionality in order to
                        check that the tool has been correctly built or installed?</catDesc>
                     <category xml:id="te128">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te129">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te130">
                     <catDesc>Portability and interoperability <ref target="#K3.8">cf. Catalogue
                           3.8</ref>
                     </catDesc>
                     <catDesc>On which platforms can the tool/software be deployed?</catDesc>
                     <category xml:id="te131">
                        <catDesc>Linux/BSD/Unix</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te132">
                        <catDesc>Mac OS X</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te133">
                        <catDesc>Android</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te134">
                        <catDesc>iOS</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te135">
                        <catDesc>Windows</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te136">
                        <catDesc>Not applicable (if web-based for example)</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te137">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te138">
                     <catDesc>Devices <ref target="#K3.8">cf. Catalogue 3.8</ref>
                     </catDesc>
                     <catDesc>On which devices can the tool/software be deployed?</catDesc>
                     <category xml:id="te139">
                        <catDesc>Desktop</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te140">
                        <catDesc>Laptop</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te141">
                        <catDesc>Smartphone</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te142">
                        <catDesc>Tablet</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te143">
                        <catDesc>Smartboard</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te144">
                        <catDesc>Unknown</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te145">
                        <catDesc>Not applicable (if web-based for example)</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te146">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te147">
                     <catDesc>Browsers <ref target="#K3.8">cf. Catalogue 3.8</ref>
                     </catDesc>
                     <catDesc>If the tool is web-based: On which browsers can the tool/software be
                        deployed?</catDesc>
                     <category xml:id="te148">
                        <catDesc>Mozilla Firefox</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te149">
                        <catDesc>Google Chrome</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te150">
                        <catDesc>Safari</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te151">
                        <catDesc>Unknown</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te152">
                        <catDesc>Not applicable (if not web-based for example)</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te153">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te154">
                     <catDesc>Plugins <ref target="#K3.8">cf. Catalogue 3.8</ref>
                     </catDesc>
                     <catDesc>If the tool is web-based: Does the tool rely on browser
                        plugins?</catDesc>
                     <category xml:id="te155">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te156">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te157">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te158">
                     <catDesc>API <ref target="#K3.8">cf. Catalogue 3.8</ref>
                     </catDesc>
                     <catDesc>Is there an API for the tool?</catDesc>
                     <category xml:id="te159">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te160">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te161">
                     <catDesc>Code <ref target="#K3.9">cf. Catalogue 3.9</ref>
                     </catDesc>
                     <catDesc>Is the source code open?</catDesc>
                     <category xml:id="te162">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te163">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te164">
                     <catDesc>License <ref target="#K3.9">cf. Catalogue 3.9</ref>
                     </catDesc>
                     <catDesc>Under what license is the tool released?</catDesc>
                     <category xml:id="te165">
                        <catDesc>GNU/GPL</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te166">
                        <catDesc>GNU/LGPL</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te167">
                        <catDesc>Apache</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te168">
                        <catDesc>MIT</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te169">
                        <catDesc>Mozilla</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te170">
                        <catDesc>CC0</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te171">
                        <catDesc>CC-BY</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te172">
                        <catDesc>CC-BY-ND</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te173">
                        <catDesc>CC-BY-NC</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te174">
                        <catDesc>CC-BY-SA</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te175">
                        <catDesc>CC-BY-NC-ND</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te176">
                        <catDesc>CC-BY-NC-SA</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te177">
                        <catDesc>No explicit license / all rights reserved</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te178">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te179">
                     <catDesc>Credits <ref target="#K3.9">cf. Catalogue 3.9</ref>
                     </catDesc>
                     <catDesc>Does the software make adequate acknowledgement and credit to the
                        project contributors?</catDesc>
                     <category xml:id="te180">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te181">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te182">
                     <catDesc>Registered <ref target="#K3.9">cf. Catalogue 3.9</ref>
                     </catDesc>
                     <catDesc>Is the tool/software registered in a software repository?</catDesc>
                     <category xml:id="te183">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te184">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te185">
                     <catDesc>Possible contribution</catDesc>
                     <catDesc>If yes, can you contribute to the software development via the
                        repository/development platform?</catDesc>
                     <category xml:id="te186">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te187">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te188">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
               </category>
               <category>
                  <catDesc>Analysability, extensibility, reusability of the code</catDesc>
                  <category xml:id="te189">
                     <catDesc>Analysability <ref target="#K3.10">cf. Catalogue 3.10</ref>
                     </catDesc>
                     <catDesc>Can the code be analyzed easily (is it structured, commented,
                        following standards)?</catDesc>
                     <category xml:id="te190">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te191">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te192">
                        <catDesc>Unknown</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te193">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te194">
                     <catDesc>Extensibility <ref target="#K3.10">cf. Catalogue 3.10</ref>
                     </catDesc>
                     <catDesc>Can the code be extended easily (because there are contribution
                        mechanisms, attribution for changes and backward compatibility)?</catDesc>
                     <category xml:id="te195">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te196">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te197">
                        <catDesc>Unknown</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te198">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te199">
                     <catDesc>Reusability <ref target="#K3.10">cf. Catalogue 3.10</ref>
                     </catDesc>
                     <catDesc>Can the code be reused easily in other contexts (because there are
                        appropriate interfaces and/or a modular architecture)?</catDesc>
                     <category xml:id="te200">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te201">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te202">
                        <catDesc>Unknown</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te203">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te204">
                     <catDesc>Security and privacy <ref target="#K3.11">cf. Catalogue 3.11</ref>
                     </catDesc>
                     <catDesc>Does the software provide sufficient information about the treatment
                        of the data entered by the users?</catDesc>
                     <category xml:id="te205">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te206">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te207">
                     <catDesc>Supportability and maintenance <ref target="#K3.12">cf. Catalogue
                           3.12</ref>
                     </catDesc>
                     <catDesc>Is there information available whether the tool will be supported
                        currently and in the future?</catDesc>
                     <category xml:id="te208">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te209">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te210">
                     <catDesc>Citability <ref target="#K3.13">cf. Catalogue 3.13</ref>
                     </catDesc>
                     <catDesc>Does the tool supply citation guidelines (e.g. using the Citation File
                        Format)?</catDesc>
                     <category xml:id="te211">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te212">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
               </category>
               <category>
                  <catDesc>User interaction, GUI and visualization</catDesc>
                  <category xml:id="te213">
                     <catDesc>User profile <ref target="#K4.1">cf. Catalogue 4.1</ref>
                     </catDesc>
                     <catDesc>What kind of users are expected?</catDesc>
                     <category xml:id="te214">
                        <catDesc>Humanities researcher</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te215">
                        <catDesc>Computer scientist</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te216">
                        <catDesc>Digital humanist</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te217">
                        <catDesc>General public</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te218">
                     <catDesc>User interaction <ref target="#K4.1">cf. Catalogue 4.1</ref>
                     </catDesc>
                     <catDesc>What kind of user interactions are expected?</catDesc>
                     <category xml:id="te219">
                        <catDesc>Reading</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te220">
                        <catDesc>Text editing</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te221">
                        <catDesc>Text analysis</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te222">
                        <catDesc>Image editing</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te223">
                        <catDesc>Searching</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te224">
                        <catDesc>Visualization</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te225">
                        <catDesc>Comparing</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te226">
                        <catDesc>Compiling</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te227">
                     <catDesc>User Interface <ref target="#K4.1">cf. Catalogue 4.2 and 0.1.1</ref>
                     </catDesc>
                     <catDesc>What kind of interface does the tool provide?</catDesc>
                     <category xml:id="te228">
                        <catDesc>Graphical User Interface (GUI)</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te229">
                        <catDesc>Command Line Interface (CLI)</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te230">
                        <catDesc>Application Programming Interface (API)</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te231">
                     <catDesc>Visualization <ref target="#K3.13">cf. Catalogue 4.3</ref>
                     </catDesc>
                     <catDesc>Does the tool provide a particular visualizations (in terms of
                        analysis) of the input and/or the output data?</catDesc>
                     <category xml:id="te232">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="te233">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te234">
                     <catDesc>User empowerment <ref target="#K3.13">cf. Catalogue 4.4</ref>
                     </catDesc>
                     <catDesc>Is the user allowed to customize the functioning of the tool and the
                        output configuration?</catDesc>
                     <category xml:id="te235">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te236">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="te237">
                     <catDesc>Accessibility <ref target="#K4.5">cf. Catalogue 4.5</ref>
                     </catDesc>
                     <catDesc>Does the tool provide particular features for improving accessibility,
                        allowing „people with the widest range of characteristics and capabilities"
                        to use it?</catDesc>
                     <category xml:id="te238">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="te239">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
               </category>
            </taxonomy>
         </classDecl>
      </encodingDesc>
      <profileDesc>
         <langUsage>
            <language ident="en"/>
         </langUsage>
         <textClass>
            <keywords xml:lang="en">
               <term>generative ai</term>
               <term>tei/xml</term>
               <term>text encoding</term>
               <term>named entities</term>
               <term>text analysis</term>
               <term>digital editions</term>
               <term>digital humanities</term>
            </keywords>
         </textClass>
      </profileDesc>
   </teiHeader>
   <text>
      <front>
         <div type="abstract">
            <p>Large language models such as OpenAI’s ChatGPT have rapidly become prominent tools in
               academic contexts, including digital scholarly editing. Although not originally
               designed for editorial practice, they are increasingly integrated into experimental
               editorial workflows. This review assesses its potential to support key editorial
               tasks and surveys recent literature on their use in digital scholarly editing.
               Drawing on published case studies and our own experiments, we analyze the benefits
               and limitations of employing ChatGPT at different stages of creating and analyzing
               digital scholarly editions, including transcription, TEI encoding, and named-entity
               recognition. At the same time, the review addresses significant concerns. As a
               commercial and largely closed system, ChatGPT operates as a ‘black box’ that allows
               only indirect control through prompting, raising challenges for transparency and
               reproducibility in academic contexts. Issues of model bias and data governance must
               be carefully considered when integrating such tools into research workflows. ChatGPT
               should therefore be adopted cautiously and critically. Nevertheless, its capacity to
               lower technical barriers and to consolidate tasks that previously required multiple
               tools and advanced programming skills makes it, or similar artificial intelligence
               tools, a potentially valuable assistant in digital editing workflows.</p>
         </div>
      </front>
      <body>
         <div xml:id="div1">
            <head>Introduction</head>
            <p xml:id="p1">In the rapidly evolving landscape of the Digital Humanities, large
               language models (LLMs)<note xml:id="ftn1">LLMs are trained with deep-learning
                  algorithms on vast corpora of web pages, books and articles to learn the patterns
                  and structures of language. With multi-billion-parameter architectures, they are
                  able to generate context-aware text.</note> have become prominent tools for
               numerous tasks, including text analysis, classification, and language translation.
               This review examines ChatGPT’s capabilities as an assisting tool for digital
               scholarly editing tasks. ChatGPT was selected due to its growing media presence and
               widespread adoption within the humanities community, including institutional
               deployments at universities such as the University of Graz, where the authors are
                  affiliated.<note xml:id="ftn2">
                  <p>Martina Scholger and Roman Bleier are both affiliated with the Department of
                     Digital Humanities at the University of Graz, where they work in the field of
                     digital scholarly editing—Scholger as a senior scientist and Bleier as a
                     postdoctoral researcher. We thank Christopher Pollin of DH Craft for reading an
                     early draft of this article and for providing valuable feedback and helpful
                     suggestions, and Thea Schaaf for proofreading.</p></note>
            </p>
            <p xml:id="p2">Introduced in November 2022 (<ref target="#OpenAI2024" type="crossref"
                  >OpenAI 2024</ref>), the chatbot ChatGPT is a generative artificial intelligence
               (AI) system that communicates through natural language, processing user inputs—known
               as prompts—to produce textual responses. ChatGPT is developed by OpenAI, a company
               founded in 2015 in San Francisco by a group of machine learning experts, research
               engineers, and scientists.<note xml:id="ftn3"><ref target="#Brockman2015" type="crossref">Brockman,
                     Sutskever, and OpenAI 2015</ref>, here: <ref
                     target="https://web.archive.org/web/20241007222900/https://openai.com/blog/introducing-openai/"
                     >https://web.archive.org/web/20241007222900/https://openai.com/blog/introducing-openai/</ref>.
               </note> There is a huge interdisciplinary team of developers behind the system: the
               GPT-4 technical report lists 280 co-authors (<ref target="#OpenAI2024"
                  type="crossref">OpenAI 2024</ref>), and financial support is provided by
               individuals and companies. ChatGPT is offered in multiple subscription tiers and
               model variants, each with different capabilities, usage limits, and available tools
               such as web browsing, image generation, and data analysis. During the revision period
               for this article, the default models and available features changed notably across
               tiers, illustrating the platform’s rapid evolution.</p>
            <p xml:id="p3"> The chatbot can be used as an assisting tool for scholars in the process
               of editing, annotating, and curating (historical) texts. The authors evaluate ChatGPT
               primarily as practitioner-users, i.e., as editors working with the web-based
               graphical user interface, rather than as developers engaging with the underlying
               models or APIs. All experiments were performed using the ChatGPT web interface,
               specifically the GPT-4o model, accessed between July 2024 and July 2025, under both
               free and Plus tier access. The source material used in the experiments comes from
               digital edition projects in which the authors are involved, namely <emph>Joseph von
                  Hammer-Purgstall. Korrespondenz</emph> (<ref target="#Hoeflechner2025"
                  type="crossref">Höflechner et al. 2025</ref>) and <emph>Der Reichstag zu
                  Regensburg 1576</emph> (<ref target="#Leeb2023" type="crossref">Leeb et al.
                  2023</ref>). While the focus of the review is clearly on the usability and
               constraints of the AI tool for editorial work, ethical questions that editors might
               face are also discussed, such as issues of reproducibility and citability of stable versions, which
               poses challenges for the transparency and documentation of editorial decisions.
               However, given the pace of development in both models and interface features, this
               review represents a time-bound snapshot rather than a comprehensive assessment.</p>
         </div>
         <div xml:id="div2">
            <head>Methods and Implementation</head>
            <p xml:id="p4">The technical architecture of ChatGPT relies on Generative Pre-trained
               Transformer (GPT) models, which are fine-tuned for natural conversation using a
               combination of supervised learning and reinforcement learning from human feedback.
               These LLMs belong to the broader class of foundation models, which are designed to
               support multiple downstream applications rather than being optimized for a
               particular, narrowly defined task. Therefore, ChatGPT can in principle be applied to
               a wide range of tasks at different stages of a digital scholarly editing workflow.</p>
            <div xml:id="div2.1">
               <head>Training Data, Transparency, and Reproducibility</head>
               <p xml:id="p5">The exact training data of the underlying models is not publicly
                  disclosed, and the models themselves are not openly available. According to
                  OpenAI, training data consists of “information that is publicly available on the
                  internet, information that we license from third parties, and information that our
                  users or our human trainers provide”.<note xml:id="ftn4"><ref target="#OpenAI2025"
                        type="crossref">OpenAI 2025</ref>, here: <ref
                        target="https://web.archive.org/web/20240913163752/https://help.openai.com/en/articles/7842364-how-chatgpt-and-our-language-models-are-developed"
                        >https://web.archive.org/web/20240913163752/https://help.openai.com/en/articles/7842364-how-chatgpt-and-our-language-models-are-developed</ref>.
                  </note> This limited transparency has been widely criticized, particularly in
                  scholarly contexts, where the provenance of training data is an important concern.
                  Another significant limitation for scholarly work relates to reproducibility. Even
                  when identical prompts are used, ChatGPT does not reliably produce identical
                  outputs. This behavior reflects the inherent non-deterministic nature of LLMs,
                  which predict token probabilities in context based on the training data (<ref
                     type="crossref" target="#Ouyang2023">Ouyang et al. 2023</ref>). This
                  complicates the documentation, verification, and long-term traceability of
                  editorial decisions.</p>
               <p xml:id="p6">Another factor affecting reproducibility concerns the availability of
                  different model versions within the ChatGPT platform. As of June 2025, free-tier
                  users have access by default to GPT-4o, OpenAI’s flagship multimodal model, though
                  access is subject to usage limits. Once these limits are reached, usage
                  automatically defaults to a smaller, cost-efficient fallback. Users of
                  subscription tiers such as Plus, Pro, or Team receive higher usage limits and
                  access to a wider range of models through the model selector, including models
                  optimized for complex reasoning tasks, high-performance multimodal interaction,
                  and lightweight, cost-efficient processing. The presence of multiple model
                  versions within a single platform therefore introduces an additional layer of
                  unpredictability for scholarly workflows.</p>
            </div>
            <div xml:id="div2.2">
               <head>Interaction Model and Prompting</head>
               <p xml:id="p7">ChatGPT operates through a conversational interface in which users
                  interact with the system using natural language prompts. While text is the primary
                  input modality, interactions can also begin with images or voice. A prompt is the
                  instruction or query provided to the model, ranging from simple questions to
                  complex scenarios, directing the LLM in its response generation. In addition to
                  user prompts, the system relies on internal system prompts that shape the model
                  behavior, but remain invisible to users. Prompt engineering refers to the practice
                  of designing prompts to guide model outputs effectively. Considerations of prompt
                  length and structure are also relevant, as model inputs are processed as tokens
                  and subject to context window limits. There are various prompting techniques, such
                  as zero-shot, few-shot, and chain-of-thought prompting, each designed to approach
                  the model differently based on the complexity of the task (<ref
                     target="#Saravia2022" type="crossref">Saravia 2022</ref>). In editorial
                  contexts, careful prompting is essential for achieving consistent results,
                  particularly when tasks involve formalized output formats or domain-specific
                  conventions. Mastering prompt engineering has become its own discipline and is
                  particularly important in digital humanities contexts, where tasks frequently
                  involve specialized terminology, historical language material, and encoding
                  standards that require precise instructions (<ref target="#Saravia2022"
                     type="crossref">Saravia 2022</ref>, <ref target="#Pollin2025" type="crossref"
                     >Pollin 2025</ref>).</p>
               <p xml:id="p8">All inputs and outputs processed by ChatGPT are internally segmented
                  into tokens, which constitute the basic unit for both text processing and usage
                  accounting. <cit>
                     <quote> Tokens are the building blocks of text that OpenAI models process. They
                        can be as short as a single character or as long as a full word, depending
                        on the language and context. Spaces, punctuation, and partial words all
                        contribute to token counts. This is how the API internally segments your
                        text before generating a response.<note xml:id="ftn5"><ref
                              target="#OpenAI2025" type="crossref">OpenAI 2025</ref>, here: <ref
                              target="https://web.archive.org/web/20251012012828/https://help.openai.com/en/articles/4936856-what-are-tokens-and-how-to-count-them"
                              >https://web.archive.org/web/20251012012828/https://help.openai.com/en/articles/4936856-what-are-tokens-and-how-to-count-them</ref>.
                        </note>
                     </quote>
                  </cit></p>
               <p xml:id="p9">How exactly tokens are calculated is often not immediately intuitive
                  for users. OpenAI suggests that, as a rule of thumb, for English texts one token
                  corresponds to approximately four characters, or about three-quarters of a word.
                  Consequently, 100 tokens amount to roughly 75 English words. OpenAI provides an
                  online tokenizer that allows users to test how specific inputs are segmented into
                     tokens.<note xml:id="ftn6">
                     <ref
                        target="https://web.archive.org/web/20251008185403/https://platform.openai.com/tokenizer/"
                        >https://web.archive.org/web/20251008185403/https://platform.openai.com/tokenizer/</ref>.
                  </note> While this approximation is slightly vague, an additional complication is
                  that tokenization is language-dependent. This is especially relevant for digital
                  scholarly editing, which very often involves historical texts in languages other
                  than contemporary English.</p>
            </div>
            <div xml:id="div2.3">
               <head>Configuration and Personalization</head>
               <p xml:id="p10">Beyond prompt-level interaction, ChatGPT also allows users to
                  configure model behavior through customizable applications known as Custom GPTs.
                  For creating them, no programming knowledge is necessary. The configuration screen
                  allows you to enter a picture, a name of the GPT, a short description, detailed
                  instructions, a conversation starter to facilitate the start of a conversation,
                  and the upload of an extra knowledge base. When such files are provided, the
                  system can retrieve relevant passages from them during response generation,
                  thereby implementing a form of retrieval-augmented generation (RAG). It is
                  recommended to provide the additional knowledge in a minimalistic format (e.g.,
                  JSON or Markdown) to save tokens instead of ‘chatty’ formats like XML, where each
                  tag consumes tokens. While this built-in retrieval mechanism is suitable for
                  small-scale text documents, larger corpora typically require interfacing with
                  external databases.<note xml:id="ftn7"><ref target="#Saravia2022" type="crossref"
                        >Saravia 2022</ref>, here <ref
                        target="https://web.archive.org/web/20250808170700/https://www.promptingguide.ai/techniques/rag"
                        >https://web.archive.org/web/20250808170700/https://www.promptingguide.ai/techniques/rag</ref>.
                  </note> Custom GPTs can be kept for internal use only or shared with the broader
                  community; they remain bound to OpenAI’s infrastructure and do not constitute
                  independent editorial tools.</p>
               <p xml:id="p11">ChatGPT can be individually configured using ‘custom instructions’, a
                  personalization feature distinct from Custom GPTs, available in the user settings.
                  These allow users to provide details about their interests and working context and
                  to specify how the model should respond, for example, by indicating a preferred
                  tone or level of detail. The instructions persist across conversations so that the
                  user does not have to repeat these preferences in each prompt.</p>
            </div>
            <div xml:id="div2.4">
               <head>Input, Output, and Data Analysis Capabilities</head>
               <p xml:id="p12">ChatGPT can handle and process text in various data formats like
                  plain text, XML, HTML, JSON, CSV, or Markdown, as well as multimodal inputs such as image, video, and audio
                  as input. Likewise, it can generate output in most textual data formats;
                  in addition, newer multimodal models support synthesized audio output, while the generation
                  of standalone video files is not natively supported in the standard ChatGPT
                  interface. Advanced Data Analysis (ADA), an integrated capability of GPT-4-class models,
                  further expands its functionalities to the automatic generation of
                  Python code for performing exploratory data analysis tasks. It can process structured data formats,
                  including Excel, CSV, and JSON, and produce outputs as Python code, statistical summaries, visualizations,
                  charts, interactive tables, and more, thereby supporting eexploratory data analysis within a single environment</p>
               <p xml:id="p13">For developers, OpenAI provides convenient and well-documented access to its API through multiple interfaces, including
                  the programming language Python, the cURL command-line tool for making HTTP requests
                  to APIs, and Node.js, a widely used JavaScript runtime environment to build applications, provided
                  one has an API key. The API supports integration into a wide range of software systems, applications and services.
                  However, the focus of this article is the chatbot interface, and the API and its 
                  development capabilities will therefore not be discussed in detail.</p>
            </div>
            <div xml:id="div2.5">
               <head>Positioning within the LLM Landscape</head>
               <p xml:id="p14">ChatGPT exists within a broader and rapidly evolving ecosystem of
                  generative language models. Proprietary systems include Claude by Anthropic,
                  Gemini by Google, as well as models integrated into platforms like Microsoft
                  Copilot. At the same time, open-weight and open-source models are advancing
                  rapidly and in some benchmarks are even outperforming proprietary systems in
                  certain tasks (<ref type="crossref" target="#Chen2024">Chen et al. 2024</ref>).
                  Prominent examples include the Llama family developed by Meta, Mistral AI’s Mistral
                  and Mixtral models, and Alibaba’s Qwen series.</p>
               <p xml:id="p15">When assessing a language model’s openness, it is important to
                  differentiate between open-source models and open-weight models. Open source
                  refers to sharing the full source code, the underlying algorithms, training
                  methods, and data, while open-weight models only share the pretrained model
                  parameters, which allows use but limits transparency and control. Open-weight
                  models are easier to use but less transparent, while open-source promotes
                  transparency and allows modification, but also requires more developer effort
                     (<ref type="crossref" target="#Ramlochan2023">Ramlochan 2023</ref>). For
                  digital scholarly editing, these distinctions are relevant for sustainability,
                  inspectability, and long-term reuse. The current leading open-source models can be
                  consulted at the Chatbot Arena.<note xml:id="ftn8">An overview of leading chatbots
                     is provided by the ‘Chatbot Arena’ (<ref type="crossref" target="#Chiang2024"
                        >Chiang et al. 2024</ref>), an online platform that ranks LLMs based on
                     crowdsourced human preference evaluations.</note>
               </p>
            </div>
         </div>
         <div xml:id="div3">
            <head>Application for Digital Scholarly Editing</head>
            <p xml:id="p16">In conceptualizing how generative AI might support scholarly editing,
               the Institute for Documentology and Scholarly Editing (IDE) has proposed a processing
               pipeline (<ref target="#Pollinetal2025" type="crossref">Pollin et al.
                  2025</ref>), tracing the path from source material through edition as data to
               edition as publication via intermediate editorial products such as digital images,
               transcriptions, and the user interface. It further differentiates between
               structural tasks (e.g., planning, documentation, tool integration, quality control)
               and operational tasks (e.g., text recognition, entity recognition, normalization,
               enrichment). Mapping ChatGPT's capabilities onto this pipeline helps locate the
               stages at which it may be effectively integrated into editorial workflows, and where
               their limitations become apparent. We will attempt a brief evaluation of some tasks in this section.</p>
            <p xml:id="p17">We have already mentioned the multifaceted applications of ChatGPT as a tool to support 
               editorial work, ranging from text summarization and translation to automated XML/TEI annotation and other 
               natural language processing (NLP) tasks. It can also be used as a ‘buddy’ to provide
               constructive feedback on existing data models or XML/TEI code, helping to identify inconsistencies or 
               suggest alternative solutions. Furthermore, ChatGPT can assist in the development of small programs or scripts for the web presentation or 
               data analysis of an edition, utilizing <emph>Promptotyping</emph>, a prompt engineering method in LLM-based
               software development (<ref type="crossref" target="#Pollin2026">Pollin 2026</ref>).</p>
            <p xml:id="p18">From a utility perspective, ChatGPT primarily supports exploratory and
               preparatory stages of editorial work rather than final, authoritative decisions, as
               its non-deterministic nature and lack of stable versioning limit scholarly
               reproducibility. While this challenges academic rigor, the non-deterministic behavior
               can also be used as an advantage. Editors can generate multiple versions of the same
               output (e.g., alternative TEI encodings) and critically identify the optimal encoding
               approach. In this way, non-reproducibility can function as a form of digital
               hermeneutics, potentially transforming what appears to be a limitation into a tool
               for deeper interpretive engagement with editorial decisions.</p>
            
            <div xml:id="div3.1">
               <head>Examples and Current Uses of Generative AI in Digital Scholarly Editing</head>
               <p xml:id="p19">GPT models are generally considered not to be trained on specific
                  domains or tasks, although user-guided fine-tuning can be applied to that end.
                  They are general-purpose models that can assist in different tasks related to the
                  digital editing pipeline, from data creation to final publication. One area of
                  experiments includes custom GPTs, i.e., user-configured applications built on top
                  of a pre-trained GPT model. Examples include <emph>teiCrafter</emph>, an “expert
                  automaton for converting plain text to TEI XML” (<ref target="#Pollin2024"
                     type="crossref">Pollin 2024</ref>); <emph>TEI Scholar </emph>(<ref
                     type="crossref" target="#Jankovic">Jankovic</ref>); and <emph>TEI Lex 0
                     Converter </emph>(<ref type="crossref" target="#Miyagawa">Miyagawa</ref>).</p>
               <p xml:id="p20">Beyond individual tools, broader community efforts further illustrate
                  these developments. A workshop at the DHd 2024 conference in Passau, organized by
                  the Institute for Documentology and Scholarly Editing (IDE), provided a broad
                  overview of ongoing experiments with generative language models in digital
                  scholarly editing (<ref target="#Pollinetal2024" type="crossref">Pollin et al.
                     2024</ref>). The ten contributions covered a wide range of editorial tasks,
                  including transcription, OCR post-correction, markup generation, normalization,
                  named entity recognition, annotation, translation, and text summarization. As
                  demonstrated in Pollin's workshop series, generative AI can be applied across
                  diverse DH use-cases: from transforming unstructured data into TEI to generating
                  and modeling RDF data to data analysis and visualization (<ref
                     target="#Pollin2025" type="crossref">Pollin 2025</ref>). Alongside these
                  exploratory applications, research has emphasized the need for robust pipelines
                  and systematic evaluation in LLM-assisted scholarly workflows. Recent
                  contributions assess, for example, the quality and reliability of LLM-assisted TEI
                  encoding (<ref target="#Strutz2025a" type="crossref">Strutz and Vogeler
                  2025</ref>, <ref target="#Strutz2026a" type="crossref">Strutz forthcoming</ref>),
                  the automated handling and resolution of editorial interventions (<ref
                     target="#Strutz2025b">Strutz and Scholger 2025</ref>), and the automated
                  extraction and normalization of metadata from historical letter transcriptions
                     (<ref target="#Strutz2026b">Strutz and Scholger 2026</ref>). Galka and Vogeler
                  compare the integration of different LLMs within a workflow for adding named
                  entity recognition annotations (<ref type="crossref" target="#Galka2026"
                     >2026</ref>). These studies highlight both the potential of LLMs for complex,
                  context-sensitive tasks and the methodological challenges that remain.</p>
               <p xml:id="p21">In order to evaluate ChatGPT’s practical value for concrete editorial
                  tasks, we selected two common use cases: (1) converting plain text into
                  TEI-compliant XML, and (2) identifying and classifying named entities. All
                  experiments were performed using GPT-4o in the browser interface. For more
                  elaborate examples, we refer to slides including chat protocols in <ref
                     target="#Pollin2025" type="crossref">Pollin 2025</ref>.</p>
            </div>
            <div xml:id="div3.2">
               <head>Testing ChatGPT with a Letter from the <emph>Joseph von Hammer-Purgstall.
                     Korrespondenz</emph></head>
               <p xml:id="p22">In the first example, a letter from the digital edition <emph>Joseph
                     von Hammer-Purgstall. Korrespondenz</emph> (<ref target="#Hoeflechner2025"
                     type="crossref">Höflechner et al. 2025</ref>) was provided as plain text and
                  should be encoded following the <emph>Guidelines of the TEI</emph> (<ref
                     target="#TEI2026">TEI Consortium 2026</ref>). The correspondence spans the late
                  eighteenth to mid-nineteenth century and constitutes a multilingual scholarly
                  exchange within the context of Oriental studies. <cit>
                     <quote>Euer Gnaden, <lb/>Unterzeichneter1 bittet um die gnädige Erlaubnis,
                        künftigen Sonntag die Redoute2 besuchen zu dürfen3, weil er <lb/>1.) im
                        letzten und sechsten Jahre seiner Studien und bereits ein Jahr länger an der
                        Akademie ist als es seine Vorfahren waren, da ihnen diese Erlaubnis erteilt
                        wurde. <lb/>2.) auf das ihm jederzeit von S[einer] H[ochwohlgeboren] dem
                        Herrn Direktor erteilte Zeugnis seines guten Verhaltens und sittlichen
                        Betragen stolz ist, und sich daher schmeichelt, dass die Besorgnis einiger
                        daraus entstehenden üblen Folgen bei ihm nicht statt haben dürfte. <lb/>3.)
                        die Vorschrift einer für diesen Fall geforderten anständigen und sicheren
                        Begleitung nicht besser erfüllt haben könnte, indem er in der Gesellschaft
                        der Frau Schwester des Herrn Direktors sich befinden wird. <lb/>Den 20ten
                        Hornung 1794 <lb/>Joseph Hammer <lb/><lb/> 1.) PvTh D.2.1.14. <lb/><lb/>2.)
                        Eine Tanzveranstaltung oder auch ein eleganter Maskenball. Um welche
                        derartige Veranstaltung es sich hier handelt, ist nicht feststellbar.
                        <lb/><lb/> 3.) Die Erledigung durch Jenisch s. das nachfolgende Stück,
                        findet sich auf demselben Blatt wie die vorangegangene Bitte HPs mit dem
                        Vermerk „Von der Kanzlei den 20. Hornung 1794“.</quote>
                     <bibl><ref target="#Hammer1794" type="crossref">Hammer-Purgstall an Jenisch
                           1794</ref></bibl>
                  </cit>
               </p>
               <p xml:id="p23">
                  <figure xml:id="img1">
                     <graphic
                        url="http://ride.i-d-e.de/wp-content/uploads/issue_19/chatgpt/pictures/picture-1.png"/>
                     <head type="legend">Prompt instructions to convert a letter from Joseph von
                        Hammer-Purgstall to Bernhard von Jenisch into TEI.</head>
                  </figure>
                  <figure xml:id="img2">
                     <graphic
                        url="http://ride.i-d-e.de/wp-content/uploads/issue_19/chatgpt/pictures/picture-2.png"/>
                     <head type="legend">XML/TEI encoding of a letter from Hammer-Purgstall to
                        Jenisch generated by ChatGPT (GPT-4o).</head>
                  </figure> The plain text of the letter, together with the prompt (<ref
                     type="crossref" target="#img1">Fig. 1</ref>), was entered into the chat. In our
                  case, the prompt is structured in a task-oriented, rule-based format consisting of
                  five main components: (1) <emph>role framing</emph>, which assigns the model the
                  role of an expert in TEI encoding; (2) <emph>task definition</emph>, which
                  specifies the transformation of an unstructured letter into well-formed XML/TEI;
                  (3) <emph>encoding rules</emph>, which specify the selection and use of TEI
                  elements for structural and semantic components; (4) <emph>output
                     constraints</emph>, which restrict the form of the response; and (5)
                     <emph>emotional prompting</emph>, which encourages a step-by-step approach to
                  improve reliability and consistency of the output. The resulting XML/TEI encoding
                     (<ref type="crossref" target="#img2">Fig. 2</ref>) shows that the overall
                  letter structure is correctly identified and appropriate XML/TEI elements are
                  applied. Abbreviations are partially resolved, the date is normalized, and notes
                  are embedded in the correct position in the text, even though the notes in the
                  input text are placed at the end of the document. However, the recognition of
                  personal names was less reliable; in addition, a place name was labeled, although
                  only the tagging of person names was requested, suggesting that unwanted
                  annotations should be explicitly excluded in the prompt. Potential risks include
                  the incomplete preservation of the input text and the repositioning of structural
                  elements such as dates or signatures in the output. Such rearrangements may
                  suggest model-internal assumptions about typical letter layouts, possibly
                  reflecting generalized structural patterns learned during training (<ref
                     target="#Scholgeretal2024" type="crossref">Scholger, Strutz, and Pollin
                  2024</ref>).</p>
               <div xml:id="div3.3">
                  <head>Testing ChatGPT with a Letter from the Edition <emph>Der Reichstag zu
                        Regensburg 1576</emph></head>
                  <p xml:id="p24">In the second example, the same TEI annotation task was applied to
                     reports of envoys present at the Imperial Diet of the Holy Roman Empire that
                     was held in Regensburg in the year 1576 (<ref target="#Leeb2023"
                        type="crossref">Leeb et al. 2023</ref>). The envoys, Dr. Wolfgang Eulenbeck
                     and Dr. Andreas Paulus, reported regularly to Prince-elector (Kurfürst) August
                     von Sachsen, who was not present at the Imperial Diet. The form and structure
                     of these reports are very similar to the above letter from the <emph>Joseph von
                        Hammer-Purgstall. Korrespondenz</emph>. However, the significant difference
                     is that they were written three centuries earlier, in Early New High German.
                     The correspondence between the envoys and August von Sachsen is published in
                     the edition <emph>Der Reichstag zu Regensburg 1576</emph>.</p>
                  <p xml:id="p25"> The following quote shows the plain text of the letter from May 9
                     1576, to August von Sachsen: <cit>
                        <quote> Neunden Maii, Regenspurgk rhäte. Präs. Annaburg, 12. Maii anno 76.
                           Zu s. kfl. Gn. henden.<lb/> Durchlauchtigster hochgeborner churfurst,
                           ewern kfl. Gn. seint unsere underthenigste gehorsame dienste jeder zeit
                           mit trewem vleiß zuvorn. Gnedigster herre.<lb/> Auf euer kfl. Gn.
                           gnedigsten bevelch und uns zugeschickter instruction haben wir uns aufn
                           wegk nach Regensburgk erhoben, und seint gestern umb acht schlage vor
                           mittage alhier ankommen. Und wiewol wir under wegs verstendigt, als solte
                           die röm. ksl. Mt. auf den vierzehenden tag ditz monats Maii alhie
                           angelangen, so werden wir doch durch des Reichs marschalch alhier
                           berichtet, das sich irer ksl. Mt. aufbruch zu Wyen bis in mitten ermelts
                           monats verweilett, und ire Mt. wenig vor ende desselben alhier ankommen
                           werden, inmassen euer kfl. Gn. aus inligender copey der höchstgedachten
                           ksl. Mt. schreiben an den bischoff [1v] alhier, item hern Conraden zu
                           Pappenheim und doctor Viecheussern gnedigst haben zuersehen.<lb/> So
                           thuen euern kfl. Gn. wir hirbey underthenigst ein vorzeichnus ubersenden,
                           was vor gesandten (derer doch wenig sein) bis auf itzo alhier
                           angelangt.<lb/> Und, euer kfl. Gn. mit underthenigstem gehorsamb trewe
                           dienste zuleisten, seint wir schuldig und geflissen. Datum Regensburgk,
                           den neunden Maii anno 76.<lb/> Ewer kfl. Gn.<lb/> underthenigste
                           gehorsame<lb/> Wolffgang Eylenbeck, Dr.<lb/> Andreas Paull
                           propria[?]</quote>
                        <bibl><ref target="#Bericht1576" type="crossref">Bericht: Dr. Wolfgang
                              Eulenbeck und Dr. Andreas Paulus an Kurfürst August von Sachsen,
                              1576-05-09</ref></bibl>
                     </cit>
                  </p>
                  <p xml:id="p26">
                     <figure xml:id="img3">
                        <graphic
                           url="http://ride.i-d-e.de/wp-content/uploads/issue_19/chatgpt/pictures/picture-3.png"/>
                        <head type="legend">The letter to August von Sachsen encoded in TEI using
                           ChatGPT (GPT-4o). The entire second paragraph was left out in order to
                           fit the beginning and end on the picture.</head>
                     </figure> The same prompt instructions as in <ref type="crossref"
                        target="#img1">Fig. 1</ref> were used together with the plain text of the
                     letter. However, the statement “keep the original language” had to be added to
                     ensure that the source text was not normalized to standard German, which
                     happened during the initial run. The result in <ref type="crossref"
                        target="#img3">Fig. 3</ref> shows that, even with a historical language like
                     Early New High German texts, ChatGPT identifies the structure of the document
                     reasonably well.</p>
                  <p xml:id="p27"> Close observation of the result shows that some text is missing.
                     For some reason, the part of the opener indicating when the letter was
                     presented to August von Sachsen: ‘Präs. Annaburg, 12. Maii anno 76’ is missing.
                     Furthermore, identification and expansion of abbreviations is a challenge.
                     While abbreviations, such as ‘s.’, ‘Mt.’ and ‘kfl.’ are correctly resolved,
                     others were not even identified as abbreviations, e.g., ‘Gn.’, or words were
                     incorrectly identified as abbreviations, e.g., ‘ewern’, ‘bevelch’,
                     ‘instruction’. This can easily be resolved by providing a list of the
                     abbreviations used in editions of the Imperial Diets.<note xml:id="ftn9">Such
                        a list is provided by every edition of the Imperial Diets: e.g., <ref
                           target="https://gams.uni-graz.at/o:rta1576.bt17331b5u"
                           >https://gams.uni-graz.at/o:rta1576.bt17331b5u</ref>. </note> Dates are
                     precisely tagged and correctly normalized using the <code>@when</code>
                     attribute. However, ChatGPT does not automatically take the Gregorian calendar
                     reform into consideration. It has to be explicitly mentioned to add
                        <code>@calendar</code>.</p>
                  <p xml:id="p28">
                     <figure xml:id="img4">
                        <graphic
                           url="http://ride.i-d-e.de/wp-content/uploads/issue_19/chatgpt/pictures/picture-4.png"/>
                        <head type="legend">First result from ChatGPT trying to identify persons and
                           places in the letter of 1576. Wrongly identified places are
                           highlighted.</head>
                     </figure>
                     <figure xml:id="img5">
                        <graphic
                           url="http://ride.i-d-e.de/wp-content/uploads/issue_19/chatgpt/pictures/picture-5.png"/>
                        <head type="legend">Geoname references of the places generated by
                           ChatGPT.</head>
                     </figure> The tagging of people and places is also fine, but the identification
                     and linking to authority files, as asked in the prompt, is missing. When asked
                     to identify people and places and list them in a table with the columns (1.
                     original name as found in the letter, 2. type of entity, 3. normalized name, 4.
                     reference to an authority file, such as GND, VIAF or Wikidata) the result shows
                     that at first, only one person could be correctly identified, Wolfgang
                     Eylenbeck, ‘GND 104287020 (also VIAF 32430582)’. ChatGPT also provides the link
                     to sources for the identification: ‘link.springer.com’ and
                     ‘deutsche-biographie.de’. However, only the link to the <emph>Deutsche
                        Biographie</emph> (‘<ref
                        target="https://www.deutsche-biographie.de/pnd104287020.html"
                        >https://www.deutsche-biographie.de/pnd104287020.html</ref>’) provides
                     additional information about Eylenbeck and the references to the correct
                     authority files. After being asked again with consideration of the date of the
                     source, ChatGPT identifies ‘Conrad zu Pappenheim’ (Conrad von Pappenheim)
                     correctly with GND and VIAF identifiers. The other references to people seem to
                     be too vague. In the case of ‘doctor Viecheussern’, the Imperial
                     Vice-Chancellor Sigismund Viehauser (oder Vieheuser), the very particular
                     variance of the name could be the reason. It is also interesting that ChatGPT
                     was not able to correctly identify the place names mentioned, although it
                     recognizes that ‘Regenspurgk’ refers to ‘Regensburg’ and ‘Wyen’ to ‘Wien
                     (Vienna)’. The GND identifiers provided by ChatGPT for the two places do not
                     actually exist (<ref type="crossref" target="#img4">Fig. 4</ref>). However, if
                     asked to provide Geoname references for the places, both are correctly
                     identified (<ref type="crossref" target="#img5">Fig. 5</ref>).</p>
               </div>
            </div>
            <div xml:id="div4">
               <head>User Experience and Ethical Considerations</head>
               <div xml:id="div4.1">
                  <head>Access and User Interface</head>
                  <p xml:id="p29">ChatGPT can be accessed via the OpenAI website, and an API is
                     available for programmatic use. The tool requires minimal setup, and the web
                     interface is minimalistic and straightforward. It works well on all modern web
                     browsers, and a ChatGPT app is available for mobile devices. Users require
                     internet access and an OpenAI account. The interface is designed primarily for
                     conversational interaction—asking questions and receiving responses—and keeps
                     this core functionality readily accessible. Critical remarks have been raised,
                     however, regarding its simplicity and limited customization options (e.g., <ref
                        target="#Sebastian2023" type="crossref">Sebastian 2023</ref>). Additional
                     services beyond the free tier, including expanded API usage and processing
                     capabilities, are only available under a pay plan based on OpenAI’s token
                        system.<note xml:id="ftn10">OpenAI uses a token system for input, output,
                        and training usage. <ref
                           target="https://web.archive.org/web/20260314111058/https://chatgpt.com/pricing/"
                           >https://web.archive.org/web/20260314111058/https://chatgpt.com/pricing/</ref>.
                        But this constantly changes.</note> This makes it less attractive for
                     sustained scholarly work and creates unequal conditions, as not all academics
                     or projects might have the resources to cover the costs. It is also worth
                     noting that access to ChatGPT varies globally.<note xml:id="ftn11">For a brief
                        period of time in 2023 even in Italy it was banned due to issues with the
                        data protection regulations, DigitalTrends: <ref
                           target="https://web.archive.org/web/20260316110636/https://www.digitaltrends.com/computing/these-countries-chatgpt-banned/"
                           >https://web.archive.org/web/20260316110636/https://www.digitaltrends.com/computing/these-countries-chatgpt-banned/</ref>.
                        See also a recent article (June 2024) about China: <ref
                           target="https://web.archive.org/web/20240630064038/https://edition.cnn.com/2024/06/21/tech/apple-ai-chatgpt-ban-china/index.html"
                           >https://web.archive.org/web/20240630064038/https://edition.cnn.com/2024/06/21/tech/apple-ai-chatgpt-ban-china/index.html</ref>.
                     </note> In regions where the tool is restricted, such as China, alternatives
                     like DeepSeek and Ernie Bot are available (<ref target="#Yang2023"
                        type="crossref">Yang 2023</ref>, <ref target="#Wikipedia2024"
                        type="crossref">Wikipedia contributors 2024</ref>). While these tools offer
                     similar functionalities, their effectiveness for digital scholarly editing
                     would require separate evaluation.</p>
               </div>
               <div xml:id="div4.2">
                  <head>Documentation, Multilinguality, and Accessibility</head>
                  <p xml:id="p30">The various language models used within ChatGPT, and their
                     differences, are documented and compared on the OpenAI website.<note
                        xml:id="ftn12">
                        <ref
                           target="https://web.archive.org/web/20260317093543/https://developers.openai.com/api/docs/models"
                           >https://web.archive.org/web/20260317093543/https://developers.openai.com/api/docs/models</ref>.</note>
                     OpenAI also has a help center and maintains a developer forum, where mostly
                     API-related issues are discussed. ChatGPT has a big user community and is
                     widely used; therefore, if you run into a general problem, the chance is very
                     high that someone else already had a similar problem, and the solution can be
                     found online. OpenAI also provides documentation and guidelines for the use of
                     the tool. For instance, guidelines for prompt engineering that explain
                     strategies and suggestions for crafting effective prompts to get better results
                     from ChatGPT.<note xml:id="ftn13"><ref
                           target="https://web.archive.org/web/20260308121716/https://developers.openai.com/api/docs/guides/prompt-engineering"
                           >https://web.archive.org/web/20260308121716/https://developers.openai.com/api/docs/guides/prompt-engineering</ref>.</note>
                     In addition to the material provided by OpenAI, numerous introductions and
                     documentation about working with ChatGPT were developed by individuals,
                     institutions, and organizations all over the world, including subject-specific
                     introductions for Digital Humanities and digital scholarly editing (e.g. <ref
                        target="#Pollin2025" type="crossref">Pollin 2025</ref>).</p>
                  <p xml:id="p31">ChatGPT is described as a multilingual chatbot that can
                     communicate in over 50 languages.<note xml:id="ftn14">The chatbot and its user
                        interface are constantly evolving and updated. OpenAI: How to use ChatGPT in
                        a language other than English (alpha), <ref
                           target="https://help.openai.com/en/articles/8357869-how-to-use-chatgpt-in-a-language-other-than-english-alpha"
                           >https://help.openai.com/en/articles/8357869-how-to-use-chatgpt-in-a-language-other-than-english-alpha</ref>.
                     </note> It also provides the possibility to translate from one language into
                     another, making it a competitor for Google Translate, DeepL, and similar
                     services (<ref target="#Quillen2023" type="crossref">Quillen 2023</ref>; <ref
                        target="#PCMAG2023" type="crossref">PCMAG 2023</ref>). The speech-to-text
                     Audio API based on the Whisper model provides support for many languages: while
                     it was trained on 98 languages, for only about 58 of them is the word error
                     rate lower than 50%—a limitation relevant for projects involving non-English or
                     historical language material.<note xml:id="ftn15">OpenAI: Speech to text: <ref
                           target="https://platform.openai.com/docs/guides/speech-to-text"
                           >https://platform.openai.com/docs/guides/speech-to-text</ref>; <ref
                           target="https://platform.openai.com/docs/guides/speech-to-text/supported-languages"
                           >https://platform.openai.com/docs/guides/speech-to-text/supported-languages</ref>.
                     </note></p>
                  <p xml:id="p32">AI tools, including ChatGPT, are frequently discussed in the
                     context of accessibility and the provision of barrier-free content. The OpenAI
                     web interface is simplistic and screen-reader friendly. But the actual benefit
                     comes from the use of the ChatGPT API in various new applications. For
                     instance, such systems can generate automated descriptions of images, real-time
                     captions, and simplify complex texts into easier language.<note xml:id="ftn16">
                        <ref
                           target="https://web.archive.org/web/20260311135431/https://netzpolitik.org/2023/gpt-4-das-naechste-grosse-ding-fuer-digitale-zugaenglichkeit/"
                           >https://web.archive.org/web/20260311135431/https://netzpolitik.org/2023/gpt-4-das-naechste-grosse-ding-fuer-digitale-zugaenglichkeit/</ref>.
                     </note></p>
               </div>
               <div>
                  <head>Ethical Dimensions</head>
                  <p xml:id="p33"> There is a broad spectrum of ethical concerns being discussed in
                     the context of AI use. Applying ChatGPT in an editorial workflow should
                     therefore be carefully considered, and not only its benefits but also its
                     broader implications must be taken into account. For instance, the increase in
                     power consumption of technology companies and the building of enormous data
                     centers cause environmental issues, which call for sustainable solutions when
                     adopting AI in daily work (<ref type="crossref" target="#Rohde2024">Rohde et
                        al. 2024</ref>).</p>
                  <p xml:id="p34"> The responsibility for output that an AI tool produces is
                     particularly important in an editorial context. ChatGPT and similar tools can
                     create image-based transcriptions, translations, and, as we have seen, also
                     XML/TEI markup. Nevertheless, the tool may also introduce errors and
                     interpretations of the source material not intended by the editor. Like in all
                     AI-driven workflows, also in editorial practices, the concept of trustworthy
                     AI, focusing on transparency, accountability, reliability, and fairness, should
                     also be considered (<ref target="#AIHLEG2019" type="crossref">AI HLEG
                        2019</ref>, <ref target="#Pope2024" type="crossref">Pope 2024</ref>). A
                     comprehensive overview and analysis of the various discussions surrounding the
                     ethical dimensions is provided by Stahl and Eke (<ref target="#Stahl2024"
                        type="crossref">2024</ref>). Our final section focuses primarily on
                     questions of data governance, transparency through citation, and bias.</p>
                  <p xml:id="p35">OpenAI assures its users that all data shared with ChatGPT is
                     encrypted, and that inputs and outputs they receive are rightfully theirs.<note
                        xml:id="ftn17">
                        <ref
                           target="https://web.archive.org/web/20260312100111/https://openai.com/enterprise-privacy/"
                           >https://web.archive.org/web/20260312100111/https://openai.com/enterprise-privacy/</ref>.</note>
                     Nevertheless, there are concerns that OpenAI uses input data for training
                     purposes, that sensitive information may end up in the company’s database and
                     become available to other users, and that OpenAI collects substantial data
                     about its users and their behavior (<ref target="#MertonMcCann2023"
                        type="crossref">Merton-McCann 2023</ref>).</p>
                  <p xml:id="p36">In academic contexts—research, academic writing, and teaching—the
                     question of how to cite (and acknowledge) the use of ChatGPT poses several
                     issues. Conversations are tightly bound to a user account, and there are no
                     permalinks, no DOI, and no URL that allows for persistent sharing. There is not
                     yet a general consensus on how to cite ChatGPT conversations.<note
                        xml:id="ftn18">As an example we provide here the recommendation by the
                        University of Graz, last update 18.08.2025: <ref
                           target="https://lehren-und-lernen-mit-ki.uni-graz.at/de/ki-nutzung-kennzeichnen/"
                           >https://lehren-und-lernen-mit-ki.uni-graz.at/de/ki-nutzung-kennzeichnen/</ref>.</note>
                     However, ChatGPT is usually not considered an author. This also means that
                     ChatGPT—like any AI—cannot claim copyright, and any AI-generated output is
                     automatically considered public domain (<ref target="#Scholger2025"
                        type="crossref">Scholger 2025</ref>). APA, for example, suggests that
                     ‘chats’ with an AI cannot be cited as personal communications, as there is no
                     person communicating.<note xml:id="ftn19">‘Unfortunately, the results of a
                        ChatGPT “chat” are not retrievable by other readers, and although
                        nonretrievable data or quotations in APA Style papers are usually cited as
                        personal communications, with ChatGPT-generated text there is no person
                        communicating.’ <ref
                           target="https://apastyle.apa.org/blog/how-to-cite-chatgpt"
                           >https://apastyle.apa.org/blog/how-to-cite-chatgpt</ref>. </note> It is
                     typically recommended to include the prompt or the entire conversation for
                     reference, for instance in an appendix.<note xml:id="ftn20">APA policy on the
                        use of generative artificial intelligence (AI) in scholarly materials, in:
                           <emph>APA Publishing Policies (Aug. 2023)</emph>: <ref
                           target="https://web.archive.org/web/20260301102507/https://www.apa.org/pubs/journals/resources/publishing-policies?tab=3"
                           >https://web.archive.org/web/20260301102507/https://www.apa.org/pubs/journals/resources/publishing-policies?tab=3</ref>.
                     </note> This reminds us of the recommendations from the early 2000s to print
                     out entire websites and attach them to a publication—an approach that can
                     quickly become unwieldy, as conversations with ChatGPT can be quite
                     extensive.</p>
                  <p xml:id="p37">Finally, we briefly address the question of bias. Even if we
                     ‘talk’ to a machine, ChatGPT is not objective. The models are trained on an
                     enormous amount of data, most of it from a North American and European context,
                     and the biases introduced through that data influence its responses. Gender,
                     racial, religious, age, or political bias, and other negative behaviors have
                     been identified and criticized.<note xml:id="ftn21">See for instance examples
                        on the UNESCO website (<ref target="#UNESCO2023" type="crossref">UNESCO
                           2023</ref>); on the matter see also the end of the keynote lecture by
                        Pierazzo (<ref type="crossref" target="#Pierazzo2024">2024</ref>).</note> 
                     OpenAI provides a disclaimer about bias and stereotypes in
                     ChatGPT responses on its website, suggesting that users should be careful with
                     generated content, particularly when dealing with culturally sensitive or
                     historically situated material.<note xml:id="ftn22"><ref target="#OpenAI2025"
                           type="crossref">OpenAI 2025</ref>, here: <ref
                           target="https://web.archive.org/web/20260311133649/https://help.openai.com/en/articles/8313359-is-chatgpt-biased"
                           >https://web.archive.org/web/20260311133649/https://help.openai.com/en/articles/8313359-is-chatgpt-biased</ref>.</note>
                  </p>
               </div>
            </div>
            <div xml:id="div6">
               <head>Conclusion</head>
               <p xml:id="p38">ChatGPT is not a tool that was explicitly developed with the digital
                  humanities or the scholarly editing community in mind. Nevertheless, it has a wide
                  range of potential applications for researchers and editors, and can support
                  different stages of the development or analysis of digital editions. It can assist
                  with transcription and data creation, support the development of scripts for data
                  processing and analysis, and facilitate related tasks.</p>
               <p xml:id="p39">There is still relatively little research and benchmarks on the use
                  of LLMs for editorial purposes, and the possibilities of what can be done with
                  ChatGPT and similar AI tools are constantly changing. We are aware that the
                  evaluation of such technology is only a snapshot that might not be relevant in a
                  couple of months, and that all predictions for future developments are quite
                  difficult, as development moves so quickly. As we outlined in the article, we
                  chose to evaluate ChatGPT (GPT-4o) over other LLMs, as it is well-known and
                  currently widely used by humanities scholars.</p>
               <p xml:id="p40">Several limitations significantly constrain the use of ChatGPT as a
                  tool for scholarly editing. First, the development of the tool is closed off as it
                  is a commercial product. For editors, this results in a black-box situation that
                  can be vaguely controlled using prompts. If prompts are not carefully crafted, the
                  results can be misleading or even totally wrong. Second, it remains unclear how
                  OpenAI handles the data provided by users and to what extent the data is used to
                  train future models. Therefore, users have been warned to be careful and not to
                  share sensitive or unpublished material with AI. For scholarly editing, this
                  significantly restricts the range of sources for which ChatGPT can be used
                  responsibly. Third, while the chatbot interface is suitable for small-scale
                  experiments and exploratory tasks, complex multi-stage editorial workflows for an
                  entire corpus—from the TEI encoding to the recognition of named entities and their
                  enrichment with norm data—can only be effectively implemented via the API. The
                  associated costs cannot be covered by every project and also contradict the
                  principles of an open-knowledge society and equal access to research. This is why
                  it is so important that we focus more on developments in the area of open-source
                  LLMs in the future. Finally, ethical issues caused by the bias in the models have
                  to be kept in mind when incorporating these tools into scholarly workflows.</p>
               <p xml:id="p41">The use cases and literature presented in this review demonstrate
                  ChatGPT’s high potential as an assistant for digital editing. Tasks that
                  previously required several tools and technical expertise can now be performed
                  with comparatively little effort using carefully designed prompting instructions.
                  At the same time, we have also discussed that the quality of the results can
                  diverge depending on the source material of the edition and a user’s ability to
                  craft ‘good prompts’. In any case, a human editor must remain in the loop to
                  control, evaluate, and, if necessary, further process the output. This is
                  especially highlighted by our little experiment using German texts from two
                  different historical language periods. It shows that ChatGPT works less
                  effectively with non-standard and historical language material. As models continue
                  to improve and open-source alternatives mature, the more pressing question for the
                  digital editing community is no longer whether to engage with these tools, but how
                  to use them in transparent, critically informed, and methodologically rigorous
                  ways.</p>
            </div>
         </div>
      </body>
      <back>
         <div type="bibliography">
            <listBibl>
               <bibl xml:id="AIHLEG2019">AI HLEG. 2019 “Ethics Guidelines for Trustworthy AI.” <ref
                     target="https://web.archive.org/web/20260324125714/https://digital-strategy.ec.europa.eu/en/library/ethics-guidelines-trustworthy-ai"
                     >https://web.archive.org/web/20260324125714/https://digital-strategy.ec.europa.eu/en/library/ethics-guidelines-trustworthy-ai</ref>.</bibl>
               <bibl xml:id="Bericht1576">Bericht: Dr. Wolfgang Eulenbeck und Dr. Andreas Paulus an
                  Kurfürst August von Sachsen, 1576-05-09. In <emph>Der Reichstag zu Regensburg
                     1576: D. Berichte und Weisungen</emph>, edited by Josef Leeb, Christiane
                  Neerfeld, Eva Ortlieb, Florian Zeilinger, Roman Bleier, Gabriele Haug-Moritz,
                  Georg Vogeler. 2023. Graz. <ref
                     target="https://web.archive.org/web/20260320100933/https://gams.uni-graz.at/o:rta1576.edd1e7d24431/sdef:TEI/get?mode=lesetext"
                     >https://web.archive.org/web/20260320100933/https://gams.uni-graz.at/o:rta1576.edd1e7d24431/sdef:TEI/get?mode=lesetext</ref>.</bibl>
               <bibl xml:id="Brockman2015">Brockman, Greg, Ilya Sutskever, and OpenAI. 2015. “Introducing OpenAI.” <ref
                     target="https://web.archive.org/web/20241007222900/https://openai.com/blog/introducing-openai/"
                     >https://web.archive.org/web/20241007222900/https://openai.com/blog/introducing-openai/</ref>.
               </bibl>
               <bibl xml:id="Chen2024">Chen, Hailin, Fangkai Jiao, Xingxuan Li, Chengwei Qin,
                  Mathieu Ravaut, Ruochen Zhao, Caiming Xiong, and Shafiq Joty. 2024. “ChatGPT's
                  One-year Anniversary: Are Open-Source Large Language Models Catching up?”
                     <emph>arXiv</emph>. <ref target="https://doi.org/10.48550/arXiv.2311.16989"
                     >https://doi.org/10.48550/arXiv.2311.16989</ref>.</bibl>
               <bibl xml:id="Chiang2024">Chiang, Wei-Lin, Lianmin Zheng, Ying Sheng, Lisa Dunlap,
                  Anastasios Angelopoulos, Christopher Chou, Tianle Li, and Siyuan Zhuang. 2024.
                  “Chatbot Arena: An Open Platform for Evaluating LLMs by Human Preference.”
                     <emph>arXiv</emph>. <ref target="https://doi.org/10.48550/arXiv.2403.04132"
                     >https://doi.org/10.48550/arXiv.2403.04132</ref>.</bibl>
               <bibl xml:id="Chudleigh2024">Chudleigh, Sarah. 2024. “Alles, was Sie über GPT wissen
                  sollten.” <ref
                     target="https://web.archive.org/web/20250608124031/https://botpress.com/de/blog/everything-you-should-know-about-gpt-5"
                     >https://web.archive.org/web/20250608124031/https://botpress.com/de/blog/everything-you-should-know-about-gpt-5</ref>.</bibl>
               <bibl xml:id="Galka2026">Galka, Selina, and Georg Vogeler. 2026. “Annotating,
                  projecting, and interpreting named entities in digital scholarly editions with
                  LLMs.” <emph>International Journal of Digital Humanities</emph>. <ref
                     target="https://doi.org/10.1007/s42803-025-00114-8"
                     >https://doi.org/10.1007/s42803-025-00114-8</ref>. </bibl>
               <bibl xml:id="Hammer1794">Joseph von Hammer-Purgstall an Bernhard von Jenisch [Wien],
                  20.2.1794. In <emph>Joseph von Hammer-Purgstall. Korrespondenz</emph>, edited by
                  Walter Höflechner, Martina Scholger, Alexandra Wagner, Sabrina Strutz, and
                  Elisabeth Steiner. 2025. Graz. <ref target="http://hdl.handle.net/11471/559.20.1"
                     >http://hdl.handle.net/11471/559.20.1</ref>.</bibl>
               <bibl xml:id="Hoeflechner2025">Höflechner, Walter, Martina Scholger, Alexandra
                  Wagner, Sabrina Strutz, Elisabeth Steiner, eds. 2025. <emph>Joseph von
                     Hammer-Purgstall. Korrespondenz</emph>. Graz. <ref
                     target="http://hdl.handle.net/11471/559.20"
                     >http://hdl.handle.net/11471/559.20</ref>.</bibl>
               <bibl xml:id="Jankovic">Jankovic, Nikola. “TEI Scholar”. <ref
                     target="https://chatgpt.com/g/g-5yZrEY1A7-tei-scholar"
                     >https://chatgpt.com/g/g-5yZrEY1A7-tei-scholar</ref>, last accessed
                  10.01.2026.</bibl>
               <bibl xml:id="Leeb2023">Leeb, Josef, Christiane Neerfeld, Eva Ortlieb, Florian
                  Zeilinger, Roman Bleier, Gabriele Haug-Moritz, Georg Vogeler, eds. 2023. <emph>Der
                     Reichstag zu Regensburg 1576</emph>. Graz. <ref
                     target="https://web.archive.org/web/20260316120750/https://gams.uni-graz.at/context:rta1576"
                     >https://web.archive.org/web/20260316120750/https://gams.uni-graz.at/context:rta1576</ref>. </bibl>
               <bibl xml:id="MertonMcCann2023">Merton-McCann, Alex. 2023. “How To Manage Your
                  Privacy When Using ChatGPT or Other Generative AI.” <ref
                     target="https://web.archive.org/web/20240804100338/https://www.mcafee.com/blogs/internet-security/chatgpts-impact-on-privacy-and-how-to-protect-yourself/"
                     >https://web.archive.org/web/20240804100338/https://www.mcafee.com/blogs/internet-security/chatgpts-impact-on-privacy-and-how-to-protect-yourself/</ref>.</bibl>
               <bibl xml:id="Miyagawa">Miyagawa, So. “Lex 0 Converter”. <ref
                     target="https://chatgpt.com/g/g-kOuPR6Q7u-tei-lex-0-converter?ref=pluginsurf"
                     >https://chatgpt.com/g/g-kOuPR6Q7u-tei-lex-0-converter?ref=pluginsurf</ref>,
                  last accessed 10.01.2026.</bibl>
               <bibl xml:id="OpenAI2024">OpenAI. 2024 (v6). “GPT-4 Technical Report.”
                     <emph>arXiv</emph>. <ref target="https://arxiv.org/abs/2303.08774v6"
                     >https://arxiv.org/abs/2303.08774v6</ref>. </bibl>
               <bibl xml:id="OpenAI2025">OpenAI. 2025. “OpenAI Help Center.” <ref
                     target="https://web.archive.org/web/20250628133335/https://help.openai.com/en/"
                     >https://web.archive.org/web/20250628133335/https://help.openai.com/en/</ref>.</bibl>
               <bibl xml:id="Ouyang2023">Ouyang, Shuyin, Jie M. Zhang, Mark Harman, and Meng Wang.
                  2023. “LLM is Like a Box of Chocolates: the Non-determinism of ChatGPT in Code
                  Generation.” <emph>arXiv</emph>. <ref
                     target="https://doi.org/10.48550/arXiv.2308.02828"
                     >https://doi.org/10.48550/arXiv.2308.02828</ref>. </bibl>
               <bibl xml:id="PCMAG2023">PCMAG. 2023. “Google Translate vs. ChatGPT: Which One Is the
                  Best Language Translator?”. PCMAG, June 10, 2023. <ref
                     target="https://web.archive.org/web/20230610132257/https://www.pcmag.com/news/google-translate-vs-chatgpt-which-one-is-the-best-language-translator"
                     >https://web.archive.org/web/20230610132257/https://www.pcmag.com/news/google-translate-vs-chatgpt-which-one-is-the-best-language-translator</ref>. </bibl>
               <bibl xml:id="Pierazzo2024">Pierazzo, Elena. 2024. “From Digital to Computational
                  Scholarly Editing: Are We Ready for ChatGPT?” YouTube video, posted 05.03.2024.
                     <ref target="https://www.youtube.com/watch?v=4_PtwZiWVz0"
                     >https://www.youtube.com/watch?v=4_PtwZiWVz0</ref>, last accessed
                  10.01.2026.</bibl>
               <bibl xml:id="Pollin2024">Pollin, Christopher. 2024a. “teiCrafter.” <ref
                     target="https://web.archive.org/web/20250804030610/https://digedtnt.github.io/teiCrafter/"
                     >https://web.archive.org/web/20250804030610/https://digedtnt.github.io/teiCrafter/</ref>.</bibl>
               <bibl xml:id="Pollinetal2024">Pollin, Christopher, Martina Scholger, Patrick Sahle,
                  Georg Vogeler, Torsten Schaßan, Stefan Dumont, Franz Fischer, Ulrike
                  Henny-Krahmer, Christiane Fritze, Torsten Roeder, and Alexander Czmiel. 2024.
                  “Workshop Generative KI, LLMs und GPT bei digitalen Editionen.” <emph>DHd 2024 Quo
                     Vadis DH (DHd2024), Passau, Deutschland</emph>. <emph>Zenodo</emph>. <ref
                     target="https://doi.org/10.5281/zenodo.10893761"
                     >https://doi.org/10.5281/zenodo.10893761</ref>. </bibl>
               <bibl xml:id="Pollin2025">Pollin, Christopher. 2025. “Workshopreihe Angewandte
                  Generative KI in den (digitalen) Geisteswissenschaften.” (v1.1.0)
                     <emph>Zenodo</emph>. <ref target="https://doi.org/10.5281/zenodo.10647754"
                     >https://doi.org/10.5281/zenodo.10647754</ref>.</bibl>
               <bibl xml:id="Pollinetal2025">Pollin, Christopher, Franz Fischer, Patrick Sahle,
                  Martina Scholger, and Georg Vogeler. 2025. “When it was 2024 – Generative AI in
                  the Field of Digital Scholarly Editions.” <emph>Zeitschrift für digitale
                     Geisteswissenschaften</emph> 10. <ref
                     target="https://doi.org/10.17175/2025_008"
                     >https://doi.org/10.17175/2025_008</ref>. </bibl>
               <bibl xml:id="Pollin2026">Pollin, Christopher. 2026. “Promptotyping: Zwischen Vibe
                  Coding, Vibe Research und Context Engineering.” <emph>L.I.S.A. Wissenschaftsportal
                     Gerda Henkel Stiftung. Digitale Geschichte(n).</emph>
                  <ref
                     target="https://web.archive.org/web/20260601000000*/https://lisa.gerda-henkel-stiftung.de/digitale_geschichte_pollin"
                     >https://web.archive.org/web/20260601000000*/https://lisa.gerda-henkel-stiftung.de/digitale_geschichte_pollin</ref>. </bibl>
               <bibl xml:id="Pope2024">Pope, Niki. 2024. “What Is Trustworthy AI?” <emph>Nvidia
                     Blog</emph>. <ref
                     target="https://web.archive.org/web/20260324125112/https://blogs.nvidia.com/blog/what-is-trustworthy-ai/"
                     >https://web.archive.org/web/20260324125112/https://blogs.nvidia.com/blog/what-is-trustworthy-ai/</ref>. </bibl>

               <bibl xml:id="Quillen2023">Quillen, Sam. 2023. “How Many Languages Does ChatGPT
                  Speak?” <emph>Medium, Apr 27, 2023</emph>. <ref
                     target="https://web.archive.org/web/20240712110304/https://sjquillen.medium.com/how-many-languages-does-chatgpt-speak-bf5cfc35a586a"
                     >https://web.archive.org/web/20240712110304/https://sjquillen.medium.com/how-many-languages-does-chatgpt-speak-bf5cfc35a586a</ref>. </bibl>
               <bibl xml:id="Ramlochan2023">Ramlochan, Sunil. 2023. “Openness in Language Models:
                  Open Source vs Open Weights vs Restricted Weights.” <ref
                     target="https://web.archive.org/web/20250314093343/https://promptengineering.org/llm-open-source-vs-open-weights-vs-restricted-weights/"
                     >https://web.archive.org/web/20250314093343/https://promptengineering.org/llm-open-source-vs-open-weights-vs-restricted-weights/</ref>. </bibl>
               <bibl xml:id="Rohde2024">Rohde, Friederike, Josephin Wagner, Andreas Meyer, Philipp
                  Reinhard, Marcus Voss, Ulrich Petschow, and Anne Mollen. 2024. “Broadening the
                  perspective for sustainable artificial intelligence: sustainability criteria and
                  indicators for Artificial Intelligence systems.” <emph>Current Opinion in
                     Environmental Sustainability</emph> 66. <ref
                     target="https://doi.org/10.1016/j.cosust.2023.101411"
                     >https://doi.org/10.1016/j.cosust.2023.101411</ref>.</bibl>
               <bibl xml:id="Saravia2022">Saravia, Elvis. 2022ff. “Prompt Engineering Guide.” <ref
                     target="https://web.archive.org/web/20240316135941/https://github.com/dair-ai/Prompt-Engineering-Guide"
                     >https://web.archive.org/web/20240316135941/https://github.com/dair-ai/Prompt-Engineering-Guide</ref>. </bibl>

               <bibl xml:id="Scholgeretal2024">Scholger, Martina, Sabrina Strutz, and Christopher
                  Pollin. 2024. “Empowering Text Encoding with Large Language Models: Benefits and
                  Challenges.” <ref target="https://doi.org/10.5281/zenodo.13969082"
                     >https://doi.org/10.5281/zenodo.13969082</ref>. </bibl>
               <bibl xml:id="Scholger2025">Scholger, Walter. 2025. “Künstliche Intelligenz im
                  Spannungsfeld von Innovation und Regulierung.” <ref
                     target="https://doi.org/10.5281/zenodo.15790422"
                     >https://doi.org/10.5281/zenodo.15790422</ref>. </bibl>
               <bibl xml:id="Sebastian2023">Sebastian, Ebin. 2023. “Beyond the Clicks: A Closer Look
                  at ChatGPT’s User Interface Through Heuristic Lenses.” <emph>Medium (Nov 22,
                     2023)</emph>. <ref
                     target="https://web.archive.org/web/20240712083258/https://medium.com/@ebinsk000/beyond-the-clicks-a-closer-look-at-chatgpts-user-interface-through-heuristic-lenses-dee5560f9316"
                     >https://web.archive.org/web/20240712083258/https://medium.com/@ebinsk000/beyond-the-clicks-a-closer-look-at-chatgpts-user-interface-through-heuristic-lenses-dee5560f9316</ref>. </bibl>
               <bibl xml:id="Stahl2024">Stahl, Bernd Carsten, and Damian Eke. 2024. “The ethics of
                  ChatGPT – Exploring the ethical issues of an emerging technology.”
                     <emph>International Journal of Information Management</emph> 74. <ref
                     target="https://doi.org/10.1016/j.ijinfomgt.2023.102700"
                     >https://doi.org/10.1016/j.ijinfomgt.2023.102700</ref>.</bibl>
               <bibl xml:id="Strutz2025a">Strutz, Sabrina, and Georg Vogeler. 2025. “Towards an
                  Evaluation Framework for Assessing Large Language Models in Text Encoding.”
                     <emph>ADHO Digital Humanities Conference 2025 (DH 2025)</emph>.
                     <emph>Zenodo</emph>. <ref target="https://doi.org/10.5281/zenodo.16364518"
                     >https://doi.org/10.5281/zenodo.16364518</ref>.</bibl>
               <bibl xml:id="Strutz2025b">Strutz, Sabrina, and Martina Scholger. 2025. “Beyond
                  Rule-Based Processing: LLM-Assisted TEI Encoding of Editorial Interventions in
                  Historical Correspondence.” <emph>TEI Annual Conference and Members' Meeting 2025,
                     Jagielloninan University in Kraków</emph>. <emph>Zenodo</emph>. <ref
                     target="https://doi.org/10.5281/zenodo.17176474"
                     >https://doi.org/10.5281/zenodo.17176474</ref>.</bibl>
               <bibl xml:id="Strutz2026a">Strutz, Sabrina. forthcoming. “A Multi-Dimensional
                  Evaluation Framework for Assessing LLM Performance in TEI Encoding.” Journal of
                  Open Humanities Data.</bibl>
               <bibl xml:id="Strutz2026b">Strutz, Sabrina, and Martina Scholger. 2026. “LLM-Assisted
                  Metadata Extraction and Normalization for Historical Correspondence: A Multi-Stage
                  Pipeline Approach.” DHd 2026 <emph>Nicht nur Text, nicht nur Daten (DHd
                     2026)</emph>, Vienna. Zenodo. <ref
                     target="https://doi.org/10.5281/zenodo.18862770"
                     >https://doi.org/10.5281/zenodo.18862770</ref>.</bibl>
               <bibl xml:id="TEI2026">TEI Consortium (eds.) 2026: “Guidelines for Electronic Text
                  Encoding and Interchange.” Version 4.11.0. <ref
                     target="https://tei-c.org/Vault/P5/4.11.0/doc/tei-p5-doc/en/html/"
                     >https://tei-c.org/Vault/P5/4.11.0/doc/tei-p5-doc/en/html/</ref>.</bibl>
               <bibl xml:id="UNESCO2023">UNESCO. 2023. “Artificial Intelligence: examples of ethical
                  dilemmas”. <ref
                     target="https://web.archive.org/web/20240712082302/https://www.unesco.org/en/artificial-intelligence/recommendation-ethics/cases"
                     >https://web.archive.org/web/20240712082302/https://www.unesco.org/en/artificial-intelligence/recommendation-ethics/cases</ref>. </bibl>
               <bibl xml:id="Wikipedia2024">Wikipedia contributors. 2024. “ErnieBot.” <ref
                     target="https://web.archive.org/web/20240712104208/https://en.wikipedia.org/w/index.php?title=Ernie_Bot&amp;oldid=1232272722"
                     >https://web.archive.org/web/20240712104208/https://en.wikipedia.org/w/index.php?title=Ernie_Bot&amp;oldid=1232272722</ref>. </bibl>
               <bibl xml:id="Yang2023">Yang, Zeyi. 2023. “Chinese ChatGPT alternatives just got
                  approved for the general public.” <emph>MIT Technology Review (Aug 30,
                     2023)</emph>. <ref
                     target="https://web.archive.org/web/20240712104430/https://www.technologyreview.com/2023/08/30/1078714/chinese-chatgpt-ernie-government-approval/"
                     >https://web.archive.org/web/20240712104430/https://www.technologyreview.com/2023/08/30/1078714/chinese-chatgpt-ernie-government-approval/</ref>.
               </bibl>
            </listBibl>
         </div>
      </back>
   </text>
</TEI>
