Author: buildbot
Date: Thu Jun 14 05:48:26 2012
New Revision: 821687
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/content/ (props changed)
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/enhancementstructure.html
Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jun 14 05:48:26 2012
@@ -1 +1 @@
-1350093
+1350094
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/enhancementstructure.html
==============================================================================
---
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/enhancementstructure.html
(original)
+++
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/enhancementstructure.html
Thu Jun 14 05:48:26 2012
@@ -218,6 +218,7 @@
<li>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. </li>
<li>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.</li>
</ol>
+<h3 id="process-suggested-entities">Process Suggested Entities</h3>
<p>The following steps are typically needed to acquire the information needed
to implement an entity tagging user interface:</p>
<ol>
<li>Iterate over all suggested Entities: This are all resources such as
"{entity-annotation} rdf:type fise:EntityAnnotation"</li>
@@ -231,7 +232,7 @@
<li>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.</li>
<li>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").</li>
</ol>
-<h3 id="content-categorizations">Content Categorizations:</h3>
+<h3 id="process-content-categorizations">Process Content Categorizations</h3>
<p>'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.</p>
<p>Typically a entity tagging UI will want to distinguish between Categories
and Entities because:</p>
<ul>
