<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Challenges and Future Directions for Accountable Machine Learning*</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Agne Zainyte</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Wei Pang</string-name>
          <email>w.pang@hw.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Heriot-Watt University</institution>
          ,
          <addr-line>Edinburgh, Scotland</addr-line>
          ,
          <country country="UK">United Kingdom</country>
          ,
          <addr-line>EH14 4AS</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>In recent years, machine learning (ML) algorithms have been applied in many areas such as healthcare, finance and autonomous vehicles. At the same time, there is an increasing need for making ML systems accountable, which would help deal with situations when these systems made wrong decisions or predictions. Currently there exist three major frameworks for Accountable ML: Model Card Toolkit, Datasheets, and FactSheets. However, the greatest limitation of these frameworks is that they are mostly focusing on qualitative information about the machine learning models. In this research, we discuss in detail these three frameworks and future development directions of Accountable ML frameworks; we recommend the implementation of causality, decision provenance, and computational tests for achieving better ML accountability.</p>
      </abstract>
      <kwd-group>
        <kwd>Accountable</kwd>
        <kwd>Machine</kwd>
        <kwd>Learning</kwd>
        <kwd>Artificial</kwd>
        <kwd>Intelligence</kwd>
        <kwd>Transparent</kwd>
        <kwd>Frameworks</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Machine Learning (ML) is a type of Artificial Intelligence (AI) algorithms that are
capable of learning from data and improving themselves accordingly. Due to fast
increasing computational power, in recent years researchers have been able to develop
sophisticated ML algorithms that are capable of solving complex problems. These ML
algorithms are now being applied to healthcare, finances, banking, marketing, and even
autopilots.</p>
      <p>
        The utilization of ML in automated decision making has brought the attention of
several regulatory bodies; for example, EU’s General Data Protection Regulation
(GDPR) commission, which has now established a legal right to explanations of
decisions made by automated means, such as ML algorithms [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Moreover, automated
decision-making systems (with ML systems being one type of these systems) have been
      </p>
      <p>**WP is supported by the RAInS project funded by EPSRC (EP/R033846/1).
increasingly used in situations that if an error occurred it would have detrimental effects
on human lives. This further accelerates the need for accountability in ML models.</p>
      <p>This paper aims at reviewing currently existing Accountable ML frameworks,
pointing out challenges associated with facilitating accountability in ML, and
suggesting future directions in developing accountable ML frameworks.</p>
      <p>The rest of the paper is organised as follows: In Section 2, we discuss the
accountability in machine learning. This followed by the introduction of the three main
accountable machine learning frameworks in Section 3. Then in Section 4, we point
out the challenges of accountable machine learning. In Section 5, we present the future
directions of accountable machine learning. Finally, Section 6 concludes the paper.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Accountability in Machine Learning</title>
      <p>
        There was an infamous incident in 1991 when Dean Pomerleau was pioneering in
autonomous vehicle research by trying to teach a computer how to drive. Pomerleau
was training the computer for a few minutes by driving himself and then later would
allow it to drive the vehicle itself. Unfortunately, the computer made an error that
would have caused a car crash if Pomerleau would have not taken control back in
time [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. The error occurred due to the training data being inefficient – it mostly
contained grassy roadsides and when the computer captured the bridge it was
confused as it was never trained on it before.
      </p>
      <p>
        Although, the research came far in last 30 years, given the fact that AI is being
extensively used in decision making, the concerns still arise what if AI makes
mistakes. The extensive discussion of who would be held accountable for AI’s
mistakes was presented by Hevelke et al., [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] who analysed the situation where an
autonomous vehicle got in a car crash. The authors stated that the most intuitive
solution would be to hold the manufacturers responsible for any crash caused by the
vehicle (if it was system error that caused it), however, the question of who is
accountable if the vehicle is designed in such a way that it continuously develops and
improves itself is highly difficult to answer [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Hevelke et al. did not reach a solid
conclusion of where accountability lies in self-improving algorithms. Furthermore,
Mittelstadt et al. [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] continued the debate, highlighting the challenge that machine
learning algorithms are capable of learning autonomously and are rather opaque in
their reasoning. However, designers could provide information about how algorithms
have been taught, which could provide more insights into the factors that could have
affected the inference that the computer has made [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
3
3.1
      </p>
    </sec>
    <sec id="sec-3">
      <title>Current Techniques for Accountable Machine Learning</title>
      <sec id="sec-3-1">
        <title>Model Card Toolkit</title>
        <p>
          The Model Card Toolkit (MCT) [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] is a library developed by Google that generates
Model Cards [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ], which are documents that give insights into models’ internal works.
Model Cards were proposed to prevent mistakes caused by systematic failure that
became apparent only after the models have been put in use; Model Cards would
define the model’s performance before the model has been put to use. Since MCT has
a collection of tools that assist in compiling and filling in Model Cards, it was meant
to be a way to standardise reporting on machine learning model’s ethics, provenance,
usage and evaluation [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ].
        </p>
        <p>
          The greatest advantage of using MCT is that it has semi-automated process when
creating Model Cards, and this ease of use could encourage developers to implement
accountability into their products. However, there are several limitations for MCT,
one of them being that it is only applicable to TensorFlow library [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. Secondly,
Model Cards are generated only after the model has been developed, and more
specifically, it is lacking stage-to-stage analysis before its model is compiled.
3.2
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>Datasheets</title>
        <p>
          In 2018, the so-called “Datasheets for Datasets” was proposed by Microsoft [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. The
authors raised the issue that there was no standardised way to document how and why
datasets were created, what information it contains, in which scenarios it is applicable
and whether it might raise any ethical or legal concerns. This type of documentations
would highly benefit datasets that were not sharing their details to public, such as
those containing sensitive information. A proposed solution was a Datasheet that
contains a set of proposed questions that had to be filled in by dataset creators. These
questions are divided into seven categories: motivation, data pre-processing, data
distribution, data maintenance and legal issues and ethical considerations [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
Datasheets primarily aim at qualitative information about datasets; however, it is
lacking any visualisation, which could give greater insights about data and would help
with interpretability.
        </p>
        <p>
          The greatest advantage of Datasheets is that it acknowledges the fact that datasets
could be held accountable; as Hutchinson et al. [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] argued, datasets directly influence
how self-improving algorithms will reassemble themselves and therefore datasets play
a major part in Algorithmic Decision Making (ADM) [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. Notably, there are no
followup research along this line as far as we are aware.
3.3
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>FactSheets</title>
        <p>
          FactSheets is a framework that was developed by IBM research team [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]. It was
probably inspired by and built upon both Model Cards and Datasheets. The idea is
that each FactSheet contains sections of information about relevant attributes of a
machine learning model, such as intended use, performance, safety and security.
Additional detailed information about how the model was created, trained and
deployed could be supplied, alongside with scenarios of use cases and legal and
ethical considerations. It is clear that FactSheets are the more detailed version of
Model Cards; however, it lacks the information that was captured automatically by
MCT during pipeline development. The aim of creating FactSheets was to help
prevent overgeneralisation of models, which would in turn help reduce the errors that
are the result of unintended use of these models [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ].
        </p>
        <p>
          Ever since their release in 2019, The development of FactSheets has been active
and research papers are openly available on IBM’s website [
          <xref ref-type="bibr" rid="ref11 ref12 ref13">11, 12, 13</xref>
          ]. However, we
feel that information required to be filled in FactSheets is quite excessive and some of
it may not be necessary the key to effective traceability and hence accountability.
4
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Challenges of Accountable Machine Learning</title>
      <p>
        We believe that the greatest challenge in accountable ML development is the
identification of what accountability in ML comprises of. According to Mohseni et al.
[
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], accountability is the desired outcome of transparency in algorithms; the. authors
argue that accountability would be inevitable if transparency and explainability were
implemented correctly [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. However, a counterargument is presented by De Laat
[
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]; De Laat states that more transparency does not equate to more accountability,
and in fact models should be able to implement accountability even when
transparency is not excessive [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. This type of approaches would also be applicable
to models that are opaque due to not being open source about their development and
to those models that are opaque due to the concerns of potential loss of competitive
edge [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
      </p>
      <p>
        Interestingly, Ananny et al. [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] argues that ML algorithms are more than just
code, and they are also artifacts that implement practices and norms captured in data
and employed by their developers – therefore, in order to facilitate accountability in
ML models, it requires more than transparency of components comprising the model,
but also information about how the algorithm works as a system. This highlights the
second challenge in accountable ML development: the problem of what information
needs to be captured in order to understand systems as a whole.
      </p>
      <p>
        According to Cambridge Dictionary definition of accountability is “the fact of
being responsible for what you do and being able to give a satisfactory reason for it,
or the degree to which this happens” [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. Similar definition but adapted to ML
systems is given by Naja et al. [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ] as authors state that “by accountability, we mean
the ability to inspect, review or otherwise interrogate an AI system”. Additionally, we
believe that accountability in ML should include sufficient level of transparency
(although not necessarily full transparency), explainability, robustness, fairness and
bias. In the section below we further discuss what additional information should be
captured to the facilitate implementation of necessary components of accountable
ML.
5
      </p>
    </sec>
    <sec id="sec-5">
      <title>Recommendations for Accountable Machine Learning</title>
    </sec>
    <sec id="sec-6">
      <title>Frameworks</title>
      <p>Current accountable machine learning frameworks focus on descriptive approaches. It
is expected that detailed factual information would allow greater transparency, which
in turn would help facilitate accountability. However, below are recommended future
directions when developing a framework for Accountability in Machine Learning
models.</p>
      <sec id="sec-6-1">
        <title>Causality</title>
        <p>
          It is crucial to understand what influence each stage of the model development has. By
understanding the effects that each component has, the design of ML models can be
improved by making sure that the effects and causes are clearly outlined and understood
[
          <xref ref-type="bibr" rid="ref19">19</xref>
          ]. This type of causality would compensate for opaqueness found in algorithms and
would allow traceability and improved transparency without having to reveal
‘sensitive’ information about the model’s development.
5.2
        </p>
      </sec>
      <sec id="sec-6-2">
        <title>Decision Provenance</title>
        <p>
          Decision provenance involves provenance methods to provide information about
decision pipelines, and it shows how data flow throughout the model and what
connections were being made that lead to the final decision. The information gained
from decision provenance could allow developers to be proactive during the model
development process and mitigate the risks associated with ADM [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ]. It would
symbiotically work with causality – understating how algorithms change and what
component of the system powers the change would provide useful insights about
models behaviour that would help with accountability of the models [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ].
5.3
        </p>
      </sec>
      <sec id="sec-6-3">
        <title>Computational Tests</title>
        <p>
          Arnold et al. [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ] discussed the concept of the “big red button” that enables developers
or users to divert or interrupt the system, however, the downfall of such approach is
that it concentrates on the point where the system has already ‘gone rogue’. A more
prominent solution would be a preventative measure, implemented in the form of tests
that would check whether a model behaves the way it was anticipated to behave. Such
tests would also allow registering the errors that occurred if model failed the tests.
Moreover, these tests could be applied to “hidden information”, which is not possible
to visualise and is hidden from the developers [
          <xref ref-type="bibr" rid="ref21 ref22 ref23">21, 22, 23</xref>
          ].
6
        </p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>Conclusion</title>
      <p>In conclusion, it is important to address the challenges of Accountable ML as ML is
being utilised in more and more areas that affect human lives and the society. This
results in more regulations being applied to automated decision making, which
increases the pressure of algorithms being developed with accountability implemented
within them. Our suggestions are that in the future, the developers would enrich
Accountable ML frameworks with information about causality, decision provenance
and would implement computational test frameworks that would check the behaviour
of models.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>General</given-names>
            <surname>Data Protection Regulation</surname>
          </string-name>
          . Online: https://gdprinfo.eu (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Pomerleau</surname>
            ,
            <given-names>D.A.</given-names>
          </string-name>
          :
          <source>Efficient Training of Artificial Neural Networks for Autonomous Navigation. Neural Computation</source>
          <volume>3</volume>
          (
          <issue>1</issue>
          ), pp.
          <fpage>88</fpage>
          -
          <lpage>97</lpage>
          (
          <year>1991</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Hevelke</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Nida-Rümelin</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          :
          <article-title>Responsibility for crashes of autonomous vehicles: an ethical analysis</article-title>
          .
          <source>Science and Engineering Ethics</source>
          <volume>21</volume>
          (
          <issue>3</issue>
          ), pp.
          <fpage>619</fpage>
          -
          <lpage>630</lpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Mittelstadt</surname>
            ,
            <given-names>B.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Allo</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Taddeo</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wachter</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Floridi</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>The ethics of algorithms: Mapping the debate</article-title>
          .
          <source>Big Data Society</source>
          ,
          <volume>3</volume>
          (
          <issue>2</issue>
          ), p.
          <volume>2053951716679679</volume>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Model</surname>
          </string-name>
          . Card Toolkit. Online: https://www.tensorflow.org/responsible_ai/model_card_toolkit/guide (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6. Mitchell,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Wu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Zaldivar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Barnes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>Vasserman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            ,
            <surname>Hutchinson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Spitzer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            ,
            <surname>Raji</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I.D.</given-names>
            and
            <surname>Gebru</surname>
          </string-name>
          , T.:
          <article-title>Model cards for model reporting</article-title>
          .
          <source>In Proceedings of the conference on fairness, accountability, and transparency</source>
          . pp.
          <fpage>220</fpage>
          -
          <lpage>229</lpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>ML</given-names>
            <surname>Metadata</surname>
          </string-name>
          . Online: https://www.tensorflow.org/tfx/guide/mind (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Gebru</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Morgenstern</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vecchione</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vaughan</surname>
            ,
            <given-names>J.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wallach</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <article-title>Daum ́e III, H. and</article-title>
          <string-name>
            <surname>Crawford</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Datasheets for datasets</article-title>
          . arXiv preprint arXiv:
          <year>1803</year>
          .
          <volume>09010</volume>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Hutchinson</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Smart</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hanna</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Denton</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Greer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kjartansson</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Barnes</surname>
          </string-name>
          , P. and Mitchell, M.:
          <article-title>Towards Accountability for Machine Learning Datasets: Practices from Software Engineering and Infrastructure</article-title>
          .
          <source>In Proceedings of the 2021 ACM Conference on Fairness, Accountability, and Transparency</source>
          , pp.
          <fpage>560</fpage>
          -
          <lpage>575</lpage>
          (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Arnold</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bellamy</surname>
            ,
            <given-names>R.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hind</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Houde</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mehta</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mojsilovic</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nair</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ramamurthy</surname>
            ,
            <given-names>K.N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Olteanu</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Piorkowski</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Reimer</surname>
          </string-name>
          , D.:
          <article-title>FactSheets: Increasing trust in AI services through supplier's declarations of conformity</article-title>
          .
          <source>IBM Journal of Research and Development</source>
          ,
          <volume>63</volume>
          (
          <issue>4</issue>
          /5), pp.
          <fpage>6</fpage>
          -
          <lpage>1</lpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Hind</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Houde</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Martino</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mojsilovic</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Piorkowski</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Richards</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Varshney</surname>
            ,
            <given-names>K.R.</given-names>
          </string-name>
          :
          <article-title>Experiences with improving the transparency of ai models and services</article-title>
          .
          <source>In Extended Abstracts of the 2020 CHI Conference on Human Factors in Computing Systems</source>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>8</lpage>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Richards</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Piorkowski</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hind</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Houde</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Mojsilovic</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>A Methodology for Creating AI FactSheets</article-title>
          . arXiv preprint arXiv:
          <year>2006</year>
          .
          <volume>13796</volume>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Piorkowski</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          , Gonz ́alez,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Richards</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            and
            <surname>Houde</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.</surname>
          </string-name>
          :
          <article-title>Towards evaluating and eliciting high-quality documentation for intelligent systems</article-title>
          . arXiv preprint arXiv:
          <year>2011</year>
          .
          <volume>08774</volume>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Mohseni</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zarei</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Ragan</surname>
          </string-name>
          , E.D.:
          <article-title>A multidisciplinary survey and frame- work for design and evaluation of explainable AI systems</article-title>
          . arXiv preprint arXiv:
          <year>1811</year>
          .
          <volume>11839</volume>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>De Laat</surname>
          </string-name>
          , P.B.:
          <article-title>Algorithmic decision-making based on machine learning from Big Data: Can transparency restore accountability?</article-title>
          .
          <source>Philosophy technology</source>
          ,
          <volume>31</volume>
          (
          <issue>4</issue>
          ), pp.
          <fpage>525</fpage>
          -
          <lpage>541</lpage>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Ananny</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Crawford</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Seeing without knowing: Limitations of the transparency ideal and its application to algorithmic accountability</article-title>
          .
          <source>new media society</source>
          ,
          <volume>20</volume>
          (
          <issue>3</issue>
          ), pp.
          <fpage>973</fpage>
          -
          <lpage>989</lpage>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17. Cambridge Dictionary. Online: https://dictionary.cambridge.org/dictionary/english/accountability (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Naja</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Markovi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Edward</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cottril</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>A semantic framework to suppost AI system accountability and audit</article-title>
          .
          <source>In: ESWC 2021</source>
          . p. in press.
          <source>Greece</source>
          (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Kacianka</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Pretschner</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Designing Accountable Systems</article-title>
          .
          <source>In Proceedings of the 2021 ACM Conference on Fairness, Accountability, and Transparency</source>
          , pp.
          <fpage>424</fpage>
          -
          <lpage>437</lpage>
          (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Singh</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cobbe</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Norval</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Decision provenance: Harnessing data flow for accountable systems</article-title>
          .
          <source>IEEE Access</source>
          ,
          <volume>7</volume>
          , pp.
          <fpage>6562</fpage>
          -
          <lpage>6574</lpage>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Nushi</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kamar</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Horvitz</surname>
          </string-name>
          , E.:
          <article-title>Towards accountable AI: Hybrid human-machine analyses for characterizing system failure</article-title>
          .
          <source>In Proceedings of the AAAI Conference on Human Computation and Crowdsourcing</source>
          <volume>6</volume>
          (
          <issue>1</issue>
          ) (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Lepri</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oliver</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          , Letouz ́e, E.,
          <string-name>
            <surname>Pentland</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Vinck</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          : Fair, transparent, and
          <article-title>accountable algorithmic decision-making processes</article-title>
          .
          <source>Philosophy Technology</source>
          ,
          <volume>31</volume>
          (
          <issue>4</issue>
          ), pp.
          <fpage>611</fpage>
          -
          <lpage>627</lpage>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Arnold</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Scheutz</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The “big red button” is too late: an alternative model for the ethical evaluation of AI systems</article-title>
          .
          <source>Ethics and Information Technology</source>
          ,
          <volume>20</volume>
          (
          <issue>1</issue>
          ), pp.
          <fpage>59</fpage>
          -
          <lpage>69</lpage>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>