1 / 13

Contents

Contents. Motivation Functional Requirements Architecture Overview WSMO API Eclipse based WSMO Studio Runtime and Plugins Implementation. Limitations of existing ontology editors Prototyping with Protègè 2000 has shown conceptual and interface design limitations

carson-hart
Download Presentation

Contents

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Contents • Motivation • Functional Requirements • Architecture • Overview • WSMO API • Eclipse based WSMO Studio Runtime and Plugins • Implementation WIW 04 - Architecture and Design of an Ontology and Web Service Modelling Studio

  2. Limitations of existing ontology editors Prototyping with Protègè 2000 has shown conceptual and interface design limitations Need for an extendable component based WSMO editor within different research projects Release of Eclipse 3.0 as ideal platform for devoloping component based IDEs Motivation WIW 04 - Architecture and Design of an Ontology and Web Service Modelling Studio

  3. Functional Requirements • A WSMO Studio needs to handle Ontologies, Goals, Mediators and Web Services • For all WSMO elements it is required to edit complex logical formulas • Compatibility with existing formalisms such as RDF and OWL • Extensibility to adopt WSMO Studio for different research projects • Reusability of components by other programs • Usability and tool support • Integration of Reasoning Support WIW 04 - Architecture and Design of an Ontology and Web Service Modelling Studio

  4. Functional Requirements:WSML Variants • WSML provides several variants with different logical expressivity that need to be handled by WSMO Studio: • WSML-Core: defined by the intersection of DL and Horn Logic • WSML-DL: extension of WSML-Core which captures the DL SHOIN(D) • WSML-Flight: extension of WSML-Core with several features of OWL Full • WSML-Rule: extension of WSML-core that supports Horn Logic • WSML-Full: unifies WSML-DL and WSML-Rule under FOL WIW 04 - Architecture and Design of an Ontology and Web Service Modelling Studio

  5. Architecture • The WSMO API and its reference implementation provides unified programmatic access to WSMO descriptions. An implementation of the Storage API will provide access to e.g. WSML files • Stand Alone Applications reuse the WSMO API, e.g. a Java Servlet that performs online validation/translation of WSML files. • WSMO Studio Runtime is an Eclipse based core plug-in without GUI elements that provides functionality to other WSMO Eclipse plug-ins, e.g. Ontology-plug-in WIW 04 - Architecture and Design of an Ontology and Web Service Modelling Studio

  6. WSMO API • WSMO API provides an interface that can have different actual implementations, reusable in various programs. • The API consists of two layers: • Representation API provides methods to query and modify the data model (including logical expressions), e.g. the interface Concept would have methods like getSuperConcepts()or addAttribute(Attribute)and the interface Instance would have methods like getAttributeValue(Attribute) or setAttributeValue(Attribute,AttributeValue) • Storage API provides a standardized way to load a model from and to export it to a data source • The API comes with a reference implementation and should be open source WIW 04 - Architecture and Design of an Ontology and Web Service Modelling Studio

  7. The Eclipse based WSMO Studio Runtime provides methods for calling the WSMO API provides ressource management via the API is a host plug-in that provide well defined extension points for Studio Plug-ins registers Studio plug-ins and manages inter plug-in communication Eclipse based Studio plug-ins plug into the WSMO Studio Runtime and provide WSMO based services, e.g. a WSML editor and browser, a validator, editor and reasoner for different logical expressions, a mapping tool between different ontologies or a WSMX plug-in The Runtime should be open source, the license for plug-ins can be choosen WSMO Studio Runtime and Studio Plug-ins WIW 04 - Architecture and Design of an Ontology and Web Service Modelling Studio

  8. Eclipse is a kind of universal tool platform – an extensible IDE for anything and nothing in particular with significant back up in industry and open source projects Eclipse is based on a well documented component model with well defined extension points. Some plug-ins (e.g. UML plug-in for WSMO visualisation) may be reusable Eclipse allows the implementation of more professional user interfaces than Swing via SWT based native platform look and feel but on the other hand existing Swing based components can hardly be reused Eclipse has a fast growing user community and backup from other projects (DIP) The initial effort for learning and implementing Eclipse plug-ins is higher than with stand-alone custom development Eclipse for WSMO Studio WIW 04 - Architecture and Design of an Ontology and Web Service Modelling Studio

  9. Eclipse based Implementation • Eclipse itself is constructed out of a set of plug-ins, e.g. the workbench provides functionality for a "project explorer" • WSMO runtime is envisioned as Workbench Core plug-in that defines extension points, registers plug-ins and provides access to the in memory model via WSMO API • Plug-ins such as an ontology editor should be based onto the WSMO runtime plug-in that provides access to the WSMO model. Additionally the plug-ins can directly use functionality provided by the platform such as the Help System WIW 04 - Architecture and Design of an Ontology and Web Service Modelling Studio

  10. WSML Text Editor for Eclipse Prototype of a WSML text editor with syntax highlighting based on an Eclipse Multipage Editor Plugin WIW 04 - Architecture and Design of an Ontology and Web Service Modelling Studio

  11. Achieve common agreement on WSMO API Implementation of importer/exporter for WSML Implementation of an Eclipse based WSMO Runtime Implementation of a WSML editing and browsing tool Implementation of a standalone application based on WSMO API (validation/transformation servlet) Future plans WIW 04 - Architecture and Design of an Ontology and Web Service Modelling Studio

  12. </studio> <q&a> WIW 04 - Architecture and Design of an Ontology and Web Service Modelling Studio

More Related