[
https://issues.apache.org/jira/browse/STANBOL-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197790#comment-13197790
]
Rupert Westenthaler commented on STANBOL-431:
---------------------------------------------
Update based on additions up to revision #1239097:
* added Web View for for
* /enhancer/chain (root resource providing infos for all running chains)
* /enhancer/engine (root resource providing infos for all running engines)
* /enhancer/engine/<engine>
* Integration tests for enhancement Chains
* the preconfigured language chain is tests as part of the integration tests
* added enhancement metadata to the ContentItem (see sub-task STANBOL-475)
Missing:
(A) RESTful interface for
* /enhancer/chain (root resource providing infos for all running chains)
* /enhancer/engine (root resource providing infos for all running engines)
This will require
1) to define an Ontology that allows to formally describe EnhancementEngine
and EnhancementChains
2) while creating this information the components need to know the
publicBaseUri. Therefore we need some way to share this information managed by
the Enhancer Jersey Module with the modules providing the EnhancementEngine and
Chain implementations.
(B) RESTful interface for
* /enhancer/engine/<engine> (resource allowing to sent requests to single
engines)
This depends mainly on the implementation of the RESTful interface for
multi-part content items, because sending an enhancement request to an engine
without also providing existing metadata does not make sense for most of the
enhancement engines
> 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
