Author: buildbot
Date: Wed Jan 30 13:21:41 2013
New Revision: 848585
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/content/ (props changed)
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/index.html
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/opennlp.html
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/paoding.html
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/smartcn.html
Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jan 30 13:21:41 2013
@@ -1 +1 @@
-1440384
+1440398
Modified:
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/index.html
==============================================================================
---
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/index.html
(original)
+++
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/index.html
Wed Jan 30 13:21:41 2013
@@ -92,12 +92,16 @@
<p>This section covers the following topics:</p>
<ul>
<li><a href="#stanbol-nlp-processing">Stanbol NLP processing</a>: Short
introduction to NLP processing in Stanbol</li>
-<li>The [NLP processing API]: Information about the Java API of the NLP
processing Framework including information on<ul>
+<li>The <a href="#nlp-processing-api">NLP processing API</a>: Information
about the Java API of the NLP processing Framework including information on<ul>
<li>How to implement an <a href="nlpengine">NLP EnhancementEngine</a> and</li>
<li>How to integrate NLP frameworks as a <a href="restintegration">RESTful NLP
Analyses Service</a></li>
</ul>
</li>
-<li>Finally this document provides information about already <a
href="#integrated-nlp-frameworks">Integrated NLP processing Frameworks</a> and
<a href="#supported-languages">Supported Languages</a></li>
+<li>Finally a list supported NLP frameworks and languages<ul>
+<li><a href="#integrated-nlp-frameworks">Integrated NLP processing
Frameworks</a> and </li>
+<li><a href="#supported-languages">Supported Languages</a></li>
+</ul>
+</li>
</ul>
<p>Additional Information can be found in</p>
<ul>
@@ -154,13 +158,13 @@
<h3 id="integrated-nlp-frameworks">Integrated NLP frameworks</h3>
<ul>
<li>
-<p><strong><a href="openly">OpenNLP</a></strong>: Apache OpenNLP is the
default NLP processing framework used by Stanbol. OpenNLP supports <em>Sentence
Detection</em>, <em>Tokenization</em>, <em>Part of Speech</em> tagging,
<em>Chunking</em> and <em>Named Entity Recognition</em> for several languages.
Users can extend support to additional languages by providing their own
statistical models.</p>
+<p><strong><a href="opennlp">OpenNLP</a></strong>: Apache OpenNLP is the
default NLP processing framework used by Stanbol. OpenNLP supports <em>Sentence
Detection</em>, <em>Tokenization</em>, <em>Part of Speech</em> tagging,
<em>Chunking</em> and <em>Named Entity Recognition</em> for several languages.
Users can extend support to additional languages by providing their own
statistical models.</p>
</li>
<li>
<p><strong><a href="smartcn">Smartcn</a></strong>: The Lucene Smartcn Analyzer
integration provides basic language support for Chinese by providing
<em>Sentence Detection</em> and <em>Tokenization</em> engines.</p>
</li>
<li>
-<p><strong><a href="padding">Paoding</a></strong>: The Paoding Analyzer is an
alternative to Smartcn for basic Chinese language support. Paoding only
supports <em>Tokenization</em> and is therefore best used in combination with
the <a href="smartcn">Smartcn</a> <em>Sentnece Detection</em> engine.</p>
+<p><strong><a href="paoding">Paoding</a></strong>: The Paoding Analyzer is an
alternative to Smartcn for basic Chinese language support. Paoding only
supports <em>Tokenization</em> and is therefore best used in combination with
the <a href="smartcn">Smartcn</a> <em>Sentnece Detection</em> engine.</p>
</li>
<li>
<p><strong><a href="celi">CELI / linguagrid.org</a></strong>: Celi contributed
Stanbol EnhancementEngines based on their NLP processing Framework. It supports
<em>Named Entity Recognition</em> for French and Italien as well as
<em>Lemmatization</em> and lexical analysis for Italien, Danish, Russian,
Romanian and Swedish. In addition CELI also provides a Language identification
service</p>
@@ -172,19 +176,19 @@
</li>
<li>
<p><strong><a
href="https://github.com/insideout10/stanbol-freeling";>Freeling</a></strong>:
<em>Freeling</em> is an <a href="http://www.fsf.org/licenses/gpl.html";>GPL</a>
licensed NLP processing framework implemented in <code>C</code>. It supports
<em>Sentence Detection</em>, <em>Tokenization</em>, <em>Part of Speech</em>
tagging, <em>Chunking</em> and <em>Named Entity Recognition</em> for several
languages including English, Spanish, Italian, Russian and Portuguese. </p>
-<p>The integration is based on the <a href="restintegration">RESTful NLP
analysis service</a> specification. That means that users will need to install
and configure Freeling and than run the <a
href="https://github.com/insideout10/stanbol-freeling/tree/master/freeling-server";>Stanbol
Freeling Server</a>. After that they can use this server by configuring the <a
href="../engines/restfulnlpanalysis">RESTful NLP Analysis Engine</a> with the
<code>/analysis</code> as well as the <a
href="../engines/restfullangident">RESTful NLP Language Identification
Engine</a> with the <code>/langident</code> endpoint of their Stanbol Freeling
Server.</p>
+<p>The integration is based on the <a href="restfulnlpanalysisservice">RESTful
NLP analysis service</a> specification. That means that users will need to
install and configure Freeling and than run the <a
href="https://github.com/insideout10/stanbol-freeling/tree/master/freeling-server";>Stanbol
Freeling Server</a>. After that they can use this server by configuring the <a
href="../engines/restfulnlpanalysis">RESTful NLP Analysis Engine</a> with the
<code>/analysis</code> as well as the <a
href="../engines/restfullangident">RESTful NLP Language Identification
Engine</a> with the <code>/langident</code> endpoint of their Stanbol Freeling
Server.</p>
<p><strong>NOTE</strong>: As the license of Freeling is not compatible with
the ASL this project is hosted on <a
href="https://github.com/insideout10/stanbol-freeling";>https://github.com/insideout10/stanbol-freeling</a>
and is NOT a part of Apache Stanbol. Users that want to use it will need to
download and install it themselves.</p>
</li>
<li>
<p><strong><a
href="https://github.com/westei/stanbol-talismane";>Talismane</a></strong>:
Talismane is an <a href="http://www.fsf.org/licenses/agpl.html";>AGPL</a>
licensed NLP processing framework implemented in Java. It supports <em>Sentence
Detection</em>, <em>Tokenization</em>, <em>Part of Speech</em> tagging for
French.</p>
-<p>The integration is based on the <a href="restintegration">RESTful NLP
analysis service</a> specification. That means that users will need to download
and build the <a
href="https://github.com/westei/stanbol-talismane";>Stanbol-Talismane</a>
project and than run the <a
href="https://github.com/westei/stanbol-talismane/tree/master/talismane-server";>Stanbol
Talismane Server</a>. After that they can use this server by configuring the
<a href="../engines/restfulnlpanalysis">RESTful NLP Analysis Engine</a> with
the <code>/analysis</code> endpoint of their Stanbol-Talismane server</p>
+<p>The integration is based on the <a href="restfulnlpanalysisservice">RESTful
NLP analysis service</a> specification. That means that users will need to
download and build the <a
href="https://github.com/westei/stanbol-talismane";>Stanbol-Talismane</a>
project and than run the <a
href="https://github.com/westei/stanbol-talismane/tree/master/talismane-server";>Stanbol
Talismane Server</a>. After that they can use this server by configuring the
<a href="../engines/restfulnlpanalysis">RESTful NLP Analysis Engine</a> with
the <code>/analysis</code> endpoint of their Stanbol-Talismane server</p>
<p><strong>NOTE</strong>: As the license of Talismane is not compatible with
the ASL this project is hosted on <a
href="https://github.com/westei/stanbol-talismane";>https://github.com/westei/stanbol-talismane</a>
and is NOT a part of Apache Stanbol. Users that want to use it will need to
download and install it themselves.</p>
</li>
</ul>
<h3 id="supported-languages">Supported Languages</h3>
<ul>
<li>
-<p><strong>Catalan</strong> <em>(ça)</em></p>
+<p><strong>Catalan</strong> <em>(ca)</em></p>
<ul>
<li><a href="https://github.com/insideout10/stanbol-freeling";>Freeling</a>:
<em>Sentence Detection</em>, <em>Tokenization</em>, <em>POS</em> tagging,
<em>Chunking</em> and basic <em>NER</em> without classification</li>
</ul>
@@ -199,7 +203,7 @@
<li>
<p><strong>Danish</strong> <em>(da)</em></p>
<ul>
-<li>[OpenNLP] (opennlp): <em>Sentence Detection</em>, <em>Tokenization</em>,
<em>POS</em> tagging</li>
+<li><a href="opennlp">OpenNLP</a>: <em>Sentence Detection</em>,
<em>Tokenization</em>, <em>POS</em> tagging</li>
<li><a href="celi">CELI</a>: <em>Lemmatization</em> and lexical analysis</li>
</ul>
</li>
@@ -212,9 +216,9 @@
<li>
<p><strong>English</strong> <em>(en)</em></p>
<ul>
-<li>[OpenNLP] (opennlp): <em>Sentence Detection</em>, <em>Tokenization</em>,
<em>POS</em> tagging, <em>Chunking</em> and full <em>NER</em> for Persons,
Organizations and Places</li>
+<li><a href="opennlp">OpenNLP</a>: <em>Sentence Detection</em>,
<em>Tokenization</em>, <em>POS</em> tagging, <em>Chunking</em> and full
<em>NER</em> for Persons, Organizations and Places</li>
<li><a href="https://github.com/insideout10/stanbol-freeling";>Freeling</a>:
<em>Sentence Detection</em>, <em>Tokenization</em>, <em>POS</em> tagging,
<em>Chunking</em> and full <em>NER</em> for Persons, Organizations and
Places</li>
-<li><a href="../engines/opencalaisengine">OpenCalais</a>:
<strong>NER</strong></li>
+<li><a href="../engines/opencalaisengine">OpenCalais</a>: <em>NER</em></li>
</ul>
</li>
<li>
@@ -222,7 +226,7 @@
<ul>
<li><a href="https://github.com/westei/stanbol-talismane";>Talismane</a>:
<em>Sentence Detection</em>, <em>Tokenization</em>, <em>Part of Speech</em></li>
<li><a href="celi">CELI</a>: <em>NER</em></li>
-<li><a href="../engines/opencalaisengine">OpenCalais</a>: <strong>Named Entity
Recoqunition</strong></li>
+<li><a href="../engines/opencalaisengine">OpenCalais</a>: <em>NER</em></li>
</ul>
</li>
<li>
@@ -234,7 +238,7 @@
<li>
<p><strong>German</strong> <em>(de)</em></p>
<ul>
-<li>[OpenNLP] (opennlp): <em>Sentence Detection</em>, <em>Tokenization</em>,
<em>POS</em> tagging including Proper Noun support and <em>Chunking</em> (only
Noun phrases)</li>
+<li><a href="opennlp">OpenNLP</a>: <em>Sentence Detection</em>,
<em>Tokenization</em>, <em>POS</em> tagging including Proper Noun support and
<em>Chunking</em> (only Noun phrases)</li>
<li><a href="celi">CELI</a>: <em>Lemmatization</em> and lexical analysis</li>
</ul>
</li>
@@ -274,9 +278,9 @@
<li>
<p><strong>Spanish</strong> <em>(es)</em></p>
<ul>
-<li>[OpenNLP] (opennlp): <em>Sentence Detection</em>, <em>Tokenization</em>,
<em>POS</em> tagging (no Proper Noun support) and <em>NER</em> for Persons,
Organizations and Places</li>
+<li><a href="opennlp">OpenNLP</a>: <em>Sentence Detection</em>,
<em>Tokenization</em>, <em>POS</em> tagging (no Proper Noun support) and
<em>NER</em> for Persons, Organizations and Places</li>
<li><a href="https://github.com/insideout10/stanbol-freeling";>Freeling</a>:
<em>Sentence Detection</em>, <em>Tokenization</em>, <em>POS</em> tagging,
<em>Chunking</em> and full <em>NER</em> for Persons, Organizations and
Places</li>
-<li><a href="../engines/opencalaisengine">OpenCalais</a>:
<strong>NER</strong></li>
+<li><a href="../engines/opencalaisengine">OpenCalais</a>: <em>NER</em></li>
</ul>
</li>
<li>
Modified:
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/opennlp.html
==============================================================================
---
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/opennlp.html
(original)
+++
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/opennlp.html
Wed Jan 30 13:21:41 2013
@@ -124,7 +124,7 @@ opennlp-ner
</pre></div>
-<p>where <code>{your-named-entity-linking}</code> refers to an instance of the
<a href="../engines/namedentitytaggingengine">NamedEntityLinkingEngine</a>
configured for the users controlled vocabulary. Users can also use multiple
NamedEntityLinkingEngines configuration in the same chain. Users that want to
use NER models for other types than Persons, Organizations or Places will need
to use the <a
href="../engines/customnermodelengine.mdtext">CustomNerModelEngine</a> instead
of the <code>opennlp-ner</code> engine. </p>
+<p>where <code>{your-named-entity-linking}</code> refers to an instance of the
<a href="../engines/namedentitytaggingengine">NamedEntityLinkingEngine</a>
configured for the users controlled vocabulary. Users can also use multiple
NamedEntityLinkingEngines configuration in the same chain. Users that want to
use NER models for other types than Persons, Organizations or Places will need
to use the <a href="../engines/opennlpcustomner">CustomNerModelEngine</a>
instead of the <code>opennlp-ner</code> engine. </p>
<p>Note that the use of the <code>opennlp-token</code> and
<code>opennlp-sentence</code> engine is optional as the
<code>opennlp-ner</code> engine will to those steps itself in case tokens and
sentences are not yet available. Including those engines explicitly in the
chain is only required in cases where custom configurations for the tokenizers
and sentence detection engines (e.g. custom OpenNLP models) need to be
applied.</p>
<p>A typical <em>Entity Linking</em> enhancement engine based on OpenNLP
includes the following engines</p>
<div class="codehilite"><pre>tika;optional
Modified:
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/paoding.html
==============================================================================
---
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/paoding.html
(original)
+++
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/paoding.html
Wed Jan 30 13:21:41 2013
@@ -95,7 +95,7 @@
<li>Tokenize parsed Chinese Text</li>
<li>Tokenizer Chinese Labels of Entities in the controlled vocabulary.</li>
</ul>
-<p>It is highly recommended to use the Paoding Analyzer in combination with
the <a href="smatcn">Smartcn</a> as the Smartcn Analyzer provide Sentence
detection.</p>
+<p>It is highly recommended to use the Paoding Analyzer in combination with
the <a href="smartcn">Smartcn</a> as the Smartcn Analyzer provide Sentence
detection.</p>
<h2 id="installation">Installation</h2>
<p>The Paoding Analyzer integration consists of three bundles as referenced by
the <a
href="http://svn.apache.org/repos/asf/stanbol/trunk/launchers/bundlelists/language-extras/paoding/src/main/bundles/list.xml";>Paoding
Bundle List</a>.
Users can either include this BundleList in their <a
href="/docs/trunk/production-mode/your-launcher.html">Custom Launcher
configuration</a> by including the</p>
@@ -129,18 +129,22 @@ paoding-token
<ol>
<li>
<p>the fieldType specification for Chinese</p>
-<p>:::xml
-<fieldType name="text_zh" class="solr.TextField">
- <analyzer class="net.paoding.analysis.analyzer.PaodingAnalyzer"/>
-</fieldType></p>
+<div class="codehilite"><pre><span class="nt"><fieldType</span> <span
class="na">name=</span><span class="s">"text_zh"</span> <span
class="na">class=</span><span class="s">"solr.TextField"</span><span
class="nt">></span>
+ <span class="nt"><analyzer</span> <span class="na">class=</span><span
class="s">"net.paoding.analysis.analyzer.PaodingAnalyzer"</span><span
class="nt">/></span>
+<span class="nt"></fieldType></span>
+</pre></div>
+
+
</li>
<li>
<p>A dynamic field using this field type that matches against Chinese language
literals</p>
-<p>:::xml
-<!--
- Dynamic field for Chinese languages.
- -->
-<dynamicField name="@zh*" type="text_zh" indexed="true" stored="true"
multiValued="true" omitNorms="false"/></p>
+<div class="codehilite"><pre><span class="c"><!--</span>
+<span class="c"> Dynamic field for Chinese languages.</span>
+<span class="c"> --></span>
+<span class="nt"><dynamicField</span> <span class="na">name=</span><span
class="s">"@zh*"</span> <span class="na">type=</span><span
class="s">"text_zh"</span> <span class="na">indexed=</span><span
class="s">"true"</span> <span class="na">stored=</span><span
class="s">"true"</span> <span class="na">multiValued=</span><span
class="s">"true"</span> <span class="na">omitNorms=</span><span
class="s">"false"</span><span class="nt">/></span>
+</pre></div>
+
+
</li>
</ol>
<p>The <a
href="https://svn.apache.org/repos/asf/stanbol/trunk/entityhub/yard/solr/src/main/resources/solr/core/smartcn.solrindex.zip";>smartcn.solrindex.zip</a>
is identical with the default configuration but uses the above fieldType and
dynamicField specification.</p>
@@ -175,7 +179,7 @@ paoding-token
<li>create the SolrYard instance and configure the "Solr Index/Core"
(org.apache.stanbol.entityhub.yard.solr.solrUri) to {name}. Make sure the "Use
default SolrCore configuration"
(org.apache.stanbol.entityhub.yard.solr.useDefaultConfig) is disabled.</li>
</ol>
<p>If you want to use the paoding.solrindex.zip as default you can rename the
file in the datafilee folder to "default.solrindex.zip" and the enable the "Use
default SolrCore configuration"
(org.apache.stanbol.entityhub.yard.solr.useDefaultConfig) when you configure a
SolrYard instance.</p>
-<p>See also the documentation on how to <a
href="http://stanbol.apache.org/docs/trunk/components/entityhub/managedsite#configuration-of-managedsites";>configure
a managed site</a>).</p>
+<p>See also the documentation on how to <a
href="http://stanbol.apache.org/docs/trunk/components/entityhub/managedsite#configuration-of-managedsites";>configure
a managed site</a>.</p>
</div>
<div id="footer">
Modified:
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/smartcn.html
==============================================================================
---
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/smartcn.html
(original)
+++
websites/staging/stanbol/trunk/content/docs/trunk/components/enhancer/nlp/smartcn.html
Wed Jan 30 13:21:41 2013
@@ -124,30 +124,34 @@ smartcn-token
<ol>
<li>
<p>A fieldType specification for Chinese</p>
-<p>:::xml
-<fieldType name="text_zh" class="solr.TextField" positionIncrementGap="100">
- <analyzer type="index">
- <tokenizer class="solr.SmartChineseSentenceTokenizerFactory"/>
- <filter class="solr.SmartChineseWordTokenFilterFactory"/>
- <filter class="solr.LowerCaseFilterFactory"/>
- <filter class="solr.RemoveDuplicatesTokenFilterFactory"/>
- </analyzer>
- <analyzer type="query">
- <tokenizer class="solr.SmartChineseSentenceTokenizerFactory"/>
- <filter class="solr.SmartChineseWordTokenFilterFactory"/>
- <filter class="solr.LowerCaseFilterFactory"/>
- <filter class="solr.RemoveDuplicatesTokenFilterFactory"/>
- <filter class="solr.PositionFilterFactory" />
- </analyzer>
-</fieldType> </p>
+<div class="codehilite"><pre><span class="nt"><fieldType</span> <span
class="na">name=</span><span class="s">"text_zh"</span> <span
class="na">class=</span><span class="s">"solr.TextField"</span> <span
class="na">positionIncrementGap=</span><span
class="s">"100"</span><span class="nt">></span>
+ <span class="nt"><analyzer</span> <span class="na">type=</span><span
class="s">"index"</span><span class="nt">></span>
+ <span class="nt"><tokenizer</span> <span
class="na">class=</span><span
class="s">"solr.SmartChineseSentenceTokenizerFactory"</span><span
class="nt">/></span>
+ <span class="nt"><filter</span> <span class="na">class=</span><span
class="s">"solr.SmartChineseWordTokenFilterFactory"</span><span
class="nt">/></span>
+ <span class="nt"><filter</span> <span class="na">class=</span><span
class="s">"solr.LowerCaseFilterFactory"</span><span
class="nt">/></span>
+ <span class="nt"><filter</span> <span class="na">class=</span><span
class="s">"solr.RemoveDuplicatesTokenFilterFactory"</span><span
class="nt">/></span>
+ <span class="nt"></analyzer></span>
+ <span class="nt"><analyzer</span> <span class="na">type=</span><span
class="s">"query"</span><span class="nt">></span>
+ <span class="nt"><tokenizer</span> <span
class="na">class=</span><span
class="s">"solr.SmartChineseSentenceTokenizerFactory"</span><span
class="nt">/></span>
+ <span class="nt"><filter</span> <span class="na">class=</span><span
class="s">"solr.SmartChineseWordTokenFilterFactory"</span><span
class="nt">/></span>
+ <span class="nt"><filter</span> <span class="na">class=</span><span
class="s">"solr.LowerCaseFilterFactory"</span><span
class="nt">/></span>
+ <span class="nt"><filter</span> <span class="na">class=</span><span
class="s">"solr.RemoveDuplicatesTokenFilterFactory"</span><span
class="nt">/></span>
+ <span class="nt"><filter</span> <span class="na">class=</span><span
class="s">"solr.PositionFilterFactory"</span> <span
class="nt">/></span>
+ <span class="nt"></analyzer></span>
+<span class="nt"></fieldType></span>
+</pre></div>
+
+
</li>
<li>
<p>A dynamic field using this field type that matches against Chinese language
literals</p>
-<p>:::xml
-<!--
- Dynamic field for Chinese languages.
- -->
-<dynamicField name="@zh*" type="text_zh" indexed="true" stored="true"
multiValued="true" omitNorms="false"/></p>
+<div class="codehilite"><pre><span class="c"><!--</span>
+<span class="c"> Dynamic field for Chinese languages.</span>
+<span class="c"> --></span>
+<span class="nt"><dynamicField</span> <span class="na">name=</span><span
class="s">"@zh*"</span> <span class="na">type=</span><span
class="s">"text_zh"</span> <span class="na">indexed=</span><span
class="s">"true"</span> <span class="na">stored=</span><span
class="s">"true"</span> <span class="na">multiValued=</span><span
class="s">"true"</span> <span class="na">omitNorms=</span><span
class="s">"false"</span><span class="nt">/></span>
+</pre></div>
+
+
</li>
</ol>
<p>The <a
href="https://svn.apache.org/repos/asf/stanbol/trunk/entityhub/yard/solr/src/main/resources/solr/core/smartcn.solrindex.zip";>smartcn.solrindex.zip</a>
is identical with the default configuration but uses the above fieldType and
dynamicField specification.</p>
@@ -169,7 +173,7 @@ smartcn-token
<li>create the SolrYard instance and configure the "Solr Index/Core"
(org.apache.stanbol.entityhub.yard.solr.solrUri) to {name}. Make sure the "Use
default SolrCore configuration"
(org.apache.stanbol.entityhub.yard.solr.useDefaultConfig) is disabled.</li>
</ol>
<p>If you want to use the smartcn.solrindex.zip as default you can rename the
file in the datafilee folder to "default.solrindex.zip" and the enable the "Use
default SolrCore configuration"
(org.apache.stanbol.entityhub.yard.solr.useDefaultConfig) when you configure a
SolrYard instance.</p>
-<p>See also the documentation on how to <a
href="http://stanbol.apache.org/docs/trunk/components/entityhub/managedsite#configuration-of-managedsites";>configure
a managed site</a>).</p>
+<p>See also the documentation on how to <a
href="http://stanbol.apache.org/docs/trunk/components/entityhub/managedsite#configuration-of-managedsites";>configure
a managed site</a>.</p>
</div>
<div id="footer">
