svn commit: r917919 - in /websites/staging/jena/trunk/content: ./ documentation/inference/index.html

[bu...@apache.org]

Author: buildbot
Date: Wed Jul 30 11:09:38 2014
New Revision: 917919

Log:
Staging update by buildbot for jena

Modified:
    websites/staging/jena/trunk/content/   (props changed)
    websites/staging/jena/trunk/content/documentation/inference/index.html

Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 30 11:09:38 2014
@@ -1 +1 @@
-1612541
+1614613

Modified: websites/staging/jena/trunk/content/documentation/inference/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/inference/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/inference/index.html Wed Jul 30 11:09:38 2014
@@ -1523,7 +1523,7 @@ triple(s1, p1, o1) :- triple(sb1, pb1, o
   to strict top-to-bottom execution. Essentially all ground facts are consulted
   before all rule clauses but the ordering of ground facts is arbitrary.</p>
 
-####Tabling
+#### Tabling
 <p>The LP engine supports tabling. When a goal is tabled then all previously computed
   matches to that goal are recorded (memoized) and used when satisfying future
   similar goals. When such a tabled goal is called and all known answers have
@@ -1620,7 +1620,7 @@ Reasoner reasoner = new GenericRuleReaso
   the current working directory.<br>
 </p>
 
-####Summary of parameters
+#### Summary of parameters
 <table width="90%" border="1" cellspacing="0" cellpadding="0">
   <tr>
     <td width="26%"><b>Parameter</b></td>
@@ -1706,7 +1706,7 @@ Reasoner reasoner = new GenericRuleReaso
 </table>
 <p>[<a href="#rules">Rule index</a>] [<a href="#index">main index</a>]</p>
 
-###<a name="RULEbuiltins"></a>Builtin primitives
+### <a name="RULEbuiltins"></a>Builtin primitives
 <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
   and registered - see below for more details.</p>
@@ -2121,12 +2121,12 @@ while (i.hasNext()) {
 <p>There are several places at which the rule system can be extended by application
   code.</p>
 
-####Rule syntax
+#### Rule syntax
 <p>First, as mentioned earlier, the rule engines themselves only see rules in
   terms of the Rule Java object. Thus applications are free to define an alternative
   rule syntax so long as it can be compiled into Rule objects.</p>
 
-####Builtins
+#### Builtins
 <p>Second, the set of procedural builtins can be extended. A builtin should implement
   the <a href="/documentation/javadoc/jena/com/hp/hpl/jena/reasoner/rulesys/Builtin.html"><code>Builtin</code></a>
   interface. The easiest way to achieve this is by subclassing <code><a href="/documentation/javadoc/jena/com/hp/hpl/jena/reasoner/rulesys/builtins/BaseBuiltin.html">BaseBuiltin</a></code>
@@ -2144,7 +2144,7 @@ while (i.hasNext()) {
 <p>The easiest way to experiment with this is to look at the examples in the builtins
   directory. </p>
 
-####Preprocessing hooks
+#### Preprocessing hooks
 <p>The rule reasoner can optionally run a sequence of procedural preprocessing
   hooks over the data at the time the inference graph is <i>prepared</i>. These
   procedural hooks can be used to perform tests or translations which are slow