Author: andy
Date: Wed Jul 30 11:09:14 2014
New Revision: 1614613
URL: http://svn.apache.org/r1614613
Log:
Add space after ### or ####
Modified:
jena/site/trunk/content/documentation/inference/index.mdtext
Modified: jena/site/trunk/content/documentation/inference/index.mdtext
URL:
http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/inference/index.mdtext?rev=1614613&r1=1614612&r2=1614613&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/inference/index.mdtext (original)
+++ jena/site/trunk/content/documentation/inference/index.mdtext Wed Jul 30
11:09:14 2014
@@ -1421,7 +1421,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
@@ -1518,7 +1518,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>
@@ -1604,7 +1604,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>
@@ -2019,12 +2019,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>
@@ -2042,7 +2042,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
