Download

The source code for the OWL-S Editor is distributed under the Mozilla Public License version 1.1.

Installation instructions


Here's how to get your hands on the OWL-S Editor.
First, make sure these software are installed:
  1. Protege. Get it here, and make sure to get the most recent release of the 3.1 beta version. Download the Full version and make sure to install the "OWL backend" plugin.
  2. GraphViz. Get it here.

Then, go to our file archive, download the most recent release, and unzip it into your Protege plugins directory.

To enable the OWL-S Editor in Protege, go to Project->Configure, and check the box for "Owlstab". You can now load, edit and create OWL-S services in the OWL-S Editor tab. You may want to read some of the documentaion first (in the documentation section of this site).

Instructions for Developers


The source code for the OWL-S Editor is available from CVS for developers and other curious people to peruse. If you want to develop for the OWL-S Editor using Eclipse, there are instructions for setting that up further down this page.

These are the steps necessary to download, compile, and install the source:

  1. First, in addition to the above, you will need these programs:
    1. Java SDK. We use 1.4.2, as earlier version are deprecated. Get it from Sun and set up your PATH and JAVA_HOME appropriately.
    2. CVS. If you are runnig Linux, you probably already have this installed. Otherwise, find the appropriate package for your distribution and install it.
      For windows, either install Cygwin and use the version that comes with that, or download the latest version from here.
    3. SSH. Same again for Linux users. For windows, we recommend PuTTY. Again, make sure it's in your PATH.
    4. Ant. Get the latest binary download here and make sure it's in your PATH.
  2. Next, to get the code using anonymous CVS (this will not let you commit changes):

    cvs -d:pserver:anonymous@projects.semwebcentral.org:/var/cvs/owlseditor login

    (when prompted for a password, just press Enter)
    Then do:

    cvs -z3 -d:pserver:anonymous@projects.semwebcentral.org:/var/cvs/owlseditor co -P owlseditor

    If you have a developer account, just do this instead:

    export CVS_RSH=the-ssh-program-you're using

    cvs -z3 -d:ext:developername@projects.semwebcentral.org:/var/cvs/owlseditor co -P owlseditor
  3. If your Protege directory is not C:\Program Files\Protege_3.0_beta, then you need to edit the build.xml script in the owlseditor directory. Search for this strind, and replace it with the directory where you have installed Protege.
  4. You should now be able to execute ant install in the main Protege directory.
    To try that it works, start Protege, create a new "OWL Files" project, and go to Project->Configure. You should be able to check "Owlstab" in the dialog box that pops up. You will then be asked to save and reload your project, after which the OWL-S Editor tab should appear.

Eclipse setup


If you want to use Eclipse for work on the OWL-S Editor, which I highly recommend, here are some instructions for that. There are quite a few steps to set it up, but it's a one time deal, and it will save loads of time later. If these instructions don't work for you, please tell me. I will see if I can simplify this process in the future. Maybe we should post some screenshots here also...

First, make sure you have Eclipse 3.0.1, which was recently released. If Eclipse gives an error when you try to start it, try starting it with:

./eclipse -vmargs -Dosgi.locking=none

Creating the project

1) In Eclipse, choose New->Project->CVS->Checkout Projects from CVS. Click Next.

2) For "host", enter: projects.semwebcentral.org
"repository path: /var/cvs/owlseditor
"user" and "password", are, of course, your user name and password for semwebcentral.
"connection type" should be: extssh
Click Next.

3) Enter "owlseditor" as the module name, and click Next.

4) Choose "Check out as a project configured using the New Project Wizard"
Hit Next.

5) Choose the HEAD branch, and hit Finish.

6) The New Project Wizard will now pop up again. This time choose "Java Project", and hit Next.

7) Choose "owlseditor" as the project name.
Make sure "create project in workspace" is selected, and change the second selection to "create separate source and output folders".
Hit Finish.
The files will now be downloaded from CVS. There will be a bunch of errors, because we haven't set up our classpath yet.

Next, we need to set up build and run settings.

Build settings

8) If you have not installed Protege in its default location (C:\Program Files\Protege_3.0_beta), you need to tell Eclipse where it is located. First, expand owlseditor in the "Package Explorer" to the left of the main Eclipse window. In the list of folders and files that comes up, find build.xml and double-click it. You will be able to edit this file in the middle part of the Eclipse window. Find a line, close to the top of the file, that says

<property name="protegedir" value="C:/Program Files/Protege_3.0_beta"/>

Change this directory to the one where you have installed Protege.

9) Right-click on owlseditor in the Package Explorer. Choose properties.

10) Go to Builders. Click New. Choose Ant Build, and click OK.

11) In the window that comes up, click "Browse workspace" under "Buildfile".
Select Owlseditor in the left panel, and "build.xml" in the right, and click ok.

12) Go to the "targets" tab, uncheck "core" and check "install" instead.

You may also want to give this ant builder a name in the field at the top.
Now we're finished here, so hit OK on this window.

13) Next, go to Java Build Path, then the "Libraries" tab.

14) Click "Add external jars", go to your protege dir, and select all the jar files there.

15) Do this once again, going to the plugins/edu.stanford.smi.protegex.owl directory under the main protege dir, and add all the jars from there.

16) And a third time, add the jars from plugins/edu.stanford.smi.protegex.standard_extensions.

17) Click "Add JARs" and add all the jar files under owlseditor/lib

How to build & install

If everything is set up correctly, you can now click Project->Clean... to build the OWL-S Editor and install it to your Protege directory.

Run settings

Now the run settings.

18) Right-click on owlseditor in the Package Explorer again, this time choosing Run->Run...

19) In the window that comes up, select Java Application, and click New.

20) Give this configuration a name, make sure the "project" field says "owlseditor", and enter
edu.stanford.smi.protege.Application
for Main class.

21) Next, go to the Arguments tab, unclick "Use default working directory", and enter your Protege directory in the "Working directory" text field.

22) If you have a lot of memory, you may want to add something like
-Xmx100M
in the "VM Arguments" field.

How to Run

If everything is now working, you can click on the green Run button, and Protege should start up. Create a new "OWL Files" project, and go to the Project->Configure menu in Protege, and click the checkbox for "Owlstab" in order to load the OWL-S Editor plugin.

How to work with CVS

Now, to commit your changes, or do a cvs update, etc, right-click on the file or package you want to do commit or update in the Package Explorer, choose Team, and use the various options there.

Emacs key bindings

One thing that a lot of people will want to do right away is to enable Emacs key bindings. Go to Window->Preferences->Workbench->Keys, and change from Default to Emacs in the "Active Configuration" combo box.