svn commit: r1638058 - /stanbol/site/trunk/content/docs/trunk/components/enhancer/engines/lucenefstlinking.mdtext

[rw...@apache.org]

Author: rwesten
Date: Tue Nov 11 10:01:19 2014
New Revision: 1638058

URL: http://svn.apache.org/r1638058
Log:
corrections to the STANBOL-1403 documentation

Modified:
    stanbol/site/trunk/content/docs/trunk/components/enhancer/engines/lucenefstlinking.mdtext

Modified: stanbol/site/trunk/content/docs/trunk/components/enhancer/engines/lucenefstlinking.mdtext
URL: http://svn.apache.org/viewvc/stanbol/site/trunk/content/docs/trunk/components/enhancer/engines/lucenefstlinking.mdtext?rev=1638058&r1=1638057&r2=1638058&view=diff
==============================================================================
--- stanbol/site/trunk/content/docs/trunk/components/enhancer/engines/lucenefstlinking.mdtext (original)
+++ stanbol/site/trunk/content/docs/trunk/components/enhancer/engines/lucenefstlinking.mdtext Tue Nov 11 10:01:19 2014
@@ -97,14 +97,14 @@ This would set the index field to "fise:
     
 #### Linking Mode
 
-The FST linking engine does support three linking modes. Those are configures using the __Linking Mode__ _(enhancer.engines.linking.lucenefst.mode)_ property.
+The FST linking engine does support two different linking modes. Those are configures using the __Linking Mode__ _(enhancer.engines.linking.lucenefst.mode)_ property.
 
-![Linking Mode Configuration](fstengine-config-indexlayout.png)
+![Linking Mode Configuration](fstengine-config-linkingmode.png)
 
-The three modes are
+The two modes are
 
-1. `PLAIN`: This mode links all words in the parsed text. This mode does not require any NLP processing as the Solr Analyzer for the configured field will be used for processing the text. The basic mode is best if the vocabulary contains entities that appear in text with tokens other than nouns (e.g. a vocabulary that contains activities)
-2. `LINKABLE_TOKEN`: This mode will use the provided [Text Processing Configuration](#text-processing-configuration). This is a good default for vocabularies that contain entities mentioned in texts as Nouns and/or ProperNouns.
+1. `PLAIN`: This mode links the plain text with the vocabulary. Every single word of the text will get looked up with the vocabulary. This mode does not use NLP results other than language detection. This mode also ot make use of the [Text Processing Configuration](#text-processing-configuration). The PLAIN mode works fine with smaller and specific vocabularies that do not only contain entities but also things like product ids, activities, adjectives ...
+2. `LINKABLE_TOKEN`: This mode links only linkable tokens of the parsed text. The provided [Text Processing Configuration](#text-processing-configuration) is used to determine linkable tokens in the text (based on NLP results). This is the default mode for this engine. It is well suited for vocabularies containing named entities (such as persons, cities, products, organizations, roles, ...)
 <!-- 3. `NER`: This mode will only consider detected Named Entities for linking. This mode is similar to using the [Named Entity Linking Engine](namedentitytaggingengine). This is a best mode if the enhancement chain contains an NER component that can detect the types of entities contained in the linked vocabulary. -->
 
 By default the FST linking engine uses the `LINKABLE_TOKEN`. In this mode this engine behaves similar as the [Entityhub Linking Engine](entityhublinking).