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

Rupert Westenthaler commented on STANBOL-303:
---------------------------------------------

Hi

The new KeywordLinkingEngine[1][2] should be a much better bases for this work. 
It already separates Tokenizing/NLP and EnttiyLookup from the matching process 
and as described in [2] it would be also possible to make the Label Matching as 
well as result processing plug-able. 

I think it would be even better to move the Tokenizing/NLP part to an own 
EnhancementEngine and store the results within the EnhancementStructure. 
because this would give us even more flexibility because multiple other Engines 
could use such results.

However I have decided against that - for now, because expressing Tokens, POS 
tags and Chunks as RDF triples and adding them to the metadata would most 
likely be much to inefficient.


[1] http://markmail.org/message/7dmjqxqafyehcnqr
[2] 
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to