IkeWiki

IkeWiki is a Java-based semantic wiki engine.

Development of IkeWiki has stopped. The developers are now working on a successor: KiWi.

SWikiFeat:ClassModel:=none
 * Homepage:
 * Demo:

Publications

 * paper:=Sebastian Schaffert. IkeWiki: A Semantic Wiki for Collaborative Knowledge Management . In: 1st International Workshop on Semantic Technologies in Collaborative Applications STICA 06, Manchester, UK, June 2006..
 * paper:=Sebastian Schaffert, Andreas Gruber, and Rupert Westenthaler : A Semantic Wiki for Collaborative Knowledge Formation . In: Semantics 2005, Vienna, Austria. November 2005.
 * http://www.bibsonomy.org/bibtex/07804f9b281358a09d3103c983733a5c4

Main wiki characteristics
Is the wiki web-based or a (standalone) desktop application?
 * Web-based

What communities (type/size) is the wiki intended for?
 * primarily knowledge engineers and researchers, advanced users

Standard project info (align with sourceforge attributes)
What is the wiki engine's software license? What programming language is it written in? What status is the project in? (project maturity) What is the estimated size of the developer community? What is the estimated size of the installation base?
 * GNU General Public License
 * Java (Server Pages, Tomcat, Jena)
 * Prototype
 * currently around 2 contributing with code and 5 contributing with ideas
 * currently around 6 installations (mainly developers)

User Features

 * Editing: standard features plus some AJAX features, editing of resource and link types, editing of metadata annotations, WYSIWIG editor, has editing paradigm::wiki-syntax
 * Markup Syntax: Wikipedia style
 * Access Rights: flexible, extensive
 * Attachments: as separate resources
 * Versioning: Diff, Rollback (not for metadata)
 * Navigation Support: Wiki links, overview over incoming and outgoing RDF edges, context-dependent visualisations (e.g. generated taxonomy box, hierarchy). Also SVG based navigator!
 * Plugins: "Wiklets" and "Views" to enrich resource presentation based on the semantic context
 * Further Features: context visualisation


 * Developer Features
 * Backend: PostgreSQL database, Jena
 * Versioning 4 Devs: Subversion
 * XML-RPC Ready: no
 * Extensions Mechanism: Plugin

Formalization
Are semantics (triples/whatever) separated from or included in the wiki markup? Is the end user supported when formalizing content/adding annotations in some way? ''autocompletion/proposal generation/schema or consistency checking What representation language is used? (RDF/OWL/...) Is there versioning support for the formalized content? Is there provenance (Herkunft) support for the formalized content? (get formalized contents/triples tagged with its author?) What things can get formalized? Is there support for typing pages/category system/page tagging? Is there support for typing links? What ontology support does the wiki provide? Is there support for loading/saving ontologies? Can ontologies be created/changed from within the wiki? Is there any reasoning support? Is the instance data required to comply with the ontologies? How can semantic information be exploited? Is there simple querying support? (search for all triples with a certain subject, predicate, object) Is there advanced querying support? (free, complex queries) Is there any real user interface for expressing advanced queries? Is there any special visualization? Is there any way to render pages from formalized content?
 * separated (Wiki links can be made "explicit")
 * yes; applicable types for links and metadata fields are determined based on the resource types and context
 * planned:
 * support for ontology editing by properly visualising classes, properties, ...
 * suggestions of the system based on text analysis (e.g. text2onto)
 * RDF and OWL
 * no, but planned
 * no
 * resource types, links, metadata
 * yes
 * yes
 * currently OWL-RDFS; OWL-DL is technically possible but too slow in practice
 * yes, import and export functionality for arbitrary RDF data
 * yes, some support for ontology editing is available (creating classes, properties, display of additional information for resources that are classes or properties)
 * yes, OWL-RDFS (see above)
 * no
 * navigation, page rendering, planned: searching
 * planned, SPARQL would be easy but is not convenient for users
 * see above
 * each ontology can be associated with almost arbitrary visualisations; examples included for a biology ontology and for RDFS/OWL itself
 * by using Wiklets, almost any content can be generated from formalized content

__SHOWFACTBOX__