<!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>
      <journal-title-group>
        <journal-title>NM);</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>A Simple Standard for Ontological Mappings 2023: Updates on data model, collaborations and tooling</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Nicolas Matentzoglu</string-name>
          <xref ref-type="aff" rid="aff7">7</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ian Braun</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Anita R. Caron</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Damien Goutte-Gattat</string-name>
          <xref ref-type="aff" rid="aff9">9</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Benjamin M. Gyori</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nomi L. Harris</string-name>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Emily Hartley</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Harshad B. Hegde</string-name>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sven Hertling</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Charles Tapley Hoyt</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>HyeongSik Kim</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Huanyu Li</string-name>
          <xref ref-type="aff" rid="aff5">5</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>James McLaughlin</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Cassia Trojahn</string-name>
          <xref ref-type="aff" rid="aff8">8</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nicole</string-name>
          <xref ref-type="aff" rid="aff6">6</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Vasilevsky</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Christopher J. Mungall</string-name>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Critical Path Institute</institution>
          ,
          <addr-line>Tucson, AZ 85718</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Data and Web Science Group, University of Mannheim</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>European Bioinformatics Institute (EMBL-EBI)</institution>
          ,
          <addr-line>Hinxton</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Harvard Medical School</institution>
          ,
          <addr-line>Boston, MA 02115</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>Lawrence Berkeley National Laboratory</institution>
          ,
          <addr-line>Berkeley, CA 94720</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff5">
          <label>5</label>
          <institution>Linköping University</institution>
          ,
          <addr-line>Linköping</addr-line>
          ,
          <country country="SE">Sweden</country>
        </aff>
        <aff id="aff6">
          <label>6</label>
          <institution>Robert Bosch LLC</institution>
        </aff>
        <aff id="aff7">
          <label>7</label>
          <institution>Semanticly</institution>
          ,
          <addr-line>Athens</addr-line>
          ,
          <country country="GR">Greece</country>
        </aff>
        <aff id="aff8">
          <label>8</label>
          <institution>Universite Toulouse 2</institution>
          ,
          <addr-line>Toulouse</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff9">
          <label>9</label>
          <institution>University of Cambridge</institution>
          ,
          <addr-line>Cambridge, CB2 3DY</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2023</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0002</lpage>
      <abstract>
        <p>The Simple Standard for Ontological Mappings (SSSOM) was first published in December 2021 (v. 0.9). After a number of revisions prompted by community feedback, we have published version 0.15.0 in July 2023. Here we report on the progress made since August 2022, in particular changes to tooling, data model and summary of ongoing standardisation efforts. Entity mappings define correspondences between entities in different semantic spaces. A “semantic space” in this context can be anything from an ontology, terminology, database or controlled vocabulary to enumerations in a data model. Entities identify/represent a real-world concept or instance in that space. Many such entities refer to the exact same, or similar, real-world concept or instance.</p>
      </abstract>
      <kwd-group>
        <kwd>standards</kwd>
        <kwd>mappings</kwd>
        <kwd>ontologies</kwd>
        <kwd>ontology mapping</kwd>
        <kwd>FAIR data1</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        The Simple Standard for Sharing Ontological Mappings (SSSOM) was created to enable the
sharing of semantic entity mappings [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. The standard provides a rich set of metadata elements
to describe entity mappings, such as mapping “justifications” (processes that generate evidence
to support the mapping), “mapping predicate” (the mapping relationship, e.g. skos:exactMatch),
“confidence” (the probability or certainty an agent has in the truthfulness of a mapping) and
“author” (the agent asserting the mapping). The data model is specified using a LinkML schema
(https://linkml.io/), which enables well-specified translations into a variety of serialisations,
from the default TSV format to JSON and Turtle. In contrast to existing mapping standards like
Alignment API (https://moex.gitlabpages.inria.fr/alignapi/), SSSOM is targeted at use cases that
require the documentation of (1) rich metadata about mappings (2) in a simple manner, such as
a spreadsheet. Tools that convert other standards (such as Alignment API) into SSSOM exist. Here,
we report on the progress made since August 2022 [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], describing updates to the data model,
SSSOM related efforts in the community, existing and new emerging tooling, and outline the vision
for the coming years.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Updates to the SSSOM standard and documentation</title>
      <p>Compared to the last few years, only few new metadata elements were added to SSSOM. This
suggests that the standard is largely stabilising, and most requirements to the current user base
are met. Four new metadata elements were added to the core model: mapping_set_title (a
humanreadable title for the mapping set), issue_tracker (a link to the issue tracker to be used for
reporting problems related to a mapping set), issue_tracker_item (a field to track an ongoing
discussion about a specific mapping) and curation_rule. A curation rule is a (potentially) complex
condition executed by an agent that led to the establishment of a mapping. Curation rules often
involve complex domain-specific considerations, which are hard to capture in an automated
fashion. For example, when curation a mapping between two vocabularies about phenotypic
abnormalities, we may define a curation rule such as “The two phenotypes inhere in homologous
anatomical structures and exhibit the same phenotypic quality (increased amount, length,
morphology)”, or “Two genes are considered matching if they are orthologous”.</p>
      <p>
        We have improved the documentation in various ways, by creating a page listing all SSSOM
talks [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] (including slides and recordings), providing a reference for “chaining rules” that can be
applied to mappings to infer additional mappings [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], and releasing two new tutorials: a guide for
setting up a new Mapping Commons [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] and a guide on how to document mapping justifications
[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Tooling-related updates</title>
      <p>
        The sssom-py library and CLI tool for processing (converting, validating, etc.) SSSOM
mapping files has been migrated to supporting extended prefix maps [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] (EPM) supplied by the
Bioregistry [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] for processing SSSOM files, especially during Extract-Transform-Load (ETL)
operations. EPMs are a novel way to manage messy identifiers in data that, in combination with
the curies [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] package, enable the standardisation and conversion between RDF/URI-based
identifiers and CURIEs, for example when converting SSSOM between different file formats.
sssom-py also has a new “invert” command for changing the direction of semantic mappings.
      </p>
      <p>The successor of the European Bioinformatics Institute’s Ontology Xref Service [11] (OxO) is
developed entirely based on the SSSOM data model. OxO2 [12] is a Docker-based UI system that
is built on top of an entirely independent REST API for the retrieval of SSSOM mappings.</p>
      <p>The Ontology Access Kit [13] (OAK) has a number of methods that provide mappings in
SSSOM format, including the “mappings” command for retrieving mappings, for example from
databases or ontologies, and the “lexmatch” command for doing basic lexical matching. Various
improvements have been implemented to provide standard conformant SSSOM, and improve
automated matching by supporting a standard system for encoding synonym rules
(“synonymiser”). A new command, boomerang, was implemented to analyse the output of
boomer [14], a tool that uses a combined logical and probabilistic approach to translate mappings
into logical axioms that can be used to merge ontologies. boomerang effectively translates the
output of boomer, which is focussed on analysing and de-conflicting mapping cliques, into
harmonised SSSOM mapping sets.</p>
      <p>The sssom-java library aims to enable basic SSSOM processing in Java. An independent
implementation of the SSSOM standard is now available for the Java programming language
[doi:10.5281/zenodo.8192579]. The SSSOM-Java project provides a Java library to read, write,
and manipulate SSSOM mappings, and allows rule-based arbitrary transformations of mappings
into any kind of objects. It also provides an experimental ROBOT plugin (to be used with future
versions of ROBOT where support for such plugins will be available) to inject SSSOM-derived
axioms into an OWL ontology.</p>
      <p>The operationalization of semantic mappings in order to support the standardised
identification of biomedical entities requires the ability to assemble, reason over, and process
semantic mappings at scale, to choose the single "best" reference within a given configurable
context, and to be able to assess the confidence of such mappings. The Semantic Reasoning
Assembler (SeMRA [15,16]) is a software tool that addresses these needs, in part by building on
the SSSOM standard and SSSOM-py implementation for standardised input and output of a
combination of primary and derived mappings.</p>
      <p>Biomappings [17] (https://github.com/biopragmatics/biomappings) is a repository of
predicted and community curated semantic mappings not available from primary resources like
ontologies. It keeps detailed provenance information about curations of predictions, including
predictions that are non-trivially untrue. It now exports all uncurated predictions (curr. 94
mappings), predictions curated as true (curr. 10306 mappings), and predictions curated as false
(curr. 1566 mappings) into a combined SSSOM that leverages detailed provenance features and
now the predicate_modifier field for representing untrue mappings.</p>
      <p>The Mapping Commons repository template [18] is a cookiecutter [19] template for
creating repositories of SSSOM mapping files. Mapping commons registries are created from the
template via cruft (https://cruft.github.io/cruft/), which is also used to keep the repository
insync with any updates made to the template. The template provides the basic infrastructure for
managing SSSOM files, including a Makefile with commands to update the repo and validate the
mapping files, and CI workflows for either GitHub or GitLab to automatically run the validation
tests. Using a standardised layout for mapping registries will help make the publication of
mappings more FAIR and transparent, but also ensure that mappings are published using and
validated against the latest metadata model versions. SSSOM itself comes with a lightweight
metadata model for defining mapping registries, which furthermore makes it easier to combine
multiple registries, for example for the purpose of building a centralised mapping server. An
example implementation can be found at
https://gitlab.c-path.org/c-pathontology/mappingcommons.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Collaborations and Community updates</title>
      <p>SSSOM at Biocuration 2023. The 2nd Mapping Commons Workshop on Simple Standard for
Sharing Ontology Mappings [20] was held in Padua, Italy. The workshop was about the limits of
the applicability of SSSOM, and ways to work around it. The discussion focussed on four
important corner cases: literal mappings (mappings between a literal string and an identifier),
complex mappings (mappings involving more than two entities), data structure mappings
(mappings that involve translation rules for converting an entity from one data schema to
another) and value set mappings (two-level mappings where two sets, such as enums, clinical
concept sets, etc are associated with each other on set-level, but also pairwise at element-level).
It was generally consensus that capturing data structure mappings was entirely out of scope for
SSSOM, with references to alternative solutions such as the LinkML transformer [21]. For literal
mappings, a new SSSOM profile is being discussed that reuses most of the metadata elements
from the main SSSOM standard, but adds a small number of additional elements to describe the
mapped literals. Value set mappings are likely to be natively supportable by the SSSOM standard
in the future, requiring only small tweaks to the mapping set level metadata (i.e. specifying the
mapped value sets). Complex mappings were the most contentious subject discussed at the
workshop. While no universal agreement could be reached by the workshop participants, it is
likely that at least one proposal will emerge that involves specifying a complex expression in a
URI string (that can then be referenced in a SSSOM file just as any individual identifier).</p>
      <p>SSSOM at OAEI 2023. Since 2004, OAEI (Ontology Alignment Evaluation Initiative) organises
yearly evaluation campaigns for ontology matching technologies. OAEI provides several test sets
in different domains (e.g., anatomy and conference), including ontologies to be matched and
reference alignments. SSSOM will be introduced at OAEI in stages. In 2023, the OAEI
benchmarking team (MELT) agreed to adding SSSOM as an optional output format. MELT [24] is
a framework used by system implementers and track organizers to develop, submit, and evaluate
matching systems. We have published a draft guide for implementing SSSOM [22] for matching
tool developers, and three matching tool developers have agreed to implement the standard for
this year’s OAEI campaign.</p>
      <p>
        SSSOM and FAIR IMPACT. The SSSOM developer community has established a fruitful
collaboration with members of the FAIR IMPACT project. We work together on promoting the
publication of FAIR mappings using the SSSOM standard in the wider life science communities
and co-organised a workshop to that end [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>SSSOM at OHDSI 2023 European Symposium. The SSSOM developer community has
established a collaboration with the OHDSI program. OHDSI maintains the widely used
Observational Medical Outcomes Partnership (OMOP) Common Data Model (CDM), an open
community data standard for representing observational medical data. The goal of the
collaboration is to improve the metadata collected for terminological mappings, both for OHDSI
managed mappings and community contributions. So far, key SSSOM elements such as
confidence, predicate_id, mapping_source, mapping_justification and mapping_tool have been
adopted for the OMOP Community Contribution template [23]. At the symposium, we also
presented a collaborative work on flowsheet mappings.</p>
      <p>Emerging mapping registries for managing collections of mapping sets. The Critical Path
Institute (C-Path) Data Collaboration Center (https://c-path.org/programs/dcc/) translated a
subset of the mappings available through the OMOP2OBO [24] project into SSSOM-conformant
mappings and metadata. This work entailed creating a simple translation between the provided
metadata elements and standard SSSOM metadata elements (e.g. “Mapping Evidence
Component'' to sssom:mapping_justification), and from the provided metadata values to
allowable terms from the ontologies supported by the SSSOM standard (e.g., “Hand Mapping'' to
semapv:ManualMappingCuration). This translation and the resulting mappings were managed
within the C-Path Mapping Commons repository, providing access to the SSSOM Toolkit
functionality for validating the mappings and exporting them in the supported file formats. This
process enabled loading the resulting mappings into a graph database, as well as providing
interoperability with additional mappings created by C-Path by conforming to the SSSOM
standard.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Discussion and Conclusions</title>
      <p>Compared to the last update a year ago, changes to the SSSOM standard are getting fewer,
which means that the metadata model is finally stabilising. Our intention is to launch version 1.0
by the year’s end. Efforts have shifted notably to community engagement and collaboration, and
expansion of SSSOM related tooling. The main aspiration of the data and terminology mapping
community should be to share well defined semantic mappings in completely open Mapping
Commons, and support domain experts to curate better, semantically meaningful mappings.</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgements</title>
      <p>NM was supported by NIH National Human Genome Research Institute Phenomics First Resource,
NIH-NHGRI # 5RM1 HG010860, a Center of Excellence in Genomic Science, and a kind gift from
Bosch LLC to LBNL; Director, Office of Science, Office of Basic Energy Sciences, of the US
Department of Energy [DE-AC0205CH11231 to N.L.H., H.B.H. and C.J.M.]; CTH and BMG were
funded under the Defense Advanced Research Projects Agency (DARPA) Young Faculty Award
[W911NF-20-1-0255] and the DARPA Automating Scientific Knowledge Extraction and Modeling
program [HR00112220036]; DGG was supported by grant BB/T014008/1 from the UK
Biotechnology and Biological Sciences Research Council (BBSRC) and the US National Science
Foundation Directorate of Biological Sciences (NSF/BIO). The Critical Path Institute is supported
by the Food and Drug Administration (FDA) of the U.S. Department of Health and Human Services
(HHS) (54.2%) and non-government source(s) (45.8%). The contents are those of the author(s)
and do not necessarily represent the official views of, nor an endorsement by, FDA/HHS or the
U.S. Government.
[11] Ontology Crossref Service (OxO). [cited 29 Jul 2023]. Available:</p>
      <p>https://www.ebi.ac.uk/spot/oxo/
[12] Oxo2: UI for OxO 2. [cited 29 Jul 2023]. Available: https://github.com/EBISPOT/oxo2
[13] Ontology Access Kit: A python library and command line application for working with
ontologies. [cited 29 Jul 2023]. Available:
https://github.com/INCATools/ontology-accesskit
[14] boomer: Bayesian OWL ontology merging. Github; Available:</p>
      <p>https://github.com/INCATools/boomer
[15] semra: Semantic Mapping Reasoning Assembler (SeMRA): tooling for semantic mappings.</p>
      <p>[cited 29 Jul 2023]. Available: https://github.com/biopragmatics/semra
[16] Hoyt CT. biopragmatics/semra: v0.0.2-alpha. 2023. doi:10.5281/zenodo.8192829
[17] Hoyt CT, Hoyt AL, Gyori BM. Prediction and curation of missing biomedical identifier
mappings with Biomappings. Bioinformatics. 2023;39.</p>
      <p>doi:10.1093/bioinformatics/btad130
[18] Mapping Commons Cookiecutter. [cited 29 Jul 2023]. Available:</p>
      <p>https://github.com/mapping-commons/mapping-commons-cookiecutter
[19] Cookiecutter. In: PyPI [Internet]. [cited 29 Jul 2023]. Available:</p>
      <p>https://pypi.org/project/cookiecutter/
[20] 2nd mapping commons workshop on simple standard for sharing ontology mappings
(SSSOM). [cited 30 Jul 2023]. Available:
https://mappingcommons.github.io/sssom/events/mc2023/
[21] linkml-transformer: ALPHA data model mapping with linkml. [cited 30 Jul 2023]. Available:
https://github.com/linkml/linkml-transformer
[22] Matching tool implementation guide - A Simple Standard for Sharing Ontology Mappings
(SSSOM). [cited 30 Jul 2023]. Available:
https://mappingcommons.github.io/sssom/matching-tool-implementation-guide/
[23] OHDSI Vocabulary: Community contribution. [cited 30 Jul 2023]. Available:
https://github.com/OHDSI/Vocabulary-v5.0/wiki/Community-contribution
[24] Callahan TJ, Stefanski AL, Wyrwa JM, Zeng C, Ostropolets A, Banda JM, et al. Ontologizing
health systems data at scale: making translational discovery a reality. NPJ Digit Med.
2023;6: 89.
[25] Hertling, Sven, Jan Portisch, and Heiko Paulheim. "Melt-matching evaluation toolkit."
International conference on semantic systems. Cham: Springer International Publishing,
2019.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>Why</given-names>
            <surname>Mappings</surname>
          </string-name>
          Matter and how to make
          <source>them FAIR? [cited 30 Jul</source>
          <year>2023</year>
          ]. Available: https://www.fair
          <article-title>-impact.eu/events/fairimpact-events/why-mappings-matter-and-howmake-them-fair</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Matentzoglu</surname>
            <given-names>N</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Balhoff</surname>
            <given-names>JP</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bello</surname>
            <given-names>SM</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bizon</surname>
            <given-names>C</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brush</surname>
            <given-names>M</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Callahan</surname>
            <given-names>TJ</given-names>
          </string-name>
          , et al.
          <article-title>A Simple Standard for Sharing Ontological Mappings (SSSOM)</article-title>
          .
          <source>Database</source>
          .
          <year>2022</year>
          ;
          <year>2022</year>
          . doi:
          <volume>10</volume>
          .1093/database/baac035
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Matentzoglu</surname>
            <given-names>N</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Flack</surname>
            <given-names>J</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Graybeal</surname>
            <given-names>J</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Harris</surname>
            <given-names>NL</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hegde</surname>
            <given-names>HB</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hoyt</surname>
            <given-names>CT</given-names>
          </string-name>
          , et al.
          <article-title>A Simple Standard for Ontological Mappings 2022: Updates of data model and outlook</article-title>
          .
          <year>2022</year>
          . doi:
          <volume>10</volume>
          .5281/zenodo.7672104
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Presentations</surname>
          </string-name>
          .
          <source>[cited 30 Jul</source>
          <year>2023</year>
          ]. Available: https://mappingcommons.github.io/sssom/presentations/
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <article-title>[5] Overview of chaining rules</article-title>
          .
          <source>[cited 30 Jul</source>
          <year>2023</year>
          ]. Available: https://mappingcommons.github.io/sssom/chaining_rules/
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <article-title>[6] Set up a mapping registry/commons - A Simple Standard for Sharing Ontology Mappings (SSSOM)</article-title>
          .
          <source>[cited 30 Jul</source>
          <year>2023</year>
          ]. Available: https://mappingcommons.github.io/sssom/mapping-commons/
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Mapping</surname>
          </string-name>
          justifications
          <article-title>- A simple standard for sharing ontology mappings (SSSOM)</article-title>
          .
          <source>[cited 30 Jul</source>
          <year>2023</year>
          ]. Available: https://mapping-commons.github.io/sssom/mappingjustifications/
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>Data</given-names>
            <surname>Structures</surname>
          </string-name>
          <article-title>- curies documentation</article-title>
          .
          <source>[cited 31 Jul</source>
          <year>2023</year>
          ]. Available: https://curies.readthedocs.io/en/latest/struct.html
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Hoyt</surname>
            <given-names>CT</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Balk</surname>
            <given-names>M</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Callahan</surname>
            <given-names>TJ</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Domingo-Fernández</surname>
            <given-names>D</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Haendel</surname>
            <given-names>MA</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hegde</surname>
            <given-names>HB</given-names>
          </string-name>
          , et al.
          <article-title>Unifying the identification of biomedical entities with the Bioregistry</article-title>
          .
          <source>Sci Data</source>
          .
          <year>2022</year>
          ;
          <volume>9</volume>
          :
          <fpage>714</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Hoyt</surname>
            <given-names>CT.</given-names>
          </string-name>
          <article-title>curies: Idiomatic conversion between URIs and compact URIs (CURIEs)</article-title>
          . Github; Available: https://github.com/cthoyt/curies
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>