svn commit: r1350094 - /incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancementstructure.mdtext

[rw...@apache.org]

Author: rwesten
Date: Thu Jun 14 05:48:19 2012
New Revision: 1350094

URL: http://svn.apache.org/viewvc?rev=1350094&view=rev
Log:
minor

Modified:
    incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/enhancementstructure.mdtext

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=1350094&r1=1350093&r2=1350094&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 Thu Jun 14 05:48:19 2012
@@ -163,6 +163,8 @@ In principle there are two Resources tha
 1. EntityAnnotations: Resources with the 'rdf:type' 'fise:EntityAnnotation' do represent the entity suggestions by the Stanbol Enhancer. This resources provide the label, type and most important the URI of the extracted Entity. In addition the value of the fise:confidence' [0..1] can be used as indication how certain the Stanbol Enhancer is about this Entity. 
 2. Entities: This refers to all resources with an incoming 'fise:entity-reference' relation (such as 'dbpedia:Bob_Marley' in the above example). Enhancement Engines can be configured to "dereference" suggested entities - meaning to use the URI of the entity to retrieve additional information. In this case additional information about suggested Entities will be available in the Enhancement results. If this in not the case users will need to dereference suggested entities themselves.
 
+### Process Suggested Entities
+
 The following steps are typically needed to acquire the information needed to implement an entity tagging user interface:
 
 1. Iterate over all suggested Entities: This are all resources such as "{entity-annotation} rdf:type fise:EntityAnnotation"
@@ -174,7 +176,7 @@ The following steps are typically needed
 3. Dereferenced {entity}: Some EnhancementEngines support to add also information about suggested Entities to the enhancement results - in other words: to dereference suggested entities. In this case additional information about the {entity} can be retrieved directly from the enhancement results. Most important those information include all available labels (in all languages) of the Entity.
 4. Dereferencing suggested Entities: If the suggested Entity is available via the Stanbol Entityhub the {entity-anntotation} does have the 'entityhub:site' property. The value of this property is the name of the ReferencedSite of the Entityhub. To dereference the Entity a GET request to "{stanbol-root-URL}/entityhub/site/{site-name}/entity?id={entity}" need to be used. The "Accept" header of the request need to be set to the according RDF serialization (e.g. "application/rdf+json").
 
-### Content Categorizations:
+### Process Content Categorizations
 
 'fise:TopicAnnotation' instances are used to formally represent categories assigned to the parsed Content. The main difference between extracted Entities and assigned Categories is that extracted Entities do have one or more explicit mentions within the text while assigned Categories are suggested based on the document as a whole - typically they are not explicitly mentioned in the text.