1 / 12

NeOn Components for Ontology Sharing and Reuse

NeOn Components for Ontology Sharing and Reuse. Mathieu d’Aquin (and the NeOn Consortium) KMi, the Open Univeristy, UK m.daquin@open.ac.uk. The NeOn Project (briefly). Enabling applications exploiting the Semantic Web at large Dynamically retrieving the relevant semantic resources

evers
Download Presentation

NeOn Components for Ontology Sharing and Reuse

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. NeOn Components for Ontology Sharing and Reuse Mathieu d’Aquin (and the NeOn Consortium) KMi, the Open Univeristy, UK m.daquin@open.ac.uk

  2. The NeOn Project (briefly) • Enabling applications exploiting the Semantic Web at large • Dynamically retrieving the relevant semantic resources • Combining several, heterogeneous Ontologies • Challenges: • heterogeneity, large-scale semantics, metadata and ontology dynamics, distributed development, etc. • Key Outcomes: • the NeOn toolkit, a complete environment for ontology lifecycle management • reference architecture for semantic applications • methodological guidelines • community building • 3 case studies in 2 domains

  3. NeOn Architecture And associated plugins! ORS Review and rating Of ontology, ranking Alignment Server alignment storage, production, evaluation Oyster ontology metadata Management and registry Watson ontology search, exploration and querying

  4. The NeOn Toolkit • Reference implementation of the NeOn architecture • Support ontology engineering and management • Support for complete ontology lifecycle • Support for different languages (OWL, F-Logic) • Support for networked ontologies (modules, mappings) • Built on the Eclipse platform • Extensible architecture • Via Eclipse plugin mechanism • Via Web Services

  5. Oyster • The NeON ontology registry system • Allows ontology designer to share ontologies by describing their metadata and…. • … distribute them over a peer-to-peer network

  6. Watson • Watson is a Gateway to the Semantic Web • It collects (through web crawling), analyses, indexes and gives access to semantic information and ontologies on the Web • At first sight: a search engine for the Semantic Web • But focuses on providing high level services and APIs for application development

  7. And Also… • The Alignment server • Store and manage ontology alignments online • Retrieve and manipulate alignments • Evaluate alignments • Produce alignments with an extensible set of mathcing techniques • Based on the alignment API • TS-ORS • An Open Rating System for Ontologies • Allow users to review different properties of ontologies (e.g. reusability, coverage, etc.) • Allow users to express trust and distrust statements on reviews • Provide customized ontology ranking mechanisms based on collaborative evaluations

  8. APIs and GUIs for search, querying, exploration, etc. Open Rating System Alignment Server Watson Engine Cupboard Interface Putting things together… Ontology submissions Mapping submissions Ontology rating Trust statements Ontology metadata

  9. Cupboard Cupboard.open.ac.uk

  10. Metadata Summary Reviews

  11. Services and APIs For ontology applications developers, Cupboard provides services to find and explore hosted ontologies (Watson API), to retrieve metadata (Oyster P2P system), assess Ontologies (TS-ORS) and manipulate aligments (Alignment Server)

  12. Building a community of ontology developers • Nice developments and interfaces are not enough • How do we encourage people to share their ontologies through our systems? • How do we attract users to retrieve and reuse ontologies from our systems? • How do we obtain feedbacks from the community, obtain reviews and quality information on ontologies, encourage discussions within the community on ontology design, application reuse? • Elements of solution? • Provide infrastructure services to facilitate the exploitation of ontologies? • Provide Web 2.0 like features (reviews, forums, tagging, comments, etc.) • ?

More Related