You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Florent ANDRE (JIRA)" <ji...@apache.org> on 2013/03/28 18:25:15 UTC

[jira] [Resolved] (STANBOL-268) Configurable processing chains for enhancement

     [ https://issues.apache.org/jira/browse/STANBOL-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Florent ANDRE resolved STANBOL-268.
-----------------------------------

    Resolution: Fixed

Solve this issue as #STANBOL-1008 is more focused on "Enhancements Workflow"
                
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira