iServe
Where Linked Data Meets Services
 
  • News

    • iServe’s code released

      After quite some time extending and reengineering iServe, we have finally released its code as open source. The project is [...]

    • iServe in the Cloud

      A new version of the linked data cloud has been released, see lod-cloud.net . We are happy to see that [...]

    • iServe presented at ORES – ESWC 2010

      iServe was presented for the first time at the ESWC 2010 Workshop on Ontology Repositories and Editors for the Semantic [...]

  • iServe Team

    Carlos Pedrinaci [Main Contact]
    John Domingue
    Dong Liu

    Funded By

    SOA4All VPH-Share

    Home

    What

    iServe is what we refer to as service warehouse which unifies service publication, analysis, and discovery through the use of lightweight semantics as well as advanced discovery and analytic capabilities. iServe provides the typical features of service registries and additional functionality that exploits service descriptions, service annotations and further data gathered and derived from the analysis of these descriptions, data crawled from the Web, periodic monitoring and user activities.

    A fundamental feature of iServe is that it publishes Semantic Web Services as Linked Data, no matter their original format. These services, which we refer to as Linked Services, help Linked Data application developers to locate Web services and Web APIs they can use to process or enrich their data.

    We currently have two main deployments:

    • Main iServe deployment which is based on an old yet stable version of the software. You can directly use this version from your application through its Web API as we won’t be updating it very frequently.
    • iServe development deployment which uses the most recent version of the software and can thus introduce some changes in the conceptual model and the API.

    Why

    Service-orientation advocates the development of complex distributed applications based on the reuse and composition of existing functionality offered as services. Essential to this vision are the publishing and discovery of services. A number of repositories have been created to this end but they have failed to provide suitable support for publishing and querying them in expressive and extensible manner.

    How

    The Web of Data proposes a set of principles that actually represent the current best practices for publishing data on the Web in a machine processable manner. iServe builds upon these principles and uses as its core what we refer to as the Minimal Service Model, a minimal vocabulary for describing services in RDF which abstracts us away from the original approach used for annotating the services, such as SAWSDLWSMO-LiteMicroWSMO or OWL-S. The Minimal Service Model provides a simple common ground for describing both WSDL services and Web APIs in RDF in a way such that it can be directly used by developers for simple service matchmaking based on SPARQL.

    iServe currently embeds a number of import mechanisms able to deal with

    Taking the original descriptions, iServe automatically generates the appropriate RDF statements according to the Minimal Service Model and expose them as linked data, thus providing a simple means for publishing Semantic Web Services in a manner that is suitable for the description and interlinking of services, people and data.

    Using iServe

    To facilitate the consumption and manipulation of the published linked data about services, iServe provides three interfaces:

    • a Web-based application, called iServe Browser, allowing users to browse, query and upload services to iServe
    • a SPARQL endpoint where all the data hosted in iServe can be accessed and queried
    • a RESTful API that enables creating, retrieving and querying for services directly from applications

    Additionally, we provide two Web-based applications, SWEETSOWER supporting the annotation of Web APIs and WSDLs based on MicroWSMO and WSMO-Lite respectively, which directly provide the means for publishing the annotations in iServe.

    iServe Architecture