svn commit: r1641783 - /jena/site/trunk/content/documentation/ontology/index.mdtext

[rv...@apache.org]

Author: rvesse
Date: Wed Nov 26 09:52:40 2014
New Revision: 1641783

URL: http://svn.apache.org/r1641783
Log:
Apply Tom Saleeba's patch, remove outdated broken link

Modified:
    jena/site/trunk/content/documentation/ontology/index.mdtext

Modified: jena/site/trunk/content/documentation/ontology/index.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/ontology/index.mdtext?rev=1641783&r1=1641782&r2=1641783&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/ontology/index.mdtext (original)
+++ jena/site/trunk/content/documentation/ontology/index.mdtext Wed Nov 26 09:52:40 2014
@@ -737,11 +737,11 @@ document from a given published URL mean
 document is loaded instead. This may be a file on the local disk, or simply a
 pointer to a local mirror web site.
 
-While the `FileManager` can be configure directly, we can also specify redirections
+While the `FileManager` can be configured directly, we can also specify redirections
 declaratively in the document manager policy file:
 
     <OntologySpec>
-      <publicURI rdf:resource="... the public URI to map from..."    />
+      <publicURI rdf:resource="... the public URI to map from..." />
       <altURL rdf:resource="... the local URL to map to ..." />
       <!-- optional ontology language term -->
       <language rdf:resource="... encoding used ..." />
@@ -753,7 +753,7 @@ For example:
 
     <OntologySpec>
       <!-- local version of the RDFS vocabulary -->
-      <publicURI rdf:resource="http://www.w3.org/2000/01/rdf-schema"    />
+      <publicURI rdf:resource="http://www.w3.org/2000/01/rdf-schema" />
       <altURL rdf:resource="file:src/main/resources/rdf-schema.rdf" />
     </OntologySpec>
 
@@ -778,7 +778,7 @@ initialised to the directory in which Je
     OntModel m = ModelFactory.createOntologyModel();
     OntDocumentManager dm = m.getDocumentManager();
     dm.addAltEntry( "http://www.eswc2006.org/technologies/ontology",
-                    "file:" + JENA + "src/examples/resources/eswc-2006-09-21.rdf"    );
+                    "file:" + JENA + "src/examples/resources/eswc-2006-09-21.rdf" );
     m.read( "http://www.eswc2006.org/technologies/ontology" );
 
 ### Specifying prefixes
@@ -1894,8 +1894,6 @@ of the ontology model:
 
 ## Working with persistent ontologies
 
-_TODO:_ update this section to refer specifically to TDB.
-
 A common way to work with ontology data is to load the ontology
 axioms and instances at run-time from a set of source documents.
 This is a very flexible approach, but has limitations. In
@@ -1919,9 +1917,7 @@ There are two somewhat separate requirem
 storing ontology data. The first is making the main or base model
 itself persistent. The second is re-using or creating persistent
 models for the imports of an ontology. These two requirements are
-handled slightly differently. A simple, but complete, example of
-using persistent database models for storing ontologies
-[is included with Jena](../examples/persistent-ont-model/index.html).
+handled slightly differently.
 
 To retrieve a Jena model from the database API, we have to know its
 name. Fortunately, common practice for ontologies on the Semantic
@@ -2020,4 +2016,4 @@ static methods. Currently available tool
     path returns `true` to the `onPath` predicate.
 -   `List namedHierarchyRoots( OntModel m )`
     Compute a list containing the uppermost fringe of the class
-    hierarchy in the given model which consists only of named classes.
+    hierarchy in the given model which consists only of named classes.
\ No newline at end of file