You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by bu...@apache.org on 2013/07/24 09:24:01 UTC
svn commit: r870946 - in /websites/staging/jena/trunk/content: ./
documentation/query/cmds.html
Author: buildbot
Date: Wed Jul 24 07:24:01 2013
New Revision: 870946
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/documentation/query/cmds.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 24 07:24:01 2013
@@ -1 +1 @@
-1503334
+1506422
Modified: websites/staging/jena/trunk/content/documentation/query/cmds.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/cmds.html (original)
+++ websites/staging/jena/trunk/content/documentation/query/cmds.html Wed Jul 24 07:24:01 2013
@@ -160,21 +160,21 @@
queries, parse queries, process result sets and run test sets.</p>
<p>You will need to set the classpath, or use the helper scripts, to
run these applications from the command line. The helper scripts
-are in <code>bin/</code> (Linux, Unix, Cygwin) and <code>bat/</code> (Windows)
+are in <code>bin/</code> (Linux, Unix, Cygwin, OS/X) and <code>bat/</code> (Windows)
directories. There are ancillary scripts in the directories that
-the main commands need - you should put the relevant directory on
-your command path and set the <code>ARQROOT</code> environment variable after
-checking these scripts are suitable.</p>
+the main commands need - see <a href="../tools/index.html">the tools page</a>
+for setup details.</p>
<ul>
<li>
-<p><a href="#arqquery"><code>arq.query</code></a> is the main query driver.
- It can be called for SPARQL, ARQ or RDQL queries and there are
- wrapper commands for each language: <code>arq.sparql</code>, <code>arq.arq</code> and
- <code>arq.rdql</code>.</p>
+<p><a href="#arqquery"><code>arq.query</code></a> is the main query driver.</p>
</li>
<li>
<p><a href="#arqqparse"><code>arq.qparse</code></a> : parse and print a
- query.</p>
+ SPARQL query.</p>
+</li>
+<li>
+<p><a href="#arquparse"><code>arq.uparse</code></a> : parse and print a
+ SPARQL update.</p>
</li>
<li>
<p><a href="#arqupdate"><code>arq.update</code></a> : execute SPARQL/Update
@@ -188,9 +188,6 @@ checking these scripts are suitable.</p>
<p><a href="#arqrset"><code>arq.rset</code></a> : transform result sets.</p>
</li>
<li>
-<p><a href="#arqqtest"><code>arq.qtest</code></a> : run a test set.</p>
-</li>
-<li>
<p><a href="#arqqexpr"><code>arq.qexpr</code></a> : evaluate and print an
expression.</p>
</li>
@@ -199,11 +196,8 @@ checking these scripts are suitable.</p>
arguments.</p>
<p>When using a query in a file, if the query file ends .rq, it is
assumed to be a SPARQL query. If it ends .arq, it is assumed to be
-an ARQ query (extensions to SPARQL) and if it ends .rdql, it is
-assumed to be an RDQL query. You can specify the syntax
+an ARQ query (extensions to SPARQL). You can specify the syntax
explicitly.</p>
-<p>The commands <code>jena.query</code>, <code>jena.sparql</code>, <code>jena.qtest</code> and
-<code>jena.rset</code> are equivalent and just call to these commands.</p>
<h3 id="arqquery"><code>arq.query</code></h3>
<p>This is the main command for executing queries on data. The
wrappers just set the query language.</p>
@@ -230,19 +224,24 @@ If a data file ends <code>.n3</code>, it
assumed to be RDF/XML. The data serialization can be explicitly
specified on the command line.</p>
<h3 id="arqqparse"><code>arq.qparse</code></h3>
-<p>Parse a query and print it out. Can be used to translate between
-syntaxes (but not perfectly - specifically, RDQL value constraints
-need further conversion as complete mechanical translation is not
-possible).</p>
+<p>Parse a query and print it out.</p>
<p><code>arq.qparse</code> will parse the query, print it out again (with line
numbers by default) and then parse the serialized query again. If
your query has a syntax error, a message is printed but no query is
printed. If a query is printed then you get a syntax error message,
then your query was syntactically correct but the ARQ serialization
-is broken.</p>
+is broken. Please report this.</p>
<p>The command <code>arq.qparse --print=op --file <i>queryFile</i></code>will
print the SPARQL algebra for the query in
<a href="../notes/sse.html">SSE format</a>.</p>
+<h3 id="arquparse"><code>arq.uparse</code></h3>
+<p>Parse a SPARQL update print it out.</p>
+<p><code>arq.uparse</code> will parse the update, print it out again (with line
+numbers by default) and then parse the serialized update again. If
+your update has a syntax error, a message is printed but no update is
+printed. If a update is printed then you get a syntax error message,
+then your query was syntactically correct but the ARQ serialization
+is broken. Please report this.</p>
<h3 id="arqupdate"><code>arq.update</code></h3>
<p>Execute <a href="http://www.w3.org/TR/sparql11-update/">SPARQL Update</a>
requests.</p>