<!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>An Analysis of Ontological Entities to Represent Knowledge on Quantum Computing Algorithms and Implementations</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Darya Martyniuk</string-name>
          <email>darya.martyniuk@fokus.fraunhofer.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michael Falkenthal</string-name>
          <email>michael.falkenthal@stoneone.de</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Naouel Karam</string-name>
          <email>naouel.karam@fokus.fraunhofer.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Adrian Paschke</string-name>
          <email>adrian.paschke@fokus.fraunhofer.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Karoline Wild</string-name>
          <email>karoline.wild@iaas.uni-stuttgart.de</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Data Analytics Center</institution>
          ,
          <addr-line>Fraunhofer FOKUS, Berlin</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Institute of Architecture of Application Systems, University of Stuttgart</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>StoneOne AG</institution>
          ,
          <addr-line>Berlin</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The field of quantum computing is developing rapidly. As a result, a variety of quantum hardware, software development kits, and quantum algorithms have been developed in recent years. However, knowledge about these artifacts is either not available or spread among diferent sources. Thus, to analyze, compare, and evaluate knowledge on quantum computing an integrated knowledge base is required. In this paper, we introduce key concepts of an ontology for quantum algorithms and their implementations. The presented ontology serves as basis for a collaborative platform for researchers and practitioners to support collection and development of knowledge on the field of quantum computing.</p>
      </abstract>
      <kwd-group>
        <kwd>Ontology</kwd>
        <kwd>Taxonomy</kwd>
        <kwd>Quantum Computing</kwd>
        <kwd>Quantum Algorithm</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        exemplary programming code, which can form a valuable body of knowledge for
the development of quantum-inspired and -enhanced applications in the future.
This is important because, even being in the so-called Noisy Intermediate Scale
Quantum (NISQ) era [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ], quantum computing has the potential to become a
disruptive innovation driver in many diferent fields, where we are facing the
limitations of execution powers of classical computers. So, for example, it is
very likely that quantum computing will allow to tackle complex problems from
molecule simulations [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], the broad topic of artificial intelligence (AI) [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ], and
even the optimization of energy systems [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        However, for companies and scientists trying to leverage quantum computing
for business, development, and research, this means hard times ahead. This is
because the knowledge about quantum computing and, especially, how to build
applications that can make use of quantum resources to gain improvements over
classical algorithms is not systematically available. Explanations of quantum
algorithms, such as estimations of the speedup over classical algorithms,
theoretical considerations of required quantum resources, and actual implementations of
the algorithms are typically spread among diferent sources. As a consequence,
required knowledge has to be collected and obtained manually from a vast amount
of scientific publications, vendor-specific documentation pages, or public code
repositories. Yet, such information has to be analyzed holistically to understand
how to implement quantum algorithms and quantum applications for specific use
cases and scientific problems at hand. Moreover, the absence of an integrated
knowledge base hinders to establish a community bridging theoretical foundations
and research on new quantum algorithms with their usage, application, and
implementation for relevant and real scenarios. In this regard, an open ecosystem is
key for rapid technological progress in quantum computing via close cooperation
and steady interchange of ideas between research and industry [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ].
      </p>
      <p>
        Therefore, it is required to come up with a systematic approach to semantically
represent and curate knowledge about quantum computing algorithms along
with their implementations, as presented in this paper. We contribute with
a semantified meta-model that was engineered to provide the core knowledge
structure for semantic knowledge curation in the project PlanQK – platform and
ecosystem for quantum-enhanced AI [
        <xref ref-type="bibr" rid="ref13 ref18">13, 18</xref>
        ]. The semantic curation of knowledge
artifacts described and managed on the PlanQK platform provides the basis for
e.g. semantic search and semantic service functionalities. PlanQK aims to lay a
body of knowledge to the field of quantum-enhanced AI via a publicly accessible
platform following the mindset already taken in classical AI [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ]. Besides the pure
capturing of quantum algorithms and their implementations it is also inevitable
to establish a community-based discussion and exchange around the captured
knowledge to enable continuous evolution of the knowledge.
      </p>
      <p>This paper is structured as following: We introduce the PlanQK project in
Sect. 2 and discuss the key objectives of the intended knowledge platform. We
introduce the mentioned core meta-model as an ontology in Sect. 3. Finally,
we conclude this paper in Sect. 4 by an outlook to future work, which will be
conducted in PlanQK based on the presented ontology.
Specialist Algorithm Developer</p>
      <p>Data Provider</p>
      <p>Researcher
QPU Provider</p>
      <p>Software Architect
and Developer</p>
      <p>Analysis and development platform for algorithms, data, and applications
Crawler IntUesrefarce Expert Portal
Customer Service Provider</p>
      <p>System Integrator Consultant</p>
      <p>Marketplace
Customer Provider
Portal Portal
API</p>
      <p>API</p>
      <p>API</p>
      <p>API
Publication
Content Store</p>
      <p>QAlgo- QC-Pattern- Data- QApp</p>
      <p>Repository Repository Repository Repository NISQ-Analyzer
ArXiv/ GitHub / Bitbucket / GitLab / Docker Hub / Dataset Search / …
Requests/
Purchases/
Offerings</p>
      <p>Deployment &amp;</p>
      <p>
        Management
QC-, Cloud- and
OnPremise-Infrastructure
The vision of a collaborative platform for the exchange of knowledge in the field
of quantum computing has already been presented in previous work [
        <xref ref-type="bibr" rid="ref11 ref12">11, 12</xref>
        ]. The
PlanQK project will realize this vision by providing a platform that enables
(i) knowledge and technology transfer between research and industry, (ii) a
vendoragnostic access to quantum computing resources, and (iii) quantum applications
as a service. Fig. 1 depicts the PlanQK architecture with the two main components:
The analysis and development platform and the marketplace. The goal of the
ifrst component is to provide a platform for quantum experts to collect, discuss,
evaluate, and share knowledge, e. g., publications, algorithms, or implementations.
Marketplace, on the other hand, ofers solutions in form of quantum applications
and consulting services to users with a specific problem to be solved.
      </p>
      <p>
        The key knowledge artifacts that are provided on the analysis and
development platform include Quantum Algorithms (QAlgos) and their Implementations
using diferent SDKs for the diferent quantum computing vendors, Quantum
Design Patterns (QC-Patterns) that provide best practices for quantum
algorithms, Datasets (Data) for specific machine learning and AI algorithm, and
Quantum Applications (QApps) that can be deployed and integrated with classical
applications. New knowledge, e. g., in form of publications, can be added using
the user interface or in an automated manner using the crawler. The knowledge
artifacts can then be extracted and linked, discussed and evaluated, and made
available to customers to identify suitable algorithms or implementations for their
specific use cases. Selected QApps can be automatically deployed and managed,
e. g., using established deployment technologies. The NISQ-Analyzer component
supports users by analyzing which implementation of a quantum algorithm and
which quantum computer are recommended for specific input data [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ].
      </p>
      <p>Publication
referenced by</p>
      <p>An important goal of the PlanQK platform is to build a quantum community
and establish knowledge exchange between scientific and commercial users. The
ontology presented in this work defines an unambiguous machine-interpretable
semantic description of the platform knowledge artifacts and intend to used to
support the user exchange through (i) proving the logical consistency of the
curated data, (ii) serving as the foundation for the realization of various
AIbased features, e.g., semantic faceted search, natural language question answering
engine, or recommendation system for the selection of an appropriate quantum
algorithm in a specific use case, and (iii) providing an opportunity to document
the expert discussions held on the platform in a semantically usable way.
3</p>
      <p>
        Towards a Unified Ontology for Quantum Algorithms
In developing the ontology, we followed existing ontology development
guidelines [
        <xref ref-type="bibr" rid="ref17 ref4 ref5">4, 5, 17</xref>
        ]. As a first step towards the knowledge definition, we derived
competency questions from general platform requirements specified by potential
users (both quantum computing researchers and industry partners). Based on the
list of competency questions, we identified key concepts related to the description
of quantum algorithms and their implementations. The ontology draft has been
then presented to quantum computing experts to collect their feedback and has
been improved accordingly.
      </p>
      <p>
        Fig. 2 depicts the connections between key concepts of the ontology, which we
specify as OWL4 classes. This design was inspired by the
Algorithm-Implementation-Execution Ontology Design Pattern (ODP) [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] and the ML-Schema Core
Vocabulary [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ]. The class Algorithm aggregates characteristics that are common
for quantum and classical algorithms and Implementation represents a realization
of an algorithm. Publication represents publications about an algorithm or an
algorithm implementation. Since the class Execution requires in-depth knowledge
about quantum hardware and input data, it will be considered in detail in
future work. In the following, we introduce the classes Algorithm (Sect. 3.1) and
Implementation (Sect. 3.2) with their related concepts in detail.
3.1
      </p>
    </sec>
    <sec id="sec-2">
      <title>Algorithms</title>
      <sec id="sec-2-1">
        <title>4 https://www.w3.org/OWL/</title>
        <p>Quantum</p>
        <p>Annealing
Measurementbased Quantum
Computation
owl:Class
owl:NamedIndividual
owl:ObjectProperty
rdfs:subclassOf
rdf:type</p>
        <p>Solution and Problem Type, and connect them with Algorithm through object
properties “provides” and “solves”. Solution is defined as algorithmic steps to
solve a computation problem, typically pseudocode or/and circuit. Solution can
have connection to the class Function when it is an essential part of the solution,
such as an appropriate objective function is a fundamental element of optimization
algorithms or a quantum oracle is a crucial part of some quantum algorithms,
e.g., Deutsch-Jozsa algorithm. Problem Type represents types of problems that
are solvable by algorithms. Many real-world problems can be mathematically
formalized in terms of other problems, e. g., a cluster problem can be expressed as
an optimization problem. Complexity Class stores knowledge about the hardness
of a problem. The class Input represents the input accepted by an algorithm,
and Output specifies the output produced by an algorithm. The ontology is able
to express two relation types between algorithms: An algorithm can improve an
existing algorithm or be based on the idea of other algorithms.</p>
        <p>
          A researcher designs an algorithm with a computational model in mind. We
distinguish between Classical and Quantum Computational Model and classify
algorithms in Quantum, Classical and Hybrid Algorithms depending on the model
for which an algorithm was designed. Quantum Algorithm is an algorithm that is
designed only for a quantum computational model. Examples of the Quantum
Computational Model are “gate model”, “measurement-based quantum
computation”, “quantum annealing”. Classical Algorithm is equivalent to an algorithm that
is constructed only for a classical computational model. Hybrid Algorithm is an
algorithm that utilizes some quantum and some classical computational models.
In addition to the above presented classification of algorithms, the ontology also
forms the taxonomy of algorithms based on the underlying problem type (machine
learning, optimization, search algorithms etc.). The classes for specific algorithm
types can act in the future as connection points for linking semantically similar
knowledge bases, e. g., machine learning algorithms can be linked with such
knowledge bases as MEX [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ], a lightweight vocabulary for exchanging machine
learning metadata, or ANNETT-O [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ], an ontology for describing artificial neural
network evaluation, topology, and training.
        </p>
        <p>realizes</p>
        <p>Classical
Computational</p>
        <p>Resource</p>
        <p>
          By exploiting quantum-mechanical efects, such as superposition,
entanglement, and quantum tunneling, quantum models perform computation more
eficiently than classical ones [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]. Thus, quantum and hybrid algorithms can
achieve speedup over their best known classical counterparts. Formalizing this
consideration, we connect the classes Quantum Algorithm and Hybrid Algorithm
through the property “achieves quantum speedup over“ with the class Classical
Algorithm.
        </p>
        <p>
          For the class Algorithm we define the following data properties (not shown
in Fig. 3):“skos:prefLabel“ and “skos:altLabel“ (algorithm name and its
abbreviation, this properties are reused from SKOS Schema [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ]), “intend“ (the idea
of the algorithm described in 1-2 sentences), “assumption“ (basic assumptions
underlying the algorithm), and “limitation“ (known limitations of the algorithm).
The classes Quantum Algorithm and Hybrid Algorithm have additional data
properties: “NISQ-ready“ from type “xsd:boolean“, which relates an expert
estimation whether the execution of an algorithm on NISQ-devices will be possible,
and “expected quantum speedup“, which specifies speedup (e. g., “exponential“)
obtained by the algorithm over the classical methods for the same task.
        </p>
        <p>A Computational Model is realized by a Computational Resource, which
collects instances utilized for the execution of an implementation. Fig. 4 illustrates
relations between Computational Model and Computational Resource. We
distinguish between Classical and Quantum Computational Resource that realize
only Classical and only Quantum Computational Model, respectively. Quantum
computational resources are categorized in Quantum Processing Unit (QPU)
and Quantum Simulator. Since quantum simulators run on a classical hardware,
Quantum Simulator is connected with Classical Computational Resource through
the property “compatible with”. Quantum computational resources have specific
characteristics defined by the class Quantum Resource Characteristic, which
has subclasses Gate Set, Fidelity, Quantum Access Random Memory (qRAM),
Number of Qubits, and Qubit Connectivity. Also quantum and hybrid algorithms
can specify hardware characteristics that are required for their realization, as
shown in Fig. 4. For example, an algorithm can require a specific set of gates
realizable only by some computational resources or show a theoretical speedup
but assumes the availability of a qRAM such as Grover‘s algorithm for database
search, or HHL for solving linear systems of equations. This information allows
Computer
Language</p>
        <p>written in
Programming</p>
        <p>Language</p>
        <p>Instruction</p>
        <p>Language</p>
        <p>Classical Quantum
Programming embedded Programming</p>
        <p>Language in Language
developers (i) to evaluate the practical usage of an algorithm, and (ii) to select
an appropriate quantum computational resource for executing an algorithm.
3.2</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Algorithm Implementation</title>
      <p>
        Fig. 5 presents classes connected with the class Implementation. An
implementation is written in a Computer Language and can depend on a Software Tool.
The class Computer Language formalizes languages that can be used to write a
machine or programming code. Similar to Lando et al. [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] and LaRose [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], we
distinguish between Instruction and Programming Language. Instruction
Language is defined as a low-level machine language used to instruct the computer
which physical operation to perform on which bit [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Instruction Language has
a subclass Quantum Instruction Language with individuals such as “Quil” and
“OpenQASM”. Programming Language has subclasses Classical and Quantum
Programming Language and contains languages that have a human readable
syntax. Some quantum vendors provide quantum programming languages that
are embedded in classical host languages, e. g., PyQuil from Forest SDK or Qiskit
from Qiskit SDK are embedded in Python [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Others introduce new programming
languages, such as Q# from Microsoft. Software Tool collects various frameworks,
libraries, SDKs, or APIs that developers can use for implementing an algorithm.
We specify classes Implementation, Computer Language and Software Tool as
subclasses of Software. Guided by Computer System ODP [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], Software is connected
with Computational Resource and with itself with the property “compatible with”.
      </p>
      <p>
        The class Quantum Provider collects vendors that provide access to quantum
computational resources. Most quantum providers supply software tools for
developing and executing implementations on their quantum computational
resources [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Analyzing various software tools, we came to the conclusion that if
a software tool supports a specific quantum hardware provider, e. g., IBM, Rigetti,
or D-Wave, it is compatible with all quantum computational resources provided
by them. To formalize it, we connect the classes Software Tool and Quantum
Hardware Provider through the property “supports“ and define the relation
“compatible with“ as a superproperty of the chain “supports“ and “provides“.
      </p>
      <p>Apart from the algorithm realization itself, an implementation can include
error correction, pre- and postprocessing. Error Correction Technique collects
methods for limiting errors that occur during information processing. Data
Preprocessing Technique specifies operations that are applied on the input data
before the actual algorithm steps will be executed. The class Data Postprocessing
Technique includes methods that are applied on the algorithm output. A common
postprocessing technique for quantum and hybrid algorithms is the Read-out
Error Correction that is specified in the ontology as a subclass of both Error
Correction Technique and Data Postprocessing Technique.</p>
      <p>Ontology source can be found in our repository5. The first prototypical
implementation of the platform services has shown that the ontology is consistent
and can be used for the realization of semantic features.
4</p>
      <p>Conclusion and Future Work
In this work we present the first key entities towards a unified ontology for
semantically curating knowledge about quantum algorithms and their
implementations. The ontology provides a basis for the AI-powered semantic features
on the PlanQK platform, such as semantic search and semantic services. The
next steps will be to extend the ontology to not yet covered knowledge artifacts,
such as quantum applications and data, and to refine the existing artifacts. In
addition, provenance data about implementation execution and performance
will be included, which is important to identify suitable algorithms for a given
problem. Furthermore, a standard-based API for supporting the semantic access
to the curated knowledge artifacts and semantic services will be developed.
Acknowledgments This work was partially funded by the BMWi project
PlanQK (01MK20005N / 01MK20005F).</p>
      <sec id="sec-3-1">
        <title>5 https://github.com/PlanQK/semantic-services</title>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Abhijith</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , et al.:
          <article-title>Quantum algorithm implementations for beginners</article-title>
          . arXiv preprint arXiv:
          <year>1804</year>
          .
          <volume>03719</volume>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Ajagekar</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>You</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Quantum computing for energy systems optimization: Challenges and opportunities</article-title>
          .
          <source>Energy</source>
          <volume>179</volume>
          ,
          <fpage>76</fpage>
          -
          <lpage>89</lpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Esteves</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moussallem</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Baron</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Soru</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Usbeck</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ackermann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lehmann</surname>
          </string-name>
          , J.:
          <article-title>Mex vocabulary: a lightweight interchange format for machine learning experiments</article-title>
          .
          <source>In: SEMANTICS '15</source>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Garijo</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Poveda-Villalón</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Best practices for implementing fair vocabularies and ontologies on the web</article-title>
          . ArXiv abs/
          <year>2003</year>
          .13084 (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Karapiperis</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Apostolou</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Consensus building in collaborative ontology engineering processes</article-title>
          .
          <source>j-jukm 1(3)</source>
          ,
          <fpage>199</fpage>
          -
          <lpage>216</lpage>
          (dec
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Klampanos</surname>
            ,
            <given-names>I.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Davvetas</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Koukourikos</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karkaletsis</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>Annett-o: An ontology for describing artificial neural network evaluation, topology and training</article-title>
          .
          <source>Int. J. Metadata Semant. Ontologies</source>
          <volume>13</volume>
          ,
          <fpage>179</fpage>
          -
          <lpage>190</lpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Kühn</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zanker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Deglmann</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marthaler</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weiß</surname>
          </string-name>
          , H.:
          <article-title>Accuracy and resource estimations for quantum chemistry on a near-term quantum computer</article-title>
          .
          <source>Journal of Chemical Theory and Computation</source>
          <volume>15</volume>
          (
          <issue>9</issue>
          ),
          <fpage>4764</fpage>
          -
          <lpage>4780</lpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Lando</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lapujade</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kassel</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fürst</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Towards a general ontology of computer programs</article-title>
          . In: ICSOFT (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>LaRose</surname>
          </string-name>
          , R.:
          <source>Overview and Comparison of Gate Level Quantum Software Platforms. Quantum</source>
          <volume>3</volume>
          ,
          <issue>130</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Lawrynowicz</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Esteves</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Panov</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Soru</surname>
          </string-name>
          , T., Dzeroski, S.,
          <string-name>
            <surname>Vanschoren</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>An algorithm, implementation and execution ontology design pattern</article-title>
          . In: Hammar,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Hitzler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>Krisnadhi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Lawrynowicz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Nuzzolese</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.G.</given-names>
            ,
            <surname>Solanki</surname>
          </string-name>
          , M. (eds.)
          <article-title>Advances in Ontology Design and Patterns</article-title>
          .
          <source>Studies on the Semantic Web</source>
          , vol.
          <volume>32</volume>
          , pp.
          <fpage>55</fpage>
          -
          <lpage>68</lpage>
          . IOS Press (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Leymann</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Barzen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Falkenthal</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Towards a Platform for Sharing Quantum Software</article-title>
          .
          <source>In: Proceedings of the 13th Advanced Summer School on Service Oriented Computing</source>
          (
          <year>2019</year>
          ). pp.
          <fpage>70</fpage>
          -
          <lpage>74</lpage>
          .
          <source>IBM Technical Report (RC25685)</source>
          ,
          <source>IBM Research Division (Sep</source>
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Leymann</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Barzen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Falkenthal</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vietz</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weder</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wild</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Quantum in the Cloud: Application Potentials and Research Opportunities</article-title>
          .
          <source>In: Proceedings of the 10th International Conference on Cloud Computing and Services Science (CLOSER</source>
          <year>2020</year>
          ). pp.
          <fpage>9</fpage>
          -
          <lpage>24</lpage>
          . SciTePress (May
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Linnhof-Popien</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          : PlanQK - Quantum
          <source>Computing Meets Artificial Intelligence. Digitale Welt</source>
          <volume>4</volume>
          ,
          <fpage>28</fpage>
          -
          <lpage>35</lpage>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Miles</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bechhofer</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>SKOS simple knowledge organization system reference</article-title>
          .
          <source>Tech. rep., W3C</source>
          (
          <year>2009</year>
          ), https://www.w3.org/TR/skos-reference/
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Mitzias</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kontopoulos</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          , Riga, M.:
          <article-title>Computer system ontology development pattern (</article-title>
          <year>2017</year>
          ), http://ontologydesignpatterns.org/wiki/Submissions:Computer_System, accessed
          <year>2020</year>
          -
          <volume>12</volume>
          -01
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Mohseni</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , et al.:
          <article-title>Commercialize quantum technologies in five years</article-title>
          .
          <source>Nature</source>
          <volume>543</volume>
          ,
          <fpage>171</fpage>
          -
          <lpage>175</lpage>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Noy</surname>
            ,
            <given-names>N.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mcguinness</surname>
            ,
            <given-names>D.L.</given-names>
          </string-name>
          :
          <article-title>Ontology development 101: A guide to creating your first ontology</article-title>
          .
          <source>Tech. rep.</source>
          , Stanford University (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18. PlanQK:
          <article-title>Planqk - platform and ecosystem for quantum-inspired artificial intelligence (</article-title>
          <year>2020</year>
          ), https://planqk.de/en/, accessed 2020-
          <volume>06</volume>
          -15
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Preskill</surname>
          </string-name>
          , J.:
          <article-title>Quantum Computing in the NISQ era and beyond</article-title>
          .
          <source>Quantum</source>
          <volume>2</volume>
          ,
          <issue>79</issue>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Publio</surname>
            ,
            <given-names>G.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Esteves</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ławrynowicz</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Panov</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Soldatova</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Soru</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vanschoren</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zafar</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          :
          <article-title>Ml-schema: Exposing the semantics of machine learning with schemas and ontologies (</article-title>
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Salm</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Barzen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Breitenbücher</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Leymann</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weder</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wild</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>A Roadmap for Automating the Selection of Quantum Computers for Quantum Algorithms</article-title>
          . arXiv preprint arXiv:
          <year>2003</year>
          .
          <volume>13409</volume>
          (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Schuld</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Petruccione</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Supervised Learning with Quantum Computers</article-title>
          .
          <source>Quantum Science and Technology</source>
          , Springer International Publishing (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Vanschoren</surname>
            , J., van Rijn,
            <given-names>J.N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bischl</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Torgo</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Openml: networked science in machine learning</article-title>
          .
          <source>SIGKDD Explorations</source>
          <volume>15</volume>
          (
          <issue>2</issue>
          ),
          <fpage>49</fpage>
          -
          <lpage>60</lpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>