Usage Guide

This is no longer in service.

Our pervious work on [1] presented a detailed requirements analysis and a specification
for an Integrated Service Environment (ISE) for WSMO1
. We outlined why certain nonfunctional
requirements such as role-oriented development, extensibility, adherence to
open standards, usability and flexible licensing are important and how they influence
the architecture of an ISE. We have also stressed the important role that robust and
easy-to-use end user tools play in the adoption of any technological innovation (such as
This document presents the first prototype of such an ISE, called WSMO Studio2
. The
Studio is a standalone, Eclipse3
based application that supplies the following
• Creating WSMO descriptions of ontologies, goals, web services and mediators
• Export and import of the WSMO descriptions
• Storing and retrieving WSML descriptions to/from remote service, goal,
mediator and ontology repositories
Future versions of this prototype will provide improvements of the existing
functionality as well as new functionality related to WSMO centric choreography and
orchestration, discovery and interaction with Semantic Web Services runtime
environments such as WSMX.
The target audience of this guide consists of:
• End users that will use WSMO Studio to work with WSMO service
descriptions. The sections that explain the user interface and the basic
functionality of WSMO Studio are intended for such readers.
• Solution providers that provide new functionality relevant to WSMO/WSMX
and that would like to integrate this functionality with WSMO Studio. These
readers should focus on the sections that contain technical details of the WSMO
Studio architecture and specifically the extension point definitions that make it
possible for new functionality to be dynamically integrated within the tool.
This document is structured as follows:
• Section 2 presents a short introduction to the GUI and the way to use its
functionality. This section is intended for the end-users of WSMO Studio that
will create semantic annotations for web services in a WSMO centric way. Related: WHY, SoWX, QgV, wWxrn, eJovmc, CEgpT, LIr, FEPvdL, wNlL, hnELkg, arcYZ, cfDyk, GwrfCb, zUC, bFObgc,