|Author(s):||User:Michel_Buffa, User:Fabien Gandon, Adil El Ghali, Amira Tifous, Guillaume Ereteo, Gael Crova, Jeremy Passeron, Claire Lecomte|
SweetWiki (Semantic WEb Enabled Technology Wiki) is a semantic wiki based on the CORESE engine. The project started in September 2005. An experimentation server is available here: . We support WYSIWYG edition of pages and annotations, and use the CORESE engine and the SeWeSe Library for all the semantic operations : navigation, search, etc... the wiki itself is really written around CORESE and RDF stuff, it is not a "regular wiki" with some support for annotations. The project is really in active development.
 Main wiki characteristics
Is the wiki web-based or a (standalone) desktop application?
What communities (type/size) is the wiki intended for?
- Intranets, identified communities. CoPs. Sweetwiki is largely used in the context of the Palette project by many Communities of Practice.
Main editing paradigm:
 Standard project info (align with sourceforge attributes)
What is the wiki engine's software license?
- The wiki engine is ditributed under the the non viral open-source licence CeCILL-C.
What programming language is it written in?
- Java (Server Pages, Tomcat)
What status is the project in? (project maturity)
What is the estimated size of the developer community?
- Currently around 5 contributing with code and 4 contributing with ideas
What is the estimated size of the installation base?
- Currently arround 20 installations.
 Standard wiki features
- User Features
- Editing: WYSIWYG
- Markup Syntax: No support for markup syntax.
- Access Rights: None, use authentification is there but access right managements per page, per web is not implemented.
- Attachments' allowed?: Yes.
- Versioning: Currently being implementated. All is in there.
- Navigation Support: Backlinks, Categories, faceted navigation
- Tagging of pages: Yes, social tagging folksonomies (including folksonomy management/editing)
- Plugins: Yes, used as Jsp tags in the wiki pages, from withing the wysiwyg editor.
- Further Features:
- Developer Features (things relevant when you want to "tap" a wiki)
- Backend: File based
- Versioning 4 Devs:
- XML-RPC Ready: Not yet.
- Extension Mechanisms: Plugins
- Backend: File based
 User Features
- Editing: WYSIWIG editor with AJAX features like local links autocompletion, tags autocompletion, etc.
- Markup Syntax: None
- Access Rights: currently none, planned
- Attachments: as separate resources
- Versioning: partially implemented.
- Navigation Support: Wiki links, tags/categoy navigation based on metadata (faceted navigation in fact), faceted navigation can be parametrized.
- Plugins: plugins are java code Jsp tags that can be added in the wiki page from within the wysiwyg editor. Sweetwiki comes with a set of tags for embedding sparql quesries, displaying results from these queries, displaying or editing parts of ontologies/folksonomies, etc.
- Further Features:
- Developer Features
- Backend: Corese semantic engine
- Versioning 4 Devs: Subversion
- XML-RPC Ready: no
- Extensions Mechanism: Plugin
Are semantics (triples/whatever) separated from or included in the wiki markup?
- triples are included in every wiki page. Wiki pages are in XHTML or JSPX format, and metadata are embedded in the pages using the RDF/A syntax. Metadata is extracted at save time in RDF and sent to the CORESE engine.
Is the end user supported when formalizing content/adding annotations in some way? autocompletion/proposal generation/schema or consistency checking
- yes, autocompletion of local links, autocompletion of metadata.
- full support for ontology editing by properly visualising classes, properties, ... just add some jsp tags in wiki pages and the page will include powerful embedded web applications for ontology/folksonomy editing.
- planned: auto-extraction of tags/keywords from the page content
What representation language is used? (RDF/OWL/...)
- RDF/RDFS 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?
- yes, full support for social tagging/faceted navigation/search in a "social tagging way" building of the folksonomy in RDF/S on the fly.
Is there support for typing links?
- yes, autocompletion.
What ontology support does the wiki provide?
- currently OWL-RDFS;
Is there support for loading/saving ontologies?
- Hmmm, not directlry, but very easy to add.
Can ontologies be created/changed from within the wiki?
- yes, full 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, searching
Is there simple querying support? (search for all triples with a certain subject, predicate, object)
- SPARQL queries can be embedded in wikipages by adding some special tags (autocompletion on these tags syntax is planned)
Is there advanced querying support? (free, complex queries) Is there any real user interface for expressing advanced queries?
Is there any special visualization?
- RDFS/OWL ontologies can be displayed in many way (trees, tables, etc...)
Is there any way to render pages from formalized content?
- Michel Buffa, Fabien Gandon, Guillaume Ereteo, Peter Sander and Catherine Faron, SweetWiki: A semantic wiki, Special Issue of the Journal of Web Semantics on Semantic Web and Web 2.0, Volume 6, Issue 1, February 2008 , Edited by Mark Greaves and Peter Mika, Elsevier, Pages 84-97.