WSMO Studio – an Integrated Service Environment for WSMO Marin Dimitrov OntoText Lab. / Sirma - PowerPoint PPT Presentation

slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
WSMO Studio – an Integrated Service Environment for WSMO Marin Dimitrov OntoText Lab. / Sirma PowerPoint Presentation
Download Presentation
WSMO Studio – an Integrated Service Environment for WSMO Marin Dimitrov OntoText Lab. / Sirma

play fullscreen
1 / 8
WSMO Studio – an Integrated Service Environment for WSMO Marin Dimitrov OntoText Lab. / Sirma
95 Views
Download Presentation
peers
Download Presentation

WSMO Studio – an Integrated Service Environment for WSMO Marin Dimitrov OntoText Lab. / Sirma

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. WSMO Studio – an Integrated Service Environment for WSMO Marin Dimitrov OntoText Lab. / Sirma WIW 2005, Innsbruck http://www.wsmostudio.org

  2. The need for ISE • Tool support is crucial for the adoption of a new technology • Provide easy to use GUI for various WSMO tasks • Working with ontologies • Creating WSMO descriptions: goals, services, mediators • Creating WSMO centric orchestration and choreography specifications • Import (export) from (to) various formats • Front-end for ontology and service repositotories • Front-end for runtime SWS environments (WSMX) • Link to existing WS landscape (WSDL, UDDI, BPEL, WS-Policy, ...) • Cover the different perspectives of the different users • Provide functionality in a way that maximizes users’ productivity (role-oriented development)

  3. Requirements • Modular design • Different users need to customise the functionality in a specific way • Easier to maintain (e.g. ship new versions and bugfixes) • More suitable for 3rd party contributions • Extensibility • SWS is an emerging domain • It is difficult to specify requirements and functionality affront • Tools need to evolve as the domain evolves

  4. Requirements (2) • Architecture based on open standards • Lowers the cost of adopting / integrating a tool • 3rd party extensions and improvements are more likely to occur • Flexible licensing • An Open Source licence improves the adoption rate • An OS licence may improve the quality of a tool • An OS licence should not collide with proprietary 3rd party extensions (by being too restrictive / viral)

  5. WSMO Studio • Goals • Provide an open architecture and implementation of Integrated Service Environment for WSMO • Java based implementation • Open Source core (LGPL) • 3rd party contributors are free to choose their respective licensing terms • Modular design • an Eclipse based plug-in architecture • Extensible • 3rd parties may contribute new functionality (plug-ins) • … or extend / modify existing functionality

  6. WSMO Studio (2) • Present status • Developed within EU funded DIP and InfraWebs projects • First stable release – 15 Jun • Limited functionality • Serve as a guideline for 3rd parties that would contribute plug-ins • Next releases will add new functionality • Development releases + sources already available

  7. WSMO Studio (3) • Architecture (initial set of plug-ins) • WSMO Studio runtime • Provides functionality common across all plug-ins • based on wsmo4j • Ontology plug-in • Ontology perspective • NOT intended to be a Yet Another Ontology Editor • WSMO plug-in • WSMO elements: goals, services, mediators • Repository plug-in • Front-end to ontology and service / goal repositories • Usage • Standalone application (customised) • Integrated into an existing Eclipse deployment

  8. More information… http://www.wsmostudio.org • sources • documentation • distribution • mail lists