You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by bu...@apache.org on 2014/06/02 09:58:31 UTC

svn commit: r910870 - in /websites/staging/stanbol/trunk/content: ./ docs/trunk/customvocabulary.html

Author: buildbot
Date: Mon Jun  2 07:58:30 2014
New Revision: 910870

Log:
Staging update by buildbot for stanbol

Modified:
    websites/staging/stanbol/trunk/content/   (props changed)
    websites/staging/stanbol/trunk/content/docs/trunk/customvocabulary.html

Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jun  2 07:58:30 2014
@@ -1 +1 @@
-1599106
+1599107

Modified: websites/staging/stanbol/trunk/content/docs/trunk/customvocabulary.html
==============================================================================
--- websites/staging/stanbol/trunk/content/docs/trunk/customvocabulary.html (original)
+++ websites/staging/stanbol/trunk/content/docs/trunk/customvocabulary.html Mon Jun  2 07:58:30 2014
@@ -104,8 +104,7 @@
 </ul>
 <h2 id="overview">Overview</h2>
 <p>The following figure shows the typical Enhancement workflow that may start with some preprocessing steps (e.g. the conversion of rich text formats to plain text) followed by the Natural Language Processing phase. Next 'Semantic Lifting' aims to connect the results of text processing and link it to the application domain of the user. During Postprocessing those results may get further refined.</p>
-<p style="text-align: center;">![Typical Enhancement Workflow](enhancementworkflow.png "This figure shows typical enhancement chains for Apache Stanbol")</p>
-
+<p><img alt="Typical Enhancement Workflow" src="enhancementworkflow.png" title="This figure shows typical enhancement chains for Apache Stanbol" /></p>
 <p>This usage scenario is all about the Semantic Lifting phase. This phase is most central to for how well enhancement results to match the requirements of the users application domain. Users that need to process health related documents will need to provide vocabularies containing life science related entities otherwise the Stanbol Enhancer will not perform as expected on those documents. Similar processing Customer requests can only work if Stanbol has access to data managed by the CRM.</p>
 <p>This scenario aims to provide Stanbol users with all information necessary to use Apache Stanbol in scenarios where domain specific vocabularies are required.  </p>
 <h2 id="managing-custom-vocabularies-with-the-stanbol-entityhub">Managing Custom Vocabularies with the Stanbol Entityhub</h2>