You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Fabian Christ (JIRA)" <ji...@apache.org> on 2012/12/12 21:10:20 UTC
[jira] [Updated] (STANBOL-807) WordLift Freeling engine
contribution
[ https://issues.apache.org/jira/browse/STANBOL-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabian Christ updated STANBOL-807:
----------------------------------
Component/s: (was: Enhancer)
> WordLift Freeling engine contribution
> -------------------------------------
>
> Key: STANBOL-807
> URL: https://issues.apache.org/jira/browse/STANBOL-807
> Project: Stanbol
> Issue Type: Wish
> Reporter: David Riccitelli
> Priority: Minor
>
> Some time ago at the Leipzig Semantic Day we presented some engines:
> - Freeling Language Identifier engine, an engine which identifies the languages along with their ranks,
> - Freeling PoS Tagging engine, an engine which performs PoS tagging analysis, for supported languages see [1]
> - Freebase Entity Recognition engine, an engine which performs entity recognition using Freebase (and loads properties using a specified referenced site, e.g. DBpedia)
> - TextAnnotations New Model engine, an engine which adds the new TextAnnotations data as specified here [2]
> - Schema.org Refactorer engine, an engine which rewrites the output graphs by using the official DBpedia mappings and custom provided rules
> There is also a draft Web module that allows a client to post an analysis Job an receive the results as a callback to a provided URL.
> The Freeling engines are based on Freeling [3] and require it to be installed on the local server to work (they use native extensions).
> The full source code and instructions on how to install and configure the engines and the required dependencies are published here:
> https://github.com/insideout10/wordlift-stanbol
> Is it feasible to integrate the above into Apache Stanbol mainstream?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira