W3C home > Mailing lists > Public > public-owl-dev@w3.org > October to December 2006

Re: OWL "Sydney Syntax", structured english

From: Kaarel Kaljurand <kaljurand@gmail.com>
Date: Thu, 30 Nov 2006 21:02:25 +0100
Message-ID: <161f6fb70611301202k573258b7o96b14791560c4225@mail.gmail.com>
To: "Dan Connolly" <connolly@w3.org>
Cc: "John McClure" <jmcclure@hypergrove.com>, "Pat Hayes" <phayes@ihmc.us>, "Anne Cregan" <annec@cse.unsw.edu.au>, public-owl-dev@w3.org


On 11/30/06, Dan Connolly <connolly@w3.org> wrote:
> On Thu, 2006-11-30 at 19:54 +0100, Kaarel Kaljurand wrote:
> >
> > That would be an easy change, but I think the round-trip requirement
> > is really important. It enables the "view source" effect, i.e. one can view
> > the OWL file in ACE, do some modifications (in ACE) and publish it
> > again (in OWL).
> > Knowing the details of ACE wouldn't be needed in many cases.
> Yes, that's a good point; I didn't happen to see tools that go the
> other way. I'm interested in any pointers.

The ACE->OWL direction is integrated into the ACE parser which can be
used as a REST-webservice. E.g. to get the OWL RDF/XML of an ACE
sentence "John likes everybody who owns a car." just click on:


The webservice is documented here:


The ACE->OWL direction is documented here:


There are limitations, it's work in progress.

I'll create a Protege plugin (that integrates both directions)
once I've figured out how the Protege API works.

Received on Thursday, 30 November 2006 20:02:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:58:14 UTC