[jira] [Commented] (STANBOL-431) Improve Enhancer/ REST endpoint

["Florent ANDRE (Commented) (JIRA)" <ji...@apache.org>]

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

Florent ANDRE commented on STANBOL-431:
---------------------------------------

I like this new proposal !
Some comments :

/enhancer/engine/<engineId> :
<engineId> can be define with the class name for "simple" engine. 
But when the engine is created throw an osgi factory (like KeywordLinkingEngine) how we define this id ? (class name is not sufficient, "instance number" is not human compliant and change on restart, there is no property for this in the api).

/enhancer/chains/<chainId> 
Rupert's comment on STANBOL-371 suggest a possibility to have multiple "ChainManagers", so the endpoint should be :
/enhancer/chains/<chainManager>/<chainId> 

++
                
> Improve Enhancer/ REST endpoint
> -------------------------------
>
>                 Key: STANBOL-431
>                 URL: https://issues.apache.org/jira/browse/STANBOL-431
>             Project: Stanbol
>          Issue Type: Improvement
>          Components: Enhancer
>            Reporter: Florent ANDRE
>
> From STANBOL-414, Reto :
> Rest
> /enhancer
> /enhancer/engine/<engineId>
> /enhancer/chains/<chainId>
> - query params:
> Optional inputWithMetadata -> expects multipart/mime with 2 sections of which the first is rdf
> Optional outputWithContentParts[=<section-ordinal>] -> the result is multipart (instead of rdf) containing rdf as the first section and the parts in the second section, if there is more than one part this second section is itself multipart, this argument might be repated to have different sections
> Optional omitMetada -> no metadate in the result, makes only sense with outputContentParts argument, the result will correspond to the second section of the malipart returned without this argument 

--
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