[jira] [Resolved] (STANBOL-488) EnhancementProperties

["Rupert Westenthaler (JIRA)" <ji...@apache.org>]

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

Rupert Westenthaler resolved STANBOL-488.
-----------------------------------------

    Resolution: Fixed

Implemented as documented in [1] with

* 0.12 http://svn.apache.org/r1594134
* trunk http://svn.apache.org/r1594140
* Documentation: http://svn.apache.org/r1597033

[1] http://stanbol.apache.org/docs/trunk/components/enhancer/enhancementproperties

> EnhancementProperties
> ---------------------
>
>                 Key: STANBOL-488
>                 URL: https://issues.apache.org/jira/browse/STANBOL-488
>             Project: Stanbol
>          Issue Type: New Feature
>          Components: Enhancer
>    Affects Versions: 1.0.0
>            Reporter: Rupert Westenthaler
>            Assignee: Rupert Westenthaler
>             Fix For: 1.0.0, 0.12.1
>
>
> Enhancement Properties aim to provide Chain and Request scoped configurations to EnhancementEngines. 
> __IMPORTANT NOTE:__ The original discussion of this issue included API changes. Those where moved to STANBOL-1336 (part of the Stanbol Enhancer API 2.0 - STANBOL-1326). That means EnhancementProperties can be released in `0.12.1` and `1.0.0` without incompatible API changes to the Enhancement Engines interface.
> Expected use ages include:
> * parse through of user names and passwords for EnhancementEngines that depend on external services. This will allow such engines to use the user account of the the one parsing the request (request scope) or the one configuring the chain (chain configuration scope)
> * parse request specific constraints (e.g. the minimum confidence level for Enhancements). The acceptable confidence might depend on the actual context of the client application (e.g. if the user will review results or not)
> * configure dereferencing on a request bases (e.g. depending on the requirements of the UI showing the enhancement results)
> * reduce the number of configured engine instances (e.g. when specifying the minimum required confidence level for a chain or on request level one would only need a single instance of a confidence-level-filter-engine; The same would be true for dbpedia-linking engines with a different amount of suggested results) 
> * mapping of HTTP header fields to enhancement properties (e.g. for using the "Content-Language" header for specifying the language of the content)
> NOTES:
> * For the documentation see the comment with the heading 'Enhancement Properties' 
> * This is not the initial description of this issue. This is important as the first 5 comments do refer to the old description. You can still read the old version by looking at the history of this issue. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)