#5 Declare Hooks for Web Service Execution

[Bart Lamiroy]

Currently the generic web service declaration and execution architecture is very straightforward (and rigid) : the plarform retrieves input and output parameter declarations, registers the input parameters in the database, calls the associated web service (which is completely unaware of the DAE provenance data model) and then retrieves the results and stores them back in the database.

One can image much finer and interesting pre- and post-processing hooks that are specific to the algorithm run. E.g. 'ocrad' layout ouput can be parsed and injected into the database as page_elements. The same holds for the OCR transcriptions of OCR engines, which are currently stored as files and not as page_element_property_values, as they should.