<!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>The Accountability Fabric: A Suite of Semantic Tools For Managing AI System Accountability and Audit?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Milan Markovic</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Iman Naja</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Peter Edwards</string-name>
          <email>p.edwardsg@abdn.ac.uk</email>
          <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="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Computing Science, University of Aberdeen</institution>
          ,
          <addr-line>Aberdeen AB24 3UE</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>School of Mathematical and Computer Sciences, Heriot-Watt University Edinburgh</institution>
          ,
          <addr-line>EH14 4AS</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The life cycle of an AI system is a complex multi-stage undertaking that typically involves a range of human stakeholders (e.g., developers, managers, users) who can potentially be held accountable if harm is caused by the system. In this paper, we present the Accountability Fabric, a suite of semantic tools for managing the creation and audit of accountability knowledge graphs. Demo Link: https://rains-uoa.github.io/ISWC_2021_Demo/</p>
      </abstract>
      <kwd-group>
        <kwd>AI</kwd>
        <kwd>Provenance</kwd>
        <kwd>Accountability</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>The widespread adoption of AI systems and the risks associated with errors,
bias and other negative consequences have highlighted the need to regulate such
systems, and have led to calls to make them (and their developers) accountable.</p>
      <p>
        To situate our work, we use the de nitions presented in our previous work [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ],
where an AI system comprises `core AI' components (e.g., a Machine Learning
model) plus other supporting ones (e.g., API wrappers); and its life cycle consists
of four stages: Design, Implementation, Deployment, and Operation. Moreover,
an accountable AI system is one which can be inspected, audited, or reviewed
with the goals of (i ) making transparent the processes of each stage of its life
cycle; (ii ) exhibiting compliance with hard laws (i.e. laws and regulations), and
soft laws (i.e. standards and guidelines); and (iii ) facilitating investigations of
erroneous decisions or failures and determining the responsible human agents.
      </p>
      <p>In recent years, and in an e ort to enhance transparency of ML systems, a
number of prominent frameworks have been proposed for recording metadata
? Supported by the award made by the UKRI Digital Economy programme to the
RAInS project (ref: EP/R033846/1).</p>
      <p>
        Copyright © 2021 for this paper by its authors. Use permitted under Creative
Commons License Attribution 4.0 International (CC BY 4.0).
about datasets [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], Machine Learning (ML) model implementations [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], and also
more comprehensive system descriptions [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. However, with the exception of
Google's Model Card Toolkit3, these frameworks only record data in
unstructured formats without the ability to manipulate data programmatically, and
none capture decisions of human agents that may have in uenced the overall AI
system (e.g., approval of a design speci cation by a project manager). Moreover,
it is typically not straightforward to collect, record and manage such metadata
due to them being generated by various agents (e.g., developers use in-code
comments, decision makers use online forms and text reports), across di erent time
frames within the system life cycle, in various siloed locations. We argue that
Semantic Web technologies are ideally suited to facilitate both the representation
and linking of such information.
      </p>
      <p>
        In our approach, we utilise PROV [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] to describe information related to the
AI system life cycle stages in the form of retrospective linked causal graphs
consisting of activities, entities, and agents; we refer to these as accountability traces.
Furthermore, we argue that to fully realise accountable AI systems, meaningful
information is required, the recording of which must be planned. We thus extend
EP-Plan [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] to describe accountability plans to specify information that should
be captured throughout the system's life cycle and to guide the recording of
corresponding accountability traces. Accountability plans and traces, together
referred to as accountability information, form semantic knowledge graphs that
can be queried for the information necessary to establish accountability of human
agents.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>System Overview</title>
      <p>
        The Accountability Fabric is a suite of tools that utilises a provenance-based
approach for recording and querying accountability information using semantic
graphs. The tools are supported by a Spring Boot4 back end server application
utilising the RDF4J library5 to communicate with the GraphDB6 repository
which stores accountability information. User interfaces are built using HTML,
CSS and Javascript. The fabric is supported by four main ontologies: PROV-O7,
EP-Plan8, SAO9, and RAInS10. SAO de nes the mechanisms for representing
accountability plans and their corresponding accountability traces, and RAInS
extends SAO to describe the life cycle of AI systems with Machine Learning
components. The reader is referred to [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] for more details on how these ontologies
are integrated.
3 https://github.com/tensorflow/model-card-toolkit
4 https://spring.io/projects/spring-boot
5 https://rdf4j.org/
6 https://www.ontotext.com/products/graphdb/
7 https://www.w3.org/TR/prov-o/
8 https://w3id.org/ep-plan
9 https://w3id.org/sao
10 https://w3id.org/rains
- Project Managers
- Regulators
- Designers
- Developers
- Decision Makers
- System engineers
- Lawyers
- System Operators
- Incident Investigators
      </p>
      <p>Plan Designer
Provenance Collector</p>
      <p>Audit Manager</p>
      <p>AccoPulnatnability
Accountability</p>
      <p>Trace</p>
      <p>Figure 1 illustrates three main components: Plan Designer, Provenance
Collector, and Audit Manager, along with examples of potential users. The Plan
Designer supports creation of accountability plans for each life cycle stage to
de ne what accountability information should be recorded (Figure 2). Plans are
described as work ows that consist of steps representing planned activities (e.g.,
implementation of an ML model). Such steps also include inputs and outputs
which represent high level references to the type of information that should be
collected (e.g., information about the dataset or ML model, or previously made
decisions). Steps may include additional metadata such as constraints, which
are evaluated against the accountability trace (e.g., the model description must
include a list of its limitations).</p>
      <p>
        The Provenance Collector supports both manual and semi-automatic
creation of accountability traces. For manual input, a user would use an interactive
Web form (Figure 3A), the automatic generation of which is guided by the
relevant accountability plan. The fabric also provides a (Python) script for
integrating data recorded by the Model Card Toolkit and executed in a Colab/Jupyter
Notebook environment11 (Figure 3B). This converter also has the ability to
visualise any violations of plan constraints, de ned using SHACL12. These can be
used, for example, to indicate to the developer that certain information should
have been provided. The Audit Manager (Figure 4) provides an interactive Web
11 https://colab.research.google.com
12 https://www.w3.org/TR/shacl/
B)
interface for exploring accountability knowledge graphs. Several visualisation
options are provided including the report-like visualisations inspired by Model
Cards [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>
        The RAInS ontology has recently been extended to cover the implementation
stage in addition to the design stage described in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. The ontology has also been
extended with OWL constraints, which are used by the Plan Designer to guide
the user during the creation of accountability plans.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Demonstration</title>
      <p>All main Accountability Fabric components are demonstrated, namely the Plan
Designer (Figure 2), Provenance Collector comprising the manual accountability
trace input UI and the mapping tool for integrating data captured using the
Model Card toolkit, and the Audit Manager for exploring accountability graphs
(Figure 4). The demonstration will take the participants through the process of
planning and recording accountability information for an example AI system.
The aim is to demonstrate three key capabilities of the Accountability Fabric:
planning, recording, and auditing.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Conclusions</title>
      <p>
        The Accountability Fabric showcases how semantic technologies can be used to
support the accountability of AI systems by collecting, integrating, and
visualising information describing the design and implementation stages of an AI
system life cycle; with other life cycle stages due to be incorporated in the near
future. Our future work will focus on evaluating the individual components of
the Accountability Fabric (see Figure 1) with users such as AI system
developers, project managers, and lawyers; we will also compare the suite's capabilities
against existing text-based approaches such as Data Sheets [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], Fact Sheets [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ],
and Model Cards [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <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>
          , et al.:
          <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), 6{
          <issue>1</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <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>
          ,
          <string-name>
            <surname>Daume</surname>
            <given-names>III</given-names>
          </string-name>
          , H.,
          <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="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Markovic</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Garijo</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Edwards</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vasconcelos</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Semantic modelling of plans and execution traces for enhancing transparency of iot systems</article-title>
          .
          <source>In: 2019 Sixth Int. Conf. on Internet of Things: Systems, Management and Security (IOTSMS)</source>
          . pp.
          <volume>110</volume>
          {
          <fpage>115</fpage>
          .
          <string-name>
            <surname>IEEE</surname>
          </string-name>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4. 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>
            ,
            <surname>Gebru</surname>
          </string-name>
          ,
          <string-name>
            <surname>T.</surname>
          </string-name>
          :
          <article-title>Model cards for model reporting</article-title>
          .
          <source>In: Proceedings of the conference on fairness, accountability, and transparency</source>
          . pp.
          <volume>220</volume>
          {
          <issue>229</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Moreau</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Groth</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cheney</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lebo</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Miles</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>The rationale of PROV</article-title>
          .
          <source>Web Semantics: Science, Services and Agents on the World Wide Web</source>
          <volume>35</volume>
          ,
          <issue>235</issue>
          {
          <fpage>257</fpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Naja</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Markovic</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Edwards</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cottrill</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>A Semantic Framework to Support AI System Accountability and Audit</article-title>
          .
          <source>In: The Semantic Web. ESWC 2021</source>
          . pp.
          <volume>160</volume>
          {
          <fpage>176</fpage>
          . Springer, Cham (
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>