<!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>Triple Space Computing for Semantic Web Services</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>A roadmap for Triple Space Computing in Semantic Web Services</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Omair Shafiq Digital Enterprise Research Institute (DERI), University of Innsbruck (UIBK) 6020 Innsbruck</institution>
          ,
          <country country="AT">Austria</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This thesis will address how to enable Triple Space Computing as a communication paradigm for Semantic Web Services. Currently, Semantic Web Services are following a message based communication paradigm. Triple Space Computing is envisioned as communication and coordination paradigm for Semantic Web Services which is an extension of tuple space computing to support RDF and then use it for communication based on the principle of persistent publication and read of data. Web Service Modeling Ontology (WSMO) is our conceptual model for Semantic Web Services. Web Service Execution Environment (WSMX) is one of the reference implementations of the WSMO conceptual model. The paper presents an overview of technical insights about integration of WSMX with Triple Space Computing and proposes that how WSMX can use Triple Space computing for its communication and coordination in terms of dynamic components management, external communication management, resource management and coordination of different interconnected WSMXs.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Introduction
inter-connected WSMX and then to build an application scenario to show the viability.
Each of the integration entry points have been described in subsections below.</p>
      <p>
        WSMX has a management component [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] that manages the over all execution by
enabling coordination of different components based on some execution scenario [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]
specified by user in Goal. In this way there is a clear separation between business and
management logic in WSMX. The individual components have clearly defined interfaces
and have component implementation well separated with communication issues. Each
component in WSMX have wrapper to handle the communication issues. The WSMX
manager and individual components wrappers are needed to be interfaced with Triple Space
in order to enable the WSMX manager to manage the components over Triple Space. The
communication between manager and wrappers of the components will be carried out by
publishing and subscribing the data as a set of RDF triples over triple space. The wrappers
of components that handle communication will be interfaced with Triple Space
middleware.
      </p>
      <p>
        WSMX acts as a semantic middleware between users and real world web services [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
Currently, due to existence of message oriented communication paradigm, users
communicate with WSMX and WSMX communicate with Web Services synchronously.
The external communication manager of WSMX is needed to provide a support to
communicate over Triple Space. The interfaces for sending and receiving external
messages by WSMX are needed provide a grounding support to alternatively communicate
over Triple Space. This needs to be resolved by addressing several issues, i.e. invoker
component in WSMX is needed to support Web Services Description Language (WSDL)
and Simple Object Access Protocol (SOAP) communication binding over Triple Space. The
Entry point interfaces will be interfaced with Triple Space middleware in order to provide
the glue between existing Web Services standards and Triple Space Computing.
      </p>
      <p>
        WSMX contains different repositories to store ontologies, goals, mediators and web
services descriptions as WSML based files [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The internal repositories of WSMX are
needed to be made optional and enable to store the WSML based data as set of RDF named
graphs in Triple Space Storage. This is mainly concerned with transforming the existing
representation of data in form of WSML into RDF representation. The repository interfaces
are needed to be interfaced with Triple Space middleware.
      </p>
      <p>After enabling WSMX with Triple Space Computing, the next step will be to enable the
communication and coordination of different WSMXs over Triple Space, i.e. forming a
cluster of different interconnected WSMX nodes to support distributed service discovery,
selection, composition, mediation, invocation etc. The management component in WSMX
is will be enhanced to coordinate with WSMX managers in other WSMXs over Triple
Space to form a cluster.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>D.</given-names>
            <surname>Fensel</surname>
          </string-name>
          ,
          <article-title>Triple-space computing: Semantic Web Services based on persistent publication of informatio:</article-title>
          <source>In Proceedings of the IFIP International Conference on Intelligence in Communication Systems, INTELLCOMM</source>
          <year>2004</year>
          , Bangkok, Thailand,
          <source>November 23-26</source>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>C.</given-names>
            <surname>Bussler</surname>
          </string-name>
          et al,
          <article-title>Web Service Execution Environment (WSMX), W3C Member Submis-sion</article-title>
          ,
          <year>June 2005</year>
          . Available at http://www.w3.org/Submission/WSMX
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>M.</given-names>
            <surname>Zaremba</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Moran</surname>
          </string-name>
          , T. Haselwanter, WSMX Architecture,
          <year>D13</year>
          .
          <year>4v0</year>
          .2 WSMX
          <string-name>
            <given-names>Working</given-names>
            <surname>Draft</surname>
          </string-name>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>O.</given-names>
            <surname>Shafiq</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Krummenacher</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Martin-Recuerda</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Ding</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Fensel</surname>
          </string-name>
          ,
          <article-title>"Triple Space Computing middleware for Semantic Web Services"</article-title>
          ,
          <source>The MWS Workshop at 10th IEEE International Enterprise Computing Conference (EDOC</source>
          <year>2006</year>
          ),
          <fpage>16</fpage>
          -20
          <source>October</source>
          <year>2006</year>
          ,
          <string-name>
            <given-names>Hong</given-names>
            <surname>Kong</surname>
          </string-name>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>T.</given-names>
            <surname>Haselwanter</surname>
          </string-name>
          , Maciej Zaremba and
          <string-name>
            <given-names>Michal</given-names>
            <surname>Zaremba</surname>
          </string-name>
          .
          <article-title>Enabling Components Management and Dynamic Execution Semantic in WSMX</article-title>
          .
          <source>WSMO Implementation Workshop 2005 (WIW</source>
          <year>2005</year>
          ),
          <fpage>6</fpage>
          -7 June, Innsbruck, Austria.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>