<!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 role of higher-order models in robotics, and its reasoning challenges</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Herman Bruyninckx KU Leuven Leuven</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Belgium</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p />
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>The expectations for modern robotic systems are towards more "smart"
control and "autonomous" decision making. Even the simplest step in
that direction involves the integration of multiple expertises: world
modelling, perception, control, mechatronics, etc. As mainstream
demonstration practice shows painfully every day, the software "digital
twins" of all these aspects can not be developed and deployed without
any coupling. This talk advocates that the approach to be followed by
the robotics community is not to keep on building systems that hide
these coupling behind opaque interfaces and lots of hand-tuned magic
numbers inside the code. But to start the e ort to model all these
aspects in a decoupled way, with explicit extra models to represent the
possible couplings. This approach has many challenges, such as getting
a community behind standardization of these models. The presentation
will discuss only technological challenges, with concrete suggestions for
solutions. The core role is played by property graphs and graph
traversal, and the core challenge is to design the "right" host languages for
higher-order modelling, and the "right" graph traversal query tools for
reasoning.</p>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>