You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by bu...@apache.org on 2012/11/23 18:04:19 UTC

svn commit: r839337 - in /websites/staging/stanbol/trunk/content: ./ docs/trunk/components/enhancer/engines/list.html

Author: buildbot
Date: Fri Nov 23 17:04:18 2012
New Revision: 839337

Log:
Staging update by buildbot for stanbol

Modified:
    websites/staging/stanbol/trunk/content/   (props changed)
    websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/list.html

Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Nov 23 17:04:18 2012
@@ -1 +1 @@
-1412971
+1412977

Modified: websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/list.html
==============================================================================
--- websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/list.html (original)
+++ websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/engines/list.html Fri Nov 23 17:04:18 2012
@@ -90,7 +90,7 @@
 <h2 id="preprocessing">Preprocessing</h2>
 <ul>
 <li>
-<p><strong><a href="tikaengine.html">Tika Engine</a></strong> (based on <a href="http://tika.apache.org/">Apache Tika</a>)</p>
+<p><strong><a href="tikaengine">Tika Engine</a>:</strong> (based on <a href="http://tika.apache.org/">Apache Tika</a>)</p>
 <ul>
 <li>content type detection</li>
 <li>text extraction from various document formats</li>
@@ -98,7 +98,7 @@
 </ul>
 </li>
 <li>
-<p><strong><a href="metaxaengine.html">Metaxa Engine</a></strong></p>
+<p><strong><a href="metaxaengine">Metaxa Engine</a>:</strong></p>
 <ul>
 <li>text extraction from various document formats</li>
 <li>extraction of metadata from document formats</li>
@@ -112,13 +112,13 @@
 <p>Language detection engines add Language annotations as defined by <a href="https://issues.apache.org/jira/browse/STANBOL-613">STANBOL-613</a> to the metadata of the <a href="../contentitem">ContentItem</a></p>
 <ul>
 <li>
-<p><strong><a href="langidengine.html">Language Identification Engine</a></strong></p>
+<p><strong><a href="langidengine">Language Identification Engine</a>:</strong></p>
 <ul>
 <li>language detection for textual content utilizing <a href="http://tika.apache.org/">Apache Tika</a></li>
 </ul>
 </li>
 <li>
-<p><strong><a href="langdetectengine.html">Language Detection Engine</a></strong></p>
+<p><strong><a href="langdetectengine">Language Detection Engine</a>:</strong></p>
 <ul>
 <li>language detection for textual content utilizing <a href="http://code.google.com/p/language-detection/">language-detection</a> Project</li>
 </ul>
@@ -133,7 +133,7 @@
 <h3 id="sentence-detection">Sentence Detection</h3>
 <p>Sentence detection engines add <em>Sentences</em> to the <a href="../nlp/analyzedtext">AnalyzedText</a> content part </p>
 <ul>
-<li>__<a href="opennlpsentence">OpenNLP Sentence Detection Engine</a><ul>
+<li><strong><a href="opennlpsentence">OpenNLP Sentence Detection Engine</a>:</strong><ul>
 <li>Sentence Detection based on <a href="http://opennlp.apache.org">OpenNLP</a></li>
 </ul>
 </li>
@@ -141,7 +141,7 @@
 <h3 id="tokenizer-engines">Tokenizer Engines</h3>
 <p>The responsibility of Tokenizer Engines is to add <em>Tokens</em> to the <a href="../nlp/analyzedtext">AnalyzedText</a> content part</p>
 <ul>
-<li>__<a href="opennlptoken">OpenNLP Tokenizer Detection Engine</a><ul>
+<li><strong><a href="opennlptoken">OpenNLP Tokenizer Detection Engine</a>:</strong><ul>
 <li>Tokenizer implementation based on <a href="http://opennlp.apache.org">OpenNLP</a></li>
 </ul>
 </li>
@@ -149,7 +149,7 @@
 <h3 id="part-of-speech-pos-tagging">Part of Speech (POS) Tagging</h3>
 <p>POS tagging engines do add <a href="../nlp/nlpannotations#part-of-speech-pos-annotations">Part-of-Speech annotations</a> to <em>Tokens</em> present in the <a href="../nlp/analyzedtext">AnalyzedText</a> content part</p>
 <ul>
-<li>__<a href="opennlppos">OpenNLP POS Tagging Engine</a><ul>
+<li><strong><a href="opennlppos">OpenNLP POS Tagging Engine</a>:</strong><ul>
 <li>POS tagger implementation based on <a href="http://opennlp.apache.org">OpenNLP</a></li>
 </ul>
 </li>
@@ -157,7 +157,7 @@
 <h3 id="chunkphrase-detection">Chunk/Phrase detection</h3>
 <p>Chunker (or Phrase Detection) Engines do add detected <em>Chunks</em> to the <a href="../nlp/analyzedtext">AnalyzedText</a> content part. They also annotate added <em>Chunks</em> with the <a href="../nlp/nlpannotations#phrase-annotations">type of the detected phrase</a></p>
 <ul>
-<li>__<a href="opennlpchunker">OpenNLP Chunker Engine</a><ul>
+<li><strong><a href="opennlpchunker">OpenNLP Chunker Engine</a>:</strong><ul>
 <li>Chunker implementation based on <a href="http://opennlp.apache.org">OpenNLP</a></li>
 </ul>
 </li>
@@ -166,7 +166,7 @@
 <p>NER engines need to write detected Named Entities as '<a href="../enhancementstructure.html#fisetextannotation">fise:TextAnnotation</a>'s to the metadata of the <a href="../contentitem">ContentItem</a>. In addition they may also add <a href="../nlp/nlpannotations#name-entity-ner-annotations">NER annotations</a> to <em>Chunks</em> in the <a href="../nlp/analyzedtext">AnalyzedText</a> content part</p>
 <ul>
 <li>
-<p><strong><a href="opennlpner">OpenNLP NER Engine</a></strong> </p>
+<p><strong><a href="opennlpner">OpenNLP NER Engine</a>:</strong> </p>
 <ul>
 <li>NLP processing using OpenNLP NER</li>
 <li>detects occurrences of persons, places and organizations only</li>
@@ -174,7 +174,7 @@
 </ul>
 </li>
 <li>
-<p><strong><a href="customnermodelengine.html">Custom NER Model Extraction Enhancement Engine</a></strong> </p>
+<p><strong><a href="customnermodelengine.html">Custom NER Model Extraction Enhancement Engine</a>:</strong> </p>
 <ul>
 <li>NLP processing using OpenNLP NER</li>
 <li>uses custom NameFinder models (user configured)</li>
@@ -182,14 +182,14 @@
 </ul>
 </li>
 <li>
-<p><strong>CELI NER engine</strong>: This engine is part of the CELI enhancement engines (see <a href="https://issues.apache.org/jira/browse/STANBOL-583">STANBOL-583</a>)</p>
+<p><strong>CELI NER engine:</strong> This engine is part of the CELI enhancement engines (see <a href="https://issues.apache.org/jira/browse/STANBOL-583">STANBOL-583</a>)</p>
 <ul>
 <li>NER based on a linguagrid.org server hosted by CELI</li>
 <li>detects occurrences of persons, places and organizations and some other types</li>
 </ul>
 </li>
 <li>
-<p><strong><a href="opencalaisengine.html">OpenCalais Enhancement Engine</a></strong></p>
+<p><strong><a href="opencalaisengine">OpenCalais Enhancement Engine</a>:</strong></p>
 <ul>
 <li>integrates service from Open Calais. (Note: You need to provide a key in order to use this engine)</li>
 <li>can be configured to do only NER and no EntityLinking</li>
@@ -199,7 +199,7 @@
 <h3 id="morphological-analysis">Morphological Analysis</h3>
 <p>This includes Engines that perform some sort of morphological analyses (e.g. lemmatization)</p>
 <ul>
-<li>__CELI AnalyzedText Lemmatizer Engine: This engine is part of the CELI enhancement engines (see <a href="https://issues.apache.org/jira/browse/STANBOL-583">STANBOL-583</a> and <a href="https://issues.apache.org/jira/browse/STANBOL-739">STANBOL-739</a>)<ul>
+<li><strong>CELI AnalyzedText Lemmatizer Engine:</strong> This engine is part of the CELI enhancement engines (see <a href="https://issues.apache.org/jira/browse/STANBOL-583">STANBOL-583</a> and <a href="https://issues.apache.org/jira/browse/STANBOL-739">STANBOL-739</a>)<ul>
 <li>lemmatization support for "it", "da", "de", "ru", "ro"</li>
 </ul>
 </li>
@@ -208,13 +208,13 @@
 <p>This category covers enhancement engines that suggest Entities for features present in the parsed content. An Entity is an uniquely identified resource. Typically it provides (or links to) further information such as the type, a description (text, pictures, videos …), spatial and/or temporal context, links to other entities … . </p>
 <ul>
 <li>
-<p><strong><a href="namedentitytaggingengine">Named Entity Linking Engine</a></strong></p>
+<p><strong><a href="namedentitytaggingengine">Named Entity Linking Engine</a>:</strong></p>
 <ul>
 <li>suggest links to several Linked Data Sources (e.g. DBpedia)</li>
 </ul>
 </li>
 <li>
-<p><strong><a href="entityhublinking">Entityhub Linking Engine</a></strong></p>
+<p><strong><a href="entityhublinking">Entityhub Linking Engine</a>:</strong></p>
 <ul>
 <li><a href="entity linking">EntityLinkingEngine</a> configuration for the Stanbol Entityhub</li>
 <li>consumes NLP processing results form the <a href="../nlp/analyzedtext">AnalyzedText</a> content part</li>
@@ -223,14 +223,14 @@
 </ul>
 </li>
 <li>
-<p><strong>DBpedia Spotlight Annotation Engine</strong>: Integration of the DBpedia Spotlight with the Stanbol Enhancer (see <a href="https://issues.apache.org/jira/browse/STANBOL-706">STANBOL-706</a>)</p>
+<p><strong>DBpedia Spotlight Annotation Engine:</strong> Integration of the DBpedia Spotlight with the Stanbol Enhancer (see <a href="https://issues.apache.org/jira/browse/STANBOL-706">STANBOL-706</a>)</p>
 <ul>
 <li>includes NLP, Entity Linking and Disambiguation of Entities using <a href="http://dbpedia.org">DBpedia</a> as knowledge base</li>
 <li>accesses a remote service</li>
 </ul>
 </li>
 <li>
-<p><strong><a href="geonamesengine">Geonames Enhancement Engine</a></strong> </p>
+<p><strong><a href="geonamesengine">Geonames Enhancement Engine</a>:</strong> </p>
 <ul>
 <li>suggests links to geonames.org</li>
 <li>provides hierarchical links for locations</li>
@@ -238,7 +238,7 @@
 </ul>
 </li>
 <li>
-<p><strong><a href="opencalaisengine">OpenCalais Enhancement Engine</a></strong></p>
+<p><strong><a href="opencalaisengine">OpenCalais Enhancement Engine</a>:</strong></p>
 <ul>
 <li>integrates service from Open Calais. (Note: You need to provide a key in order to use this engine)</li>
 <li>provides both NER and Entity Linking</li>
@@ -246,7 +246,7 @@
 </ul>
 </li>
 <li>
-<p><strong><a href="zemantaengine">Zemanta Enhancement Engine</a></strong></p>
+<p><strong><a href="zemantaengine">Zemanta Enhancement Engine</a>:</strong></p>
 <ul>
 <li>integrates the Zemanta services. (Note: You need to provide a key in order to use this engine)</li>
 <li>provides both NLP and Entity Linking</li>
@@ -254,7 +254,7 @@
 </ul>
 </li>
 <li>
-<p><em><a href="keywordlinkingengine">KeywordLinkingEngine</a></em> <strong>depreacted</strong> use <a href="entityhublinking">EntityhubLinkingEngine</a> instead!</p>
+<p><em><a href="keywordlinkingengine">KeywordLinkingEngine</a>:</em> <strong>depreacted</strong> use <a href="entityhublinking">EntityhubLinkingEngine</a> instead!</p>
 <ul>
 <li>NLP processing using OpenNLP</li>
 <li>supports multiple languages</li>
@@ -266,14 +266,14 @@
 <p>This includes Engines that perform word/chunk level sentiment classifications on the <a href="../nlp/analyzedtext">AnalyzedText</a> content part as well as Engines that summarize those lower level annotations to Sentiments for sentences, sections or the whole text. Sentiment summarizations are represented as 'fise:SentimentAnnotation's (TODO: not yet fully specified (see <a href="https://issues.apache.org/jira/browse/STANBOL-760">STANBOL-760</a>).</p>
 <ul>
 <li>
-<p><strong>Sentiment WordClassifier Engine</strong>: This engine annotates <em>Tokens</em> of the  <a href="../nlp/analyzedtext">AnalyzedText</a> content part with sentiment annotations (a double value in the range [-1..1]</p>
+<p><strong>Sentiment WordClassifier Engine:</strong> This engine annotates <em>Tokens</em> of the  <a href="../nlp/analyzedtext">AnalyzedText</a> content part with sentiment annotations (a double value in the range [-1..1]</p>
 <ul>
 <li>supports de and en</li>
 <li>can be extended to support additional languages by implementing the <em>SentimentClassifier</em> interface</li>
 </ul>
 </li>
 <li>
-<p><em>Sentiment Summarization Engine</em>: <strong>under development</strong> (see <a href="https://issues.apache.org/jira/browse/STANBOL-760">STANBOL-760</a>)</p>
+<p><em>Sentiment Summarization Engine:</em> <strong>under development</strong> (see <a href="https://issues.apache.org/jira/browse/STANBOL-760">STANBOL-760</a>)</p>
 <ul>
 <li>summarizes sentiments on word level to chunks, sentences and the whole text</li>
 <li>create 'fise:SentimentAnnotations'</li>
@@ -284,7 +284,7 @@
 <p>Enhancement Engines in this category can disambiguate Entities based on contextual information (e.g. if "Apple" in a sentence refers to the fruit or the company). Based on that such engines can adjust existing Entity suggestions or also create new one.</p>
 <ul>
 <li>
-<p><strong>DBpedia Spotlight Disambiguation Engine</strong>: (see <a href="https://issues.apache.org/jira/browse/STANBOL-706">STANBOL-706</a>)</p>
+<p><strong>DBpedia Spotlight Disambiguation Engine:</strong> (see <a href="https://issues.apache.org/jira/browse/STANBOL-706">STANBOL-706</a>)</p>
 <ul>
 <li>consumes existing fise:TextAnnotations and disambiguate them by using DBpedia Spotlight</li>
 <li>create Entity suggestions (fise:EntityAnnotations) for the processed fise:TextAnnotations</li>
@@ -292,7 +292,7 @@
 </ul>
 </li>
 <li>
-<p><em>Solr More-like-This Disambiguation Engine</em>: __under development_ (see <a href="https://issues.apache.org/jira/browse/STANBOL-723">STANBOL-723</a>)</p>
+<p><em>Solr More-like-This Disambiguation Engine:</em> __under development_ (see <a href="https://issues.apache.org/jira/browse/STANBOL-723">STANBOL-723</a>)</p>
 <ul>
 <li>disambiguates Entities managed by the Stanbol Entityhub by using Solr MLT queries</li>
 <li>only available via the <a href="http://svn.apache.org/repos/asf/stanbol/branches/disambiguation-engine/">disambiguation-engine</a> branch</li>
@@ -303,14 +303,14 @@
 <h2 id="postprocessing-other">Postprocessing / Other</h2>
 <ul>
 <li>
-<p><em>NLP 2 RDF Engine</em>: <strong>under development</strong> (see <a href="https://issues.apache.org/jira/browse/STANBOL-741">STANBOL-741</a>)</p>
+<p><em>NLP 2 RDF Engine:</em> <strong>under development</strong> (see <a href="https://issues.apache.org/jira/browse/STANBOL-741">STANBOL-741</a>)</p>
 <ul>
 <li>converts NLP processing results stored in the <a href="../nlp/analyzedtext">AnalyzedText</a> content part to RDF and adds them to the metadata of the <a href="../contentitem">ContentItem</a></li>
 <li>generated RDF uses the NIF (NLP Interchange Format)</li>
 </ul>
 </li>
 <li>
-<p><strong><a href="refactorengine">Refactor Engine</a></strong></p>
+<p><strong><a href="refactorengine">Refactor Engine</a>:</strong></p>
 <ul>
 <li>transforms enhancements according to a target ontology, requires KRES launcher.</li>
 </ul>