<!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>Matching Web Entities with Potential Actions</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Ioannis Stavrakantonakis</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Anna Fensel</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dieter Fensel</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of Innsbruck, STI Innsbruck Technikerstr. 21a</institution>
          ,
          <addr-line>6020 Innsbruck</addr-line>
          ,
          <country country="AT">Austria</country>
        </aff>
      </contrib-group>
      <fpage>35</fpage>
      <lpage>38</lpage>
      <abstract>
        <p>The creation of schema.org as the de facto vocabulary for the implementation of Semantic Annotations was the dawn of a new era for the Web by motivating the Web developers to start weaving semantics in the content, mainly, for visibility reasons in search engine results. Moving further, the new version of the vocabulary enables Web entities to self-describe the Actions with which they interact with users, agents or services. In this scope, we present our ongoing work on automatic weaving of Actions based on the existing semantic annotations of a website.</p>
      </abstract>
      <kwd-group>
        <kwd>Semantic Annotations</kwd>
        <kwd>schema</kwd>
        <kwd>org</kwd>
        <kwd>actions</kwd>
        <kwd>Web APIs</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        The idea to build web agents to understand web content and interact with it in
order to realise a given plan and achieve goals has been part of the Semantic Web
vision [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] since the very rst steps of the related working groups. As described by
Hendler [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] with the example of intelligent travel agents, those systems should
be communicative, capable, autonomous and adaptive. The various vocabularies
and ontologies, that have been developed until today, contribute towards making
web content machine-understandable through semantic annotations, which will
enable web agents to behave as described before. The schema.org initiative aimed
to accelerate the adoption and creation of semantic annotations and play the
role of the de facto vocabulary in this area. An example of applying semantic
annotations to an already existing infrastructure is demonstrated in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], in a real
world scenario of the touristic sector.
      </p>
      <p>
        In the same direction, but from another perspective, the discovery of Web
Services [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] aimed to build a layer that would enable the web agents to be capable
of interacting with web entities. In this direction, the very recent extension of
the schema.org vocabulary [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] brings these ideas from the research initiatives to
the realisation layer of the Web by allowing entities to have a self-explanatory
presentation of the actions they enable and how these actions can be invoked. In
this scope, our approach aims to facilitate the uptake of the vocabulary as well
as the scalability of the semantic annotations implementation.
      </p>
      <p>The remainder of the paper describes the structure of the actions dimension
of schema.org and highlights the di culties of using it in section 2; outlines
the ongoing work of the proposed approach in section 3; and closes with our
conclusions and the current outlook in section 4.</p>
    </sec>
    <sec id="sec-2">
      <title>Background</title>
      <p>One of the great features of the new extension is the exibility of combining
any Action to any type of object/entity of the vocabulary. This is allowed by
design as the related property has been hooked to the most generic class, the
Thing. Speci cally, the action property is named potentialAction with domain
the class Thing and range the class Action, which is at the top of the inheritance
hierarchy of the actions. Thinking in triples, the schema has been designed in
such a way that more than one triple could be created in order to enable a
negrained description of the action, participating agents, objects, results of it and
time variables.</p>
      <p>For example, a Hotel object could participate in many di erent actions as
shown in Fig. 1.</p>
      <p>The above described exibility enables developers to build very descriptive
websites and web applications. On the other hand, it needs deep understanding
of the actions hierarchy for matching the two sides in order to make the right
decisions that would result in meaningfully described content with a high
potential of usability and visibility. Our ongoing work aims to tackle those obstacles
in the scope of a broader idea of leveraging websites to open self-described APIs
by annotating the content and the provided services.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Our approach</title>
      <p>The approach that we follow aims to address the di culties of developing Actions
on websites and web applications. The added value of our contribution is the
generation of suggestions about potential actions with which the described web
entities of a website could support and interact. We de ne the problem as follows.
We assume that semantic annotations have already been implemented for a
given website, which contains entities that would be meaningful to interact with
other entities in the Web sphere. For example, in case of lodging businesses, the
o ered services (e.g. reserve rooms) could be potential objects that an agent
would be interested to interact beyond a simple read-only consumption (e.g. to
make/cancel or update a reservation). Therefore, let W = fE1; E2; : : : ; Eng with
n 2 N be the set of all entities described in a website. Each entity E 2 W is the
subject for properties such that E = PT [ PA, where PT stands for properties
derived from any class and PA for those that refer to the action class. We
make this arti cial distinction between properties in order to explain better our
approach.</p>
      <p>Furthermore, let T = fT1; T2; : : : ; Ttg with t 2 N be the set of all entity classes
in schema.org and A = fA1; A2; : : : ; Amg with m 2 N be the set of all action
classes in schema.org. We de ne the function : T ! P (A) that maps each
entity to the set of actions that could be used by the entity type. Thus, having
speci ed these mappings, we are able to de ne an entity E and its properties
PT and PA. The core of our approach consists of the idea that we could de ne
potential actions for a class T , by studying the range of the properties in an
Action class A. In the scope of this paper, we identify two possible cases. The
rst case, which is the simplest one, refers to the direct mapping of the range
of PA to classes T . For example, according to Fig.1, the DepartAction A1 2 A
has the property fromLocation PA1 2 PA with range Place T1 2 T . Thus, any
subclass of T1 is in the range of PA1 and we could assume the A1 as a potential
action for the class Hotel (Place ! Hotel).</p>
      <p>In the second case, we assume that when properties PA of a class A1 2 A and
properties PT of a class T1 2 T , and PT are not derived from superclasses (e.g.
the Thing ), have matching ranges, then A1 is a potential action for T1. Building
on the example of Fig.1 we apply the above idea as shown in Table 1. In
particular, the LodgingReservation class and the ReserveAction of the schema.org
vocabulary are described in the table with all their properties, excluding any
derived properties from superclasses. The former models a reservation entity of
a lodging business and the latter depicts an action of reserving concrete
objects like a hotel or a restaurant. The middle column of the table indicates the
elds that map from the Reservation class to the related Action class. As it is
shown, the range of all the properties of the Action class map to a subset of the
Reservation's properties.</p>
      <p>At the evaluation part of the described approach, we employ datasets based
on entities that instantiate schema.org classes and websites collected via web
crawling in order to determine the occurrence of false positives and false negatives
based on precision and recall measurements. An example of such dataset is our
ongoing Linked Open Data dataset of touristic service providers in Innsbruck
and its surroundings1.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Conclusion</title>
      <p>Our approach could be summarised as an initiative towards the realisation of the
paradigm that will transform websites to machine-readable data feeds, in other
words, to APIs. At the core of this paradigm, lie the annotation of Web resources
with a widely adopted vocabulary. The bene t of enabling the automatic
extension of existing annotated entities with actions is threefold: a) supports the easy
description of more content on a website, e.g. \Last reservation for the 24th of
August was made 3 minutes ago"; b) promotes the exposure of speci c potential
actions of existing entities of a Website, e.g. a potential action for the Hotel is a
ReserveAction; and c) facilitates the establishment of a communication channel
between agents and the provided services of a Website.</p>
      <p>
        In the future work, we consider the EntryPoint property of the Action class,
which is specially interesting for Web agents, as it gives information about how
to formulate a request and what to expect as a response. Furthermore, we aim
to explore the matching of classes and actions with more ways and to integrate
it with the infrastructure provided by the Hydra [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] approach, that enables the
development of hypermedia-driven Web APIs.
      </p>
      <p>Acknowledgments. This work has been partially supported by the EU projects
BIG, BYTE, eFreight, FITMAN, LDBC, MSEE, PlanetData and PRELIDA,
FWF project OntoHealth, as well as FFG projects OpenFridge and TourPack.
1 http://loi.sti2.at/openrdf-workbench/repositories/STI/summary</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Fensel</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hendler</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lieberman</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wahlster</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Spinning the semantic web</article-title>
          .
          <source>In IEEE Intelligent Systems</source>
          (
          <year>2003</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Hendler</surname>
          </string-name>
          , J.:
          <article-title>Is there an intelligent agent in your future?</article-title>
          <source>Nature</source>
          , vol.
          <volume>11</volume>
          (
          <year>1999</year>
          ) http: //www.nature.com/nature/webmatters/agents/agents.html
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Toma</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stanciu</surname>
            ,
            <given-names>C.V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fensel</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stavrakantonakis</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fensel</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Improving the online visibility of touristic service providers by using semantic annotations</article-title>
          .
          <source>In the 11th ESWC</source>
          (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Fensel</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lausen</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Polleres</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>de Bruijn</surname>
          </string-name>
          , J.,
          <string-name>
            <surname>Stollberg</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Roman</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Domingue</surname>
          </string-name>
          , J.:
          <source>Enabling semantic web services</source>
          . Springer-Verlag Berlin Heidelberg (
          <year>2007</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Brickley</surname>
            <given-names>D.</given-names>
          </string-name>
          : Announcing Schema.
          <source>org Actions. (April</source>
          ,
          <year>2014</year>
          ) http://blog.schema. org/
          <year>2014</year>
          /04/announcing-schemaorg-actions.html
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Lanthaler</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Creating 3rd generation web APIs with hydra</article-title>
          .
          <source>In Proceedings of the 22nd international conference on World Wide Web companion</source>
          (pp.
          <fpage>35</fpage>
          -
          <lpage>38</lpage>
          ).
          <source>International World Wide Web Conferences Steering Committee</source>
          (
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>