<?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.14.1">
   <teiHeader>
      <fileDesc>
         <titleStmt>
            <title>Reviewing the bread and butter of CoReMa, Cooking Recipes of the Middle
               Ages</title>
            <author ref="https://orcid.org/0000-0002-8627-1367">
               <name>
                  <forename>Helena</forename>
                  <surname>Bermúdez Sabel</surname>
               </name>
               <affiliation>
                  <orgName>Université de Neuchâtel</orgName>
                  <placeName ref="https://www.geonames.org/2659496">Neuchâtel, Switzerland</placeName>
               </affiliation>
               <email>helena.bermudez@unine.ch</email>
            </author>
         </titleStmt>
         <publicationStmt>
            <publisher>Institut für Dokumentologie und Editorik e.V.</publisher>
            <date when="2021-11">November 2021</date>
            <idno type="URI">http://ride.i-d-e.de/issues/issue-14/corema</idno>
            <idno type="DOI">10.18716/ride.a.14.1</idno>
            <idno type="archive">https://github.com/i-d-e/ride/raw/master/issues/issue14/corema/corema.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-0001-7043-7820">Torsten Roeder</editor>
            <editor ref="https://orcid.org/0000-0003-1438-3236">Martina Scholger</editor>
            <editor ref="https://orcid.org/0000-0003-2852-065X" role="managing">Ulrike
               Henny-Krahmer</editor>
            <editor ref="https://orcid.org/0000-0001-8279-9298" role="managing">Frederike
               Neuber</editor>
            <biblScope unit="issue" n="14">Digital Scholarly Editions</biblScope>
            <idno type="URI">http://ride.i-d-e.de/issues/issue-14</idno>
            <idno type="DOI">10.18716/ride.a.14</idno>
         </seriesStmt>
         <notesStmt>
            <relatedItem type="reviewed_resource">
               <bibl>
                  <title>CoReMA: Cooking Recipes of the Middle Ages</title>
                  <editor>Helmut W. Klug</editor>
                  <respStmt>
                     <resp>Editor</resp>
                     <persName>Klug, Helmut W.</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Editor</resp>
                     <persName>Böhm, Astrid</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Editor</resp>
                     <persName>Steiner, Christian</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Editor</resp>
                     <persName>Eibinger, Julia</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Contributor</resp>
                     <persName>Raunig, Elisabeth</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Contributor</resp>
                     <persName>Ardesi, Denise</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Contributor</resp>
                     <persName>Laurioux, Bruno</persName>
                  </respStmt>
                  <respStmt>
                     <resp>Contributor</resp>
                     <persName>Montaigu, Corentin Poirier</persName>
                  </respStmt>
                  <date type="publication">2020-2022</date>
                  <idno type="URI">http://gams.uni-graz.at/corema</idno>
                  <date type="accessed">2021-04-31</date>
               </bibl>
            </relatedItem>
            <relatedItem type="reviewing_criteria">
               <bibl>
                  <ref target="http://www.i-d-e.de/criteria-version-1-1">Criteria for Reviewing
                     Scholarly Digital Editions</ref>
               </bibl>
            </relatedItem>
         </notesStmt>
         <sourceDesc>
            <p>born digital</p>
         </sourceDesc>
      </fileDesc>
      <encodingDesc>
         <classDecl>
            <taxonomy xml:base="http://www.i-d-e.de/publikationen/weitereschriften/criteria-version-1-1">
               <category>
                  <catDesc>Documentation</catDesc>
                  <category xml:id="se001">
                     <catDesc>Bibliographic description <ref target="#K1.2">cf. Catalogue 1.2</ref>
                     </catDesc>
                     <catDesc>Is it easily possible to describe the project bibliographically along
                        the schema "responsible editors, publishing/hosting institution, year(s) of
                        publishing"?</catDesc>
                     <category xml:id="se002">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se003">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se004">
                     <catDesc>Contributors <ref target="#K1.4">cf. Catalogue 1.4</ref>
                     </catDesc>
                     <catDesc>Are the contributors (editors, institutions, associates) of the
                        project fully documented?</catDesc>
                     <category xml:id="se005">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se006">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se007">
                     <catDesc>Contacts <ref target="#K1.5">cf. Catalogue 1.5</ref>
                     </catDesc>
                     <catDesc>Does the project list contact persons?</catDesc>
                     <category xml:id="se008">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se009">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se010">
                     <catDesc>Selection <ref target="#K2.1">cf. Catalogue 2.1</ref>
                     </catDesc>
                     <catDesc>Is the selection of materials of the project explicitly
                        documented?</catDesc>
                     <category xml:id="se011">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se012">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se013">
                     <catDesc>Reasonability of the selection<ref target="#K2.1">cf. Catalogue
                           2.1</ref>
                     </catDesc>
                     <catDesc>Is the selection by and large reasonable?</catDesc>
                     <category xml:id="se014">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se015">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se016">
                     <catDesc>Archiving of data <ref target="#K4.16">cf. Catalogue 4.16</ref>
                     </catDesc>
                     <catDesc>Does the documentation include information about the long term
                        sustainability of the basic data (archiving of the data)?</catDesc>
                     <category xml:id="se017">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se018">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se019">
                     <catDesc>Aims <ref target="#K3.1">cf. Catalogue 3.1</ref>
                     </catDesc>
                     <catDesc>Are the aims and purposes of the project explicitly
                        documented?</catDesc>
                     <category xml:id="se020">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se021">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se022">
                     <catDesc>Methods <ref target="#K3.1">cf. Catalogue 3.1</ref>
                     </catDesc>
                     <catDesc>Are the methods employed in the project explicitly
                        documented?</catDesc>
                     <category xml:id="se023">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se024">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se025">
                     <catDesc>Data model <ref target="#K3.7">cf. Catalogue 3.7</ref>
                     </catDesc>
                     <catDesc>Does the project document which data model (e.g. TEI) has been used
                        and for what reason?</catDesc>
                     <category xml:id="se026">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se027">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se028">
                     <catDesc>Help <ref target="#K4.15">cf. Catalogue 4.15</ref>
                     </catDesc>
                     <catDesc>Does the project offer help texts concerning the use of the
                        project?</catDesc>
                     <category xml:id="se029">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se030">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se031">
                     <catDesc>Citation <ref target="#K4.8">cf. Catalogue 4.8</ref>
                     </catDesc>
                     <catDesc>Does the project supply citation guidelines (i.e. how to cite the
                        project or a part of it)?</catDesc>
                     <category xml:id="se032">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se033">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se034">
                     <catDesc>Completion <ref target="#K4.16">cf. Catalogue 4.16</ref>
                     </catDesc>
                     <catDesc>Does the editon regard itself as a completed project (i.e. not promise
                        further modifications and additions)?</catDesc>
                     <category xml:id="se035">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se036">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se037">
                     <catDesc>Institutional curation <ref target="#K4.16">cf. Catalogue 4.16</ref>
                     </catDesc>
                     <catDesc>Does the project provide information about institutional support for
                        the curation and sustainability of the project?</catDesc>
                     <category xml:id="se038">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se039">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
               </category>
               <category>
                  <catDesc>Contents</catDesc>
                  <category xml:id="se040">
                     <catDesc>Previous edition <ref target="#K2.2">cf. Catalogue 2.2</ref>
                     </catDesc>
                     <catDesc>Has the material been previously edited (in print or
                        digitally)?</catDesc>
                     <category xml:id="se041">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se042">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se043">
                     <catDesc>Materials used <ref target="#K2.2">cf. Catalogue 2.2</ref>
                     </catDesc>
                     <catDesc>Does the edition make use of these previous editions?</catDesc>
                     <category xml:id="se044">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se045">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se046">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se047">
                     <catDesc>Introduction <ref target="#K4.15">cf. Catalogue 4.15</ref>
                     </catDesc>
                     <catDesc>Does the project offer an introduction to the subject-matter (the
                        author(s), the work, its history, the theme, etc.) of the project?</catDesc>
                     <category xml:id="se048">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se049">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se050">
                     <catDesc>Bibliography <ref target="#K2.3">cf. Catalogue 2.3</ref>
                     </catDesc>
                     <catDesc>Does the project offer a bibliography?</catDesc>
                     <category xml:id="se051">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se052">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se053">
                     <catDesc>Commentary <ref target="#K2.3">cf. Catalogue 2.3</ref>
                     </catDesc>
                     <catDesc>Does the project offer a scholarly commentary (e.g. notes on unclear
                        passages, interpretation, etc.)?</catDesc>
                     <category xml:id="se054">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se055">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se056">
                     <catDesc>Contexts <ref target="#K2.3">cf. Catalogue 2.3</ref>
                     </catDesc>
                     <catDesc>Does the project include or link to external resources with contextual
                        material?</catDesc>
                     <category xml:id="se057">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se058">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se059">
                     <catDesc>Images <ref target="#K2.3">cf. Catalogue 2.3</ref>
                     </catDesc>
                     <catDesc>Does the project offer images of digitised sources?</catDesc>
                     <category xml:id="se060">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se061">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se062">
                     <catDesc>Image quality <ref target="#K4.6">cf. Catalogue 4.6</ref>
                     </catDesc>
                     <catDesc>Does the project offer images of an acceptable quality?</catDesc>
                     <category xml:id="se063">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se064">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se065">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se066">
                     <catDesc>Transcriptions <ref target="#K2.3">cf. Catalogue 2.3</ref>
                     </catDesc>
                     <catDesc>Is the text fully transcribed?</catDesc>
                     <category xml:id="se067">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se068">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se069">
                     <catDesc>Text quality <ref target="#K4.6">cf. Catalogue 4.6</ref>
                     </catDesc>
                     <catDesc>Does the project offer texts of an acceptable quality (typos, errors,
                        etc.)?</catDesc>
                     <category xml:id="se070">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se071">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se072">
                     <catDesc>Indices <ref target="#K4.5">cf. Catalogue 4.5</ref>
                     </catDesc>
                     <catDesc>Does the project feature compilations indices, registers or
                        visualisations that offer alternative ways to access the material?</catDesc>
                     <category xml:id="se073">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se074">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se075">
                     <catDesc>Types of documents <ref target="#K1.3 #K2.1">cf. Catalogue 1.3 and
                           2.1</ref>
                     </catDesc>
                     <catDesc>Which kinds of documents are at the basis of the project?</catDesc>
                     <category xml:id="se076">
                        <catDesc>Single manuscript</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se077">
                        <catDesc>Single work</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se078">
                        <catDesc>Collection of texts</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se079">
                        <catDesc>Collected works</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se080">
                        <catDesc>Papers</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se081">
                        <catDesc>Archival holding</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se082">
                        <catDesc>Charters</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se083">
                        <catDesc>Letters</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se084">
                        <catDesc>Diary</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se085">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se086">
                     <catDesc>Document era <ref target="#K1.3 #K2.1">cf. Catalogue 1.3 and 2.1</ref>
                     </catDesc>
                     <catDesc>What era(s) do the documents belong to?</catDesc>
                     <category xml:id="se087">
                        <catDesc>Classics</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se088">
                        <catDesc>Medieval</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se089">
                        <catDesc>Early modern</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se090">
                        <catDesc>Modern</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se091">
                     <catDesc>Subject <ref target="#K1.3">cf. Catalogue 1.3</ref>
                     </catDesc>
                     <catDesc>Which perspective(s) do the editors take towards the edited material?
                        How can the edition be classified in general terms?</catDesc>
                     <category xml:id="se092">
                        <catDesc>History</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se093">
                        <catDesc>Philology / Literary Studies</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se094">
                        <catDesc>Philosophy / Theology</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se095">
                        <catDesc>History of Science</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se096">
                        <catDesc>Musicology</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se097">
                        <catDesc>Art History</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se098">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se099">
                     <catDesc>Spin-Offs <ref target="#K4.11">cf. Catalogue 4.11</ref>
                     </catDesc>
                     <catDesc>Does the project offer any spin-offs?</catDesc>
                     <category xml:id="se100">
                        <catDesc>App</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se101">
                        <catDesc>Mobile</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se102">
                        <catDesc>PDF</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se103">
                        <catDesc>None</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se104">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
               </category>
               <category>
                  <catDesc>Access modes</catDesc>
                  <category xml:id="se105">
                     <catDesc>Browse by <ref target="#K4.3">cf. Catalogue 4.3</ref>
                     </catDesc>
                     <catDesc>By which categories does the project offer to browse the
                        contents?</catDesc>
                     <category xml:id="se106">
                        <catDesc>Authors</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se107">
                        <catDesc>Works</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se108">
                        <catDesc>Versions</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se109">
                        <catDesc>Structure</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se110">
                        <catDesc>Pages</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se111">
                        <catDesc>Documents</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se112">
                        <catDesc>Type of material</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se113">
                        <catDesc>Images</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se114">
                        <catDesc>Dates</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se115">
                        <catDesc>Persons</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se116">
                        <catDesc>Places</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se117">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                        <catDesc>
                           <gloss>Language, content-specific categories, like the
                              ingredients</gloss>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se118">
                     <catDesc>Simple search <ref target="#K4.4">cf. Catalogue 4.4</ref>
                     </catDesc>
                     <catDesc>Does the project offer a simple search?</catDesc>
                     <category xml:id="se119">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se120">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se121">
                     <catDesc>Advanced search <ref target="#K4.4">cf. Catalogue 4.4</ref>
                     </catDesc>
                     <catDesc>Does the project offer an advanced search?</catDesc>
                     <category xml:id="se122">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se123">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se124">
                     <catDesc>Wildcard search <ref target="#K4.4">cf. Catalogue 4.4</ref>
                     </catDesc>
                     <catDesc>Does the search support the use of wildcards?</catDesc>
                     <category xml:id="se125">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se126">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se127">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se128">
                     <catDesc>Index <ref target="#K4.4">cf. Catalogue 4.4</ref>
                     </catDesc>
                     <catDesc>Does the search offer an index of the searched field?</catDesc>
                     <category xml:id="se129">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se130">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se131">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se132">
                     <catDesc>Suggest functionalities <ref target="#K4.4">cf. Catalogue 4.4</ref>
                     </catDesc>
                     <catDesc>Does the search offer autocompletion or suggest
                        functionalities?</catDesc>
                     <category xml:id="se133">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se134">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se135">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se136">
                     <catDesc>Help texts <ref target="#K4.4">cf. Catalogue 4.4</ref>
                     </catDesc>
                     <catDesc>Does the project offer help texts for the search?</catDesc>
                     <category xml:id="se137">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se138">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se139">
                        <catDesc>Not applicable</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
               </category>
               <category>
                  <catDesc>Aims and methods</catDesc>
                  <category xml:id="se140">
                     <catDesc>Audience <ref target="#K3.3">cf. Catalogue 3.3</ref>
                     </catDesc>
                     <catDesc>Who is the intended audience of the project?</catDesc>
                     <category xml:id="se141">
                        <catDesc>Scholars</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se142">
                        <catDesc>Interested public</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se143">
                     <catDesc>Typology <ref target="#K3.3 #K5.1">cf. Catalogue 3.3 and 5.1</ref>
                     </catDesc>
                     <catDesc>Which type fits best for the reviewed project?</catDesc>
                     <category xml:id="se144">
                        <catDesc>Facsimile edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se145">
                        <catDesc>Archive edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se146">
                        <catDesc>Documentary edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se147">
                        <catDesc>Diplomatic edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se148">
                        <catDesc>Genetic edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se149">
                        <catDesc>Work critical edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se150">
                        <catDesc>Text critical edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se151">
                        <catDesc>Enriched edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se152">
                        <catDesc>Database edition</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se153">
                        <catDesc>Digital library</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se154">
                        <catDesc>Collection of texts</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se155">
                        <catDesc>None</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se156">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se158">
                     <catDesc>Critical editing <ref target="#K3.6">cf. Catalogue 3.6</ref>
                     </catDesc>
                     <catDesc>In how far is the text critically edited?</catDesc>
                     <category xml:id="se159">
                        <catDesc>Transmission examined</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se160">
                        <catDesc>Palaeographic annotations</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se161">
                        <catDesc>Normalization</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se162">
                        <catDesc>Variants</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se163">
                        <catDesc>Emendation</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se164">
                        <catDesc>Commentary notes</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se165">
                        <catDesc>None</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se166">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                        <catDesc>
                           <gloss>Identification of semantic elements (there is no normalization in
                              the transcriptions, but lemmata and concepts are identified)</gloss>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se167">
                     <catDesc>XML <ref target="#K3.7">cf. Catalogue 3.7</ref>
                     </catDesc>
                     <catDesc>Is the data encoded in XML? </catDesc>
                     <category xml:id="se168">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se169">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se170">
                     <catDesc>Standardized data model <ref target="#K3.7">cf. Catalogue 3.7</ref>
                     </catDesc>
                     <catDesc>Is the project employing a standardized data model (e.g.
                        TEI)?</catDesc>
                     <category xml:id="se171">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se172">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se173">
                     <catDesc>Types of text <ref target="#K3.5">cf. Catalogue 3.5.</ref>
                     </catDesc>
                     <catDesc>Which kinds or forms of text are presented?</catDesc>
                     <category xml:id="se174">
                        <catDesc>Facsimiles</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se175">
                        <catDesc>Diplomatic transcription</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se176">
                        <catDesc>Edited text</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se177">
                        <catDesc>Translations</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se178">
                        <catDesc>Commentaries</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se179">
                        <catDesc>Semantic data</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                  </category>
               </category>
               <category>
                  <catDesc>Technical accessability</catDesc>
                  <category xml:id="se180">
                     <catDesc>Persistent identification <ref target="#K4.8">cf. Catalogue 4.8</ref>
                     </catDesc>
                     <catDesc>Are there persistent identifiers and an addressing system for the
                        edition and/or parts/objects of it and which mechanism is used to that
                        end?</catDesc>
                     <category xml:id="se181">
                        <catDesc>DOI</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se182">
                        <catDesc>ARK</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se183">
                        <catDesc>URN</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se184">
                        <catDesc>PURL.ORG</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se185">
                        <catDesc>Persistent URLs</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se186">
                        <catDesc>None</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se187">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se188">
                     <catDesc>Interfaces <ref target="#K4.9">cf. Catalogue 4.9</ref>
                     </catDesc>
                     <catDesc>Are there technical interfaces like OAI-PMH, REST etc., which allow
                        the reuse of the data of the project in other contexts?</catDesc>
                     <category xml:id="se189">
                        <catDesc>OAI-PMH</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se190">
                        <catDesc>REST</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se191">
                        <catDesc>General API</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se192">
                        <catDesc>None</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se193">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se194">
                     <catDesc>Open Access</catDesc>
                     <catDesc>Is the edition Open Access?</catDesc>
                     <category xml:id="se195">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se196">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se197">
                     <catDesc>Accessability of the basic data <ref target="#K4.12">cf. Catalogue
                           4.12</ref>
                     </catDesc>
                     <catDesc>Is the basic data (e.g. the XML) of the project accessible for each
                        part of the edition (e.g. for a page)?</catDesc>
                     <category xml:id="se198">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se199">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se200">
                     <catDesc>Download <ref target="#K4.9">cf. Catalogue 4.9</ref>
                     </catDesc>
                     <catDesc>Can the entire raw data of the project be downloaded (as a
                        whole)?</catDesc>
                     <category xml:id="se201">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se202">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se203">
                     <catDesc>Reuse <ref target="#K4.9">cf. Catalogue 4.9</ref>
                     </catDesc>
                     <catDesc>Can you use the data with other tools useful for this kind of
                        content?</catDesc>
                     <category xml:id="se204">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se205">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se206">
                     <catDesc>Declaration of rights <ref target="#K4.13">cf. Catalogue 4.13</ref>
                     </catDesc>
                     <catDesc>Are the rights to (re)use the content declared?</catDesc>
                     <category xml:id="se207">
                        <catDesc>Yes</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se208">
                        <catDesc>No</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                  </category>
                  <category xml:id="se209">
                     <catDesc>License <ref target="#K4.13">cf. Catalogue 4.13</ref>
                     </catDesc>
                     <catDesc>Under what license are the contents released?</catDesc>
                     <category xml:id="se210">
                        <catDesc>CC0</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se211">
                        <catDesc>CC-BY</catDesc>
                        <catDesc>
                           <num type="boolean" value="1"/>
                        </catDesc>
                     </category>
                     <category xml:id="se212">
                        <catDesc>CC-BY-ND</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se213">
                        <catDesc>CC-BY-NC</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se214">
                        <catDesc>CC-BY-SA</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se215">
                        <catDesc>CC-BY-NC-ND</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se216">
                        <catDesc>CC-BY-NC-SA</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se217">
                        <catDesc>PDM</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se218">
                        <catDesc>No license</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se219">
                        <catDesc>Multiple licenses</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                     </category>
                     <category xml:id="se220">
                        <catDesc>Other</catDesc>
                        <catDesc>
                           <num type="boolean" value="0"/>
                        </catDesc>
                        <catDesc>
                           <gloss/>
                        </catDesc>
                     </category>
                  </category>
               </category>
            </taxonomy>
         </classDecl>
      </encodingDesc>
      <profileDesc>
         <langUsage>
            <language ident="en"/>
         </langUsage>
         <textClass>
            <keywords xml:lang="en">
               <term>annotation</term>
               <term>diplomatic transcription</term>
               <term>food history</term>
               <term>germanic varieties</term>
               <term>german</term>
               <term>medieval</term>
               <term>interface</term>
            </keywords>
         </textClass>
      </profileDesc>
   </teiHeader>
   <text>
      <front>
         <div type="abstract">
            <p>
               <emph>CoReMa, Cooking Recipes of the Middle Ages</emph> is an ongoing project whose
               method involves a semantically annotated, conservative edition of medieval
               manuscripts containing cooking recipes. With a rigorous philological approach and the
               aid of semantic web technologies, CoReMa’s method aims at teasing out the textual
               relations between different recipe collections, even enabling the comparison between
               manuscripts in different languages. Its semantic model covers many and very
               heterogeneous aspects of the transmission of cooking knowledge including, just to
               give an example, the treatments of a condition or illness. CoReMa is an ambitious
               project and food historians will not be the only scholars that will benefit from such
               a comprehensive (and intuitive) resource.</p>
         </div>
      </front>
      <body>
         <div xml:id="div1">
            <head>Introduction<note xml:id="ftn1">This review was updated in April 2021 as the
               result of detailed peer-review that greatly improved its contents. The reviewer is
               a postdoc in Historical Linguistics and Digital Humanities at the University of
               Neuchâtel. She holds a PhD in Medieval Studies and, although the framework of her
               thesis project was philological, her postgraduate program was interdisciplinary
               and she holds a minor specialisation in Medieval History and Medieval Art
               History.</note>
            </head>
            <p xml:id="p1">Collections of cooking recipes have a rich textual tradition in medieval
               Europe that goes beyond the famous compilations of <emph>De re
                  coquinaria</emph>,<note xml:id="ftn2">See Grocock and Grainer (<ref type="crossref" target="#grocockgrainger2006">2006, 116-20</ref>) for an
                  overview of the transmission of this work showing its great success.</note> and
                  <emph>CoReMa, Cooking Recipes of the Middle Ages</emph> provides a rigorous method
               to tackle its complexity. With the objective of pursuing an in-depth analysis of the
               transmission and interrelation of medieval cooking recipes, CoReMa proposes an
               interdisciplinary approach that produces a semantically annotated digital scholarly
               edition (<ref type="crossref" target="#kluglaurioux2020">Klug and Laurioux
               2020</ref>). </p>
            <p xml:id="p2">At the time of writing, the project holds the edition of fifteen
               manuscripts from the Late Middle Ages in several German dialects. Thus, this review
               concerns the edition of the German Cooking Recipe Collections, although the project
               has a much larger scope. CoReMa defends a cross-linguistic approach as one of the
               defining features of this project in comparison to previous national-based
               initiatives. Therefore, either the addition of other languages or, at least, the
               enrichment of the German materials with the corresponding references to other textual
               traditions is expected considering the overall goals of the project.</p>
            <p xml:id="p3">There are a few resources that are of invaluable help for researchers in
               food history (or food historiography). One of the resources which has received the
               most attention outside specialised circles<note xml:id="ftn3">It has been covered in
                  large-circulation periodicals or news media like the <emph>BBC News</emph> (<ref type="crossref" target="#thomas2017">Thomas 2017</ref>), <emph>New York Times
                     Magazine</emph> (<ref type="crossref" target="#wilson2015">Wilson 2015</ref>)
                  or <emph>El País</emph> (<ref type="crossref" target="#perez2020">Pérez
                  2020</ref>).</note> is <emph>The Sifter</emph> (<ref type="crossref" target="#wheaton2020">Wheaton 2020</ref>), a database of recipes, ingredients, and
               cooking techniques retrieved from more than 7,000 bibliographic works. Another
               relevant resource is <emph>The Food Timeline</emph> (<ref type="crossref" target="#olver2015">Olver 2015</ref>). On the one hand, this resource provides
               information about when foods were first introduced (visualised, as expected, in a
               graphical timeline). On the other hand, this information is complemented with
               historic recipes using those foods, together with various food-related topics such as
               historic food prices, historic menu collections, adaption of old recipes, and other
               information about culinary research. This database provides both scholarly sources
               and ‘popular’ ones from outside academia (such as famous cooking blogs or chefs’
                  websites).<note xml:id="ftn4">For a more academic resource that is exclusively
                  focused on the compilation of bibliographic references, scholars can consult
                     <emph>The Food Bibliography</emph> (<ref type="crossref" target="#foodbibliography2020">‘The Food Bibliography’ n.d.</ref>).</note>
               Although all these resources somehow cover the same historical and geographic
               framework as CoReMa, in the sense that Medieval Europe is well represented in both
               databases, the project being reviewed provides a philological approach not shared by
               the aforementioned resources. Thanks to the scholarly edition of the recipes, the
               codicological analysis of the manuscripts that contain them and the phylogenetic
               study of these sources, it is possible to obtain an exhaustive knowledge on the
               socio-historical and cultural factors that brought about those recipes. This
               comprehensive analysis can hardly be achieved by more generic endeavours.</p>
            <p xml:id="p4">Considering that CoReMa’s work is still in progress, I will dedicate a
               section to briefly discuss the project and its overall goals in relation to its
               current status (see section ‘<ref type="crossref" target="#div2">Presentation of the
                  project and its status</ref>’). ‘<ref type="crossref" target="#div3">CoReMa’s
                  method: a transdisciplinary approach</ref>’ presents an overview of the
               methodology and the section ‘<ref type="crossref" target="#div4">Interface</ref>’
               discusses the main functionalities of the graphical user interface. The review ends
               with some final remarks that mainly expand on the scholarly contribution of this
               project (see section ‘<ref type="crossref" target="#div5">Conclusion</ref>’).</p>
         </div>
         <div xml:id="div2">
            <head>Presentation of the project and its status</head>
            <p xml:id="p5">
               <figure xml:id="img1">
                  <graphic url="http://ride.i-d-e.de/wp-content/uploads/issue_14/corema/pictures/picture-1.png"/>
                  <head type="legend">The front page of CoReMa including the menu items that
                     describe this project.</head>
               </figure>The website of the project is very well organised. The menu items take the
               user to the relevant pieces of information that can be consulted before exploring a
               project’s contents. CoReMa provides comprehensive documentation, both from the
               perspective of its conceptualisation and also its implementation (see <ref type="crossref" target="#img1">Fig. 1</ref>). </p>
            <p xml:id="p6">The information related to the agents and agencies behind this project is
               accessible, clear and well-organised. CoReMa stems from the international cooperation
               between the Centre for Information Modelling - Austrian Centre for Digital Humanities
               of the University of Graz (ZIM-ACDH) and the Centre for Advanced Renaissance Studies
               of the University of Tours. The principal investigators are Helmut W. Klug, who leads
               the Austrian participation, and Bruno Laurioux, who is in charge of the French team.
               The project is funded by the Agence Nationale de la Recherche (ANR) and by the
               Austrian Science Foundation (FWF). Project start and end dates are not explicitly
               mentioned on the website. However, an online search for the grant number showed that
               the project is being funded from March 2018 until October 2021.</p>
            <p xml:id="p7">The overall goal of CoReMa is to gain new knowledge on cooking traditions
               from a cross-cultural perspective by studying how medieval European cooking recipes
               were transmitted. To achieve it, the core of the methodology is the scholarly digital
               edition of the recipes. The texts of this edition are semantically annotated in order
               to tease out the answers for the overall research question: what were the food habits
               in Medieval Europe. The contents of this annotation are exploited thanks to different
               search functions. At the moment, it is possible to filter the recipes according to
               different criteria, like period or dialects. A search by ingredient(s) is also
               enabled. These search functions make it possible to trace the distribution of certain
               recipes and ingredients. Accordingly, the tool is already a useful resource to shed light
               on certain gastronomical trends even at this stage of the project, where all
               manuscripts have not yet been edited. Besides its use by a specialised public, any
               person interested in cooking will enjoy browsing the contents of the project and
               learning the particularities of medieval cuisine. </p>
            <p xml:id="p8">At the time of writing, we can access the edition of fifteen manuscripts,
               all of them pertaining to the German Cooking Recipe Collections. For
               these witnesses, a curated text is provided and, for most of them, the structural and
               semantic components of the texts are also identified, like the categorisation of
               ingredients, instructions or tools. A useful resource to evaluate the state of the
               project is the to-do list accessible from the main menu.<note xml:id="ftn5">
                  <ref target="https://web.archive.org/web/20210502085119/https://gams.uni-graz.at/archive/objects/context:corema/methods/sdef:Context/get?mode=todos">https://web.archive.org/web/20210502085119/https://gams.uni-graz.at/archive/objects/context:corema/methods/sdef:Context/get?mode=todos</ref>.</note>
               This list gives us a quick overview of the state of the corpus in terms of its
               development. The manuscripts whose edition is planned are listed and it is clear
               which ones have already been incorporated to the website (about a fourth of the
               collection). What is unclear to a user is the criteria for the selection of sources.
               Considering the goals and the description of the project provided, it is to be
               expected that their scope includes every manuscript of cooking recipes inside the
               pertinent chronological framework. However, no information is given about how the
               source compilation was done.</p>
            <p xml:id="p9">Besides giving an overview of the state of the collection in terms of
               progress, the to-do list contains tasks related to other development areas like the
               graphical user interface, or aspects of the analysis that still need to be
               implemented. With the complete edition of a number of witnesses and the
               implementation of a faceted search, we have a fair glimpse at what will be the final
               product. The most relevant functionality that is yet to be implemented at the
               moment of writing is related to intertextual relations between recipes and the
               analysis of recipes migration.</p>
            <p xml:id="p10">In the goals of the project, a development of an ontology to formalise
               the semantic annotation is mentioned. No information about this task is collected in
               the to-do list so it can be assumed that the list was conceived as a practical work
               document for the development of the portal and thus has little use for the more
               general tasks.</p>
         </div>
         <div xml:id="div3">
            <head>CoReMa’s method: a transdisciplinary approach</head>
            <p xml:id="p11">CoReMa is presented by its creators as an interdisciplinary project, but
               I argue that the final result can be described as transdisciplinary: a cohesive unit
               of frameworks that surpasses the disciplinary perspectives (<ref type="crossref" target="#jensenius2012">Jensenius 2012</ref>). In this sense, a scholarly digital
               edition is transdisciplinary by definition, but it is worth highlighting some of the
               other elements that interact to create a project as the one being reviewed. Thus, I
               will decompose what so smoothly comes together to provide an overview of some of the
               components of the project.</p>
            <div xml:id="div3.1">
               <head>Material philology </head>
               <p xml:id="p12">For each manuscript of the collection, a codicological description is
                  provided. The user can either access an overview of the edited manuscripts thanks
                  to a timeline or a more ‘traditional’ description by selecting a specific
                  manuscript.</p>
               <p xml:id="p13">
                  <figure xml:id="img2">
                     <graphic url="http://ride.i-d-e.de/wp-content/uploads/issue_14/corema/pictures/picture-2.png"/>
                     <head type="legend">One of the entries of the manuscript timeline.</head>
                  </figure>The manuscript timeline is an excellent visualisation to examine the
                  chronological framework of the project, especially useful when discussing a work
                  in progress that will be frequently updated (as inferred by their to-do list).
                  This timeline presents each manuscript in chronological order with a succinct
                  codicological description (see <ref type="crossref" target="#img2">Fig. 2</ref>).
                  The visualized timeline is displayed below each description and each
                  manuscript appears identified with its sigla in the corresponding time frame. As
                  of April 2021, the timeline groups the different manuscripts in four different
                  lines (see <ref type="crossref" target="#img2">Fig. 2</ref>). Although I could not
                  find the specific documentation, as a reader I understand that the different lines
                  represent branches of the manuscript tradition and manuscripts sharing the same
                  line present a filiation relation.</p>
               <p xml:id="p14">In regards to the more thorough codicological description given for
                  each manuscript, it should be noted that not all descriptions present the same
                  level of detail, thus the available metadata varies from one artefact to the
                  other. However, in general terms, this physical description includes a description
                  of the support, containing information about the cover and binding, together with
                  aspects of the <emph>mise en page</emph>. </p>
               <p xml:id="p15">The codicological analysis is complemented with bibliographic
                  references. When possible, the link to a digital facsimile is included. The
                  metadata provided for all manuscripts concerns the catalogue references with a
                  Zotero link that enables the immediate import of any bibliographic reference.</p>
               <p xml:id="p16">The contents of the codicological description are mostly in German:
                  all the available manuscripts come from libraries in German-speaking countries and
                  the contents of this section are likely collected with the help of catalogues in
                  German. Thus, the presence of German would be understandable if the contents were
                  generated on the fly, but it does not seem to be the case. Nevertheless, if users
                  can read the edition of the text in a historical Germanic variety, the manuscript
                  description should not pose any problems.</p>
               <p xml:id="p17">Considering that the edition may involve just a very small portion of
                  the codex, the detailed description of the manuscript, with all the references
                  provided, renders a more accurate view of the artefact.</p>
            </div>
            <div xml:id="div3.2">
               <head>Paleography</head>
               <p xml:id="p18">The last part of this section is dedicated to the ecdotic component
                  of the project in which the edition decisions will be further discussed. However,
                  at this point it is pertinent to announce that the criteria of a digital
                  documentary edition are already an inestimable source of palaeographic information
                     (<ref type="crossref" target="#pierazzo2011">Pierazzo 2011, 475</ref>). This is
                  even more straightforward when the transcription is always displayed next to a
                  facsimile rendition of the folium, as it is the case in this project.</p>
               <p xml:id="p19">Besides the palaeographic knowledge that can be retrieved from the
                  edition of these manuscripts that have different provenances (and thus, diverging
                  writing practises), palaeographic metadata are given for each manuscript. As with
                  the previous codicological description, the availability and detail of this
                  information vary from one manuscript to the other, but all entries include the
                  identification of the hands and of the script types. The most comprehensive
                  palaeographic descriptions include an inventory of letterforms and specific
                  graphical uses with their location in the manuscript. </p>
               <p xml:id="p20">Considering the particularities of the transmission of cookbooks, the
                  identification of hands is crucial to identify the socio-historical context in
                  which latter additions, comments or even modifications of the recipes are
                  done.</p>
            </div>
            <div xml:id="div3.3">
               <head>Linguistics</head>
               <p xml:id="p21">Any scholarly edition of a medieval text requires a profound
                  knowledge of the historic variants of the language under analysis. However, the
                  semantic annotation of this project explicitly formalises part of that knowledge.
                  At the moment, the semantic annotation not only consists of the description of the
                  different parts of the recipe, like the opener, tips or instructions, but it also
                  contains an under-the-hood standardisation of its contents. Certain elements like
                  those which model the ingredients, the dish name or the cooking instrument are
                  given not only the English translation in an attribute, but the Wikidata
                  identifier as well. The latter not only increases the interoperability of the
                  dataset but it could also be used to disambiguate concepts for which English lacks
                  specific terminology.<note xml:id="ftn6">The English translations are provided
                     using the corresponding Wikidata label, which might not always be the most
                     intuitive translation of certain terms. See, for example, the recipe in Klug
                     and Eibinger (<ref type="crossref" target="#klugeibinger2021a">2021a</ref>)
                     where the label ‘mus’ in English is used to translate Bavarian ‘Taig’ (not to
                     be confused with the standard German word for ‘dough’). Even if the lemma ‘mus’
                     does not appear in English dictionaries like the OED, the Wikidata identifier
                     (Q1953925) provides the user with the necessary information to interpret the
                     term.</note>
               </p>
               <p xml:id="p22">In addition, access to historical socio-linguistic information is
                  enabled through an interactive map of the linguistic varieties covered in the
                  editions. The manuscript descriptions include the languages of the artefact, but
                  through the map it is easier to approach the materials written in a particular
                  variety.</p>
            </div>
            <div xml:id="div3.4">
               <head>Semantic Web technologies</head>
               <p xml:id="p23">As presented in the section ‘<ref type="crossref" target="#div2">Presentation of the project and its status</ref>’, this part of the project is
                  not fully implemented. It is worth mentioning, nevertheless, that certain steps
                  were already taken, like the implementation of Wikidata identifiers to
                  unambiguously map certain concepts. Even if no information is provided about the
                  state of development of the ontology, a possible approach is to use the editions
                  themselves to elicit the informational requirements of the ontology. In any case,
                  even if the ontology is not fully implemented until a considerable number of texts
                  is edited, it would be interesting to see how the different editions are linked to the ontology.<note xml:id="ftn7">See for instance this discussion in the TEI
                     Github repository: <ref target="https://web.archive.org/web/20201213212835/https://github.com/TEIC/TEI/issues/1860">https://web.archive.org/web/20201213212835/https://github.com/TEIC/TEI/issues/1860</ref>.</note>
                  It should be noted that the project is stored in the open management system
                  GAMS (<ref type="crossref" target="#zim2021">Zentrum für Informationsmodellierung 2006-2021</ref>), 
                  an archive for managing, publishing and long-term archiving of digital resources
                  from the Humanities. It provides the project resources with permanent
                  identification and enriched metadata among other functionalities that can
                  facilitate the implementation of semantic web technologies. </p>
            </div>
            <div xml:id="div3.5">
               <head>Textual scholarship: ecdotic model and text encoding</head>
               <p xml:id="p24">As stated in the objectives of the project, CoReMa’s goal is to
                  provide a philological edition of the source texts that follows a hyperdiplomatic
                  transcription model (<ref type="crossref" target="#klugboehm2020">Klug and Böhm
                     2020</ref>). The theoretical framework of this editorial model is found in
                  Hofmeister-Winter (<ref type="crossref" target="#hofmeisterwinter2003">2003</ref>). This model is being implemented in other ongoing edition projects at
                  the University of Graz and this use backs up, in a way, CoReMa’s choice (<ref type="crossref" target="#kluglaurioux2020">Klug and Laurioux 2020</ref>).</p>
               <p xml:id="p25">The specific advantages of this model in relation to the research
                  questions and goals of the project are not explicitly addressed in the
                  documentation. Even if the objectives of the project argue the need of providing
                  scholarly curated texts, there is no specific discussion of the adequacy of the
                  hyperdiplomatic model to CoReMa’s particular goals. Details are given, however,
                  about the implementation of this edition typology in the project
                     <emph>Mittelalterlabor</emph>
                  <note xml:id="ftn8">
                     <ref target="https://web.archive.org/web/20201214151226/http://gams.uni-graz.at/context:malab">https://web.archive.org/web/20201214151226/http://gams.uni-graz.at/context:malab</ref>.</note>
                  for which it is said that the moderately diplomatic criteria, with no
                  normalisation, pursue the representation of writer specific features in the
                  palaeographic dimension, together with ‘text-genetic information, and dialectal
                  markers that are represented on character level (e.g. sound changes, dialect
                  markers)’ (<ref type="crossref" target="#kluglaurioux2020">Klug and Laurioux
                     2020</ref>). It is inferred that similar goals are intended by the CoReMa
                  project. Due to the conservative criteria, CoReMa’s edition depicts a faithful
                  representation of each of the witnesses. It should be noted that the same recipes
                  are preserved in different witnesses and therefore a multi-witness critical
                  edition of those recipes would shed light about their transmission. However, the
                  comparison of recipes and the deeper analysis of recipe migration is not yet
                  available, thus we need to wait to see what will be CoReMa’s strategy to formalise
                  and visualise the witnesses’ comparison. </p>
               <p xml:id="p26">The actual implementation of the hyperdiplomatic model by CoReMa is
                  very detailed: From the main menu we can access a thorough documentation in which
                  the editorial criteria are exhaustively explained (<ref type="crossref" target="#klugboehm2020">Klug and Böhm 2020</ref>). Besides expounding how the
                  structural elements are encoded, and how specific phenomena should be treated
                  (like abbreviations or punctuation marks), there is a detailed guide about
                  character representation. They are following the guidelines of the <emph>MUFI
                     character recommendation</emph> (<ref type="crossref" target="#haugen2015">Haugen 2015</ref>) and they present a list of common allographs and how they
                  should be encoded. The criteria in this aspect are very conservative and the
                  general norm is ‘the text of the source is represented as detailed as feasible’
                     (<ref type="crossref" target="#klugboehm2020">Klug and Böhm 2020</ref>). The
                  documentation about the edition model ends with an explanation on how certain
                  encoded information will be displayed.</p>
               <p xml:id="p27">Besides the general editorial guidelines, specific criteria may apply
                  to certain manuscripts. In the description of each manuscript we might find
                  ‘encoding remarks’ where these particular criteria are explained. Considering the
                  heterogeneous sources (different languages, different periods, different writing
                  traditions) it is appropriate to present these specific sections to reveal (and
                  formalise) the idiosyncrasies of a particular manuscript.</p>
               <p xml:id="p28">In addition to the criteria concerning the representation of the
                  primary sources, CoReMa provides their semantic annotation guide. In this valuable
                  piece of documentation, they propose a very fine-grained segmentation of the
                  recipes in semantic elements. Besides classifying the different types of recipes
                  and their structural parts (like the opener or closer), it identifies the mentions
                  to dishes, ingredients, tools, household tips, kitchen tips, serving tips,
                  instructions, time spans and explicit health benefits.</p>
               <p xml:id="p29">The guide presents, on the one hand, the specific use of TEI elements
                  and attributes needed to convey the semantics of the textual elements, and, on the
                  other hand, the CoReMa-specific elements. The distinction between one type and the
                  other is not always explicit. Nevertheless, the explanations are brief but clear
                  with examples that illustrate very well the specific uses at hand. </p>
               <p xml:id="p30">The ingredients, dishes and tools are annotated with their Wikidata
                  identifier, if possible. The lack of an identifier can be due to issues when
                  interpreting a term (see <ref type="crossref" target="#klugeibinger2021a">Klug and
                     Eibinger 2021a</ref> for an example) or because there is no equivalent item in
                  Wikidata. The CoReMa team might consider creating the Wikidata entries themselves
                  for some of the most obscure terms.<note xml:id="ftn9">See for example the
                     English label ‘trysenet’ used in a few recipes like in Klug and Eibinger (<ref type="crossref" target="#klugeibinger2021d">2021d</ref>) but with the
                     spelling ‘trisenet’ as the title of a recipe in Klug and Eibinger (<ref type="crossref" target="#klugeibinger2021c">2021c</ref>). Even if the term
                     is well documented in historical and specialised dictionaries of German (<ref type="crossref" target="#woerterbuchnetz2020">Wörterbuchnetz 2020,
                        ‘trisenet’</ref>), no pertinent references to ‘trysenet’ in English were
                     found online.</note>
               </p>
               <p xml:id="p31">There were only two minor aspects that could be reviewed in a future
                  version. First, the presence of the element <code>&lt;unclear&gt;</code> in the
                  semantic model description: it should solely belong, in my opinion, to the
                  documentation about the editorial criteria. Second, the use of the attribute
                     <code>@commodity</code> in the CoReMa-specific elements
                     <code>&lt;ingredient&gt;</code>, <code>&lt;dish&gt;</code>, and
                     <code>&lt;tool&gt;</code>. Considering the semantics of the attribute, it only
                  seems appropriate in the last one of them. Also, the expected value is a Wikidata
                  identifier, therefore, an attribute of the TEI classes
                     <code>att.global.linking</code>, <code>att.canonical</code> or
                     <code>att.identified</code> could be a more suitable candidate. </p>
               <p xml:id="p32">As stated in the documentation, ‘all information relevant to the
                  cooking process and related spheres (e.g. conservation) can be represented’ (<ref type="crossref" target="#eibingerklug2020">Eibinger and Klug 2020</ref>) and
                  the level of detail formalised in the encoding scheme is indeed remarkable. The
                  digital edition from the point of view of the graphical user interface will be
                  described in the section ‘<ref type="crossref" target="#div4.2">The digital
                     edition</ref>’.</p>
            </div>
         </div>
         <div xml:id="div4">
            <head>Interface</head>
            <div xml:id="div4.1">
               <head>Browse and search functionalities</head>
               <p xml:id="p33">The German Cooking Recipe Collection is accessible from a
                  user-friendly, aesthetically pleasing interface (<ref type="crossref" target="#klugsteingerboehmeibinger2020">Klug et al. 2020</ref>). The front page
                     (<ref type="crossref" target="#img1">Fig. 1</ref>) presents an image of each
                  edited manuscript (with its sigla) from which we can directly access its
                  transcription or the description of that manuscript (Gallery view). This is a
                  particularly convenient front page for recurrent visitors. Manuscripts that have
                  already been semantically annotated present, in addition, the option ‘Recipes’.
                  This presentation is very convenient because one can access a specific manuscript
                  immediately from the front page without having to perform any queries first. Just
                  above the manuscript images, a secondary navigation bar offers five options to
                  browse the manuscript collection with different views:<list rend="ordered">
                     <item>The first one presents a map of all the archives: clicking on one of the
                        pinpoints displays a list of the manuscripts that are available from that
                        archive.</item>
                     <item>‘View Dialect Map’ displays a map with the dialects. By clicking on one
                        of the dialect areas we can access the list of edited manuscripts written in
                        that linguistic variety.</item>
                     <item>The timeline described above (see section ‘<ref type="crossref" target="#div3.1">Material philology</ref>’) is accessible from this menu.
                        Even if its function is not to be a chronological filter, but to explore the
                        historical dimension of the collection, the contents of edited manuscripts
                        can be accessed from here. This means that the timeline can be also used to
                        select a manuscript from a specific time frame.</item>
                     <item>The option ‘Indices’ takes the user to a table of the recipes with a
                        number of properties that can be used to filter its contents. In addition,
                        there is a text field that filters the complete collection based on string
                        match. Among the metadata fields available there is the name of the recipe
                        (both in English and the original one), the witness, the archive and the
                        provenance of the manuscript that contains the recipe, and the language. It
                        is possible to toggle the different columns, to export the results, and to
                        change the layout, displaying the recipes as cards instead of table
                        rows.</item>
                     <item>The last one filters the manuscripts available in the ‘Gallery view’ by
                        archive.</item>
                  </list>
               </p>
               <p xml:id="p34">At the moment of writing, the project has edited almost 25% of the
                  planned collection. This means that many of the archives or the dialects presented
                  in the maps of options 2 and 3 have no representing manuscripts. A visual cue to
                  differentiate the areas of both the dialect and archive maps that have no
                  manuscripts would improve the user experience.</p>
               <p xml:id="p35">Besides the options given on the home page to browse the collection,
                  the ‘Analysis’ tab on the main menu provides additional search functions. New
                  analytical functions are expected to appear under this section in the future.<list rend="ordered">
                     <item>
                        ‘Fuzzy full-text recipe search’: A text field (that allows
                        wildcards) from which you can search the contents of any of the recipes
                        targeting specific components of the recipe: the title, the full text, the
                        tags or any field. The ‘fuzzy’ aspect of this search is a good approach to
                        deal with the scripto-linguistic variants considering the corpus is not
                        lemmatised.</item>
                     <item>
                        ‘Manuscript description search’: A text field that allows
                        wildcards. The search can be restricted to specific fields: title, full text
                        or tags.</item>
                     <item>
                        ‘Advanced ingredient search’: Two different types of search to
                        filter the recipes depending on their ingredients. One of them is a text
                        field that searches the English title of the recipe. The other is a faceted
                        search with autocomplete function that allows you to see the possible
                        ingredient combinations: after selecting one ingredient in a drop-down menu,
                        another one that contains the ingredients with which the selection shares a
                        recipe appears. New drop-down menus will be presented until no more options
                        are available. A small inconvenience is that these drop-down menus present
                        the ingredients in a counter-intuitive case sensitive order. The results,
                        that is, the list of recipes that match the search criteria, are exportable
                        in CSV and PDF format and they contain the permanent URI and the title of
                        each recipe.</item>
                  </list>
               </p>
            </div>
            <div xml:id="div4.2">
               <head>The digital edition</head>
               <p xml:id="p36">
                  <figure xml:id="img3">
                     <graphic url="http://ride.i-d-e.de/wp-content/uploads/issue_14/corema/pictures/picture-3.png"/>
                     <head type="legend">Transcription view: hyperdiplomatic edition.</head>
                  </figure>Once a manuscript is selected, the edited text is presented to the left
                  of its facsimile, so it is easy to follow the transcription of each folio (<ref type="crossref" target="#img3">Fig. 3</ref>). The images are of a great quality
                  and navigation buttons facilitate the perusing of the facsimile. The folio number
                  is clearly displayed each time a new page begins and lines are numbered. The
                  edition documents the change of colours of the original. However, the text
                  rendered in a brownish colour and italics indicates an abbreviation expansion.
                  Hovering over the expansion fires a tooltip that informs us of the abbreviation
                  mark that was expanded.</p>
               <p xml:id="p37">The only caveat of this edition might be the use of colour to encode
                  two different types of information: ink use of the source and abbreviations. It
                  might not be uncommon to find a decorated initial that contains an abbreviation,
                  for instance, so one wonders which criterion would prevail.</p>
               <p xml:id="p38">At the bottom of the screen (<ref type="crossref" target="#img3">Fig.
                     3</ref>), there is a menu with four tabs (five, if the manuscript is
                  semantically annotated) that facilitates the navigation from the contents of one
                  tab to the other. The first tab contains the manuscript description; if available,
                  the tab ‘Recipes’ takes you to the results of the semantic annotation; the tab
                  ‘Transcription’ corresponds to the edited text; the ‘Full-Width’ one presents a
                  display of the edition with a vertical layout: the facsimile appears on top and in
                  a bigger frame than in the ‘Transcription view’; and the last tab ‘Metadata’
                  provides very detailed metadata of the edition in different standards that are
                  available for download. </p>
               <p xml:id="p39">
                  <figure xml:id="img4">
                     <graphic url="http://ride.i-d-e.de/wp-content/uploads/issue_14/corema/pictures/picture-4.png"/>
                     <head type="legend">Recipes view: semantic annotation.</head>
                  </figure>
                  <figure xml:id="img5">
                     <graphic url="http://ride.i-d-e.de/wp-content/uploads/issue_14/corema/pictures/picture-5.png"/>
                     <head type="legend">Visualisation of the semantic annotation: kitchen tips are
                        highlighted in blue and serving tips are highlighted in light green.</head>
                  </figure>If the text is semantically annotated, the recipes view is available
                     (<ref type="crossref" target="#img4">Fig. 4</ref>). Each one of the recipes is
                  clearly identified and the locus with the folio number is provided. Each recipe
                  has, as its heading, an English name for the recipe, and then in the edition its
                  original title appears in bold. The English title is highlighted depending on the
                  type of content of the recipe: for example, cooking recipes appear in green and
                  kitchen tips in red. This categorisation is also made explicit in this heading. An
                  icon at the end of the heading takes the user to the single recipe view (see <ref type="crossref" target="#img6">Fig. 6</ref> and description below). On the
                  right side, we have a text field search that looks for specific contents in the
                  edition and below it, a list of buttons with each of the semantic categories
                  annotated. By clicking on one of these items, the textual fragments corresponding
                  to that element are highlighted in the text (see <ref type="crossref" target="#img5">Fig. 5</ref> with an example).</p>
               <p xml:id="p40">A single recipe can be accessed either from the query in the
                  ‘Analysis’ or the recipes overview. This presentation displays a slightly
                  different layout than the views discussed above although it presents most of the
                  same functionalities. Above the text of the recipe, we can find a text block that
                  contains a list of the ingredients and tools mentioned in the recipe. Note that
                  the list presents two types of ingredients, the base ingredients and what we might
                  call ‘intermediate ingredients’, that is, the results of mixing some of the base
                  ingredients before completing the dish. See as an example the presence of ‘juniper
                  berry broth’ and ‘sweet juniper berry broth’ in the ingredient list of the recipe
                  Klug and Eibinger (<ref type="crossref" target="#klugeibinger2021a">2021a</ref>).
                  A differentiation between both types of ingredients could be practical.</p>
               <p xml:id="p41">
                  <figure xml:id="img6">
                     <graphic url="http://ride.i-d-e.de/wp-content/uploads/issue_14/corema/pictures/picture-6.png"/>
                     <head type="legend">Single recipe view.</head>
                  </figure>Next to the ingredients and tools card, a summary of the recipes’
                  metadata is presented (see <ref type="crossref" target="#img6">Fig. 6</ref>). This
                  description contains a link to both the hyperdiplomatic edition and the recipes
                  view so as to see the current recipe in its context. To the right, we can see a
                  facsimile view of the folio that contains the recipe and the list of buttons with
                  the semantic elements that highlight the pertinent information.</p>
            </div>
            <div xml:id="div4.3">
               <head>Data sharing</head>
               <p xml:id="p42">As mentioned in the section ‘<ref type="crossref" target="#div3.4">Semantic Web technologies</ref>’, CoReMa is managed via the GAMS system. Not
                  only this guarantees the preservation of the project, especially in terms of data
                  safety and integrity, but it is also an asset for data sharing strategies. From
                  the edition of the witnesses (both from the transcription view and the recipes
                  view) it is possible to access the metadata of the manuscript in different
                  formats, all of them downloadable. The TEI file of every released version of the
                  edition is provided together with the metadata in Dublin Core XML format. The fact
                  that they supply an individual file for each version of the edition means that
                  anybody interested only in the hyperdiplomatic edition, but not in the semantic
                  annotation, can download directly the relevant file that matches their interest.
                  It is possible that in the future other formats will be available for download,
                  like an RDF serialisation.</p>
               <p xml:id="p43">The contents of the portal, including the edition and the facsimile
                  images, have an explicit Creative Commons license (BY-NC-SA 4.0). ‘How to cite’
                  information is also available on each page and in every recipe, thus the dataset
                  (and the documentation) of the project can be reused and easily credited.</p>
            </div>
         </div>
         <div xml:id="div5">
            <head>Conclusion</head>
            <p xml:id="p44">This review analyses the edition of the German Cooking Recipe
                  Collections of the CoReMa project. The CoReMa project has a very ambitious
               goal, a comprehensive understanding of the food habits in Medieval Europe, but the
               work so far done with this collection is an excellent proof of concept and a
               compelling show-case of their method. </p>
            <p xml:id="p45">CoReMa defends a cross-linguistic approach to overcome the possible
               deficiencies of national-based or monolingual methods that can hardly keep track of
               the intertextuality relations among recipes of different manuscript traditions. It
               will be interesting to see exactly the type of interrelations between recipes that
               will be studied and how they are going to be formalised and implemented.
               Nevertheless, considering the current use of semantic web technologies, and the
               future work planned, it is expected that an extended use of these technologies will
               be the preferred method to tackle this specific challenge. </p>
            <p xml:id="p46">Guided by a research question in food history, the philological approach
               is the cornerstone of the project. One of the most noteworthy features of the project
               is the semantic annotation. The semantic model is a fascinating reading in itself,
               and I am eager to see how it will be further put to use by the project. Their
               annotation schema goes beyond the mere identification of ingredients or dishes and it
               is indisputable that their annotated corpus will be relevant for adjacent disciplines
               to food history, such as the history of medicine or the philosophy of medicine.</p>
            <p xml:id="p47">Besides the current and future contribution of this project to food
               history, other disciplines will benefit from its corpus. Just as an example, together
               with all the heterogeneous linguistic information amenable to be retrieved from a
               digital documentary edition, the semantic annotation of the edition can be further
               exploited from a diachronic linguistics perspective. In this sense, I believe that
               the project resources could be exploited to study semantic shifts in food-related
               vocabulary; in addition, the fact that the corpus covers different linguistic
               varieties opens the door to historical socio-linguistic studies.</p>
            <p xml:id="p48">With transparent policies, thorough documentation and great usability,
               CoReMa is publishing a high-quality scholarly digital edition. As it is an ongoing
               project, its extensive functionalities will be even further enhanced.</p>
         </div>
      </body>
      <back>
         <div type="bibliography">
            <listBibl>
               <bibl xml:id="eibingerklug2020">Eibinger, Julia, and Helmut W. Klug. 2020. ‘Semantic
                  Model’. In <emph>CoReMA - Cooking Recipes of the Middle Ages. Corpus - Analysis -
                     Visualisation</emph>, edited by Helmut W. Klug. Centre for Information
                  Modelling (ZIM-ACDH), University of Graz. <ref target="https://web.archive.org/web/20201212131944/http://gams.uni-graz.at/o:corema.semanticdec">https://web.archive.org/web/20201212131944/http://gams.uni-graz.at/o:corema.semanticdec</ref>.</bibl>
               <bibl xml:id="grocockgrainger2006">Grocock, C. W, and Sally Grainger, eds. 2006.
                     <emph>Apicius: a critical edition with an introduction and an English
                     translation of the Latin recipe text Apicius</emph>. Totnes [England]:
                  Prospect.</bibl>
               <bibl xml:id="haugen2015">Haugen, Odd Einar. 2015. <emph>MUFI Character
                     Recommendation v. 4.0</emph>. Medieval Unicode Font Initiative. <ref target="https://bora.uib.no/bora-xmlui/handle/1956/10699">https://bora.uib.no/bora-xmlui/handle/1956/10699</ref>. </bibl>
               <bibl xml:id="hofmeisterwinter2003">Hofmeister-Winter, Andrea. 2003. <emph>Das
                     Konzept einer ‘Dynamischen Edition’ dargestellt an der Erstausgabe des ‘Brixner
                     Dommesnerbuches’ von Veit Feichter (Mitte 16. Jh.): Theorie und praktische
                     Umsetzung</emph>. Kümmerle.</bibl>
               <bibl xml:id="jensenius2012">Jensenius, Alexander Refsum. 2012. ‘Disciplinarities:
                  Intra, Cross, Multi, Inter, Trans’. <ref target="https://web.archive.org/web/20201212163539/https://www.arj.no/2012/03/12/disciplinarities-2/">https://web.archive.org/web/20201212163539/https://www.arj.no/2012/03/12/disciplinarities-2/</ref>.</bibl>
               <bibl xml:id="klugboehm2020">Klug, Helmut W., and Astrid Böhm. 2020. ‘Editorial
                  Declaration’. In <emph>CoReMA - Cooking Recipes of the Middle Ages. Corpus -
                     Analysis - Visualisation</emph>, edited by Helmut W. Klug. Centre for
                  Information Modelling (ZIM-ACDH), University of Graz. <ref target="https://web.archive.org/web/20201212190013/http://gams.uni-graz.at/o:corema.editorialdec">https://web.archive.org/web/20201212190013/http://gams.uni-graz.at/o:corema.editorialdec</ref>.</bibl>
               <bibl xml:id="klugeibinger2021a">Klug, Helmut W., and Julia Eibinger. 2021a. ‘Cooking
                  Recipe for “Drink, a healthy water” (bs1.163)’. In <emph>CoReMA - Cooking Recipes
                     of the Middle Ages. Corpus - Analysis - Visualisation</emph>, edited by Helmut
                  W. Klug. GAMS. <ref target="https://hdl.handle.net/11471/562.10.657">https://hdl.handle.net/11471/562.10.657</ref>. <ref target="https://web.archive.org/web/20210502091756/http://gams.uni-graz.at/o:corema.bs1.163">https://web.archive.org/web/20210502091756/http://gams.uni-graz.at/o:corema.bs1.163</ref>.</bibl>
               <bibl xml:id="klugeibinger2021b">Klug, Helmut W., and Julia Eibinger. 2021b. ‘Cooking
                  Recipe for “Electuary from quince, pear, or apple” (h2a.10)’. In <emph>CoReMA -
                     Cooking Recipes of the Middle Ages. Corpus - Analysis - Visualisation</emph>,
                  edited by Helmut W. Klug. With the help of A. Böhm, J. Eibinger, and C. Steiner.
                  GAMS. <ref target="https://hdl.handle.net/11471/562.10.1149">https://hdl.handle.net/11471/562.10.1149</ref>. <ref target="https://web.archive.org/web/20210502091730/http://gams.uni-graz.at/o:corema.h2a.10">https://web.archive.org/web/20210502091730/http://gams.uni-graz.at/o:corema.h2a.10</ref>.</bibl>
               <bibl xml:id="klugeibinger2021c">Klug, Helmut W., and Julia Eibinger. 2021c. ‘Cooking
                  Recipe for “Trisenet” (h2a.1)’. In <emph>CoReMA - Cooking Recipes of the Middle
                     Ages. Corpus - Analysis - Visualisation</emph>, edited by Helmut W. Klug. With
                  the help of A. Böhm, J. Eibinger, and C. Steiner.<ref target="http://hdl.handle.net/11471/562.10.1148"> </ref>GAMS. <ref target="https://hdl.handle.net/11471/562.10.1148">https://hdl.handle.net/11471/562.10.1148</ref>. <ref target="https://web.archive.org/web/20210502092842/https://gams.uni-graz.at/o:corema.h2a.1">https://web.archive.org/web/20210502092842/https://gams.uni-graz.at/o:corema.h2a.1</ref>.</bibl>
               <bibl xml:id="klugeibinger2021d">Klug, Helmut W., and Julia Eibinger. 2021d. ‘Cooking
                  Recipe for “Wine sauce” (h2a.2)’. In <emph>CoReMA - Cooking Recipes of the Middle
                     Ages. Corpus - Analysis - Visualisation</emph>, edited by Helmut W. Klug. With
                  the help of A. Böhm, J. Eibinger, and C. Steiner. GAMS. <ref target="https://hdl.handle.net/11471/562.10.1159">https://hdl.handle.net/11471/562.10.1159</ref>. <ref target="https://web.archive.org/web/20210502090227/https://gams.uni-graz.at/o:corema.h2a.2">https://web.archive.org/web/20210502090227/https://gams.uni-graz.at/o:corema.h2a.2</ref>.</bibl>
               <bibl xml:id="kluglaurioux2020">Klug, Helmut W., and Bruno Laurioux. 2020. ‘About the
                  Project’. In <emph>CoReMA - Cooking Recipes of the Middle Ages. Corpus - Analysis
                     - Visualisation</emph>, edited by Helmut W. Klug with Astrid Böhm and Christian
                  Steiner. Centre for Information Modelling (ZIM-ACDH). <ref target="https://hdl.handle.net/11471/562.10">https://hdl.handle.net/11471/562.10</ref>. <ref target="https://web.archive.org/web/20210502121335/https://gams.uni-graz.at/archive/objects/context:corema/methods/sdef:Context/get?mode=about">https://web.archive.org/web/20210502121335/https://gams.uni-graz.at/archive/objects/context:corema/methods/sdef:Context/get?mode=about</ref>.</bibl>
               <bibl xml:id="klugsteingerboehmeibinger2020">Klug, Helmut W., Christian Steiner,
                  Astrid Böhm, and Julia Eibinger. 2020. ‘CoReMA - Cooking Recipes of the Middle
                  Ages’. Website. Centre for Information Modelling (ZIM-ACDH), University of Graz.
                  2020. <ref target="https://hdl.handle.net/11471/562.10">https://hdl.handle.net/11471/562.10</ref>.</bibl>
               <bibl xml:id="oed2021">OED = <emph>Oxford English Dictionary Online</emph>. March
                  2021. Oxford University Press. <ref target="https://web.archive.org/web/20210501193952/https://www.oed.com/">https://web.archive.org/web/20210501193952/https://www.oed.com/</ref>.</bibl>
               <bibl xml:id="olver2015">Olver, Lynne. 2015. ‘Food Timeline: Food History Research
                  Service’. 2015. <ref target="https://web.archive.org/web/20201212133025/http://www.foodtimeline.org/">https://web.archive.org/web/20201212133025/http://www.foodtimeline.org/</ref>.</bibl>
               <bibl xml:id="perez2020">Pérez, Montse Hidalgo. 2020. ‘Recetarios medievales y
                  tarjetas perforadas: la historiadora que lleva 50 años creando el gran archivo
                  culinario de Internet’. EL PAÍS RETINA. 9 October 2020. <ref target="https://retina.elpais.com/retina/2020/10/09/tendencias/1602249882_078647.html">https://retina.elpais.com/retina/2020/10/09/tendencias/1602249882_078647.html</ref>.</bibl>
               <bibl xml:id="pierazzo2011">Pierazzo, Elena. 2011. ‘A Rationale of Digital
                  Documentary Editions’. <emph>Literary and Linguistic Computing</emph> 26 (4):
                  463-77. <ref target="https://doi.org/10.1093/llc/fqr033">https://doi.org/10.1093/llc/fqr033</ref>.</bibl>
               <bibl xml:id="foodbibliography2020">‘The Food Bibliography’. n.d. Accessed 12
                  December 2020. <ref target="https://web.archive.org/web/20201213132009/http://www.foodbibliography.eu/index_en.asp">https://web.archive.org/web/20201213132009/http://www.foodbibliography.eu/index_en.asp</ref>
               </bibl>
               <bibl xml:id="thomas2017">Thomas, Emily. 2017. ‘The Unlikely Power of Cookbooks, The
                  85-Year-Old Woman Who Wants to Collect Every Recipe in the World’. BBC. 2017. <ref target="https://web.archive.org/web/20201213131120/https://www.bbc.co.uk/programmes/p0576bvc">https://web.archive.org/web/20201213131120/https://www.bbc.co.uk/programmes/p0576bvc</ref>.</bibl>
               <bibl xml:id="wheaton2020">Wheaton, Barbara K. 2020. ‘The Sifter - A Food History
                  Research Tool’. 2020. <ref target="https://web.archive.org/web/20201213131731/https://thesifter.org/Home">https://web.archive.org/web/20201213131731/https://thesifter.org/Home</ref>
               </bibl>
               <bibl xml:id="wilson2015">Wilson, Bee. 2015. ‘The Archive of Eating’. <emph>The New
                     York Times</emph>, 29 October 2015, sec. Magazine. <ref target="https://web.archive.org/web/20201213131850/https://www.nytimes.com/2015/11/01/magazine/the-archive-of-eating.html">https://web.archive.org/web/20201213131850/https://www.nytimes.com/2015/11/01/magazine/the-archive-of-eating.html</ref>.</bibl>
               <bibl xml:id="woerterbuchnetz2020">Wörterbuchnetz. 2020. s.v. ‘trisenet’. Version
                  01/21. Trier Center for Digital Humanities, Universität Trier. <ref target="https://api.woerterbuchnetz.de/dictionaries/Meta/lemmata/lemma/trisenet/0/tei-xml">https://api.woerterbuchnetz.de/dictionaries/Meta/lemmata/lemma/trisenet/0/tei-xml</ref>.</bibl>
               <bibl xml:id="zim2021">Zentrum für Informationsmodellierung - Austrian Centre for Digital Humanities. 2006-2021. ‘GAMS. Geisteswissenschaftliches Asset Management System’ <ref target="https://hdl.handle.net/11471/521.1">https://hdl.handle.net/11471/521.1</ref>.</bibl>
            </listBibl>
         </div>
      </back>
   </text>
</TEI>
