You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by rw...@apache.org on 2012/06/18 14:53:29 UTC
svn commit: r1351326 - in
/incubator/stanbol/site/trunk/content/stanbol/docs/trunk: ./ enhancer/
enhancer/engines/
Author: rwesten
Date: Mon Jun 18 12:53:28 2012
New Revision: 1351326
URL: http://svn.apache.org/viewvc?rev=1351326&view=rev
Log:
added links to the Enhancement Structure documentation
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/keywordlinkingengine.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/langidengine.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/opencalaisengine.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/tikaengine.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/zemantaengine.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancementstructure.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancerrest.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/multilingual.mdtext
Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext?rev=1351326&r1=1351325&r2=1351326&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/contentitem.mdtext Mon Jun 18 12:53:28 2012
@@ -57,7 +57,7 @@ returns the same blob instance.
The metadata of the ContentItem is managed by a lockable MGraph. This is basically a normal <code>java.util.Collections</code> for triples. The only RDF specific method is the support for filtered iterators which support wildcards for subjects, predicates and objects.
-This graph is used to store all enhancement results as well as metadata about the content item (such as content parts) and the enhancement process (see [execution metadata](executionmetadata.html)).
+This graph is used to store all [enhancement results](enhancementstructure.html) as well as metadata about the content item (such as content parts) and the enhancement process (see [execution metadata](executionmetadata.html)).
### Read/Write locks
Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/keywordlinkingengine.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/keywordlinkingengine.mdtext?rev=1351326&r1=1351325&r2=1351326&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/keywordlinkingengine.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/keywordlinkingengine.mdtext Mon Jun 18 12:53:28 2012
@@ -18,13 +18,13 @@ The example in the scene shows an config
* __Referenced Site__ _(org.apache.stanbol.enhancer.engines.keywordextraction.referencedSiteId)_: The name of the ReferencedSite of the Stanbol Entityhub that holds the controlled vocabulary to be used for extracting Entities. "entityhub" or "local" can be used to extract Entities managed directly by the Entityhub.
* __Label Field__ _(org.apache.stanbol.enhancer.engines.keywordextraction.nameField)_: The name of the property used to lookup Entities. Only a single field is supported for performance reasons. Users that want to use values of several fields should collect such values by an according configuration in the mappings.txt used during indexing. This [usage scenario](../../customvocabulary.html) provides more information on this.
* __Case Sensitivity__ _(org.apache.stanbol.enhancer.engines.keywordextraction.caseSensitive)_: This allows to activate/deactivate case sensitive matching. It is important to understand that even with case sensitivity activated an Entity with the label such as "Anaconda" will be suggested for the mention of "anaconda" in the text. The main difference will be the confidence value of such a suggestion as with case sensitivity activated the starting letters "A" and "a" are NOT considered to be matching. See the second technical part for details about the matching process. Case Sensitivity is deactivated by default. It is recommended to be activated if controlled vocabularies contain abbreviations similar to commonly used words e.g. CAN for Canada.
-* __Type Field__ _(org.apache.stanbol.enhancer.engines.keywordextraction.typeField)_: Values of this field are used as values of the "fise:entity-types" property of created "fise:EntityAnnotation"s. The default is "rdf:type".
+* __Type Field__ _(org.apache.stanbol.enhancer.engines.keywordextraction.typeField)_: Values of this field are used as values of the "fise:entity-types" property of created "[fise:EntityAnnotation](../enhancementstructure.html#fiseentityannotation)"s. The default is "rdf:type".
* __Redirect Field__ _(org.apache.stanbol.enhancer.engines.keywordextraction.redirectField)_ and __Redirect Mode__ _(org.apache.stanbol.enhancer.engines.keywordextraction.redirectMode)_: Redirects allow to tell the KeywordLinkingEngine to follow a specific property in the knowledge base for matched entities. This feature e.g. allows to follow redirects from "USA" to "United States" as defined in Wikipedia. See "Processing of Entity Suggestions" for details. Possible valued for the Redirect Mode are "IGNORE" - deactivates this feature; "ADD_VALUES" - uses label, type informations of redirected entities, but keeps the URI of the extracted entity; "FOLLOW" - follows the redirect
* __Min Token Length__ _(org.apache.stanbol.enhancer.engines.keywordextraction.minSearchTokenLength)_: While the KeywordLinkingEngine preferable uses POS (part-of-speach) taggers to determine if a word should matched with the controlled vocabulary the minimum token length provides a fall back if (a) no POS tagger is available for the language of the parsed text or (b) if the confidence of the POS tagger is lower than the threshold.
* __Keyword Tokenizer__ _(org.apache.stanbol.enhancer.engines.keywordextraction.keywordTokenizer)_: This allows to use a special Tokenizer for matching keywords and alpha numeric IDs. Typical language specific Tokenizers tend to split such IDs in several tokens and therefore might prevent a correct matching. This Tokenizer should only be activated if the KeywordLinkingEngine is configured to match against IDs like ISBN numbers, Product IDs ... It should not be used to match against natural language labels.
* __Suggestions__ _(org.apache.stanbol.enhancer.engines.keywordextraction.maxSuggestions)_: The maximum number of suggested Entities.
* __Languages__ _(org.apache.stanbol.enhancer.engines.keywordextraction.processedLanguages)_ and __Default Matching Language__ _(org.apache.stanbol.enhancer.engines.keywordextraction.defaultMatchingLanguage)_: The first allows to specify languages that should be processed by this engine. This is e.g. useful if the controlled vocabulary only contains labels in for a specific language but does not formally specify this information (by setting the "xml:lang" property for labels). The default matching language can be used to work around the exact opposite case. As an example in DBpedia labels do get the language of the dataset they are extracted from (e.g. all data extracted from en.wikipedia.org will get "xml:lang=en"). The default matching language allows to tell the KeywordLinkingEngine to use labels of that language for matching regardless of the language of the parsed content. In the case of DBpedia this allows e.g. to match persons mentioned in an Italian text with the eng
lish labels extracted from en.wikipedia.org. Details about natural language processing features used by this engine are provided in the section "Multiple Language Support"
-* __Type Mappings__ _(org.apache.stanbol.enhancer.engines.keywordextraction.typeMappings)_: The FISE enhancement structure (as used by the Stanbol Enhancer) distinguishes TextAnnotations and EntityAnnotations. The Keyword linking engine needs to create both types of Annotations: TextAnnotations selecting the words that match some Entities in the Controlled Vocabulary and EntityAnnotations that represent an Entity suggested for a TextAnnotation. The Type Mappings are used to determine the "dc:type" of the TextAnnotation based on the types of the suggested Entity. The default configuration comes with mappings for Persons, Organizations, Places and Concepts but this fields allows to define additional mappings. For details see the section "Type Mapping Syntax" and "Processing of Entity Suggestions".
+* __Type Mappings__ _(org.apache.stanbol.enhancer.engines.keywordextraction.typeMappings)_: The FISE enhancement structure (as used by the Stanbol Enhancer) distinguishes [TextAnnotation](../enhancementstructure.html#fisetextannotation) and [EntityAnnotation](../enhancementstructure.html#fiseentityannotation)s. The Keyword linking engine needs to create both types of Annotations: TextAnnotations selecting the words that match some Entities in the Controlled Vocabulary and EntityAnnotations that represent an Entity suggested for a TextAnnotation. The Type Mappings are used to determine the "dc:type" of the TextAnnotation based on the types of the suggested Entity. The default configuration comes with mappings for Persons, Organizations, Places and Concepts but this fields allows to define additional mappings. For details see the section "Type Mapping Syntax" and "Processing of Entity Suggestions".
* __Dereference Entities__ _(org.apache.stanbol.enhancer.engines.keywordextraction.dereference)_: If enabled this engine adds additional information about the suggested Entities to the Metadata of the enhanced content item.
* __Ranking__ _(service.ranking)_: This property is used of two engines do use the same __Name__. In such cases the one with the higher ranking will be used to enhance content items. Typically users will not need to change this.
@@ -35,7 +35,7 @@ Additionally the following properties ca
### Type Mappings Syntax
-The Type Mappings are used to determine the "dc:type" of the TextAnnotation based on the types of the suggested Entity. The field "Type Mappings" (property: _org.apache.stanbol.enhancer.engines.keywordextraction.typeMappings_) can be used to customize such mappings.
+The Type Mappings are used to determine the "dc:type" of the [TextAnnotation](../enhancementstructure.html#fisetextannotation) based on the types of the suggested Entity. The field "Type Mappings" (property: _org.apache.stanbol.enhancer.engines.keywordextraction.typeMappings_) can be used to customize such mappings.
This field uses the following syntax
@@ -43,7 +43,7 @@ This field uses the following syntax
{source} > {target}
{source1}; {source2}; ... {sourceN} > {target}
-The first variant is a shorthand for {uri} > {uri} and therefore specifies that the {uri} should be used as 'dc:type' for TextAnnotations if the matched entity is of type {uri}. The second variant matches a {source} URI to a {target}. Variant three shows the possibility to match multiple URIs to the same target in a single configuration line.
+The first variant is a shorthand for {uri} > {uri} and therefore specifies that the {uri} should be used as 'dc:type' for [TextAnnotation](../enhancementstructure.html#fisetextannotation)s if the matched entity is of type {uri}. The second variant matches a {source} URI to a {target}. Variant three shows the possibility to match multiple URIs to the same target in a single configuration line.
Both 'ns:localName' and full qualified URIs are supported. For supported namespaces see the [NamespaceEnum](http://svn.apache.org/repos/asf/incubator/stanbol/trunk/entityhub/generic/servicesapi/src/main/java/org/apache/stanbol/entityhub/servicesapi/defaults/NamespaceEnum.java). Information about accepted (INFO) and ignored (WARN) type mappings are available in the logs.
@@ -133,7 +133,7 @@ In case there are one or more [Suggestio
LinkedEntity is an object model representing the Stanbol Enhancement Structure. After the processing of the parsed content is completed, the LinkedEntities are "serialized" as RDF triples to the metadata of the ContentItem.
-TextAnnotations as defined in the [Stanbol Enhancement Structure](http://wiki.iks-project.eu/index.php/EnhancementStructure) do use the [dc:type](http://www.dublincore.org/documents/dcmi-terms/#terms-type) property to provide the general type of the extracted Entity. However suggested Entities might have very specific types. Therefore the [EntityLinkerConfig](http://svn.apache.org/repos/asf/incubator/stanbol/trunk/enhancer/engines/keywordextraction/src/main/java/org/apache/stanbol/enhancer/engines/keywordextraction/linking/EntityLinkerConfig.java) provides the possibility to map the specific types of the Entity to types used for the dc:type property of TextAnnotations. The [EntityLinkerConfig](http://svn.apache.org/repos/asf/incubator/stanbol/trunk/enhancer/engines/keywordextraction/src/main/java/org/apache/stanbol/enhancer/engines/keywordextraction/linking/EntityLinkerConfig.java).DEFAULT_ENTITY_TYPE_MAPPINGS contains some predefined mappings.
+[TextAnnotation](../enhancementstructure.html#fisetextannotation)s as defined in the [Stanbol Enhancement Structure](../enhancementstructure.html) do use the [dc:type](http://www.dublincore.org/documents/dcmi-terms/#terms-type) property to provide the general type of the extracted Entity. However suggested Entities might have very specific types. Therefore the [EntityLinkerConfig](http://svn.apache.org/repos/asf/incubator/stanbol/trunk/enhancer/engines/keywordextraction/src/main/java/org/apache/stanbol/enhancer/engines/keywordextraction/linking/EntityLinkerConfig.java) provides the possibility to map the specific types of the Entity to types used for the dc:type property of TextAnnotations. The [EntityLinkerConfig](http://svn.apache.org/repos/asf/incubator/stanbol/trunk/enhancer/engines/keywordextraction/src/main/java/org/apache/stanbol/enhancer/engines/keywordextraction/linking/EntityLinkerConfig.java).DEFAULT_ENTITY_TYPE_MAPPINGS contains some predefined mappings.
*Note that the field used to retrieve the types of a suggested Entity can be configured by the EntityLinkerConfig. The default value for the type field is "rdf:type".*
In some cases suggested entities might redirect to others. In the case of Wikipedia/DBpedia this is often used to link from acronyms like [IMF](http://en.wikipedia.org/w/index.php?title=IMF&redirect=no) to the real entity [International Monetary Fund](http://en.wikipedia.org/wiki/International_Monetary_Fund). But also some Thesauri define labels as own Entities with an URI and users might want to use the URI of the Concept rather than one of the label.
Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/langidengine.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/langidengine.mdtext?rev=1351326&r1=1351325&r2=1351326&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/langidengine.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/langidengine.mdtext Mon Jun 18 12:53:28 2012
@@ -13,7 +13,7 @@ The text to be checked must be provided
:::html
<pre><code>http://www.semanticdesktop.org/ontologies/2007/01/19/nie#plainTextContent</pre></code>
-The result of language identification is added as TextAnnotation to the content item's metadata as string value of the property
+The result of language identification is added as [fise:TextAnnotation](../enhancementstructure.html#fisetextannotation) to the content item's metadata as string value of the property
:::text
http://purl.org/dc/terms/language
Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.mdtext?rev=1351326&r1=1351325&r2=1351326&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.mdtext Mon Jun 18 12:53:28 2012
@@ -7,7 +7,7 @@ This engine is based on the NLP features
## Example Result
-This engine adds **TextAnnotation-Enhancements** for the text "The Stanbol enhancer can detect famous cities such as Paris and people such as Bob Marley.", (amongst other) the following information to the enhancement graph, suggesting Bob Marley (of type: Person) for the string "Bob Marley":
+This engine adds [fise:TextAnnotation](../enhancementstructure.html#fisetextannotation) for the text "The Stanbol enhancer can detect famous cities such as Paris and people such as Bob Marley.", (amongst other) the following information to the enhancement graph, suggesting Bob Marley (of type: Person) for the string "Bob Marley":
:::text
{
@@ -17,12 +17,16 @@ This engine adds **TextAnnotation-Enhanc
"dc:creator": "org.apache.stanbol.enhancer.engines.opennlp.impl.NEREngineCore",
"dc:type": "dbp-ont:Person",
"enhancer:confidence": 0.94647044,
- "enhancer:end": 89,
+ "enhancer:end": 59,
"enhancer:extracted-from": "urn:content-item-sha1-37c8a8244041cf6113d4ee04b3a04d0a014f6e10",
"enhancer:selected-text": "Bob Marley",
"enhancer:selection-context":
- "The Stanbol enhancer can detect famous cities such as Paris and people such as Bob Marley.",
- "enhancer:start": 79
+ "The Stanbol enhancer can detect famous Entities such as Paris or Bob Marley.",
+ "enhancer:start": 69
}
-This enhancement statement provides you with the ID and date of the enhancement, the suggested type with a confidence for it, the position of the selected text and its (sentence) context as well as the link to the source document.
+The following figure provides a visual representation of the above graph
+
+!['fise:TextAnnotation'](enhancer/es_textannotation.png "This figure shows a TextAnnotation describing the occurrence of "Bob Marley" located from character 59 to 69 in the given text")
+
+See the documentation of the [Enhancement Structure](../enhancementstructure.html) for details.
Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/opencalaisengine.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/opencalaisengine.mdtext?rev=1351326&r1=1351325&r2=1351326&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/opencalaisengine.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/opencalaisengine.mdtext Mon Jun 18 12:53:28 2012
@@ -7,7 +7,8 @@ Webservice](http://www.opencalais.com/)
The engine will send the text of content item to the OpenCalais service and
retrieve the NER annotations in RDF format. The OpenCalais annotations are
-added to the content item's metadata as Stanbol text enhancement structures.
+added to the content item's metadata as specified by the Stanbol [Enhancement
+ Structures](../enhancementstructure.html).
The engine natively supports the mime types *text/plain* and
*text/html*. Additionally, text can be processed that is provided in the content
Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/tikaengine.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/tikaengine.mdtext?rev=1351326&r1=1351325&r2=1351326&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/tikaengine.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/tikaengine.mdtext Mon Jun 18 12:53:28 2012
@@ -32,6 +32,8 @@ Supported Ontologies:
* RDFS: Allows to map labels and comments to "rdfs:label" and "rdfs:comment"
+Note that the metadata extracted by the Tika engine are not covered by the Stanbol [Enhancement Structure](../enhancementstructure.html) as they are outside of its scope.
+
### ContentType:
The detected content type for the parsed contentItem is added by using the following two properties:
Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/zemantaengine.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/zemantaengine.mdtext?rev=1351326&r1=1351325&r2=1351326&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/zemantaengine.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/engines/zemantaengine.mdtext Mon Jun 18 12:53:28 2012
@@ -17,4 +17,10 @@ To use this Enhancement Engine it is imp
* Watch the console when you add text using commands such as:
:::bash
- curl -T myText.txt -H Content-Type:text/plain http://localhost:8080/enhancer
\ No newline at end of file
+ curl -T myText.txt -H Content-Type:text/plain http://localhost:8080/enhancer
+
+## Enhancements
+
+This engine supports Extracted Entities and Topic Classification. The occurrence of extracted entities are represented by '[fise:TextAnnotation](../enhancementstructure.html#fisetextannotation)' while suggested Entities are represented as '[fise:EntityAnnotation](../enhancementstructure.html#fiseentityannotation)' with a 'dc:relation' link to the 'fise:TextAnnotation'. Categories are represented as '[fise:TopicAnnotation](../enhancementstructure.html#fisetopicannotation)'s.
+
+Enhancemetns created by the ZemantaEngine are compatible to those created by similar engines such as the [Named Entity Extraction Enhancement Engine](namedentityextractionengine.html), [KeywordLinkingEngine](keywordlinkingengine.html) or [Named Entity Tagging Engine](namedentitytaggingengine.html). This ensures that Stanbol Users can arbitrary mix those engines with the Zemanta based variant without the need to adapt client side code.
\ No newline at end of file
Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancementstructure.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancementstructure.mdtext?rev=1351326&r1=1351325&r2=1351326&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancementstructure.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancementstructure.mdtext Mon Jun 18 12:53:28 2012
@@ -11,7 +11,7 @@ Its two main purposes are to facilitate
* group Entity suggestion based on detected "Named Entities" (disambiguation support)
* show the occurrence of detected Entities within the analyzed text (similar to spell checker UIs)
-While this document focuses on the first Engine and provides details on how the Stanbol Enhancement Structure it the integral part of the Stanbol Enhancer there is also a [Usage Scenario](../consumningenhancements.html) available that focuses on how the Enhancements can be consumed by Stanbol Enhancer users.
+While this document focuses on the first Engine and provides details on how the Stanbol Enhancement Structure it the integral part of the Stanbol Enhancer there is also a [Usage Scenario](../enhancementusage.html) available that focuses on how the Enhancements can be consumed by Stanbol Enhancer users.
## Overview on the Stanbol Enhancement Structure
Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancerrest.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancerrest.mdtext?rev=1351326&r1=1351325&r2=1351326&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancerrest.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancerrest.mdtext Mon Jun 18 12:53:28 2012
@@ -268,7 +268,7 @@ Note that for such requests [Metaxa](eng
### Example 4: Parse existing free text annotations
-This example shows how the multi-part content item API can be used to parse already existing tags for an parsed content to the Stanbol Enhancer. For this example it is important to understand that parsed metadata need to confirm to the Stanbol Enhancement Structure. Because of that this example consist of two main steps:
+This example shows how the multi-part content item API can be used to parse already existing tags for an parsed content to the Stanbol Enhancer. For this example it is important to understand that parsed metadata need to confirm to the Stanbol [Enhancement Structure](enhancementstructure.html). Because of that this example consist of two main steps:
1. Convert user tags to <code>TextAnnotation</code>s
2. Send existing Metadata along with the Content to the Stanbol Enhancer
Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/multilingual.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/multilingual.mdtext?rev=1351326&r1=1351325&r2=1351326&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/multilingual.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/multilingual.mdtext Mon Jun 18 12:53:28 2012
@@ -3,15 +3,15 @@ Title: Configure Apache Stanbol to work
To understand multi lingual support with Apache Stanbol one needs to consider that Stanbol supports two different workflows for extracting Entities from parsed text:
-1. __Named Entity Linking__: This first uses Named Entity Recoqunition (NER) for spotting Entities and second linked found Named Entities with Entities defined by the Controlled Vocabulary (e.g. DBpedia.or). For the NER step the [NamedEntityExtraction](enhancer/engines/namedentityextractionengine.html), the CELI NER engine - using the [linguagrid.org](http://linguagrid.org) service or the [OpenCalais](enhancer/engines/opencalaisengine.html) can be used. The linking functionality is implemented by the [NamedEntityTaggingEngine](enhancer/engines/namedentitytaggingengine.html). Multi lingual support depends on the availability of NER models for a language. Note also that separate models are required for each Entity type. Typical supported types are Persons, Organizations and Places.
+1. __Named Entity Linking__: This first uses Named Entity Recoqunition (NER) for spotting Entities and second linked found Named Entities with Entities defined by the Controlled Vocabulary (e.g. DBpedia.or). For the NER step the [NamedEntityExtraction](enhancer/engines/namedentityextractionengine.html), the CELI NER engine - using the [linguagrid.org](http://linguagrid.org) service or the [OpenCalais](enhancer/engines/opencalaisengine.html) /work/workspace/stanbol-website/content/stanbol/docs/trunk/enhancer/engines/refactorengine.mdtextcan be used. The linking functionality is implemented by the [NamedEntityTaggingEngine](enhancer/engines/namedentitytaggingengine.html). Multi lingual support depends on the availability of NER models for a language. Note also that separate models are required for each Entity type. Typical supported types are Persons, Organizations and Places.
2. __Keyword Linking__: Entity label based spotting and linking of Entities as implemented by the [KeywordLinkingEngine](enhancer/engines/keywordlinkingengine.html). Natural Language Processing (NLP) techniques such as Part-of-Speach (POS) processing are used to improve performance and result of the extraction process but are not a absolute requirement. As extraction only requires a label this method is also independent of the types of the Entities.
The following Languages are supported for NER - and can therefore be used for Named Entity Linking:
* __English__ (via [NamedEntityTaggingEngine](enhancer/engines/namedentitytaggingengine.html), [OpenCalais](enhancer/engines/opencalaisengine.html))
-* __Spansh__ (via [NamedEntityTaggingEngine](enhancer/engines/namedentitytaggingengine.html))
+* __Spansh__ (via [NamedEntityTaggingEngine](enhancer/engines/namedentitytaggingengine.html), [OpenCalais](enhancer/engines/opencalaisengine.html))
* __Dutch__ ((via [NamedEntityTaggingEngine](enhancer/engines/namedentitytaggingengine.html))
-* __French__ (via CELI NER engine)
+* __French__ (via CELI NER engine, [OpenCalais](enhancer/engines/opencalaisengine.html))
* __Italien__ (via CELI NER engine)
_NOTE:_ The CELI and OpenCalais engine require users to create an Account with the according services. In addition analyzed Content will be sent to those services!