You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by aj...@apache.org on 2017/01/17 17:16:49 UTC
svn commit: r1779218 -
/jena/site/trunk/content/documentation/query/arq-query-eval.mdtext
Author: ajs6f
Date: Tue Jan 17 17:16:49 2017
New Revision: 1779218
URL: http://svn.apache.org/viewvc?rev=1779218&view=rev
Log:
Correcting bad hyphenation and mis-aimed internal links
Modified:
jena/site/trunk/content/documentation/query/arq-query-eval.mdtext
Modified: jena/site/trunk/content/documentation/query/arq-query-eval.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/query/arq-query-eval.mdtext?rev=1779218&r1=1779217&r2=1779218&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/query/arq-query-eval.mdtext (original)
+++ jena/site/trunk/content/documentation/query/arq-query-eval.mdtext Tue Jan 17 17:16:49 2017
@@ -24,7 +24,7 @@ like RDF. There is a common implementati
written for a read-only data source. Basic find works well is many
cases, and the whole Jena API will be able to use the extension.
For higher SPARQL performance, ARQ can be extended at the
-[basic graph matching](#stage-generator) or
+[basic graph matching](#graph-matching-and-a-custom-stagegenerator) or
[algebra level](#opexecutor).
Applications writers who extend ARQ at the query execution level
@@ -34,7 +34,7 @@ found in the `src-examples` directory in
- [Overview of ARQ Query processing-](#overview)
- [The Main Query Engine](#main-query-engine)
-- [Graph matching and a custom StageGenerator](#stage-generator)
+- [Graph matching and a custom StageGenerator](#graph-matching-and-a-custom-stagegenerator)
- [OpExecutor](#opexecutor)
- [Quads](#quads)
- [Mixed Graph Implementation Datasets](#mixed-datasets)