|Last release:||2.0 (2008/03/05)|
IkeWiki is a Java-based semantic wiki engine.
Development of IkeWiki has stopped. The developers are now working on a successor: KiWi.
- 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.. 
- Sebastian Schaffert, Andreas Gruber, and Rupert Westenthaler : A Semantic Wiki for Collaborative Knowledge Formation . In: Semantics 2005, Vienna, Austria. November 2005. 
 Main wiki characteristics
Is the wiki web-based or a (standalone) desktop application?
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?
- GNU General Public License
What programming language is it written in?
- Java (Server Pages, Tomcat, Jena)
What status is the project in? (project maturity)
What is the estimated size of the developer community?
- currently around 2 contributing with code and 5 contributing with ideas
What is the estimated size of the installation base?
- currently around 6 installations (mainly developers)
 Standard wiki features
 User Features
- Editing: standard features plus some AJAX features, editing of resource and link types, editing of metadata annotations, WYSIWIG editor, 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
Are semantics (triples/whatever) separated from or included in the wiki markup?
- separated (Wiki links can be made "explicit")
Is the end user supported when formalizing content/adding annotations in some way? autocompletion/proposal generation/schema or consistency checking
- yes; applicable types for links and metadata fields are determined based on the resource types and context
- support for ontology editing by properly visualising classes, properties, ...
- suggestions of the system based on text analysis (e.g. text2onto)
What representation language is used? (RDF/OWL/...)
- RDF and OWL
Is there versioning support for the formalized content?
- no, but planned
Is there provenance (Herkunft) support for the formalized content? (get formalized contents/triples tagged with its author?)
What things can get formalized?
- resource types, links, metadata
Is there support for typing pages/category system/page tagging?
Is there support for typing links?
What ontology support does the wiki provide?
- currently OWL-RDFS; OWL-DL is technically possible but too slow in practice
Is there support for loading/saving ontologies?
- yes, import and export functionality for arbitrary RDF data
Can ontologies be created/changed from within the wiki?
- yes, some support for ontology editing is available (creating classes, properties, display of additional information for resources that are classes or properties)
Is there any reasoning support?
- yes, OWL-RDFS (see above)
Is the instance data required to comply with the ontologies?
How can semantic information be exploited?
- navigation, page rendering, planned: searching
Is there simple querying support? (search for all triples with a certain subject, predicate, object)
- planned, SPARQL would be easy but is not convenient for users
Is there advanced querying support? (free, complex queries) Is there any real user interface for expressing advanced queries?
- see above
Is there any special visualization?
- each ontology can be associated with almost arbitrary visualisations; examples included for a biology ontology and for RDFS/OWL itself
Is there any way to render pages from formalized content?
- by using Wiklets, almost any content can be generated from formalized content