You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by gi...@apache.org on 2020/04/30 21:07:50 UTC
[jena-site] branch asf-site updated: Updated site from master
(6401bb3a08d3a62acbc7e44c3ec4bf2b04ea586a)
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/jena-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 8f1a0d3 Updated site from master (6401bb3a08d3a62acbc7e44c3ec4bf2b04ea586a)
8f1a0d3 is described below
commit 8f1a0d3149dbb91c1340f0befa21a38219285dab
Author: jenkins <bu...@apache.org>
AuthorDate: Thu Apr 30 21:07:46 2020 +0000
Updated site from master (6401bb3a08d3a62acbc7e44c3ec4bf2b04ea586a)
---
content/documentation/inference/index.html | 44 +++++++++++++++---------------
content/sitemap.xml | 4 +--
2 files changed, 24 insertions(+), 24 deletions(-)
diff --git a/content/documentation/inference/index.html b/content/documentation/inference/index.html
index 5d15422..d3e574f 100644
--- a/content/documentation/inference/index.html
+++ b/content/documentation/inference/index.html
@@ -249,7 +249,7 @@
<li>Generic rule reasoner: A rule based reasoner that supports user defined rules. Forward chaining,
tabled backward chaining and hybrid execution strategies are supported.</li>
</ol>
-<p>[<a href="#index">index</a>]</p>
+<p>[<a href="#index">Index</a>]</p>
<h2 id="api">The Inference API</h2>
<ol>
<li><a href="#reasonerAPI">Generic reasoner API</a></li>
@@ -331,7 +331,7 @@
locate reasoners with appropriate properties. The calls <code>Reasoner.getCapabilities</code>
and <code>Reasoner.supportsProperty</code> are used to access this descriptive
metadata.</p>
-<p>[<a href="#api">API index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#api">API Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="generalExamples">Some small examples</h3>
<p>These initial examples are not designed to illustrate the power of the reasoners
but to illustrate the code required to set one up.</p>
@@ -407,7 +407,7 @@ InfModel inf = ModelFactory.createInfModel(boundReasoner, data);
will see the schema statements, the data statements and any statements entailed
from the combination of the two. Any updates to the InfModel will be reflected
in updates to the underlying data model - the schema model will not be affected.</p>
-<p>[<a href="#api">API index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#api">API Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="operationsOnInferenceModels">Operations on inference models</h3>
<p>For many applications one simply creates a model incorporating some inference
step, using the <code>ModelFactory</code> methods, and then just works within
@@ -616,7 +616,7 @@ out.flush();
<p>Dynamic tracing control is sometimes possible on the InfModel itself by retrieving
its underlying InfGraph and calling <code>setTraceOn()</code> call. If you need
to make use of this see the full javadoc for the relevant InfGraph implementation.</p>
-<p>[<a href="#api">API index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#api">API Index</a>] [<a href="#index">Main Index</a>]</p>
<h2 id="rdfs">The RDFS reasoner</h2>
<ol>
<li><a href="#RDFSintro">RDFS reasoner - introduction and coverage</a></li>
@@ -651,7 +651,7 @@ _:anon1 rdf:type datatype .
the datatype of the literal. The value to applications of directly seeing the
additional bNode triples, even in <i>virtual</i> triple form, is negligible
and so this has been deliberately omitted from the reasoner. </p>
-<p>[<a href="#rdfs">RDFS index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#rdfs">RDFS Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="RDFSconfiguration">RDFS configuration</h3>
<p>The RDFSRuleReasoner can be configured to work at three different compliance
levels: </p>
@@ -739,7 +739,7 @@ Reasoner reasoner = RDFSRuleReasonerFactory.theInstance()Create(config);
</td>
</tr>
</table>
-<p>[<a href="#rdfs">RDFS index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#rdfs">RDFS Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="RDFSexamples">RDFS Example</h3>
<p>As a complete worked example let us create a simple RDFS schema, some instance
data and use an instance of the RDFS reasoner to query the two.</p>
@@ -819,7 +819,7 @@ Datatype[http://www.w3.org/2001/XMLSchema#integer -> class java.math.BigInteg
that is not compatible with 13</i></pre>
<p>because the age was given using an RDF plain litera where as the schema requires
it to be a datatyped literal which is compatible with xsd:integer.</p>
-<p>[<a href="#rdfs">RDFS index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#rdfs">RDFS Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="RDFSnotes">RDFS implementation and performance notes</h3>
<p>The RDFSRuleReasoner is a hybrid implementation. The subproperty and subclass
lattices are eagerly computed and stored in a compact in-memory form using the
@@ -877,7 +877,7 @@ that is not compatible with 13</i></pre>
the absence of caching we would expect the performance to be poor. Future work
on adapting the rule engines to exploit the capabilities of the more sophisticated
database backends will be considered.</p>
-<p>[<a href="#rdfs">RDFS index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#rdfs">RDFS Index</a>] [<a href="#index">Main Index</a>]</p>
<h2 id="owl">The OWL reasoner</h2>
<ol>
<li><a href="#OWLintro">OWL reasoner introduction</a></li>
@@ -1113,7 +1113,7 @@ configuration still leaves something to be desired and will the subject of futur
<li>Too many literal-values for a DatatypeProperty restricted by a maxCardinality(N)
restriction.</li>
</ul>
-<p>[<a href="#owl">OWL index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#owl">OWL Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="OWLconfiguration">OWL Configuration</h3>
<p>This reasoner is accessed using <code>ModelFactory.createOntologyModel</code>
with the prebuilt <a href="/documentation/javadoc/jena/org/apache/jena/ontology/OntModelSpec.html"><code>OntModelSpec</code></a>
@@ -1150,7 +1150,7 @@ configuration still leaves something to be desired and will the subject of futur
<p>As we gain experience with the ways in which OWL is used and the capabilities
of the rule-based approach we imagine useful subsets of functionality emerging
- like that supported by the RDFS reasoner in the form of the level settings.</p>
-<p>[<a href="#owl">OWL index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#owl">OWL Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="OWLexamples">OWL Example</h3>
<p>As an example of using the OWL inference support, consider the sample schema
and data file in the data directory - <a href="data/owlDemoSchema.xml">owlDemoSchema.xml</a>
@@ -1243,7 +1243,7 @@ Implicated node: eg:bigNameSpecialMB</i>
<p>This is due to the two records for the <code>bigName42</code> configuration
referencing two motherboards which are explicitly defined to be different resources
and thus violate the FunctionProperty nature of <code>hasMotherBoard</code>.</p>
-<p>[<a href="#owl">OWL index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#owl">OWL Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="OWLnotes">OWL notes and limitations</h3>
<h4 id="comprehension-axioms">Comprehension axioms</h4>
<p>A critical implication of our variant of the instance-based approach is that
@@ -1313,7 +1313,7 @@ class B = cardinality(P,1)</pre>
the current implementation is still under development and may well have ommissions
and oversights. We intend that the reasoner should be sound (all inferred triples
should be valid) but not complete. </p>
-<p>[<a href="#owl">OWL index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#owl">OWL Index</a>] [<a href="#index">Main Index</a>]</p>
<h2 id="transitive">The transitive reasoner</h2>
<p>The TransitiveReasoner provides support for storing and traversing class and
property lattices. This implements just the <i>transitive</i> and <i>symmetric</i>
@@ -1362,7 +1362,7 @@ class B = cardinality(P,1)</pre>
<p>The rule reasoner can also be extended by registering new procedural primitives.
The current release includes a starting set of primitives which are sufficient
for the RDFS and OWL implementations but is easily extensible.</p>
-<p>[<a href="#rules">rule index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#rules">Rule Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="RULEsyntax">Rule syntax and structure</h3>
<p>A rule for the rule-based reasoner is defined by a Java <code><a href="/documentation/javadoc/jena/org/apache/jena/reasoner/rulesys/Rule.html">Rule</a></code>
object with a list of body terms (premises), a list of head terms (conclusions)
@@ -1470,7 +1470,7 @@ a single extra rule is:
[rule1: (?f pre:father ?a) (?u pre:brother ?f) -&gt; (?u pre:uncle ?a)]
</code></pre>
</p>
-<p>[<a href="#rules">Rule index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#rules">Rule Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="RULEforward">Forward chaining engine</h3>
<p>If the rule reasoner is configured to run in forward mode then only the forward
chaining engine will be used. The first time the inference Model is queried
@@ -1508,7 +1508,7 @@ a single extra rule is:
efficient in some circumstances but has identical external semantics. This alternative
engine is likely to be eliminated in a future release once more tuning has been
done to the default RETE engine.</p>
-<p>[<a href="#rules">Rule index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#rules">Rule Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="RULEbackward">Backward chaining engine</h3>
<p>If the rule reasoner is run in backward chaining mode it uses a logic programming
(LP) engine with a similar execution strategy to Prolog engines. When the inference
@@ -1574,7 +1574,7 @@ triple(s1, p1, o1) :- triple(sb1, pb1, ob1), ...
<p>Note that backward rules can only have one consequent so that if writing rules that
might be run in either backward or forward mode then they should be limited to a single consequent each.
</p>
-<p>[<a href="#rules">Rule index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#rules">Rule Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="RULEhybrid">Hybrid rule engine</h3>
<p>The rule reasoner has the option of employing both of the individual rule engines
in conjunction. When run in this <i>hybrid</i> mode the data flows look something
@@ -1614,7 +1614,7 @@ might be run in either backward or forward mode then they should be limited to a
all the tabled LP results, as they do in the pure backward case. However, the
forward rules still work incrementally, including incrementally asserting or
removing backward rules in response to the data changes.</p>
-<p>[<a href="#rules">Rule index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#rules">Rule Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="RULEconfiguration">GenericRuleReasoner configuration</h3>
<p>As with the other reasoners there are a set of parameters, identified by RDF
properties, to control behaviour of the <code>GenericRuleReasoner</code>. These
@@ -1715,7 +1715,7 @@ Reasoner reasoner = new GenericRuleReasoner(rules);</pre>
</td>
</tr>
</table>
-<p>[<a href="#rules">Rule index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#rules">Rule Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="RULEbuiltins">Builtin primitives</h3>
<p>The procedural primitives which can be called by the rules are each implemented
by a Java object stored in a registry. Additional primitives can be created
@@ -1936,7 +1936,7 @@ do not "pollute" the inference results.</div>
</td>
</tr>
</table>
-<p>[<a href="#rules">Rule index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#rules">Rule Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="RULEexamples">Example</h3>
<p>As a simple illustration suppose we wish to create a simple ontology language
in which we can declare one property as being the concatenation of two others
@@ -2029,7 +2029,7 @@ System.out.println(” - " + PrintUtil.print(i.nextStatement()));
[ (?X ?P ?Y) <- (?Y ?P ?X) ]
[ (?A ?P ?C) <- (?A ?P ?B), (?B ?P ?C) ]
] </pre></p>
-<p>[<a href="#rules">rule index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#rules">Rule Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="RDFSPlusRules">Combining RDFS/OWL with custom rules</h3>
<p>Sometimes one wishes to write generic inference rules but combine them
with some RDFS or OWL inference. With the current Jena architecture limited forms of this
@@ -2086,7 +2086,7 @@ InfModel inf = ModelFactory.createInfModel(reasoner, data);
[rdfs6: (?a ?p ?b), (?p rdfs:subPropertyOf ?q) -> (?a ?q ?b)]
[rdfs9: (?x rdfs:subClassOf ?y), (?a rdf:type ?x) -> (?a rdf:type ?y)]
</pre>
-<p>[<a href="#rules">rule index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#rules">Rule Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="RULEnotes">Notes</h3>
<p>One final aspect of the general rule engine to mention is that of validation
rules. We described earlier how reasoners can implement a <code>validate</code>
@@ -2116,7 +2116,7 @@ InfModel inf = ModelFactory.createInfModel(reasoner, data);
</p>
<p>Future extensions will improve the formatting capabilities and flexibility
of this mechanism. </p>
-<p>[<a href="#rules">Rule index</a>] [<a href="#index">main index</a>]</p>
+<p>[<a href="#rules">Rule Index</a>] [<a href="#index">Main Index</a>]</p>
<h3 id="RULEextensions">Extensions</h3>
<p>There are several places at which the rule system can be extended by application
code.</p>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index ec3ee22..72b7580 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -299,7 +299,7 @@
<url>
<loc>https://jena.apache.org/documentation.html</loc>
- <lastmod>2020-04-29T21:07:36+01:00</lastmod>
+ <lastmod>2020-04-30T22:07:16+01:00</lastmod>
</url>
<url>
@@ -664,7 +664,7 @@
<url>
<loc>https://jena.apache.org/documentation/inference/</loc>
- <lastmod>2020-04-28T17:30:14+01:00</lastmod>
+ <lastmod>2020-04-30T22:07:16+01:00</lastmod>
</url>
<url>