Collaborative Ontology Building with Wiki@nt
•Download as PPT, PDF•
2 likes•829 views
Wiki@nt is a collaborative ontology building tool that uses wiki technology. It allows multiple users to edit ontologies simultaneously. Wiki@nt supports modularity through ontology packages. It also handles inconsistencies between packages using defeasible reasoning. The tool has an underlying wiki engine for editing, with markup script to represent ontologies. It dynamically loads partial ontology models from wiki pages for memory management.
![Outline ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
Similar to Collaborative Ontology Building with Wiki@nt
Similar to Collaborative Ontology Building with Wiki@nt (20)
More from Jie Bao
More from Jie Bao (20)
Recently uploaded
Recently uploaded (20)
Collaborative Ontology Building with Wiki@nt
- 1. Collaborative Ontology Building with Wiki@nt Preliminary Report Jie Bao and Vasant Honavar Artificial Intelligence Research Laboratory Computer Science Department Iowa State University Ames IA USA 50010 {baojie,honavar}@cs.iastate.edu
- 6. Proposed Approach Wiki Engine for Collaborative Editing Underlying Language to support modularity and reconciliation Browser-based Editor Agent Community Dynamic loading of Partial Model Serialization
- 9. Interface
- 27. Backups
Editor's Notes
- My name it Jie Bao from Iowa State University, United States . I’m glad to have this opportunity to introduce wikiont, the Collaborative Ontology Building tool we have designed.
- The first question to many of our audience is that why bother to have a new ontology editing tool since there are already many of them? The answer is simple, those existing tools still have their own limitations. First of all, by its very nature, ontology construction is a collaborative process. It involves either direction cooperation … and indirect cooperation… Thus, the whole process of ontology building, or say knowledge modeling includes two important sub-processes The first subprocess is knowledge integration… The second subprocess is knowledge reconciliation… In another word, ontology construction is more a team work other than a personal work. However, existing ontology editors … Wikiont is our tentative solution to overcome such limitations.
- The name of Wiki@nt may look a little kind of weird. Let me have a little explanation. The first part of the name is ‘wiki’. I think most of you have used or heard of wiki. Wiki is a kind… The second part of wiki@nt actually is the sum of two words, ‘ont’ for ontology, and ‘ant’ for the little collaborative bug. So the name of Wiki@nt reveals that it is a col…
- May this small poem better explains the idea behind Wiki@nt…
- This is the overall architecture of [email_address] , the collaborative ontology building environment The heart of Wiki@nt is the wiki engine . A usual wiki engine supports a script language, the editing of such script language, translating from the script language to HTML, version control, page locking, page storage, navigation, and user management. In additional to those features, Wiki@nt engine also provide the translation between ontology and the script language, the composition and decomposition of ontology from/into small ‘packages’, improved transaction management, and memory management. Underlying Language used by Wiki@nt is based on an extension to OWL, with two additional constructors: O (partial order on axioms) and P (localized axioms in package). A web browser based user interface is provided, to enable users to edit the ontology on the fly. A RPC communication interface is also reserved for software agents. In general, all participants involved are called ‘agent’ and constitute an Agent Community Ontologies are saved in a set of wiki packages in the form of files or database. We use Jena to build in-memory ontology model only when it is needed, such as in query and reasoning. Usually only a partial model is dynamically loaded. The ontology could be imported from or exported to external ontology files, such as an OWL file.
- Now let’s briefly introduce the underlying language we used. Due to limited time, I will only introduce the very basic idea of the language. You can see the unabridged version of this paper to get details. They are the reference 4 and 5 in the reference list, as technique reports of ISU Computer science department. The first extension is ‘package’. Package aims to provide a mechanism for knowledge integration. Package is … A term is defined… The constructor of package is called P.
- Here is the summary of all constructors we used in Package-extended ontology language. Delta P is the domain of all packages. Delata I T is the domain of all names of classes, properties and instances.
- The second extension is ‘partial order’ over axioms. Partial order is aimed to provide a mechanism for knowledge reconciliation. Inconsistencies could arose when two or more packages are brought together. For example, we know dog is a carnivore animal and plant is disjoint from animal. We model this knowledge in module A. However, we also know a sick dog may sometimes eats grass, a kind of plant. This is modeled in module B. This two modules will be inconsistent without proper reconciliation. We use defeasible logic to extend OWL. This approach is proposed by Heymans on SHOW(D) DL. And the constructor is called O. A partial order is assigned on axioms….
- There is an example of ontology wirh P and O constructors. We have two packages. Package 1 tells us that Dog, Animal and eats are public terms in this package, Dog is a Carnivore and also a Pet. Carnivore is Animal that only eats Animal; billy is a Dog. Package 2 tells us that Plant is public in this package, Plant is disjoint to Animal in package 1. SickDog is a Dog and some of them may eat Plant. This two packages are inconsistent. However, if we define a partial order over axioms, such as 2d >(stronger) than 1g, the inconsistency could be resolved.
- With the new language in hand. We now try to use a wiki to edit the ontology. Some basic idea in designing Wiki@nt include: … .. (the three things)
- This is the web interface of Wiki@nt. You can access it from the given URL.
- The heart of Wiki@nt is the wiki engine. The wiki engine is an extension of standard wiki engine. It will … ..
- Ontologies in wiki@nt is represented in a script language.
- A ontology written is such script language are organized in this way.