[jira] [Resolved] (STANBOL-1280) EnhancementProperties for 0.12

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

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

Rupert Westenthaler resolved STANBOL-1280.
------------------------------------------

    Resolution: Not a Problem

With the redefinition of STANBOL-488 to exclude changes that do require API changes (moved to STANBOL-1336) support for EnhancementProperties will be the same for 0.12.1 and 1.0.0.

The description of STANBOL-488 was adapted accordingly and now includes some restrictions stated by this issue.

> EnhancementProperties for 0.12
> ------------------------------
>
>                 Key: STANBOL-1280
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1280
>             Project: Stanbol
>          Issue Type: Sub-task
>          Components: Enhancer
>            Reporter: Rupert Westenthaler
>            Assignee: Rupert Westenthaler
>             Fix For: 0.12.1
>
>
> This issue has the goal to provide (a possible feature reduced version) of EnhancementProperties to 0.12.+ versions of Apache Stanbol.
> Basic Idea is:
> * support parsing EnhancementProperties as QueryParameters in EnhancementRequests (as defined by STANBOL-488)
> * No support for defining EnhancementProperties for EnhancementChains
> * Instead of changing the API of EnhancementEngine parse EnhancementProperties as ContentPart in the ContentItem
>     * provide a Utility method that retrieves EnhancementProperties from that ContentPart to the EnhancementEngine.
> This will not only make this feature available to Stanbol 0.12.0 users but also make it much easier to back port EnhancementEngines that do use that feature.
> Required Code Changes are minimal
> * extend the ContentItemReader to parse Request Parameter
> * define a URI constant to be used for the ContentPart
> * add an Helper method ti the ContentItemHelper that retrieved the EnhancementProperties from the ContentPart
> This will be introduced after 0.12.0 is released



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