Re: Deploying an OWL ontology via an Web Services interface

Rob --

You may be interested in the Internet Business Logic system for this.  It's 
live, online at www.reengineeringllc.com .   The author- and user-interface 
is a browser.

Several people can point their browsers to one ontology, and cooperatively 
edit it (with locking).  If one person has the ontology locked for changes, 
others can run, the prior unchanged version.

The notation is closer to English than OWL, supported by a heavyweight 
inference engine.

Your points 1-5 below are supported, though 4 might need a bit more work.

A good example to start with is RDFQueryLangComparison1 .

HTH.  Thanks in advance for comments.          -- Adrian



                                            INTERNET BUSINESS LOGIC

                                              www.reengineeringllc.com

Dr. Adrian Walker
Reengineering LLC
PO Box 1412
Bristol
CT 06011-1412 USA

Phone: USA 860 583 9677
Cell:    USA  860 830 2085
Fax:    USA  860 314 1029






At 09:11 AM 5/10/04 +1000, you wrote:

>Hi
>
>Apologies if there is an obvious answer to this, but I havent been able to 
>locate it via browsing, searching or asking yet: is there a working group, 
>standard, best practice or even published proprietary API for deploying an 
>ontology via Web Services.
>
>I am interested in the case of a community managed ontology, where working 
>groups can be delegated to maintain parts of the ontology, all via a 
>single web accessible repository. Applications would be able to search 
>this repository as required.
>
>I would like the ability to:
>1) insert, update or delete classes
>2) find references that directly depend on a class
>3) query
>4) ideally, insert an entire OWL ontology including relationships to 
>pre-existing classes...
>5) ... which implies having a stable URI to reference items within the 
>deployed ontology in the first place
>
>Maybe there is no API that makes sense, and its always only possible to 
>think about publishing a single file, and using xlink to try to glue it 
>all together - in which case there should be some serious thought 
>somewhere about the query mechanisms you would use to perform typical 
>ontology traversals. I'd be happy with a registry-friendly model where the 
>transactions can be defined to be honest.
>
>Can anyone point me to where such deployment issues are being worked out?
>
>Regards
>Rob Atkinson

Received on Monday, 10 May 2004 07:32:27 UTC