Author: rwesten
Date: Wed Jan 22 10:18:51 2014
New Revision: 1560304

URL: http://svn.apache.org/r1560304
Log:
STANBOL-1191: applied patch provided by Bruno P.

Modified:
    stanbol/site/trunk/content/docs/trunk/enhancementusage.mdtext

Modified: stanbol/site/trunk/content/docs/trunk/enhancementusage.mdtext
URL: 
http://svn.apache.org/viewvc/stanbol/site/trunk/content/docs/trunk/enhancementusage.mdtext?rev=1560304&r1=1560303&r2=1560304&view=diff
==============================================================================
--- stanbol/site/trunk/content/docs/trunk/enhancementusage.mdtext (original)
+++ stanbol/site/trunk/content/docs/trunk/enhancementusage.mdtext Wed Jan 22 
10:18:51 2014
@@ -2,7 +2,7 @@ Title: Making use of Apache Stanbol Enha
 
 This document describes how to implement client side, i.e. user interface 
components by using the [enhancement 
results](components/enhancer/enhancementstructure.html) returned by the [Apache 
Stanbol Enhancer](components/enhancer). It does so by using three different 
scenarios:
 
-* __Entity Tagging__ - replacing text based tags such as "Bob Marley" with 
entities - [dbpedia:Bob_Marley](dbpedia.org/resource/Bob_Marley) - to improve 
content search and categorization. As added value this can also be used for 
mashups with already available information about linked entities and search 
engine optimization by [including 
metadata](http://schema.org/docs/datamodel.html) of tagged entities within the 
content.
+* __Entity Tagging__ - replacing text based tags such as "Bob Marley" with 
entities - [dbpedia:Bob_Marley](http://dbpedia.org/resource/Bob_Marley) - to 
improve content search and categorization. As added value this can also be used 
for mashups with already available information about linked entities and search 
engine optimization by [including 
metadata](http://schema.org/docs/datamodel.html) of tagged entities within the 
content.
 * __Entity Disambiguation__ - enhance the entity tagging experience by 
explicit support for disambiguation between different suggested entities. This 
allows users to explicitly link to Paris (Texas), Bob Marley (Comedian) or in 
between any other entities that do share similar labels.
 * __Entity Checker__ - interact with extracted entities similar as with todays 
spellchecker: Show extracted/suggested dirtily within the content; Allow users 
to interact with suggestions and to disambiguate between different matches if 
necessary; Support search for additional/other entities.
 
@@ -177,4 +177,4 @@ The following assumes {text-annotation} 
 3. Retrieving additional information about referenced entities: While the 
EntityAnnotation includes some basic information some users might want to 
retrieve all available information of referenced entities - to dereference the 
entity:
     * As this is a rather common use case the [EntityLinkingEngine]() and 
[KeywordLinkingEngine]() are by default configured to include information of 
Entities within the EnhancementResults. So users that use those 
EnhancementEngines will not need to dereference Entities as those information 
are already available within the enhancement results.
     * If a 'fise:EntityAnnotation' has the 'entityhub:site' property, entities 
can be dereferenced by using the Apache Stanbol Entityhub (see the section for 
[fise:EntityAnnotation](components/enhancer/enhancementstructure.html#fiseentityannotation)
 for details)
-    * In all other cases the URI of the suggested entity need to be used for 
dereferencing. If the referenced entity is part of the [linked 
data](http://linkeddata.org/) cloud, this is often possible by the 
[CoolURI](http://www.w3.org/TR/cooluris/) - basically sending a "GET -h 
"Accept: application/json+rdf" {entity-uri}".
\ No newline at end of file
+    * In all other cases the URI of the suggested entity need to be used for 
dereferencing. If the referenced entity is part of the [linked 
data](http://linkeddata.org/) cloud, this is often possible by the 
[CoolURI](http://www.w3.org/TR/cooluris/) - basically sending a "GET -h 
"Accept: application/json+rdf" {entity-uri}".


Reply via email to