Author: buildbot
Date: Mon Jul 16 13:15:55 2012
New Revision: 825992
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/content/ (props changed)
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components/rules/refactor.html
Propchange: websites/staging/stanbol/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jul 16 13:15:55 2012
@@ -1 +1 @@
-1362023
+1362024
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components/rules/refactor.html
==============================================================================
---
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components/rules/refactor.html
(original)
+++
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components/rules/refactor.html
Mon Jul 16 13:15:55 2012
@@ -106,12 +106,12 @@ Stanbol's ontologies. Figure 1 gives a v
benefit from the Refactor showing how external data can be aligned and used
within the CMS.</p>
<p><center>
<figure>
-<img width="500px" src="../../../images/rules/refactor.png" alt="Vocabulary
harmonization via Stanbol Refactor">
+<img width="500px" src="refactor.png" alt="Vocabulary harmonization via
Stanbol Refactor">
<figcaption>Figure 1: the refactor is used to align external data to the
ontologies used in a generic CMS enhanced with Stanbol.</figcaption>
<figure>
</center></p>
<p>We can specify a concrete scenario for a better understanding of the
-Refactor. Suppose we have configured the CMS (i.e. <a
href="../entityhub.html">Stanbol EntityHub</a>) in order
+Refactor. Suppose we have configured the CMS (i.e. <a
href="../entityhub/">Stanbol EntityHub</a>) in order
to fetch entities about persons from DBpedia. Now we want to represent these
entities adopting the vocabulary from schema.org and produce
schema.org Rich Snippets in order to provide search engine
