<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD with OASIS Tables with MathML3 v1.1 20151215//EN" "JATS-journalpublishing-oasis-article1-mathml3.dtd">
<article dtd-version="1.1" 
  xmlns:xlink="http://www.w3.org/1999/xlink" 
  xmlns:mml="http://www.w3.org/1998/Math/MathML">
  <front>
    <journal-meta>
      <journal-id journal-id-type="doi">https://doi.org/10.31784/zvr</journal-id>
      <journal-title-group>
        <journal-title xml:lang="hr">Zbornik Veleučilišta u Rijeci</journal-title>
      </journal-title-group>
      <issn pub-type="ppub">1848-1299</issn>
      <issn pub-type="epub">1849-1723</issn>
      <publisher>
        <publisher-name xml:lang="hr">Veleučilište u Rijeci</publisher-name>
        <publisher-name xml:lang="en">Polytechnic of Rijeka</publisher-name>
        <publisher-loc>Trpimirova 2, 51000 Rijeka
          <email xlink:href="zbornik@veleri.hr">zbornik@veleri.hr</email>
          <ext-link ext-link-type="url" xlink:href="https://www.veleri.hr/?q=zbornik">http://www.veleri.hr/?q=zbornik</ext-link>
        </publisher-loc>
      </publisher>
    </journal-meta>
    
    <article-meta>
      
      <article-id pub-id-type="doi">https://doi.org/10.31784/zvr.7.1.7</article-id>
      
      <article-categories>
        <subj-group subj-group-type="heading" xml:lang="en">
          <subject>Preliminary communication</subject>
        </subj-group>  
        <subj-group subj-group-type="heading" xml:lang="hr">
          <subject>Prethodno priopćenje</subject>
        </subj-group>  
      </article-categories>
      
      <title-group>
        <article-title xml:lang="en">TRANSLATION ERROR ANALYSIS IN TREAT: A WINDOWS APP USING THE MQM FRAMEWORK</article-title>
        <trans-title-group>
          <trans-title xml:lang="hr">ANALIZA POGREŠAKA U PREVOĐENJU U APLIKACIJI TREAT: WINDOWS APLIKACIJI KOJA SE TEMELJI NA MQM OKVIRU </trans-title>
        </trans-title-group>
      </title-group>
      
      <contrib-group>
        <contrib contrib-type="author">
          <name>
            <surname>Majcunić</surname>
            <given-names>Suzana</given-names>
          </name>
          <email xlink:href="suzana.majcunic@gmail.com">suzana.majcunic@gmail.com</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        
        
        <contrib contrib-type="author">
          <contrib-id contrib-id-type="orcid">https://orcid.org/0000-0003-4571-1546</contrib-id>
          <name>
            <surname>Matetić</surname>
            <given-names>Maja</given-names>
          </name>
          <email xlink:href="majam@uniri.hr">majam@uniri.hr</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        
        <contrib contrib-type="author">
          <contrib-id contrib-id-type="orcid">https://orcid.org/0000-0003-4079-4012</contrib-id>
          <name>
            <surname>Brkić Bakarić</surname>
            <given-names>Marija</given-names>
          </name>
          <email xlink:href="mbrkic@uniri.hr">mbrkic@uniri.hr</email>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        
        <aff id="aff1">
          <institution xml:lang="hr">University of Rijeka, Department of Informatics</institution>
          <addr-line>Radmile Matejčić 2, 51 000 Rijeka, Croatia</addr-line>
        </aff>
        
        <aff id="aff2">
          <institution xml:lang="hr">University of Rijeka, Department of Informatics</institution>
          <addr-line>Radmile Matejčić 2, 51 000 Rijeka, Croatia</addr-line>
        </aff>
        
        <aff id="aff3">
          <institution xml:lang="hr">University of Rijeka, Department of Informatics</institution>
          <addr-line>Radmile Matejčić 2, 51 000 Rijeka, Croatia</addr-line>
        </aff>
        
      </contrib-group>
      
      <pub-date>
        <day></day>
        <month>5</month>
        <year>2019</year>
      </pub-date>
      
      <volume>7</volume>
      <issue>1</issue>
      <fpage>149</fpage>
      <lpage>162</lpage>
      
      <history>
        <date date-type="received">
          <day>15</day>
          <month>1</month>
          <year>2019</year>
        </date>
        <date date-type="accepted">
          <day>4</day>
          <month>2</month>
          <year>2019</year>
        </date>
      </history>
      
      <permissions>
        <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by-nc/4.0/legalcode">
          <license-p>Creative Commons CC BY-NC 4.0</license-p>
        </license>
        
        <license license-type="open-access" xml:lang="en">
          <license-p>The usage of full-text of the articles can be used exclusively for personal, research-related or educational purposes, with regard to the authors' and publishers' rights.
            The users are allowed to read, download, copy, distribute, print and transform or use them for any other lawful purpose as long as they attribute the source in an appropriate manner and for the non-commercial purpose of the usage.</license-p>
        </license>
        
        
        <license license-type="open-access" xml:lang="hr">
          <license-p>Puni tekst objavljenih radova besplatno se smije koristiti za osobne, edukacijske ili istraživačke svrhe uz poštovanje autorskih prava autora i izdavača.
            Korisnici radove smiju besplatno čitati, preuzimati, kopirati, distribuirati, tiskati, prerađivati ili koristiti ih na druge zakonite načine, uz ispravno navođenje izvornika i nekomercijalnu svrhu uporabe.
          </license-p>
        </license>
        
      </permissions>
      
      <abstract xml:lang="en">
        <p>
          <italic>The aim of this research paper is to conduct a thorough analysis of
            inter-annotator agreement in the process of error analysis, which is well-known for its
            subjectivity and low level of agreement. Since the process is tiresome in its nature and
            the available user interfaces are pretty distinct from what the average annotator is
            accustomed to, a user-friendly Windows 10 application offering a more attractive user
            interface is developed with the aim to simplify the process of error analysis.
            Translations are performed with Google Translate engine and English-Croatian is selected
            as the language pair. Since there has been a lot of dispute on inter-annotator agreement
            and the need for guidelines has been often been emphasized as crucial, the annotators
            are given a very detailed introduction into the process of error analysis itself. They
            are given a presentation with a list of the MQM guidelines enriched with tricky cases.
            All annotators are native speakers of Croatian as the target language and have a
            linguistic background. The results demonstrate that a stronger agreement indicates more
            similar backgrounds and that the task of selecting annotators should be conducted more
            carefully. Furthermore, a training phase on a similar test set is deemed necessary in
            order to gain a stronger agreement.</italic>
        </p>
      </abstract>
      
      <trans-abstract xml:lang="hr">
        <p><italic>Cilj rada je izvršiti temeljitu analizu slaganja među označivačima u postupku
            analize pogrešaka koji je poznat po svojoj subjektivnosti i niskoj razini slaganja.
            Budući da je sam postupak po prirodi zamoran, a sučelja dostupnih alata i usluga
            poprilično se razlikuju od onog na što je prosječni označivač naviknut, u svrhu
            pojednostavljenja samog postupka analize pogrešaka razvijena je Windows 10 aplikacija s
            poznatim i atraktivnim korisničkim sučeljem. Englesko-hrvatski prijevodi preuzeti su s
            usluge Google Translate. Budući da je slaganje među označivačima čest predmet rasprave i
            da je od neospornog značaja istaknuta potreba za smjernicama, označivačima je dan vrlo
            detaljan uvid u postupak analize pogrešaka. Također, popis MQM smjernica uz primjere
            potencijalnih pogrešaka uobličen je u prezentaciju i dan označivačima na raspolaganje.
            Označivačima je ciljni, tj. hrvatski jezik materinski, a svi imaju određenu razinu
            lingvističke pozadine. Rezultati otkrivaju da veća razina slaganja ukazuje na sličnije
            formalno obrazovanje i da proces odabira označivača treba biti pažljivo osmišljen.
            Štoviše, testiranje na sličnom skupu podataka trebalo bi prethoditi odabiru označivača
            kako bi se postigla veća razina slaganja.</italic>
        </p>
      </trans-abstract>

      <kwd-group xml:lang="en">
        <kwd><italic>Windows 10 application</italic></kwd>
        <kwd><italic>error analysis</italic></kwd> 
        <kwd><italic>inter-annotator agreement</italic></kwd>
        <kwd><italic>machine translation evaluation</italic></kwd>
      </kwd-group>

      <kwd-group xml:lang="hr">
        <kwd><italic> Windows 10 aplikacija</italic></kwd>
        <kwd><italic>analiza pogrešaka</italic></kwd> 
        <kwd><italic>slaganje među označivačima</italic></kwd>
        <kwd><italic>evaluacija strojnog prevođenja</italic></kwd>
      </kwd-group>
      
      <funding-group>
        <award-group>
          <funding-source source-type="project">Grant No. 17.14.2.2.01.</funding-source>
          <funding-source source-type="funding organization">University of Rijeka</funding-source>
        </award-group>
      </funding-group>
      
    </article-meta>  
  </front>
  <body>
    <sec sec-type="intro"><label>1. INTRODUCTION</label><p>Ever since the machine translation (MT)
        society has made a huge shift from a phrase-based statistical MT to a neural MT (NMT), a lot
        of research initiatives have focused on translation error types in an attempt to better
        describe differences between these two approaches. Since the quality evaluation of machine
        translation is inherently subjective and the quality is context-dependent, there is no
        single standard in assessing translation quality 
        <xref ref-type="bibr" rid="r10">
        (Secara, 2001)
        </xref>
        . A single sentence can be
        translated in many ways. All this makes the quality assessment one of the most debated
        topics in translation. </p> <p>Automatic and human evaluations of MT mostly provide
      quantitative evaluation 
          <xref ref-type="bibr" rid="r11">
      (Stymne, 2011)
      </xref>
      . Error analysis refers to the identification and
      classification of individual errors in a translated text 
          <xref ref-type="bibr" rid="r12">
      (Stymne and Ahrenberg, 2012)
      </xref>
      . It is
      one of the well-accepted ways to assess translation in qualitative terms as it can point to
        strengths as well as weaknesses of a certain MT system 
          <xref ref-type="bibr" rid="r12">
        (Stymne and Ahrenberg, 2012)
        </xref>
        . When
        analysing or comparing different translation systems, one wants to get answers such as what
        kind of errors systems make more often, whether one system is superior in any or all
        aspects, whether a modification brings some improvements though invisible on the score, etc.
          <xref ref-type="bibr" rid="r9">
        (Popovic and Burchardt, 2011)
        </xref>
        . </p><p>Multidimensional quality framework (MQM) is a result
        of a thorough investigation of major human and machine translation assessment metrics
          <xref ref-type="bibr" rid="r6">
        (Lommel, Uszkoreit and Burchardt, 2014)
        </xref>
        . It can be described as a comprehensive list of
        quality issue types which serves as a mechanism for declaring specific metrics for quality
        assessment and error annotation tasks. </p><p>Human quality annotations are well-known for
        their low inter-annotator agreement (IAA)
          <xref ref-type="bibr" rid="r5">
        (Lommel, Popovic and Burchardt, 2014)
        </xref>
        . The low IAA
        might arise due to the disagreement on the severity of an error or on its precise span, but
        also due to errors which reflect multiple issues. Some authors 
          <xref ref-type="bibr" rid="r5">
        (Lommel, Popovic and
        Burchardt, 2014)
        </xref>
        even create a formal decision tree and improved guidelines to assist with
        annotation in order to improve IAA. Furthermore, the authors Stymne and Ahrenberg 
          <xref ref-type="bibr" rid="r12">
        (Stymne
        and Ahrenberg, 2012)
        </xref>
        argue that it is possible to get a reasonable agreement either by using
        a simple error taxonomy or by using a more detailed taxonomy and a set of
        guidelines.</p><p>There is a whole line of research comparing NMT to SMT with the aim of
        detecting its strengths or weaknesses. As expected, there is not much research in this area
        involving Croatian. A detailed human analysis of the outputs produced by NMT and PBMT
        systems when translating news texts in the English-to-Croatian language direction is
        performed in Kubička 
          <xref ref-type="bibr" rid="r3">
        (Klubička, 2017)
        </xref>
        . Errors are annotated according to a detailed error
        taxonomy relevant to the problematic linguistic phenomena of the language pair and compliant
        with the hierarchical listing of issue types defined as part of the MQM. </p><p>Compared to
        Kubička 
          <xref ref-type="bibr" rid="r3">
        (Klubička, 2017)
        </xref>
        , the number of annotators in this paper is doubled, i.e. there are
        four annotators. However, their background is less similar. Three out of four annotators are
        final-year master students. The IAA is calculated on three levels: the sentence level
        irrespective of the error type, number, and position; the sentence level irrespective of the
        error type and position; and error type. Since the task of evaluation or annotation is
        generally often given to students, this paper puts focus on checking their suitability by
        comparing IAA scores with respect to their formal education background.Please note that the
        analysis is less detailed compared to Kubička 
          <xref ref-type="bibr" rid="r3">
        (Klubička, 2017)
        </xref>
        , which should result in
        higher IAA scores.</p><p>The paper is organized as follows. In the next section the
        methodology is described. It is followed by results. The discussion is provided in section
        4. Section 5 concludes the paper.</p><p> </p></sec>
    
    <sec sec-type="Methods">
      <label>5. METHODOLOGY</label>
      <p>The following section is divided into two subsections. In the first subsection the
        development of the tool used for annotation is outlined, and its user interface and features
        are presented, and in the second subsection the experimental study is described.</p>
      <p><bold>2.1 TREAT application </bold></p>
      <p>Since annotators do not usually have advanced computer skills, the first goal set for this
        study is to create a friendly working environment to which they are accustomed to. The app
        should support displays of any size and orientation so that the annotators can do their job
        anytime and anywhere. Universal Windows Platform (UWP) is chosen as the new open-source and
        cross-platform framework for building applications for all operating systems, including
        Windows, Mac, and Linux. UWP apps work on all Windows 10 devices (Figure 1). .NET Core is
        chosen as the application programming interface (API). The programming language used is C#.
        Graphical part of the application is implemented in the declarative eXtensible Application
        Markup Language (XAML), which is also developed by Microsoft. The name of the app is TREAT
        (TRanslation Error Annotation Tool). The user interface is shown in Figure 2. </p>
      
      <p>
        <fig id="f1">
          <label>Figure 1.</label>
          <caption><p>Windows device family overview</p></caption>
          <graphic xlink:href="zbornik-veleri-7-149-g1.jpg"/>
          <p>Source: 
            <xref ref-type="bibr" rid="r7">
            (Microsoft, 2018)</xref>
          </p>
        </fig>
      </p>
      
      <p>
        <fig id="f2">
          <label>Figure 2.</label>
          <caption><p>TREAT user interface</p></caption>
          <graphic xlink:href="zbornik-veleri-7-149-g2.jpg"/>
        </fig>
      </p>
      <p>Since using older versions of Microsoft Visual Studio on certain platforms that precede
        Windows 10 has some limitations, the development is done on Windows 10 platform. The
        integrated development environment the app is built in, is the Microsoft Visual Studio
        Enterprise 2017 (version 15.7.4). </p>
      <p>The app has a built-in support for MQM hierarchy. Since the tree-view control is used for
        the purpose, the minimum Windows version the app can run on is 1083. The annotation process
        in TREAT is shown in Figure 3. The input to the annotation process are two textual files –
        the source file and the target file. Additionally, the file with reference translations can
        be provided. If the annotation project has already been created, then the project file can
        be used as input.</p>
      
      <p>
        <fig id="f3">
          <label>Figure 3.</label>
          <caption><p>Annotation in TREAT</p></caption>
          <graphic xlink:href="zbornik-veleri-7-149-g3.jpg"/>
        </fig>
      </p>
      
      <p>Basic features of the developed app are listed below:</p>
      <list list-type="bullet">
        <list-item><p>MQM hierarchy can be easily modified (new nodes can be added, nodes can be excluded from evaluation, etc.)</p></list-item>
        <list-item><p>a detailed statistics of annotated issue types can be generated and basic visualizations of statistical data can be generated (Figure 4)</p></list-item>
        <list-item><p>statistics can be saved in a textual file (Figure 5).</p></list-item>
        </list>
      
      <p>
        <fig id="f4">
          <label>Figure 4.</label>
          <caption><p>Statistics and visualizations in TREAT</p></caption>
          <graphic xlink:href="zbornik-veleri-7-149-g4.jpg"/>
        </fig>
      </p>
      
      <p>
        <fig id="f5">
          <label>Figure 5.</label>
          <caption><p>An excerpt from the file with statistics</p></caption>
          <graphic xlink:href="zbornik-veleri-7-149-g5.jpg"/>
        </fig>
      </p>
      <p><bold>2.2 	Experimental study
      </bold></p>
      <p> The following subsection is divided into five parts, which give the details on the MQM
        framework, the annotators, the test set, the official MQM annotation guidelines, and the
        inter-annotator agreement scores. Google Translate NMT engine is used for obtaining Croatian
        translations of English sentences which are then annotated by human annotators and the
        obtained annotations are used for calculating inter-annotator agreement scores. </p>
      <p><bold>2.2.1	MQM framework</bold>
      </p>
      <p>MQM defines over 100 issue types. The term<italic> issue</italic> is used to refer to any
        potential error detected in a text. At the top level there are 10 categories:
          <italic>accuracy, design, fluency, internationalization, locale convention, style,
          terminology, verity, compatibility,</italic> and <italic>other</italic>.Since it would not
        be viable to perform the annotation process using the full MQM tag set, it is necessary to
        choose a smaller subset in accordance with research questions. Naturally, starting with the
        core tag set is considered to be a good practice (Figure 6). </p>
      
      <p>
        <fig id="f6">
          <label>Figure 6.</label>
          <caption><p>MQM core</p></caption>
          <graphic xlink:href="zbornik-veleri-7-149-g6.jpg"/>
          <p>Source: 
            <xref ref-type="bibr" rid="r8">
            (MQM definition, 2015)</xref>
          </p>
        </fig>
      </p>
      <p>Since the focus of this research is on testing the software and investigating IAA in
        relation to linguistic background, the annotators are instructed to use only the MQM core. </p>
      <p>While issue types such as <italic>addition, mistranslation, omission, untranslated
          </italic>or<italic> spelling </italic>should be pretty clear, short clarifications are
        provided for the remaining issues present in the MQM core. <italic>Grammar </italic>should
        be applied to all the grammar or syntax related issues of the text, other than
          <italic>spelling</italic> and <italic>orthography</italic>. Maybe somewhat
        counter-intuitive, when the content uses wrong pronouns or verb forms when their formal
        counterparts are required or vice-versa, <italic>grammatical register </italic>should be
        annotated and not <italic>style</italic>. <italic>Consistency </italic>issueis detected by
        reading the text with understanding. For example, the text states one fact or certain
        instructions in one place and something contradictory in the other. Issues related to the
        mechanical presentation of a text (punctuation is used incorrectly or a text has an
        extraneous hard return in the middle of a paragraph) should be annotated as
          <italic>typography</italic>. This category should be used for any typographical errors
        other than spelling. If the exact nature of the error cannot be determined and a major break
        down in fluency occurs, <italic>unintelligible </italic>mark-up should be applied. An
        example of issue annotated as <italic>locale convention</italic> might be using a comma (,)
        instead of a period (.) as a thousands separator. An example of a <italic>style
        </italic>issue is when the source text is light and humorous, while the target one is
        serious and formal in style. <italic>Terminology</italic> should not be used if a text is
        simply mistranslated but it should be used in cases where the translation could be a valid
        translation of the source if certain terminology is not mandated. Since
          <italic>Design</italic> refers to incorrect formatting, and the annotators were provided
        with source and target sentences in textual format, this issue category might have been
        easily excluded from the annotation process. <italic>Verity</italic> issue is triggered when
        the text makes statements that contradict the world of the text, i.e. the text says a
        feature is present on a certain model of automobile (because it is true in the source
        locale) when in fact it is not available in the target locale. <italic>Completeness</italic>
        can be contrasted with <italic>omission</italic> as it refers to instances in which needed
        content is missing in the source language, while <italic>omission</italic> refers to
        instances in which content present in the source language is not present in the translation.
        Cases in which the source text does not meet <italic>legal requirements</italic> are
        generally critical errors that will require rewriting the source text. An example might be
        the translation of some notice which should have been replaced according to the instructions
        and not merely translated. An example of a <italic>locale-specific content</italic> might be
        a text in a manual which describes a feature not available in the product on the target
        market. As expected, due to the nature of the source text, no issues under the category
          <italic>Verity</italic> have been detected.</p>
      <p>Since the annotations for <italic>Omission </italic>were not uniformly laid (i.e. some
        annotators annotated source words as omissions and some annotated spaces in the target as
        omissions), this issue subtype has been excluded from our analysis. Reference sentences have
        not been provided.</p>
      <p><bold>2.2.2	Annotators</bold></p>
      <p>Annotators are all native speakers of Croatian. One of the annotators has a BA degree in
        English language (E1), two in German (E2, E3), and one has a Master degree in English (E4).
        They all have a BA degree in Informatics and the first three are on their final year of
        Master studies. All the annotators are very confident of their knowledge of English
        language. Additionally, student annotators are awarded additional credits for the completion
        of the task within the elective course on translation tools. The possibility of gaining
        scores ought to make annotators more perceptive, cautious, and adherent to the
        guidelines.</p>
      <p><bold>2.2.3	Test set</bold></p>
      <p> Our test set consists of the randomly selected sentences of the English test set of 2016
        news translation shared task at WMT <fn>
          <label>1</label>
          <p>http://www.statmt.org/wmt16/translation-task.html</p>
        </fn> . The annotators annotated 50 sentences. The size of the test set is limited to 50
        sentences due to several reasons. The first reason is that the annotation process is
        extremely time-consuming so it would be too much to ask annotators to annotate more
        sentences under the volunteering framework. The second reason is that annotators might
        become too tired and thus less attentive under annotation overload. They were only presented
        with the English source text, and its respective GT output
        <fn><label>2</label><p>obtained December 6, 2018 </p></fn>
        . The reader should be aware of
        the fact that GT output evolves with time and that the translations obtained only a month
        later differ greatly and are of seemingly much better quality. </p>
      <p><bold>2.2.4	Guidelines</bold></p>
      <p> Prior to annotation, the annotators were familiarized with the TREAT software and the
        official MQM annotation guidelines, which offer detailed instructions for annotation within
        the MQM framework
        <fn><label>3</label><p>A decision tree provided to aid the annotation process can be found at http://www.qt21.eu/downloads/ annotatorsGuidelines-2014-06-11.pdf.</p></fn>
        . These guidelines include the decision tree. The decision tree is
        organized in such a way that it eliminates specific issues before moving to general ones.
        Some of the guidelines are outlined here to familiarize the reader with the annotation
        process. </p>
      <list>
        <list-item><p>Always select the level about which you are most certain – do not guess!</p></list-item>
        <list-item><p>If multiple types apply, select the first one that the decision tree guides you to.</p></list-item>
        <list-item><p>Annotate only the words that constitute an error, even if there are other words in between.</p></list-item>
        <list-item><p>If correcting one error will eliminate other errors, tag only that error.</p></list-item>
      </list>
      <p><bold>2.2.5	IAA</bold></p>
      <p>After the process of annotation, IAA is calculated using Cohen’s kappa (κ) 
        <xref ref-type="bibr" rid="r1">
        (Cohen, 1960)
        </xref>
        .
        The Cohen’s Kappa is given in (1), where po refers to the relative observed agreement among
        annotators or the accuracy, and pe refers to the expected agreement. Since Cohen's Kappa is
        appropriate only for pair-wise comparisons, the similarity between each pair of annotators
        is evaluated separately. The authors Lommel, Popovic and Burchardt 
        <xref ref-type="bibr" rid="r9">
        (Lommel, Popovic and
        Burchardt, 2014)
        </xref>
        additionally take the average score as the final measure. </p>
      <disp-formula>
        <label>(1)</label>
        <mml:math>
          <mml:mi>K</mml:mi>
          <mml:mo>=</mml:mo>
          <mml:mfrac>
            <mml:mrow>
              <mml:msub>
                <mml:mrow>
                  <mml:mi>p</mml:mi>
                </mml:mrow>
                <mml:mrow>
                  <mml:mi>o</mml:mi>
                </mml:mrow>
              </mml:msub>
              <mml:mo>-</mml:mo>
              <mml:msub>
                <mml:mrow>
                  <mml:mi>p</mml:mi>
                </mml:mrow>
                <mml:mrow>
                  <mml:mi>e</mml:mi>
                </mml:mrow>
              </mml:msub>
            </mml:mrow>
            <mml:mrow>
              <mml:mn>1</mml:mn>
              <mml:mo>-</mml:mo>
              <mml:msub>
                <mml:mrow>
                  <mml:mi>p</mml:mi>
                </mml:mrow>
                <mml:mrow>
                  <mml:mi>e</mml:mi>
                </mml:mrow>
              </mml:msub>
            </mml:mrow>
          </mml:mfrac>
        </mml:math>
      </disp-formula>
      
      <p>IAA scores are calculated at the sentence level, meaning that positions or the exact tokens
        annotated as errors are disregarded. As Lommel
        <xref ref-type="bibr" rid="r5">
        (Lommel, Popovic and Burchardt, 2014)
        </xref>
        point
        out, though annotators can agree that a sentence contains the same issue, they might
        disagree on the span that the issue covers. In the first calculations only error as the most
        general category is taken into account or whether there is an agreement that error exists at
        all. This agreement is labelled ‘Any errors’, similarly to the authors in Klubička
        <xref ref-type="bibr" rid="r3">
        (Klubička, 2017)
        </xref>
        . A refined score is calculated by taking into account the number of errors
        detected in the sentence. Afterwards, calculations are performed for every error type
        separately. All three level calculations exclude error positions. This means that the scores
        can be either equal to the scores which take positions into account or overestimates. Since
        Cohen's Kappa is appropriate only for pair-wise comparisons, Fleiss’ kappa is also
        calculated
        <xref ref-type="bibr" rid="r2">
        (Fleiss, 1971)
        </xref>
        . </p>
      <p>The value <italic>p<sub>e</sub></italic>is the sum of squares of the proportions of all assignments
        made to each category. In order to calculate <italic>p<sub>e</sub></italic>, first the extent to which
        annotators agree is calculated for each individual sentence according to (2), where
          <italic>n </italic>stands for the number of annotators and <italic>k </italic>for the
        number of categories, and then the average is taken.</p>
      <disp-formula>
        <label>(2)</label>
        <mml:math>
          <mml:msub>
            <mml:mrow>
              <mml:mi>P</mml:mi>
            </mml:mrow>
            <mml:mrow>
              <mml:mi>i</mml:mi>
            </mml:mrow>
          </mml:msub>
          <mml:mo>=</mml:mo>
          <mml:mfrac>
            <mml:mrow>
              <mml:mn>1</mml:mn>
            </mml:mrow>
            <mml:mrow>
              <mml:mi>n</mml:mi>
              <mml:mfenced separators="|">
                <mml:mrow>
                  <mml:mi>n</mml:mi>
                  <mml:mo>-</mml:mo>
                  <mml:mn>1</mml:mn>
                </mml:mrow>
              </mml:mfenced>
            </mml:mrow>
          </mml:mfrac>
          <mml:mfenced open="[" close="]" separators="|">
            <mml:mrow>
              <mml:mfenced separators="|">
                <mml:mrow>
                  <mml:mrow>
                    <mml:munderover>
                      <mml:mo stretchy="false">∑</mml:mo>
                      <mml:mrow>
                        <mml:mi>j</mml:mi>
                        <mml:mo>=</mml:mo>
                        <mml:mn>1</mml:mn>
                      </mml:mrow>
                      <mml:mrow>
                        <mml:mi>k</mml:mi>
                      </mml:mrow>
                    </mml:munderover>
                    <mml:mrow>
                      <mml:msubsup>
                        <mml:mrow>
                          <mml:mi>n</mml:mi>
                        </mml:mrow>
                        <mml:mrow>
                          <mml:mi>i</mml:mi>
                          <mml:mi>j</mml:mi>
                        </mml:mrow>
                        <mml:mrow>
                          <mml:mn>2</mml:mn>
                        </mml:mrow>
                      </mml:msubsup>
                    </mml:mrow>
                  </mml:mrow>
                </mml:mrow>
              </mml:mfenced>
              <mml:mo>-</mml:mo>
              <mml:mi>n</mml:mi>
            </mml:mrow>
          </mml:mfenced>
        </mml:math>
      </disp-formula>
      
    </sec>
    
    <sec sec-type="Resaults">
      <label>3.	RESULTS</label>
      <p>Table 1 shows the distribution of issue types per annotator. </p>
      <p>First Cohen's kappa is calculated pairwise by just taking into account whether a sentence
        has been annotated as erroneous or not (labelled 'Any error' as mentioned previously). The
        agreement on the number of errors per sentence is also calculated. The IAA scores are shown
        in Table 2. The darker shade of grey colour indicates stronger IAA. The asterisk (*) next to
        the annotators' labels stands for Fleiss' kappa. </p>
      <p>Table 3 gives IAA scores per issue type. <italic>Terminology</italic>,
          <italic>Style</italic> and <italic>Grammatical Register</italic> are omitted, as these
        annotations seem to be tied to a specific annotator.</p>
    </sec>
    
    <sec sec-type="Discussion">
      <label>4.	DISCUSSION </label>
      <p>Taking a closer look at the IAA results, it can be concluded that despite very precise
        guidelines and getting additional credits for the task, solely linguistic background is not
        enough to get a substantial or almost perfect IAA. According to Landis 
        <xref ref-type="bibr" rid="r4">
        (Landis and Koch,
        1977)
        </xref>
        , 0–0.2 represents slight, 0.2–0.4 fair, 0.4–0.6 moderate, 0.6–0.8 substantial, and
        0.8–1.0 almost perfect agreement. The ’Any errors’ value represents agreement on whether
        there are errors in a given sentence, while ‘Number of errors’ represents agreement on the
        number of errors recorded per sentence.</p>
      <p>The numbers of errors recorded per annotator differ greatly (Table 1). If the annotator
        with the highest number of errors recorded is taken as the base, it is evident that the
        remaining three annotators detect only between 72 to 88% errors. It is also interesting that
        one annotator has many doubts as far as the issues under the accuracy category are concerned
        and therefore, reluctant to make guesses, used the superordinate category level, while
        others have no such doubts.</p>
      
      <p>
        <table-wrap position="margin">
          <label>Table 1.</label>
          <caption>
            <title>The distribution of issue types found per annotator</title>
          </caption>
          <table border="1" frame="box" width="100%">
            <col width=""/>
            <col width=""/>
            <col width=""/>
            <col width=""/>
            <col width=""/>
            <thead>
              <tr>
                <th/>
                <th align="left" valign="middle">E1 </th>
                <th align="left" valign="middle">E2 </th>
                <th align="left" valign="middle">E3 </th>
                <th align="left" valign="middle">E4</th>
                
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left" valign="middle">Accuracy </td>
                <td align="left" valign="middle">12</td>
                <td align="left" valign="middle">0</td>
                <td align="left" valign="middle">0 </td>
                <td align="left" valign="middle">0 </td>
                <td align="left" valign="middle"/>
              </tr>
              <tr>
                <td align="left" valign="middle">Addition </td>
                <td align="left" valign="middle">2 </td>
                <td align="left" valign="middle">11 </td>
                <td align="left" valign="middle">3 </td>
                <td align="left" valign="middle">19</td>
              </tr>
              <tr>
                <td align="left" valign="middle">Grammar </td>
                <td align="left" valign="middle">22 </td>
                <td align="left" valign="middle">42 </td>
                <td align="left" valign="middle">64 </td>
                <td align="left" valign="middle">69</td>
              </tr>
              <tr>
                <td align="left" valign="middle">Grammatical register </td>
                <td align="left" valign="middle">13</td>
                <td align="left" valign="middle"> 0</td>
                <td align="left" valign="middle"> 0</td>
                <td align="left" valign="middle"> 0</td>
              </tr>
              <tr>
                <td align="left" valign="middle">Inconsistency </td>
                <td align="left" valign="middle">27</td>
                <td align="left" valign="middle"> 0</td>
                <td align="left" valign="middle"> 0</td>
                <td align="left" valign="middle"> 1</td>
              </tr>
              <tr>
                <td align="left" valign="middle">Locale convention </td>
                <td align="left" valign="middle">1 </td>
                <td align="left" valign="middle">0 </td>
                <td align="left" valign="middle">0 </td>
                <td align="left" valign="middle">6</td>
              </tr>
              <tr>
                <td align="left" valign="middle">Mistranslation </td>
                <td align="left" valign="middle">28</td>
                <td align="left" valign="middle"> 43</td>
                <td align="left" valign="middle"> 47</td>
                <td align="left" valign="middle"> 40</td>
              </tr>
              <tr>
                <td align="left" valign="middle">Spelling </td>
                <td align="left" valign="middle">1 </td>
                <td align="left" valign="middle">0 </td>
                <td align="left" valign="middle">0 </td>
                <td align="left" valign="middle">1</td>
              </tr>
              <tr>
                <td align="left" valign="middle">Style</td>
                <td align="left" valign="middle"> 0 </td>
                <td align="left" valign="middle">0</td>
                <td align="left" valign="middle"> 0</td>
                <td align="left" valign="middle"> 1</td>
              </tr>
              <tr>
                <td align="left" valign="middle">Terminology </td>
                <td align="left" valign="middle">0</td>
                <td align="left" valign="middle"> 0</td>
                <td align="left" valign="middle"> 5</td>
                <td align="left" valign="middle"> 0</td>
              </tr>
              <tr>
                <td align="left" valign="middle">Typography </td>
                <td align="left" valign="middle">1 </td>
                <td align="left" valign="middle">0 </td>
                <td align="left" valign="middle">0 </td>
                <td align="left" valign="middle">4</td>
              </tr>
              <tr>
                <td align="left" valign="middle">Unintelligible </td>
                <td align="left" valign="middle">0 </td>
                <td align="left" valign="middle">0 </td>
                <td align="left" valign="middle">1 </td>
                <td align="left" valign="middle">1</td>
              </tr>
              <tr>
                <td align="left" valign="middle">Untranslated </td>
                <td align="left" valign="middle">7 </td>
                <td align="left" valign="middle">7 </td>
                <td align="left" valign="middle">6 </td>
                <td align="left" valign="middle">2</td>
              </tr>
              <tr>
                <td align="left" valign="middle">TOTAL </td>
                <td align="left" valign="middle">114</td>
                <td align="left" valign="middle"> 103</td>
                <td align="left" valign="middle"> 126</td>
                <td align="left" valign="middle"> 144</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </p>
      
      <p>
        <table-wrap position="margin">
          <label>Table 2.</label>
          <caption>
            <title>‘Any error’ and the number of errors IAA κ scores</title>
          </caption>
          <table border="1" frame="box" width="60%">
            <col width=""/>
            <col width=""/>
            <col width=""/>
            <thead>
              <tr>
                <th/>
                <th align="left" valign="middle">Any error</th>
                <th align="left" valign="middle"> Number of errors</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left" valign="middle">E1-E2 </td>
                <td align="right" valign="middle">0.42 </td>
                <td align="right" valign="middle">0.27</td>
              </tr>
              <tr>
                <td align="left" valign="middle">E1-E3</td>
                <td align="right" valign="middle"> 0.41 </td>
                <td align="right" valign="middle">0.33</td>
              </tr>
              <tr>
                <td align="left" valign="middle">E1-E4 </td>
                <td align="right" valign="middle">0.63 </td>
                <td align="right" valign="middle">0.52</td>
              </tr>
              <tr>
                <td align="left" valign="middle">E2-E3 </td>
                <td align="right" valign="middle">0.45 </td>
                <td align="right" valign="middle">0.39</td>
              </tr>
              <tr>
                <td align="left" valign="middle">E2-E4 </td>
                <td align="right" valign="middle">0.42 </td>
                <td align="right" valign="middle">0.1</td>
              </tr>
              <tr>
                <td align="left" valign="middle">E3-E4 </td>
                <td align="right" valign="middle">0.41 </td>
                <td align="right" valign="middle">0.2</td>
              </tr>
              <tr>
                <td align="left" valign="middle">E1-E2-E3-E4 </td>
                <td align="right" valign="middle">0.46 </td>
                <td align="right" valign="middle">0.21</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </p>
      
      <p>
        <table-wrap position="margin">
          <label>Table 3.</label>
          <caption>
            <title>. IAA per issue type</title>
          </caption>
          <table border="1" frame="box" width="100%">
            <col width=""/>
            <col width=""/>
            <col width=""/>
            <col width=""/>
            <col width=""/>
            <col width=""/>
            <col width=""/>
            <col width=""/>
            <col width=""/>
            <col width=""/>
            <col width=""/>
            <thead>
              <tr>
                <th/>
                <th align="center" valign="bottom">Accuracy </th>
                <th align="center" valign="bottom">Addition </th>
                <th align="center" valign="bottom">Grammar </th>
                <th align="center" valign="bottom">Inconsist. </th>
                <th align="center" valign="bottom">Mistransl. </th>
                <th align="center" valign="bottom">Locale conven. </th>
                <th align="center" valign="bottom">Spelling</th>
                <th align="center" valign="bottom"> Typography </th>
                <th align="center" valign="bottom">Unintellig.</th>
                <th align="center" valign="bottom"> Untransl.</th>
                
              </tr>
            </thead>
            <tbody>
              <tr>
                <td align="left" valign="bottom">E1-E2 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">0.41 </td>
                <td align="right" valign="bottom">0.21 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">0.51</td>
                <td align="right" valign="bottom"> 0 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">- </td>
                <td align="right" valign="bottom">0.43</td>
              </tr>
              <tr>
                <td align="left" valign="bottom">E1-E3 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">-0.05 </td>
                <td align="right" valign="bottom">0.24 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">0.46 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">0.49</td>
              </tr>
              <tr>
                <td align="left" valign="bottom">E1-E4 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">0.21 </td>
                <td align="right" valign="bottom">0.32 </td>
                <td align="right" valign="bottom">0.12 </td>
                <td align="right" valign="bottom">0.57 </td>
                <td align="right" valign="bottom">-0.03 </td>
                <td align="right" valign="bottom">-0.02 </td>
                <td align="right" valign="bottom">-0.03 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">0.20</td>
              </tr>
              <tr>
                <td align="left" valign="bottom">E2-E3 </td>
                <td align="right" valign="bottom">- </td>
                <td align="right" valign="bottom">0.34 </td>
                <td align="right" valign="bottom">0.45 </td>
                <td align="right" valign="bottom">- </td>
                <td align="right" valign="bottom">0.23</td>
                <td align="right" valign="bottom"> -</td>
                <td align="right" valign="bottom"> -</td>
                <td align="right" valign="bottom"> -</td>
                <td align="right" valign="bottom"> 0</td>
                <td align="right" valign="bottom"> 0.29</td>
              </tr>
              <tr>
                <td align="left" valign="bottom">E2-E4 </td>
                <td align="right" valign="bottom">- </td>
                <td align="right" valign="bottom">0.51 </td>
                <td align="right" valign="bottom">0.44 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">0.56</td>
                <td align="right" valign="bottom"> 0</td>
                <td align="right" valign="bottom"> 0</td>
                <td align="right" valign="bottom"> 0</td>
                <td align="right" valign="bottom"> 0</td>
                <td align="right" valign="bottom"> 0.20</td>
              </tr>
              <tr>
                <td align="left" valign="bottom">E3-E4 </td>
                <td align="right" valign="bottom">- </td>
                <td align="right" valign="bottom">0.17</td>
                <td align="right" valign="bottom"> 0.60</td>
                <td align="right" valign="bottom"> 0 </td>
                <td align="right" valign="bottom">0.36 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">0 </td>
                <td align="right" valign="bottom">1 </td>
                <td align="right" valign="bottom">-0.06</td>
              </tr>
              <tr>
                <td align="left" valign="bottom">E1-E2-E3-E4* </td>
                <td align="right" valign="bottom">-0.29 </td>
                <td align="right" valign="bottom">0.24 </td>
                <td align="right" valign="bottom">0.22 </td>
                <td align="right" valign="bottom">-0.02 </td>
                <td align="right" valign="bottom">0.24 </td>
                <td align="right" valign="bottom">-0.03 </td>
                <td align="right" valign="bottom">-0.01 </td>
                <td align="right" valign="bottom">-0.02 </td>
                <td align="right" valign="bottom">0.33 </td>
                <td align="right" valign="bottom">0.29</td>
              </tr>
            </tbody>
          </table>
          
        </table-wrap>
      </p>
      <p>In the work of Klubička 
        <xref ref-type="bibr" rid="r3">
        (Klubička, 2017)
        </xref>
        , the κ scores are relatively consistent across all
        error types for each analysed system, mostly ranging between 0.35 and 0.55. The obtained IAA
        is mostly fair for the ‘number of errors’, and moderate for the 'any error' scenario. Given
        the lowered complexity of the annotation schema, higher scores have been expected. However,
        it seems that scores encode annotators’ backgrounds. A substantial agreement exists between
        the two annotators who graduated or will graduate English in the ‘Any error’ category. If
        the number of errors annotated per sentence is taken into account, the agreement is lower,
        but still the highest for E1 and E4. For most IAA tasks, agreement of at least 0.85 is
        required for a measure to be considered reliable. </p>
      <p>The discussion is restricted to the obtained agreements on the four issue subtypes for
        which each individual annotator has spent at least 1% of his or her annotations –
          <italic>addition, grammar, mistranslation,</italic> and <italic>untranslated</italic>.
        Although <italic>fluency</italic> can be judged by looking only at the target sentence, the
        agreement in the constituting issue sub-type <italic>grammar</italic> is surprisingly low,
        i.e. from fair to moderate, with the exception of agreement between E3 and E4 which is
        substantial. The agreement in the category <italic>mistranslation</italic> is the highest
        for annotators E1 and E4, although very close to the agreement between E2 and E4. Although
        these pairwise agreements reach moderate and sporadically substantial agreements, Fleiss’
        kappa scores are fair for all but ‘any error’ category. </p>
      <p>Since the agreement on the <italic>untranslated</italic> content is not strikingly high as
        one would expect, a manual analysis of the sentences is conducted. It turns out that as far
        as <italic>untranslated</italic> content is concerned, annotators mostly disagree on proper
        nouns. Also, untranslated word to which a suffix is added in accordance with target language
        grammar is treated by one of the annotators as <italic>unintelligible</italic> and by others
        as <italic>untranslated</italic>. </p>
      <p>A particular attention is paid to the sparse annotation types. It can be concluded that it
        is worth investigating whether even intra-annotator agreement would reach substantial level.
        For example, a period missing after the year has once been annotated as locale convention
        and some other time as typography by the same annotator. By taking a closer look at the
        explanations given previously, the annotator’s confusion is justified. First the annotators
        are instructed to annotate issues related to the mechanical presentation of the text
        (punctuation is used) as <italic>typography</italic>, and later on using a comma (,) instead
        of a period (.) as a thousands separator is provided as an example of <italic>locale
          convention</italic> issue. Although some errors stem from incomplete or confusing
        instructions, some can be attributed to the lack of attention. Some annotators fail to
        detect some issues (e.g. ft as the unit of measure), morphologically wrong term has been
        identified as misspelling by one of the annotators, style annotation has been applied to one
        pronoun, although instructions explicitly say that such cases should be annotated as
        grammatical register, etc.</p>
    </sec>
    
    <sec sec-type="Conclusion">
      <label>5.	CONCLUSION</label>
      <p>Annotators did not report any bugs or problems with the developed application. However,
        during the result analysis phase it became obvious that some features had to be added. The
        main drawback was that one had to use additional tools and filters on the project files for
        more in-depth analysis which included calculating Cohen’s and Fleiss’ kappa scores. It would
        be extremely useful if the scores could be obtained from the very app. The first feature
        should enable reading in two project files and calculating Cohen’s kappa scores per error as
        well as per error type on a sentence basis. The second should enable reading in any number
        of project files and calculating Fleiss’ kappa score on the same basis.</p>
      <p>More importantly, the results presented in this paper raise concerns about employing
        students as annotators since it is difficult to measure their background knowledge and
        select those with similar knowledge levels. Although one might conclude that not even
        awarding additional credits motivates annotators enough to read guidelines and study
        examples, it seems plausible that guidelines and examples are too simplistic and that
        annotators lack training on a set of sentences compiled from the same source as the test
        set. An evaluation filter might also be employed which would correct annotations of less
        competent evaluators. In that way the annotation process might be conducted in two passes –
        first pass by all the annotators and then second pass by the ‘super-annotator’, i.e. someone
        who is more competent or has the best score on the test taken by annotators. To conclude,
        the goal of the analysis presented in this and similar papers should not be merely pursuing
        high IAA but aim at obtaining high-quality annotations as these affect the future of MT. In
        future researches a similar test set with referent annotations will be prepared and a
        training on these real-world examples will be conducted prior to the annotation task. A
        suggested two phase annotation procedure will also be further investigated. </p>
    </sec>
    
  </body>
  
  <back>
    <ref-list>
      <ref id="r1">
        <label>1</label>
        <mixed-citation publication-type="journal">
          <person-group>
            <name>
              <surname>Cohen</surname>
              <given-names>J.</given-names>
            </name>
          </person-group>
          <date date-type="pub">
            <year>1960</year>
          </date>
          <article-title>‘A Coefficient of Agreement For Nominal Scales’</article-title>
          <source>Educational and Psychological Measurement</source>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>37</fpage>
          <lpage>46</lpage>
          <ext-link xlink:href="https://doi.org/10.1177/001316446002000104"></ext-link>
        </mixed-citation>
      </ref>
      
      <ref id="r2">
        <label>2</label>
        <mixed-citation publication-type="journal">
          <person-group>
            <name>
              <surname>Fleiss</surname>
              <given-names>J.L.</given-names>
            </name>
            <name>
              <surname></surname>
              <given-names></given-names>
            </name>
          </person-group>
          <date date-type="pub">
            <year>1971</year>
          </date>
          <article-title>‘Measuring nominal scale agreement among many raters’</article-title>
          <source>Psychological Bulletin</source>
          <volume>76</volume>
          <issue>5</issue>
          <fpage>378</fpage>
          <lpage>382</lpage>
          <ext-link xlink:href="https://doi.org/10.1037/h0031619"></ext-link>
        </mixed-citation>
      </ref>
      
      <ref id="r3">
        <label>3</label>
        <mixed-citation publication-type="book">
          <person-group>
            <name>
              <surname>Klubička</surname>
              <given-names>F.</given-names>
            </name>
          </person-group>
          <source>‘Fine-grained Human Evaluation of an English to Croatian Hybrid Machine Translation System’</source>
          <date date-type="pub">
            <year>2017.</year>
          </date>
          <ext-link xlink:href="https://doi.org/10.1515/pralin-2017-0014"></ext-link>
        </mixed-citation>
      </ref>
      
      
      <ref id="r4">
        <label>4</label>
        <mixed-citation publication-type="journal">
          <person-group>
            <name>
              <surname>Landis</surname>
              <given-names>J.R.</given-names>
            </name>
            <name>
              <surname>Koch</surname>
              <given-names>G.G.</given-names>
            </name>
          </person-group>
          <date date-type="pub">
            <year>1977</year>
          </date>
          <article-title>‘The Measurement of Observer Agreement for Categorical Data Data for Categorical of Observer Agreement The Measurement’</article-title>
          <source>Biometrics</source>
          <volume>33</volume>
          <issue>1</issue>
          <fpage>159</fpage>
          <lpage>174</lpage>
          <ext-link xlink:href="https://doi.org/10.2307/2529310"></ext-link>
        </mixed-citation>
      </ref>
      
      <ref id="r5">
        <label>5</label>
        <mixed-citation publication-type="book">
          <person-group>
            <name>
              <surname>Lommel</surname>
              <given-names>A.</given-names>
            </name>
            <name>
              <surname>Popovic</surname>
              <given-names>M.</given-names>
            </name>
            <name>
              <surname>Burchardt</surname>
              <given-names>A.</given-names>
            </name>
          </person-group>
          <source>‘Assessing Inter-Annotator Agreement for Translation Error Annotation Assessing Inter - A nnotator Agreement for Translation Error Annotation’</source>
          <publisher-name>MTE: Workshop on Automatic and Manual Metrics for Operational Translation Evaluation</publisher-name>,
          <date date-type="pub">
            <year>2014.</year>
          </date>
        </mixed-citation>
      </ref>
      
      <ref id="r6">
        <label>6</label>
        <mixed-citation publication-type="journal">
          <person-group>
            <name>
              <surname>Lommel</surname>
              <given-names>A.</given-names>
            </name>
            <name>
              <surname>Uszkoreit</surname>
              <given-names>H.</given-names>
            </name>
            <name>
              <surname>Burchardt</surname>
              <given-names>A.</given-names>
            </name>
          </person-group>
          <date date-type="pub">
            <year>2014.</year>
          </date>
          <article-title>‘Multidimensional Quality Metrics : A Flexible System for Assessing Translation Quality’</article-title>
          <source>12(Tradumàtica 12)</source>
          <fpage>455</fpage>
          <lpage>463</lpage>
          <ext-link xlink:href="https://doi.org/10.5565/rev/tradumatica.77"></ext-link>
        </mixed-citation>
      </ref>
      
      <ref id="r7">
        <label>7</label>
        <mixed-citation publication-type="data" publication-format="electronic">
          <collab>Microsoft</collab>
          <date>
            <year>2018.</year>
          </date>
          <ext-link xlink:href="https://docs.microsoft.com/"></ext-link>
        </mixed-citation>
      </ref>
      
      <ref id="r8">
        <label>8</label>
        <mixed-citation publication-type="data" publication-format="electronic">
          <data-title>MQM definition</data-title>
          <date>
            <year>2015.</year>
          </date>
          <ext-link xlink:href="http://www.qt21.eu/"></ext-link>
        </mixed-citation>
      </ref>
      
      <ref id="r9">
        <label>9</label>
        <mixed-citation publication-type="journal">
          <person-group>
            <name>
              <surname>Popovic</surname>
              <given-names>M.</given-names>
            </name>
            <name>
              <surname>Burchardt</surname>
              <given-names>A.</given-names>
            </name>
          </person-group>
          <date date-type="pub">
            <year>2011.</year>
          </date>
          <article-title>‘From Human to Automatic Error Classification for Machine Translation Output’</article-title>
          <ext-link xlink:href="https://doi.org/10.2478/v10108-011-0011-4"></ext-link>
        </mixed-citation>
      </ref>
      
      
      <ref id="r10">
        <label>10</label>
        <mixed-citation publication-type="data" publication-format="electronic">
          <person-group>
            <name>
              <surname>Secara</surname>
              <given-names>A.</given-names>
            </name>
          </person-group>
          <data-title>‘Translation Evaluation - a State of the Art Survey’</data-title>
          <date>
            <year>2001.</year>
          </date>
          <fpage>39</fpage>
          <lpage>44</lpage>
        </mixed-citation>
      </ref>
      
      <ref id="r11">
        <label>11</label>
        <mixed-citation publication-type="journal">
          <person-group>
            <name>
              <surname>Stymne</surname>
              <given-names>S.</given-names>
            </name>
          </person-group>
          <date date-type="pub">
            <year>2011.</year>
          </date>
          <article-title>‘B LAST : A Tool for Error Analysis of Machine Translation Output’</article-title>
          <fpage>56</fpage>
          <lpage>61</lpage>
        </mixed-citation>
      </ref>
      
      <ref id="r12">
        <label>12</label>
        <mixed-citation publication-type="journal">
          <person-group>
            <name>
              <surname>Stymne</surname>
              <given-names>S.</given-names>
            </name>
            <name>
              <surname>Ahrenberg</surname>
              <given-names>L.</given-names>
            </name>
          </person-group>
          <date date-type="pub">
            <year>2012.</year>
          </date>
          <article-title>‘On the practice of error analysis for machine translation evaluation’</article-title>
          <fpage>1785</fpage>
          <lpage>1790</lpage>
        </mixed-citation>
      </ref>
      
    </ref-list>  
  </back>  
  
</article>
