You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/05 23:53:57 UTC
[jira] [Resolved] (STANBOL-303) EntityFetch engine
[ https://issues.apache.org/jira/browse/STANBOL-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-303.
-----------------------------------------
Resolution: Fixed
see [1] for the documentation of the KeywordLinkingEngine (the new name of this engine)
[1] http://incubator.apache.org/stanbol/docs/trunk/enhancer/engines/keywordlinkingengine.html
> EntityFetch engine
> ------------------
>
> Key: STANBOL-303
> URL: https://issues.apache.org/jira/browse/STANBOL-303
> Project: Stanbol
> Issue Type: Improvement
> Components: Enhancer
> Reporter: Florent ANDRE
>
> Hi,
> I extracted "entity fetching" related code from taxonomylinking engine and create a new engine based on.
> I also make the query.addSelectedField() configurable by felix configuration.
> This engine is runnable in ServiceProperties.ORDERING_EXTRACTION_ENHANCEMENT position.
> I see 2 advantages of such an engine :
> 1) users can develop an extraction engine without think about entity retrieve
> 2) if this engine provide helpful lib, entity fetching will easily be embed into user's engine and limit code duplication for entity fetch.
> Could it be an interesting engine for trunk ?
> ++
--
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