[ 
https://issues.apache.org/jira/browse/STANBOL-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222702#comment-13222702
 ] 

Rupert Westenthaler commented on STANBOL-268:
---------------------------------------------

EnhancementChains (see STANBOL-431, and [1]) do solve the principle problem of 
allowing different enhancement configurations as described here. 

However Enhancement-Workflows defined by using enterporise-integration-patterns 
are not covered by the current EnhancementChains.

I see strong evidence that one needs both

* Enhancement-Chains as something that helps to configure the Stanbol Enhancer 
(semantic lifting layer) - different semantic lifting workflows
* Enhancement-workflows as something that integrates semantic lifting with the 
business layer - esases the integration of semantic lifting with the enterprise.

So my proposal would be to further work on Enhancement-Workfows as integration 
pattern of Apache Stanbol with the entierpise.

WDYT
Rupert

[1] http://incubator.apache.org/stanbol/docs/trunk/enhancer/chains/
                
> Configurable processing chains for enhancement
> ----------------------------------------------
>
>                 Key: STANBOL-268
>                 URL: https://issues.apache.org/jira/browse/STANBOL-268
>             Project: Stanbol
>          Issue Type: New Feature
>          Components: Enhancer
>            Reporter: Florent ANDRE
>
> Depending on the application client need, a same Stanbol instance could 
> provide different processing chain.
> At least, two types of processing chain could be useful :
> - The first one - fast - with just one or two "essentials" engines, provide 
> entities to the users in (near) "real time"
> - The second one - slower -with a lot of engines, provided a detailed 
> analysis, and computations that help for classification, summary, detailed 
> enhancements, etc... and are displayed to the user later or when reopen 
> document.
> Another types of chains can be useful depending on the type or the source of 
> document (e.g. engine A is not useful for mail and picture, but relevant for 
> scientific paper)
> Depending on the chain configuration, the endpoint could be sync or Async 
> (see STANBOL-263), in a push or pull mode.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to