Main changes

• The arbitrary number of module can be configured.
• The sequence of modules executed can be configured.
• A KB address can be configured with a tuple of KB address and graph IRI.
• Example: https://sites.google.com/site/okbqa4/development/documentation/controller?pli=1

• Every output of each module is co-printed with its input.
• Each log of each module is printed with sorting.
• Processing times of each module are noticed.
• Exception messages are simplified.
• Example: https://sites.google.com/site/okbqa4/development/documentation/controller?pli=1

• The controller is changed so that the web interface can receive and print log messages and result of the controller asynchronously via the mysql database located in the okbqa server.
• If you do not specify the "sync" field on the "conf" field of the input json, the controller will return immediately with "rid" value, which is the record ID of a controller's log messages and result written asynchronously on the mysql database.
• If you specify the "sync" field as "on" value (see the sample input below), the controller will operate in the previous manner that returns log messages and results for an input json, synchronously.

Limitations

• There are a lot of SPARQL queries produced, which causes the entire processing time of the pipeline.
• One of solutions can be to filter out the queries with scores under a threshold.
• To do so, a controller should be able to deal with module-scores properly.