svn commit: r795333 - /websites/staging/jena/trunk/content/jena/documentation/ontology/index.html

[bu...@apache.org]

Author: buildbot
Date: Mon Sep  5 21:34:29 2011
New Revision: 795333

Log:
Staging update by buildbot

Modified:
    websites/staging/jena/trunk/content/jena/documentation/ontology/index.html

Modified: websites/staging/jena/trunk/content/jena/documentation/ontology/index.html
==============================================================================
--- websites/staging/jena/trunk/content/jena/documentation/ontology/index.html (original)
+++ websites/staging/jena/trunk/content/jena/documentation/ontology/index.html Mon Sep  5 21:34:29 2011
@@ -768,7 +768,7 @@ ontology models.</p>
 actually a collection of models, one per imported model. This means
 we have to modify figure 2 a bit. Figure 4 shows how the ontology
 model builds a collection of import models:</p>
-<p><img alt="Diagram of compound document for imports" src="./Ont-model-layers-import.png" title="ontology model compound document structure for imports" />
+<p><img alt="Diagram of compound document for imports" src="./ont-model-layers-import.png" title="ontology model compound document structure for imports" />
 <br />
 Figure 4: ontology model compound document structure for imports</p>
 <p>We will use the term <em>document</em> to describe an ontology serialized
@@ -1190,7 +1190,7 @@ something between the complete list of t
 only the asserted values. Consider the class hierarchy in figure 5
 (i):</p>
 <p><img alt="Diagram showing direct relationships" src="./direct-hierarchy.png" title="asserted and direct relationships" />
-Figure 5: asserted and inferred relationships</p>
+<br />Figure 5: asserted and inferred relationships</p>
 <p>Figure 5 (i) shows a base model, containing a class hierarchy and
 an instance <code>x</code>. Figure 5 (ii) shows the full set of relationships
 that might be inferred from this base model. In Figure 5 (iii), we