Author: buildbot
Date: Mon Jun 2 08:03:06 2014
New Revision: 910871
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 08:03:06 2014
@@ -1 +1 @@
-1599107
+1599111
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 08:03:06 2014
@@ -202,7 +202,7 @@ org.apache.stanbol.entityhub.indexing.ge
<p>We assume that you already have a running Apache Stanbol instance at
http://{stanbol-host} and that {stanbol-working-dir} is the working directory
of that instance on the local hard disk. To install the created index you need
to </p>
<ul>
<li>copy the "{name}.solrindex.zip" file to the
<code>{stanbol-working-dir}/stanbol/datafiles</code> directory (NOTE if you run
the 0.9.0-incubating version the path is
<code>{stanbol-working-dir}/sling/datafiles</code>).</li>
-<li>install the <code>org.apache.stanbol.data.site.{name}-{version}.jar</code>
to the OSGI environment of your Stanbol instance e.g. by using the Bundle tab
of the Apache Felix web console at
</code>http://{stanbol-host}/system/console/bundles</code></li>
+<li>install the <code>org.apache.stanbol.data.site.{name}-{version}.jar</code>
to the OSGI environment of your Stanbol instance e.g. by using the Bundle tab
of the Apache Felix web console at
<code>http://{stanbol-host}/system/console/bundles</code></li>
</ul>
<p>You find both files in the
<code>{indexing-working-dir}/indexing/dist/</code> folder.</p>
<p>After the installation your data will be available at</p>
@@ -216,11 +216,11 @@ org.apache.stanbol.entityhub.indexing.ge
<p>Generally there are two possible ways you can use to recognize entities of
your vocabulary:</p>
<ol>
<li><strong>Named Entity Linking</strong>: This first uses Named Entity
Recoqunition (NER) for spotting "named entities" in the text and second try to
link those named entities with entities defined in your vocabulary. This
approach is limited to entities with the type person, organization and places.
So if your vocabulary contains entities of other types, they will not be
recognized. In addition it also requires the availability of NER for the
language(s) of the processed documents.</li>
-<li><strong>Keyword Linking</strong>: This uses the labels of entities in your
vocabulary for the recognition and linking process. Natural Language Processing
(NLP) techniques such as part-of-speach (POS) detection can be used to improve
performance and results but this works also without NLP support. As extraction
and linking is based on labels mentioned in the analyzed content this method
has no restrictions regarding the types of your entities.</li>
+<li><strong>Entity Linking</strong>: This uses the labels of entities in your
vocabulary for the recognition and linking process. Natural Language Processing
(NLP) techniques such as part-of-speach (POS) detection can be used to improve
performance and results but this works also without NLP support. As extraction
and linking is based on labels mentioned in the analyzed content this method
has no restrictions regarding the types of your entities.</li>
</ol>
<p>For more information about this you might also have a look at the
introduction of the <a href="multilingual">multi lingual</a> usage scenario.</p>
<p><em>TIP</em>: If you are unsure about what to use you can also start with
configuring both options to give it a try. </p>
-<p>Depending on if you want to use named entity linking or keyword linking the
configuration of the <a href="components/enhancer/chains">enhancement chain</a>
and the <a href="components/enhancer/engines">enhancement engine</a> making use
of your vocabulary will be different.</p>
+<p>Depending on if you want to use <em>named entity linking</em> or <em>entity
linking</em> the configuration of the <a
href="components/enhancer/chains">enhancement chain</a> and the <a
href="components/enhancer/engines">enhancement engine</a> making use of your
vocabulary will be different. The following two sub-sections provide more
information on that.</p>
<h3 id="configuring-named-entity-linking">Configuring Named Entity Linking</h3>
<p>In case named entity linking is used the linking with the custom vocabulary
is done by the <a
href="components/enhancer/engines/namedentitytaggingengine.html">Named Entity
Tagging Engine</a>.
For the configuration of this engine you need to provide the following
parameters</p>
@@ -257,7 +257,7 @@ For the configuration of this engine you
</ul>
</li>
<li>The "Link ProperNouns only": If the custom Vocabulary contains Proper
Nouns (Named Entities) than this parameter should be activated. This options
causes the Entity Linking process to not making queries for commons nouns and
by that receding the number of queries agains the controlled vocabulary by
~70%. However this is not feasible if the vocabulary does contain Entities that
are common nouns in the language. </li>
-<li>The "Type Mappings" might be interesting for you if your vocabulary
contains custom types as those mappings can be used to map 'rdf:type's of
entities in your vocabulary to 'dc:type's used for 'fise:TextAnnotation's -
created by the Apache Stanbol Enhancer to annotate occurrences of extracted
entities in the parsed text. See the <a
href="components/enhancer/engines/keywordlinkingengine.html#type-mappings-syntax">type
mapping syntax</a> and the <a
href="enhancementusage.html#entity-tagging-with-disambiguation-support">usage
scenario for the Apache Stanbol Enhancement Structure</a> for details.</li>
+<li>The "Type Mappings" might be interesting for you if your vocabulary
contains custom types as those mappings can be used to map 'rdf:type's of
entities in your vocabulary to 'dc:type's used for 'fise:TextAnnotation's -
created by the Apache Stanbol Enhancer to annotate occurrences of extracted
entities in the parsed text. See the <a
href="components/enhancer/engines/entitylinking.html#type-mappings-syntax">type
mapping syntax</a> and the <a
href="enhancementusage.html#entity-tagging-with-disambiguation-support">usage
scenario for the Apache Stanbol Enhancement Structure</a> for details.</li>
</ol>
<p>The following Example shows an Example of an <a
href="components/enhancer/chains">enhancement chain</a> using OpenNLP for
NLP</p>
<ul>
