Introduction

The core of WP11 is an existing wiki system AceWiki which is going to be developed into a multilingual controlled natural language wiki system within the MOLTO project.

Important links

The AceWiki homepage (http://attempto.ifi.uzh.ch/acewiki/) contains:

• demo wikis
• list of related publications
• further links

AceWiki development is hosted on GitHub (https://github.com/AceWiki/AceWiki)

• Contributions to the AceWiki codebase can be made via GitHub pull requests (see http://help.github.com/send-pull-requests/)
• Bugs can be reported via the AceWiki Issues list (https://github.com/AceWiki/AceWiki/issues)
• Documentation and brainstorming pages are on the AceWiki project wiki (https://github.com/AceWiki/AceWiki/wiki)

Tasks

• Task 11.1: Make the AceWiki design multilingual and implement a small AceWiki engine for multilingual GF grammars
• Task 11.2: General refactoring of the AceWiki code

Meetings

• 13 December 2011

To do

Phase 1

AceWiki side:

• Refactor AceWiki to support different implementations of predictive parsers (at the moment, AceWiki's chartparser is hardwired) [done: Tobias]
• Extract from the package "aceowl" everything that should be reused in GFAceWiki into a new package (mostly OWL-related stuff) [done: Tobias]
• Connect AceWiki to GF (via JPGF) [done: Tobias]
• Change the AceWiki architecture to support multilinguality [done: Tobias]
• Implement a simple AceWiki language engine for multilingual GF grammars (as an alternative to the current ACE-OWL engine) [done: Tobias]

GF side:

• Check the following three options of getting a multilingual OWL-capable ACE-implementation in GF (there might be more options):
  • Start with the official GF implementation of ACE [assigned: Kaarel], see: https://github.com/Attempto/ACE-in-GF
  • Start with Normunds' GF implementation of ACE [assigned: Kaarel] (discontinued), see: https://github.com/Kaljurand/AceWiki/tree/normunds/grammars/aceowl/normunds
  • Create a GF implementation based on (parts of) the AceWiki grammar
• Create a stable multilingual OWL-capable ACE-implementation in GF

Phase 2

• Implement support for adding/changing/deleting words
• Implement more languages
• Choose application domain(s) and build exemplary knowledge base
• Perform user studies

Releases

Release notes: https://raw.github.com/AceWiki/AceWiki/master/CHANGES.txt

• 2012-01-05: v0.5.2

Unsorted

AceWiki as a webservice

See also https://github.com/yuchangyuan/AceWiki

See also the thread starting with: https://lists.ifi.uzh.ch/pipermail/attempto/2011-December/000818.html

• There could be potentially multiple front-ends
  • the current front-end
  • an existing GF front-end
  • Emacs
  • Unix commandline
  • ACE View
  • native Android/iOS app
  • ...
• REST API
  • allows to easily push content (existing lexicon, existing ACE text) into the wiki
  • should support GET as much as possible
• Make AceWiki easily deployable on hosting providers such as Google App Engine
  • reasons: speed, reliability, etc.
  • for that to work, AceWiki should be completely in Java (i.e. no using of APELocal), i.e. ape.exe would still have to be on a different host (because it is in Prolog)
  • would reasoning performance profit in a major way?

AceWiki more configurable

• [done: Changyuan/Kaarel] Support APESocket and APEWebservice in addition to APELocal. Configuration at the XML file level. See also: http://attempto.ifi.uzh.ch/site/docs/java/ch/uzh/ifi/attempto/ape/ACEPar...