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 2015/07/26 12:50:20 UTC
svn commit: r959629 [8/10] - in /websites/staging/jena/trunk/content: ./
about_jena/ documentation/ documentation/assembler/ documentation/csv/
documentation/extras/ documentation/extras/querybuilder/
documentation/fuseki2/ documentation/hadoop/ docume...
Modified: websites/staging/jena/trunk/content/documentation/tools/eyeball-manual.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/tools/eyeball-manual.html (original)
+++ websites/staging/jena/trunk/content/documentation/tools/eyeball-manual.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Jena Eyeball manual</h1>
- <p>This document describes Eyeball, an
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>This document describes Eyeball, an
"<a href="http://www.w3.org/RDF/">RDF</a>
<a href="http://en.wikipedia.org/wiki/Lint_programming_tool">lint</a>".
See
@@ -155,7 +166,7 @@ RDF/OWL tools. For help and support with
<a href="/help_and_support/index.html">the Jena support page</a></p>
<p>Throughout this document, the prefix <code>eye:</code> stands for the URL
<code>http://jena.hpl.hp.com/Eyeball\#</code>.</p>
-<h2 id="introduction">Introduction</h2>
+<h2 id="introduction">Introduction<a class="headerlink" href="#introduction" title="Permanent link">¶</a></h2>
<p>Eyeball is a library and command-line tool for checking RDF and OWL
models for various common problems. These problems often result in
technically correct but implausible RDF. Eyeball checks against
@@ -181,7 +192,7 @@ assumptions.</p>
customised by the user. Rendering its reports to output is
performed by Renderer plug-ins which can also be customised by the
user.</p>
-<h2 id="installation">Installation</h2>
+<h2 id="installation">Installation<a class="headerlink" href="#installation" title="Permanent link">¶</a></h2>
<p>Fetch the Eyeball distribution zipfile and unpack it somewhere
convenient. Eyeball 2.1 comes with its own copy of Jena 2.5 with CVS updates.
Do <em>not</em> attempt to use other versions of Jena with Eyeball.
@@ -196,7 +207,7 @@ mailing list or file a Jira issue.</p>
<p>If the tests have passed, you can use Eyeball from the installation
directory, or copy <em>lib</em>, <em>etc</em> and <em>mirror</em> to somewhere
convenient.</p>
-<h2 id="command-line-operation">Command line operation</h2>
+<h2 id="command-line-operation">Command line operation<a class="headerlink" href="#command-line-operation" title="Permanent link">¶</a></h2>
<p>You must ensure that <em>all</em> the Eyeball jars from <em>lib</em> are on your
classpath. (Note that Eyeball comes with its own Jena jar files and
<em>may not work</em> with other Jena jars.) The directories <em>etc</em> and
@@ -226,7 +237,7 @@ file manager to possibly map those names
<code>http:</code> URL to a local cached copy). See the
<a href="../notes/file-manager.html">file manager howto</a>
for details on how to configure the file manager.</p>
-<h3 id="examples-of-command-line-use">Examples of command-line use</h3>
+<h3 id="examples-of-command-line-use">Examples of command-line use<a class="headerlink" href="#examples-of-command-line-use" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="n">java</span> <span class="n">jena</span><span class="p">.</span><span class="n">eyeball</span> <span class="o">-</span><span class="n">version</span>
<span class="n">java</span> <span class="n">jena</span><span class="p">.</span><span class="n">eyeball</span> <span class="o">-</span><span class="n">check</span> <span class="n">myDataFile</span><span class="p">.</span><span class="n">rdf</span>
@@ -241,7 +252,7 @@ for details on how to configure the file
</pre></div>
-<h3 id="-check-specialurl">-check specialURL+</h3>
+<h3 id="-check-specialurl">-check specialURL+<a class="headerlink" href="#-check-specialurl" title="Permanent link">¶</a></h3>
<p>The <em>-check</em> command checks the specified models for problems. The
<em>specialURL</em>s designate the models to be checked. In the simplest
case, these are plain filenames, <code>file:</code> URLs, or <code>http:</code> URLs. At
@@ -282,7 +293,7 @@ specified independently using the <em>je
</pre></div>
-<h3 id="-config-fileorurl-and-root-rooturi">-config fileOrURL and -root rootURI</h3>
+<h3 id="-config-fileorurl-and-root-rooturi">-config fileOrURL and -root rootURI<a class="headerlink" href="#-config-fileorurl-and-root-rooturi" title="Permanent link">¶</a></h3>
<p>The <em>-config fileOrURL</em> options specify the Eyeball
<a href="../assembler/index.html">assembler</a>
configuration files to load. A single configuration model is
@@ -306,7 +317,7 @@ the configuration file.</p>
</pre></div>
-<h3 id="-set-setting42">-set Setting*</h3>
+<h3 id="-set-setting42">-set Setting*<a class="headerlink" href="#-set-setting42" title="Permanent link">¶</a></h3>
<p>The <em>-set</em> option allows command-line tweaks to the configuration,
<em>eg</em> for enabling checking URIs for empty local names.
<em>You will rarely need to use this</em>; it is presented here because of
@@ -343,7 +354,7 @@ URIs with empty local names, use:</p>
<p>Note the nested different quotes required to pass 'true' to Eyeball
so that it can interpret this as a literal.</p>
-<h3 id="-include-exclude-shortnames">-include/-exclude shortNames</h3>
+<h3 id="-include-exclude-shortnames">-include/-exclude shortNames<a class="headerlink" href="#-include-exclude-shortnames" title="Permanent link">¶</a></h3>
<p>The various Eyeball inspectors are given <em>short names</em> in the
configuration file. By default, an Eyeball check uses a specific
set of inspectors with short name <em>defaultInspectors</em>. Additional
@@ -358,7 +369,7 @@ configure inspectors.</p>
</pre></div>
-<h3 id="-assume-reference">-assume Reference</h3>
+<h3 id="-assume-reference">-assume Reference<a class="headerlink" href="#-assume-reference" title="Permanent link">¶</a></h3>
<p>The -assume <em>Reference</em>s identifies any assumed schemas used to
specify the predicates and classes of the data model. The reference
may be a file name or a URL (and may be mapped by the file
@@ -373,7 +384,7 @@ to the Dublin Core terms schema, and <em
</pre></div>
-<h3 id="-sign-and-accept-experimental">-sign and -accept (experimental)</h3>
+<h3 id="-sign-and-accept-experimental">-sign and -accept (experimental)<a class="headerlink" href="#-sign-and-accept-experimental" title="Permanent link">¶</a></h3>
<p>If <em>-sign</em> is specified, Eyeball first does a <em>-check</em>. If no
problem reports are generated, Eyeball writes a <em>signed</em> version of
the current model to the standard output. The signature records the
@@ -392,18 +403,18 @@ the desired properties, without having t
validation checks every time a model is loaded.</p>
<p><em>Important</em>. Model signing is intended to catch careless mistakes,
not for security against malicious users.</p>
-<h3 id="-version">-version</h3>
+<h3 id="-version">-version<a class="headerlink" href="#-version" title="Permanent link">¶</a></h3>
<p>Eyeball will print its version on the standard error stream
(currently "<em>Eyeball 2.1 (Nova Embers)</em>").</p>
-<h3 id="-remark">-remark</h3>
+<h3 id="-remark">-remark<a class="headerlink" href="#-remark" title="Permanent link">¶</a></h3>
<p>Normally Eyeball issues its report or signed model to the standard
output and exits with code 0 (success) or 1 (failure) with no
additional output. Specifying <em>-remark</em> causes it to report
<em>success</em> or <em>some problems reported</em> to standard error.</p>
-<h3 id="-repair-and-analyse-experimental">-repair and -analyse (experimental)</h3>
+<h3 id="-repair-and-analyse-experimental">-repair and -analyse (experimental)<a class="headerlink" href="#-repair-and-analyse-experimental" title="Permanent link">¶</a></h3>
<p>These operations are not currently documented. Try them at your
peril: <em>-repair</em> may attempt to update your models.</p>
-<h3 id="-render-name">-render Name</h3>
+<h3 id="-render-name">-render Name<a class="headerlink" href="#-render-name" title="Permanent link">¶</a></h3>
<p>The eyeball reports are written to the standard output; by default,
the reports appear as text (RDF rendered by omitting the subjects -
which are all blank nodes - and lightly prettifying the predicate
@@ -416,7 +427,7 @@ associates renderer names with their cla
</pre></div>
-<h3 id="setting-the-proxy">setting the proxy</h3>
+<h3 id="setting-the-proxy">setting the proxy<a class="headerlink" href="#setting-the-proxy" title="Permanent link">¶</a></h3>
<p>If any of the data or schema are identified by an http: URL, and
you are behind a firewall, you will need specify the proxy to Java
using system properties; one way to do this is by using the Java
@@ -427,30 +438,30 @@ command line options:</p>
</pre></div>
-<h2 id="inspectors-shipped-with-eyeball">Inspectors shipped with Eyeball</h2>
+<h2 id="inspectors-shipped-with-eyeball">Inspectors shipped with Eyeball<a class="headerlink" href="#inspectors-shipped-with-eyeball" title="Permanent link">¶</a></h2>
<p>Eyeball comes with a collection of inspectors that do relatively
simple checks.</p>
-<h3 id="propertyinspector-short-name-property">PropertyInspector (short name: "property")</h3>
+<h3 id="propertyinspector-short-name-property">PropertyInspector (short name: "property")<a class="headerlink" href="#propertyinspector-short-name-property" title="Permanent link">¶</a></h3>
<p>Checks that every predicate that appears in the model is declared
in some <em>-assume</em>d schema or <code>owl:import</code>ed model -- that is, is
given <code>rdf:type</code> <code>rdf:Property</code> or some subclass of it.</p>
-<h3 id="classinspector-short-name-presumed-class">ClassInspector (short name: "presumed-class")</h3>
+<h3 id="classinspector-short-name-presumed-class">ClassInspector (short name: "presumed-class")<a class="headerlink" href="#classinspector-short-name-presumed-class" title="Permanent link">¶</a></h3>
<p>Checks that every resource in the model that is used as a class,
<em>ie</em> that appears as the object of an <code>rdf:type</code>, <code>rdfs:domain</code>, or
<code>rdfs:range</code> statement, or as the subject or object of an
<code>rdfs:subClassOf</code> statement, has been declared as a <code>Class</code> in the
<em>-assume</em>d schemas or in the model under test.</p>
-<h3 id="uriinspector-short-name-uri">URIInspector (short name: "URI")</h3>
+<h3 id="uriinspector-short-name-uri">URIInspector (short name: "URI")<a class="headerlink" href="#uriinspector-short-name-uri" title="Permanent link">¶</a></h3>
<p>Checks that every URI in the model is well-formed according to the
rules of the Jena IRI library. May apply additional rules specified
in the configuration file: see
<a href="#uri-configuration">uri configuration</a> later for details.</p>
-<h3 id="literalinspector-short-name-literal">LiteralInspector (short name: "literal")</h3>
+<h3 id="literalinspector-short-name-literal">LiteralInspector (short name: "literal")<a class="headerlink" href="#literalinspector-short-name-literal" title="Permanent link">¶</a></h3>
<p>Checks literals for syntactically correct language codes,
syntactically correct datatype URIs (using the same rules as the
URIInspector), and conformance of the lexical form of typed
literals to their datatype.</p>
-<h3 id="prefixinspector-short-name-prefix">PrefixInspector (short name: "prefix")</h3>
+<h3 id="prefixinspector-short-name-prefix">PrefixInspector (short name: "prefix")<a class="headerlink" href="#prefixinspector-short-name-prefix" title="Permanent link">¶</a></h3>
<p>The PrefixInspector checks that the prefix declarations of the
model have namespaces that are valid URIs and that if the prefix
name is "well-known" (<code>rdf</code>, <code>rdfs</code>, <code>owl</code>, <code>xsd</code>, and <code>dc</code>) then
@@ -459,7 +470,7 @@ the associated URI is the one usually as
an Jena automatically-generated prefix, <code>j.<i>Number</i></code>. (Jena
generates these prefixes when writing RDF/XML if the XML
syntactically requires a prefix but the model hasn't defined one.)</p>
-<h3 id="vocabularyinspector-short-name-vocabulary">VocabularyInspector (short name: "vocabulary")</h3>
+<h3 id="vocabularyinspector-short-name-vocabulary">VocabularyInspector (short name: "vocabulary")<a class="headerlink" href="#vocabularyinspector-short-name-vocabulary" title="Permanent link">¶</a></h3>
<p>Checks that every URI in the model with a namespace which is
mentioned in some schema is one of the URIs declared for that
namespace -- that is, it assumes that the schemas define a closed
@@ -467,24 +478,24 @@ set of URIs.</p>
<p>The inspector may be configured to suppress this check for
specified namespaces: see
<a href="#configure-vocabulary">vocabulary configuration</a> later.</p>
-<h3 id="owlsyntaxinspector-short-name-owl">OwlSyntaxInspector (short name: "owl")</h3>
+<h3 id="owlsyntaxinspector-short-name-owl">OwlSyntaxInspector (short name: "owl")<a class="headerlink" href="#owlsyntaxinspector-short-name-owl" title="Permanent link">¶</a></h3>
<p>This inspector looks for "suspicious restrictions" which have some
of the OWL restriction properties but not exactly one
owl:onProperty and exactly one constraint (owl:allValuesFrom,
etc).</p>
-<h3 id="sparqldriveninspector-short-name-sparql">SparqlDrivenInspector (short name: "sparql")</h3>
+<h3 id="sparqldriveninspector-short-name-sparql">SparqlDrivenInspector (short name: "sparql")<a class="headerlink" href="#sparqldriveninspector-short-name-sparql" title="Permanent link">¶</a></h3>
<p>The SparqlDrivenInspector is configured according to
<a href="#sparql-driven">configuring the SPARQL-driven inspector</a>, and
applies arbitrary SPARQL queries to the model. The queries can be
required to match or prohibited from matching; a problem is
reported if the constraint fails.</p>
-<h3 id="alltypedinspector-short-name-all-typed">AllTypedInspector (short name: "all-typed")</h3>
+<h3 id="alltypedinspector-short-name-all-typed">AllTypedInspector (short name: "all-typed")<a class="headerlink" href="#alltypedinspector-short-name-all-typed" title="Permanent link">¶</a></h3>
<p>Checks that all URI and bnode resources in the model have an
rdf:type property in the model or the schema(s). If there is a
statement in the confiuration with property <code>eye:checkLiteralTypes</code>
and value <code>eye:true</code>, also checks that every literal has a type or
a language. <em>Not</em> in the default set of inspectors.</p>
-<h3 id="consistenttypeinspector-short-name-consistent-type">ConsistentTypeInspector (short name: "consistent-type")</h3>
+<h3 id="consistenttypeinspector-short-name-consistent-type">ConsistentTypeInspector (short name: "consistent-type")<a class="headerlink" href="#consistenttypeinspector-short-name-consistent-type" title="Permanent link">¶</a></h3>
<p>Checks that every subject in the model can be given a type which is
the intersection of the subclasses of all its "attached" types -- a
"consistent type".</p>
@@ -492,7 +503,7 @@ the intersection of the subclasses of al
<code>Right</code>, with <code>Left</code> and <code>Right</code> both being subtypes of <code>Top</code> and
with no other subclass statements, then some <code>S</code> with <code>rdf:type</code>s
<code>Left</code> and <code>Right</code> would generate this warning.</p>
-<h3 id="cardinalityinspector-short-name-cardinality">CardinalityInspector (short name: "cardinality")</h3>
+<h3 id="cardinalityinspector-short-name-cardinality">CardinalityInspector (short name: "cardinality")<a class="headerlink" href="#cardinalityinspector-short-name-cardinality" title="Permanent link">¶</a></h3>
<p>Looks for classes <em>C</em> that are subclasses of cardinality
restrictions on some property <em>P</em> with cardinality range <em>min</em> to
<em>max</em>. For any <em>X</em> of <code>rdf:type</code> <em>C</em>, it checks that the number of
@@ -502,7 +513,7 @@ it isn't.</p>
lexical form) are distinct. Resources are counted as distinct if
they have different case-sensitive URIs: the CardinalityInspector
takes no account of <code>owl:sameAs</code> statements.</p>
-<h3 id="listinspector-short-name-list">ListInspector (short name: "list")</h3>
+<h3 id="listinspector-short-name-list">ListInspector (short name: "list")<a class="headerlink" href="#listinspector-short-name-list" title="Permanent link">¶</a></h3>
<p>The ListInspector performs two separate checks:</p>
<ul>
<li>looks for lists that are ill-formed by having multiple or
@@ -528,7 +539,7 @@ also subclasses of any bnode (such as th
an object either <code>rdf:first</code> or <code>rdf:rest</code> is a subclass defined by
the full idiom above: if not, it reports it as a
<code>suspectListIdiom</code>.</p>
-<h2 id="eyeball-problem-reports">Eyeball problem reports</h2>
+<h2 id="eyeball-problem-reports">Eyeball problem reports<a class="headerlink" href="#eyeball-problem-reports" title="Permanent link">¶</a></h2>
<p>Eyeball generates its reports as <em>items</em> in a model. Each item has
<code>rdf:type</code> <code>eye:Item</code>, and its other properties determine what
problem report it is. The default text renderer displays a
@@ -537,21 +548,21 @@ complete report structure.</p>
<p>One of the item's properties is its <em>main property</em>, which
identifies the problem; the others are qualifications supplying
additional detail.</p>
-<h3 id="propertyinspector-predicate-not-declared">PropertyInspector: predicate not declared</h3>
+<h3 id="propertyinspector-predicate-not-declared">PropertyInspector: predicate not declared<a class="headerlink" href="#propertyinspector-predicate-not-declared" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">unknownPredicate</span> "<span class="o">*</span><span class="n">URIString</span><span class="o">*</span>"<span class="p">.</span>
</pre></div>
<p>The predicate with the given URI is not defined in any of the
<em>-assumed</em> schemas.</p>
-<h3 id="classinspector-class-not-declared">ClassInspector: class not declared</h3>
+<h3 id="classinspector-class-not-declared">ClassInspector: class not declared<a class="headerlink" href="#classinspector-class-not-declared" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">unknownClass</span> "<span class="o">*</span><span class="n">URIString</span><span class="o">*</span>"<span class="p">.</span>
</pre></div>
<p>The resource with the given URI is used as a Class, but not defined
in any of the <em>-assumed</em> schemas.</p>
-<h3 id="uriinspector-bad-uri">URIInspector: bad URI</h3>
+<h3 id="uriinspector-bad-uri">URIInspector: bad URI<a class="headerlink" href="#uriinspector-bad-uri" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">badURI</span> "<span class="o">*</span><span class="n">URIString</span><span class="o">*</span>"<span class="p">;</span> <span class="nb">eye</span><span class="p">:</span><span class="n">forReason</span> <span class="o">*</span><span class="n">Reason</span><span class="o">*</span><span class="p">.</span>
</pre></div>
@@ -559,7 +570,7 @@ in any of the <em>-assumed</em> schemas.
<p>The <em>URIString</em> isn't legal as a URI, or is legal but fails a
user-specified spelling constraint. <em>Reason</em> is a resource or
string identifying the reason.</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>reason</th>
@@ -617,28 +628,28 @@ string identifying the reason.</p>
</tr>
</tbody>
</table>
-<h3 id="literalinspector-illegal-language-code">LiteralInspector: illegal language code</h3>
+<h3 id="literalinspector-illegal-language-code">LiteralInspector: illegal language code<a class="headerlink" href="#literalinspector-illegal-language-code" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">badLanguage</span> "<span class="o">*</span><span class="n">badCode</span><span class="o">*</span>"<span class="p">;</span> <span class="nb">eye</span><span class="p">:</span><span class="n">onLiteral</span> "<span class="o">*</span><span class="n">spelling</span><span class="o">*</span>"<span class="p">.</span>
</pre></div>
<p>A literal with the lexical form <em>spelling</em> has the illegal language
code <em>badCode</em>.</p>
-<h3 id="literalinspector-bad-datatype-uri">LiteralInspector: bad datatype URI</h3>
+<h3 id="literalinspector-bad-datatype-uri">LiteralInspector: bad datatype URI<a class="headerlink" href="#literalinspector-bad-datatype-uri" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">badDatatypeURI</span> "<span class="o">*</span><span class="n">badURI</span><span class="o">*</span>"<span class="p">;</span> <span class="nb">eye</span><span class="p">:</span><span class="n">onLiteral</span> "<span class="o">*</span><span class="n">spelling</span><span class="o">*</span>"<span class="p">.</span>
</pre></div>
<p>A literal with the lexical form <em>spelling</em> has the illegal datatype
URI <em>badURI</em>.</p>
-<h3 id="literalinspector-bad-lexical-form">LiteralInspector: bad lexical form</h3>
+<h3 id="literalinspector-bad-lexical-form">LiteralInspector: bad lexical form<a class="headerlink" href="#literalinspector-bad-lexical-form" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">badLexicalForm</span> "<span class="o">*</span><span class="n">spelling</span><span class="o">*</span>"<span class="p">;</span> <span class="nb">eye</span><span class="p">:</span><span class="n">forDatatype</span> "<span class="o">*</span><span class="n">dtURI</span><span class="o">*</span>"<span class="p">.</span>
</pre></div>
<p>A literal with the datatype URI <em>dtURI</em> has the lexical form
<em>spelling</em>, which isn't legal for that datatype.</p>
-<h3 id="prefixinspector-bad-namespace-uri">PrefixInspector: bad namespace URI</h3>
+<h3 id="prefixinspector-bad-namespace-uri">PrefixInspector: bad namespace URI<a class="headerlink" href="#prefixinspector-bad-namespace-uri" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">badNamespaceURI</span> "<span class="o">*</span><span class="n">URIString</span><span class="o">*</span>" <span class="p">;</span> <span class="nb">eye</span><span class="p">:</span><span class="n">onPrefix</span> "<span class="o">*</span><span class="n">prefix</span><span class="o">*</span>" <span class="p">;</span> <span class="nb">eye</span><span class="p">:</span><span class="n">forReason</span> <span class="o">*</span><span class="n">Reason</span><span class="o">*</span><span class="p">.</span>
</pre></div>
@@ -646,28 +657,28 @@ URI <em>badURI</em>.</p>
<p>The namespace <em>URIString</em> for the declaration of <em>prefix</em> is
suspicious for the given <em>Reason</em> (see the URIInspector reports for
details of the possible reasons).</p>
-<h3 id="prefixinspector-jena-prefix-found">PrefixInspector: Jena prefix found</h3>
+<h3 id="prefixinspector-jena-prefix-found">PrefixInspector: Jena prefix found<a class="headerlink" href="#prefixinspector-jena-prefix-found" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">jenaPrefixFound</span> "<span class="o">*</span><span class="nb">j</span><span class="p">.</span><span class="n">Digits</span><span class="o">*</span>"<span class="p">;</span> <span class="nb">eye</span><span class="p">:</span><span class="n">forNamespace</span> "<span class="o">*</span><span class="n">URIString</span><span class="o">*</span>"<span class="p">.</span>
</pre></div>
<p>The namespace <em>URIString</em> has an automatically-generated Jena
prefix.</p>
-<h3 id="prefixinspector-multiple-prefixes-for-namespace">PrefixInspector: multiple prefixes for namespace</h3>
+<h3 id="prefixinspector-multiple-prefixes-for-namespace">PrefixInspector: multiple prefixes for namespace<a class="headerlink" href="#prefixinspector-multiple-prefixes-for-namespace" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre>[] eye:multiplePrefixesForNamespace "*NameSpace*" ; eye:onPrefix "*prefix<span class="nt"><sub></span>1<span class="nt"></sub></span>"* ...
</pre></div>
<p>There are multiple prefix declarations for <em>NameSpace</em>, namely,
<em>prefix<sub>1</sub></em> etc.</p>
-<h3 id="vocabularyinspector-not-from-schema">VocabularyInspector: not from schema</h3>
+<h3 id="vocabularyinspector-not-from-schema">VocabularyInspector: not from schema<a class="headerlink" href="#vocabularyinspector-not-from-schema" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">notFromSchema</span> "<span class="o">*</span><span class="n">NameSpace</span><span class="o">*</span>"<span class="p">;</span> <span class="nb">eye</span><span class="p">:</span><span class="n">onResource</span> <span class="o">*</span><span class="n">Resource</span><span class="o">*</span><span class="p">.</span>
</pre></div>
<p>The <em>Resource</em> has a URI in the <em>NameSpace</em>, but isn't declared in
the schema associated with that <em>NameSpace</em>.</p>
-<h3 id="owlsyntaxinspector-suspicious-restriction">OwlSyntaxInspector: suspicious restriction</h3>
+<h3 id="owlsyntaxinspector-suspicious-restriction">OwlSyntaxInspector: suspicious restriction<a class="headerlink" href="#owlsyntaxinspector-suspicious-restriction" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">suspiciousRestriction</span> <span class="o">*</span><span class="n">R</span><span class="o">*</span><span class="p">;</span> <span class="nb">eye</span><span class="p">:</span><span class="n">forReason</span> <span class="o">*</span><span class="n">Reason</span><span class="o">*</span><span class="p">...</span>
</pre></div>
@@ -689,7 +700,7 @@ the schema associated with that <em>Name
<p>The restriction <em>R</em> is identified by (a) supplying its immediate
properties, and (b) identifying its named equivalent classes and
subclasses.</p>
-<h3 id="sparqldriveninspector-require-failed">SparqlDrivenInspector: require failed</h3>
+<h3 id="sparqldriveninspector-require-failed">SparqlDrivenInspector: require failed<a class="headerlink" href="#sparqldriveninspector-require-failed" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">sparqlRequireFailed</span> "<span class="o">*</span><span class="n">message</span><span class="o">*</span>"<span class="p">.</span>
</pre></div>
@@ -697,7 +708,7 @@ subclasses.</p>
<p>A SPARQL query that was required to succeed against the model did
not. The <em>message</em> is either the query that failed or a meaningful
description, depending on the inspector configuration.</p>
-<h3 id="sparqldriveninspector-prohibit-failed">SparqlDrivenInspector: prohibit failed</h3>
+<h3 id="sparqldriveninspector-prohibit-failed">SparqlDrivenInspector: prohibit failed<a class="headerlink" href="#sparqldriveninspector-prohibit-failed" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">sparqlProhibitFailed</span> "<span class="o">*</span><span class="n">message</span><span class="o">*</span>"<span class="p">.</span>
</pre></div>
@@ -705,7 +716,7 @@ description, depending on the inspector
<p>A SPARQL query that was required to fail against the model did not.
The <em>message</em> is either the query that succeeded or a meaningful
description, depending on the inspector configuration.</p>
-<h3 id="alltypedinspector-should-have-type">AllTypedInspector: should have type</h3>
+<h3 id="alltypedinspector-should-have-type">AllTypedInspector: should have type<a class="headerlink" href="#alltypedinspector-should-have-type" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">shouldHaveType</span> <span class="o">*</span><span class="n">Resource</span><span class="o">*</span><span class="p">.</span>
</pre></div>
@@ -714,7 +725,7 @@ description, depending on the inspector
inference, this report is unlikely, since inference may well give
the resource a type even if it has no explicit type in the original
model.</p>
-<h3 id="consistenttypeinspector-inconsistent-types-for-resource">ConsistentTypeInspector: inconsistent types for resource</h3>
+<h3 id="consistenttypeinspector-inconsistent-types-for-resource">ConsistentTypeInspector: inconsistent types for resource<a class="headerlink" href="#consistenttypeinspector-inconsistent-types-for-resource" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre>[] eye:noConsistentTypeFor *URI* ; eye:hasAttachedType *TypeURI<span class="nt"><sub></span>i<span class="nt"></sub></span>*
...
</pre></div>
@@ -734,7 +745,7 @@ with.</p>
<p>While, technically, a resource with no attached types at all is
automatically inconsistent, Eyeball quietly ignores such resources,
since they turn up quite often in simple RDF models.</p>
-<h3 id="cardinalityinspector-cardinality-failure">CardinalityInspector: cardinality failure</h3>
+<h3 id="cardinalityinspector-cardinality-failure">CardinalityInspector: cardinality failure<a class="headerlink" href="#cardinalityinspector-cardinality-failure" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">cardinalityFailure</span> <span class="o">*</span><span class="n">Subject</span><span class="o">*</span><span class="p">;</span> <span class="nb">eye</span><span class="p">:</span><span class="n">onType</span> <span class="o">*</span><span class="n">T</span><span class="o">*</span><span class="p">;</span> <span class="nb">eye</span><span class="p">:</span><span class="n">onProperty</span> <span class="o">*</span><span class="n">P</span><span class="o">*</span>
</pre></div>
@@ -752,7 +763,7 @@ values found:</p>
<li><code>eye:values</code> <em>Set</em>: A blank node of type <code>eye:Set</code> with an
<code>rdfs:member</code> value for each of the values of <em>P</em>.</li>
</ul>
-<h3 id="listinspector-ill-formed-list">ListInspector: ill-formed list</h3>
+<h3 id="listinspector-ill-formed-list">ListInspector: ill-formed list<a class="headerlink" href="#listinspector-ill-formed-list" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre>[] eye:illFormedList *URI* ; eye:because [eye:element *index<span class="nt"><sub></span>i<span class="nt"></sub></span>*; *Problem<span class="nt"><sub></span>i~*]~i<span class="nt"></sub></span> ...
</pre></div>
@@ -767,15 +778,15 @@ index <em>index<sub>i</sub></em> had <em
<li><code>eye:hasMultipleFirsts</code> -- the element has more than one
<code>rdf:rest</code> property.</li>
</ul>
-<h3 id="listinspector-suspect-list-idiom">ListInspector: suspect list idiom</h3>
+<h3 id="listinspector-suspect-list-idiom">ListInspector: suspect list idiom<a class="headerlink" href="#listinspector-suspect-list-idiom" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="nb">eye</span><span class="p">:</span><span class="n">suspectListIdiom</span> <span class="o">*</span><span class="n">Type</span><span class="o">*</span><span class="p">.</span>
</pre></div>
<p>The resource <em>Type</em> looks like it's supposed to be a use of the
"typed list idiom", but it isn't complete/accurate.</p>
-<h2 id="inside-the-eyeball-configuration-file">Inside the Eyeball configuration file</h2>
-<h3 id="configuration-files">Configuration files</h3>
+<h2 id="inside-the-eyeball-configuration-file">Inside the Eyeball configuration file<a class="headerlink" href="#inside-the-eyeball-configuration-file" title="Permanent link">¶</a></h2>
+<h3 id="configuration-files">Configuration files<a class="headerlink" href="#configuration-files" title="Permanent link">¶</a></h3>
<p>The Eyeball command-line utility is configured by files (or URLs)
specified on the command line: their RDF contents are unioned
together into a single config model. If no config file is
@@ -790,7 +801,7 @@ default. You can provide your own <em>et
earlier on your classpath or in your current directory; this config
replaces the default. You may provide <em>additional</em> location-mapping
files earlier on your classpath or in your current directory.</p>
-<h3 id="configuring-schema-names">Configuring schema names</h3>
+<h3 id="configuring-schema-names">Configuring schema names<a class="headerlink" href="#configuring-schema-names" title="Permanent link">¶</a></h3>
<p>To avoid having to quote schema names in full on the Eyeball
command line, (collections of) schemas can be given short names.
[] eye:shortName shortNameLiteral
@@ -801,7 +812,7 @@ command line, (collections of) schemas c
short names <em>rdf</em>, <em>rdfs</em>, <em>owl</em>, and <em>dc</em> for the corresponding
schemas (and mirror versions of those schemas so that they don't
need to be downloaded each time Eyeball is run.)</p>
-<h3 id="configuring-inspectors">Configuring inspectors</h3>
+<h3 id="configuring-inspectors">Configuring inspectors<a class="headerlink" href="#configuring-inspectors" title="Permanent link">¶</a></h3>
<p>The inspectors that Eyeball runs over the model are specfied by
<em>eye:inspector</em> properties of inspector resources. These resources
are identified by <code>eye:shortName</code>s (supplied on the command line).
@@ -814,7 +825,7 @@ include their inspectors, using either o
property should be another inspector resource; the value of an
<code>includeByName</code> property should be the <code>shortName</code> of an inspector
resource.</p>
-<h3 id="configuring-the-uri-inspector">Configuring the URI inspector</h3>
+<h3 id="configuring-the-uri-inspector">Configuring the URI inspector<a class="headerlink" href="#configuring-the-uri-inspector" title="Permanent link">¶</a></h3>
<p>As well as applying the standard URI rules, Eyeball allows extra
pattern-oriented checks to be applied to URIs. These are specified
by <code>eye:check</code> properties of the <code>URIInspector</code> object in the
@@ -851,7 +862,7 @@ This is sometimes confusing.</p>
<code>eye:reportEmptyLocalNames</code> to the inspector <code>eye:URIInspector</code>
with the property value <code>true</code>. You may edit the configuration file
or use the <code>-set</code> command-line option.</p>
-<h3 id="configuring-the-vocabulary-inspector">Configuring the vocabulary inspector</h3>
+<h3 id="configuring-the-vocabulary-inspector">Configuring the vocabulary inspector<a class="headerlink" href="#configuring-the-vocabulary-inspector" title="Permanent link">¶</a></h3>
<p>The vocabulary inspector defaults to assuming that schema
namespaces are closed. To disable this for specified namespaces,
the inspector object in the configuration can be given
@@ -863,7 +874,7 @@ not report problems.</p>
</pre></div>
-<h3 id="configuring-the-sparql-driven-inspector">Configuring the SPARQL-driven inspector</h3>
+<h3 id="configuring-the-sparql-driven-inspector">Configuring the SPARQL-driven inspector<a class="headerlink" href="#configuring-the-sparql-driven-inspector" title="Permanent link">¶</a></h3>
<p>The SPARQL inspector object in the configuration may be given
<code>eye:sparql</code> properties whose objects are resources specifying
SPARQL queries and problem messages.</p>
@@ -891,7 +902,7 @@ replaced by "@".</p>
<p>Using <code>eye:prohibit</code> rather than <code>eye:require</code> means that the
problem is reported if the query succeeds, rather than if it
fails.</p>
-<h3 id="configuring-renderers">Configuring renderers</h3>
+<h3 id="configuring-renderers">Configuring renderers<a class="headerlink" href="#configuring-renderers" title="Permanent link">¶</a></h3>
<p>The renderer class that Eyeball uses to render the report into text
is giving in the config file by triples of the form:</p>
<div class="codehilite"><pre><span class="p">[]</span>
@@ -917,10 +928,10 @@ strings which are used to render resourc
<p>The model names are strings which are interpreted by Jena's
<code>FileManager</code>, so they may be redirected using Jena's file
mappings.</p>
-<h2 id="inside-the-eyeball-code">Inside the Eyeball code</h2>
+<h2 id="inside-the-eyeball-code">Inside the Eyeball code<a class="headerlink" href="#inside-the-eyeball-code" title="Permanent link">¶</a></h2>
<p>Eyeball can be used from within Java code; the command line merely
provides a convenient external interface.</p>
-<h3 id="creating-an-eyeball">Creating an Eyeball</h3>
+<h3 id="creating-an-eyeball">Creating an Eyeball<a class="headerlink" href="#creating-an-eyeball" title="Permanent link">¶</a></h3>
<p>An Eyeball object has three subcomponents: the assumptions against
which the model is to be checked, the inspectors which do the
checking, and the renderer used to display the reports.</p>
@@ -938,7 +949,7 @@ interface.</p>
</pre></div>
-<h3 id="to-eyeball-a-model">To eyeball a model</h3>
+<h3 id="to-eyeball-a-model">To eyeball a model<a class="headerlink" href="#to-eyeball-a-model" title="Permanent link">¶</a></h3>
<p>Models to be inspected are provided as OntModels. The problems are
delivered to a Report object, where they are represented as an RDF
model.</p>
@@ -953,7 +964,7 @@ EYE vocabulary, and are used in the stan
<p>Every report item in the model is a blank node with
<code>rdf:type eye:Item</code>. See earlier sections for the descriptions of
the properties attached to an Item.</p>
-<h2 id="rebuilding-eyeball">Rebuilding Eyeball</h2>
+<h2 id="rebuilding-eyeball">Rebuilding Eyeball<a class="headerlink" href="#rebuilding-eyeball" title="Permanent link">¶</a></h2>
<p>The provided ant script can be used to rebuild Eyeball from
source:</p>
<div class="codehilite"><pre><span class="n">ant</span> <span class="n">clean</span> <span class="n">build</span> <span class="n">jar</span>
@@ -964,11 +975,11 @@ source:</p>
changes.)</p>
<p>The libraries required by Eyeball are all in the <code>lib</code> directory,
including the necessary Jena jars.</p>
-<h2 id="creating-and-configuring-an-inspector">Creating and configuring an inspector</h2>
+<h2 id="creating-and-configuring-an-inspector">Creating and configuring an inspector<a class="headerlink" href="#creating-and-configuring-an-inspector" title="Permanent link">¶</a></h2>
<p>To make a new inspector available to Eyeball, a new Inspector class
must be created and that class has to be described in the Eyeball
configuration.</p>
-<h3 id="creating-an-inspector">Creating an Inspector</h3>
+<h3 id="creating-an-inspector">Creating an Inspector<a class="headerlink" href="#creating-an-inspector" title="Permanent link">¶</a></h3>
<p>Any inspector must implement the Inspector interface, which has
four operations:</p>
<ul>
@@ -995,7 +1006,7 @@ implementations for all the <code>Inspec
<code>InspectorTestBase</code> useful when writing their inspector's tests,
both for its convenience methods and because it requires that their
class has the appropriate constructors.</p>
-<h3 id="reports-and-report-properties">Reports and report properties</h3>
+<h3 id="reports-and-report-properties">Reports and report properties<a class="headerlink" href="#reports-and-report-properties" title="Permanent link">¶</a></h3>
<p>Eyeball reports are statements in a report model. To let the
renderer know which property of a report is the "main" one, and
which order the other properties should appear in, the inspector's
@@ -1017,7 +1028,7 @@ being inspected; a report renderer will
<p>To add the main property to a report item <code>R</code>, use
<code>R.addMainProperty(P,O)</code>; to add non-main properties, use
<code>R.addProperty(P,O)</code>.</p>
-<h3 id="configuring-an-inspector">Configuring an inspector</h3>
+<h3 id="configuring-an-inspector">Configuring an inspector<a class="headerlink" href="#configuring-an-inspector" title="Permanent link">¶</a></h3>
<p>To add an inspector to a configuration file, choose a URI for it
(here we're using <code>my:Fresh</code> and assuming a prefix declaration for
<code>my:</code>) and a short name (here, "fresh") and add a description to
Modified: websites/staging/jena/trunk/content/documentation/tools/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/tools/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/tools/index.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,15 +144,26 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Command-line and other tools for Jena developers</h1>
- <p>Jena includes various command-line utilities which can help you with
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Jena includes various command-line utilities which can help you with
a variety of tasks in developing Jena-based applications.</p>
-<h3 id="index-of-tools">Index of tools</h3>
+<h3 id="index-of-tools">Index of tools<a class="headerlink" href="#index-of-tools" title="Permanent link">¶</a></h3>
<ul>
<li><a href="schemagen.html">schemagen</a></li>
<li><a href="schemagen-maven.html">using schemagen from maven</a></li>
<li><a href="eyeball-getting-started.html">eyeball</a></li>
</ul>
-<h3 id="setting-up-your-environment">Setting up your Environment</h3>
+<h3 id="setting-up-your-environment">Setting up your Environment<a class="headerlink" href="#setting-up-your-environment" title="Permanent link">¶</a></h3>
<p>An environment variable <code>JENAROOT</code> is used by all the command line tools to configure the class path automatically for you. You can set this up as follows:</p>
<p><strong>On Linux / Mac</strong></p>
<ul>
@@ -164,7 +175,7 @@ a variety of tasks in developing Jena-ba
<li><code>SET JENAROOT=</code><em>the directory you downloaded Jena to</em></li>
<li><code>SET PATH=%PATH%;%JENAROOT%\bat</code></li>
</ul>
-<h3 id="running-the-tools">Running the Tools</h3>
+<h3 id="running-the-tools">Running the Tools<a class="headerlink" href="#running-the-tools" title="Permanent link">¶</a></h3>
<p>Once you've done the above you should now be able to run the tools from the command line like so:</p>
<p><strong>On Linux / Mac</strong></p>
<ul>
@@ -176,7 +187,7 @@ a variety of tasks in developing Jena-ba
</ul>
<p>This command will simply print the versions of Jena and ARQ used in your distribution, all the tools support the <code>--version</code> option. To find out how to use a specific tool add the <code>--help</code> flag instead.</p>
<p>Note that many examples of using Jena tools typically use the Linux style invocation because most of the Jena developers work on Linux/Mac platforms. When running on windows simply add <code>.bat</code> as an extension to the name of the command line tool to run it, on some versions of Windows this may not be required.</p>
-<h3 id="common-issues-with-running-the-tools">Common Issues with Running the Tools</h3>
+<h3 id="common-issues-with-running-the-tools">Common Issues with Running the Tools<a class="headerlink" href="#common-issues-with-running-the-tools" title="Permanent link">¶</a></h3>
<p>If you receive errors stating that a class is not found then it is most likely that <code>JENAROOT</code> is not set correctly. As a quick sanity check you can try the following to see if it is set appropriately:</p>
<p><strong>On Linux / Mac</strong></p>
<ul>
Modified: websites/staging/jena/trunk/content/documentation/tools/schemagen-maven.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/tools/schemagen-maven.html (original)
+++ websites/staging/jena/trunk/content/documentation/tools/schemagen-maven.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title"></h1>
- <h1 id="schemagen-maven-generating-java-source-files-from-owl-and-rdfs-ontologies-via-maven">Schemagen-maven: generating Java source files from OWL and RDFS ontologies via Maven</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="schemagen-maven-generating-java-source-files-from-owl-and-rdfs-ontologies-via-maven">Schemagen-maven: generating Java source files from OWL and RDFS ontologies via Maven<a class="headerlink" href="#schemagen-maven-generating-java-source-files-from-owl-and-rdfs-ontologies-via-maven" title="Permanent link">¶</a></h1>
<p>The <a href="http://jena.apache.org">Apache Jena</a> command line tool
<a href="http://jena.apache.org/documentation/tools/schemagen.html"><code>schemagen</code></a>
provides an automated way of creating
@@ -157,14 +168,14 @@ constants from the ontology.</p>
is sufficient. For projects organised around Apache Maven, it would be convenient to integrate
the schemagen translation step into Maven's normal build process. This plugin
provides a means to do just that.</p>
-<h2 id="pre-requisites">Pre-requisites</h2>
+<h2 id="pre-requisites">Pre-requisites<a class="headerlink" href="#pre-requisites" title="Permanent link">¶</a></h2>
<p>This plugin adds a step to the Maven build process to automatically translate RDFS
and OWL files, encoded as RDF/XML, Turtle or N-triples into Java source files.
This plugin is designed to be used with a Java project that is already using Apache Maven to
control the build. Non-Java projects do not need this tool. Projects that are
not using Maven should see the <a href="schemagen.html">schemagen documentation</a>
for ways to run <code>schemagen</code> from the command line.</p>
-<h2 id="installing">Installing</h2>
+<h2 id="installing">Installing<a class="headerlink" href="#installing" title="Permanent link">¶</a></h2>
<p>Schemagen is available from the maven central repository. To use it, add
the following dependency to your <code>pom.xml</code>:</p>
<div class="codehilite"><pre><span class="nt"><build></span>
@@ -197,7 +208,7 @@ the following dependency to your <code>p
<p>Replace the <code>x.y.z</code> above with the latest versions as found by
browsing <a href="http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/">jena-maven-tools</a>
and <a href="http://central.maven.org/maven2/org/apache/jena/jena-core/">jena-core</a> in Maven Central.</p>
-<h2 id="configuration-basic-principles">Configuration: basic principles</h2>
+<h2 id="configuration-basic-principles">Configuration: basic principles<a class="headerlink" href="#configuration-basic-principles" title="Permanent link">¶</a></h2>
<p>Schemagen supports a large number of options, controlling such things as the name of the
input file, the RDF namespace to expect, which Java package to place the output in and
so forth. For a command line or Ant-based build, these options are normally passed on
@@ -238,7 +249,7 @@ Maven to use the plugin via the <code>&l
browsing <a href="http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/">jena-maven-tools</a>
in Maven Central.</p>
<p>The configuration options all nest inside the <code><configuration></code> section.</p>
-<h3 id="specifying-files-to-process">Specifying files to process</h3>
+<h3 id="specifying-files-to-process">Specifying files to process<a class="headerlink" href="#specifying-files-to-process" title="Permanent link">¶</a></h3>
<p>An <code><include></code> directive specifies one file pattern to include in the set of
files to process. Wildcards may be used. For example, the following section
specifies that the tool will process all Turtle files, and the <code>foaf.rdf</code> file,
@@ -250,7 +261,7 @@ in <code>src/main/vocabs</code>:</p>
</pre></div>
-<h3 id="specifying-processing-options">Specifying processing options</h3>
+<h3 id="specifying-processing-options">Specifying processing options<a class="headerlink" href="#specifying-processing-options" title="Permanent link">¶</a></h3>
<p>Options are, in general, given in the <code><fileOptions></code> section. A given
<code><source></code> refers to one input source - one file - as named by the
<code><input></code> name. The actual option names are taken from the RDF <a href="http://jena.apache.org/documentation/tools/schemagen.html">config
@@ -275,7 +286,7 @@ across all input sources:</p>
</pre></div>
-<h2 id="example-configuration">Example configuration</h2>
+<h2 id="example-configuration">Example configuration<a class="headerlink" href="#example-configuration" title="Permanent link">¶</a></h2>
<p><strong>Note:</strong> Replace the <code>x.y.z</code> below with the latest versions as found by
browsing <a href="http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/">jena-maven-tools</a>
and <a href="http://central.maven.org/maven2/org/apache/jena/jena-core/">jena-core</a> in Maven Central.</p>
Modified: websites/staging/jena/trunk/content/documentation/tools/schemagen.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/tools/schemagen.html (original)
+++ websites/staging/jena/trunk/content/documentation/tools/schemagen.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
Modified: websites/staging/jena/trunk/content/download/index.html
==============================================================================
--- websites/staging/jena/trunk/content/download/index.html (original)
+++ websites/staging/jena/trunk/content/download/index.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,13 +144,24 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Apache Jena Releases</h1>
- <p>Jena is packaged as downloads which contain the most commonly used portions of the systems:</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Jena is packaged as downloads which contain the most commonly used portions of the systems:</p>
<ul>
<li><strong>apache-jena</strong> – contains the APIs, SPARQL engine, the TDB native RDF database and command line tools</li>
<li><strong>apache-jena-fuseki</strong> – the Jena SPARQL server</li>
</ul>
<p>Jena requires Java7 (from Jena version 2.12.0 onwards).</p>
-<h2 id="download-mirrors">Download Mirrors</h2>
+<h2 id="download-mirrors">Download Mirrors<a class="headerlink" href="#download-mirrors" title="Permanent link">¶</a></h2>
<p>[if-any logo]
<a href="[link]">
<img align="right" src="[logo]" border="0" />
@@ -176,7 +187,7 @@ Other mirrors: <select name="Preferred">
</form>
<p>You may also consult the <a href="http://www.apache.org/mirrors/">complete list of mirrors</a></p>
-<h3 id="apache-jena">Apache Jena</h3>
+<h3 id="apache-jena">Apache Jena<a class="headerlink" href="#apache-jena" title="Permanent link">¶</a></h3>
<p>This distribution contains the APIs, SPARQL engine, the TDB native RDF database and a variety of command line scripts and tools for working with these systems.</p>
<p>The binary distribution may be downloaded at:</p>
<p><a href="[preferred]jena/binaries/apache-jena-2.13.0.tar.gz">apache-jena-2.13.0.tar.gz</a>
@@ -189,7 +200,7 @@ Other mirrors: <select name="Preferred">
<p><a href="[preferred]jena/source/jena-2.13.0-source-release.zip">jena-2.13.0-source-release.zip</a>
(<a href="http://www.apache.org/dist/jena/source/jena-2.13.0-source-release.zip.md5">MD5</a>,
<a href="http://www.apache.org/dist/jena/source/jena-2.13.0-source-release.zip.asc">PGP</a>)</p>
-<h3 id="apache-jena-fuseki">Apache Jena Fuseki</h3>
+<h3 id="apache-jena-fuseki">Apache Jena Fuseki<a class="headerlink" href="#apache-jena-fuseki" title="Permanent link">¶</a></h3>
<p>The binary distribution of Fuseki2 (this includes both the standalone and
WAR file packaing) may be downloaded at:</p>
<p><a href="[preferred]jena/binaries/apache-jena-fuseki-2.0.0.tar.gz">apache-jena-fuseki-2.0.0.tar.gz</a>
@@ -198,17 +209,17 @@ WAR file packaing) may be downloaded at:
<p><a href="[preferred]jena/binaries/apache-jena-fuseki-2.0.0.zip">apache-jena-fuseki-2.0.0.zip</a>
(<a href="http://www.apache.org/dist/jena/binaries/apache-jena-fuseki-2.0.0.zip.md5">MD5</a>,
<a href="http://www.apache.org/dist/jena/binaries/apache-jena-fuseki-2.0.0.zip.asc">PGP</a>)</p>
-<p>Fuseki1,bult for the current version of Jena is available at:</p>
+<p>Fuseki1, built for the current version of Jena is available at:</p>
<p><a href="[preferred]jena/binaries/jena-fuseki1-1.1.2-distribution.tar.gz">jena-fuseki1-1.1.2-distribution.tar.gz</a>
(<a href="http://www.apache.org/dist/jena/binaries/jena-fuseki1-1.1.2-distribution.tar.gz.md5">MD5</a>,
<a href="http://www.apache.org/dist/jena/binaries/jena-fuseki1-1.1.2-distribution.tar.gz.asc">PGP</a>)</p>
<p><a href="[preferred]jena/binaries/jena-fuseki1-1.1.2-distribution.zip">jena-fuseki1-1.1.2-distribution.zip</a>
(<a href="http://www.apache.org/dist/jena/binaries/jena-fuseki1-1.1.2-distribution.zip.md5">MD5</a>,
<a href="http://www.apache.org/dist/jena/binaries/jena-fuseki1-1.1.2-distribution.zip.asc">PGP</a>)</p>
-<h3 id="individual-modules">Individual Modules</h3>
+<h3 id="individual-modules">Individual Modules<a class="headerlink" href="#individual-modules" title="Permanent link">¶</a></h3>
<p>Apache Jena publishes a range of modules beyond those included in the binary distributions (code for all modules may be found in the source distribution).</p>
<p>Individual modules may be obtained using a dependency manager which can talk to Maven repositories, some modules are only available via Maven.</p>
-<h4 id="maven">Maven</h4>
+<h4 id="maven">Maven<a class="headerlink" href="#maven" title="Permanent link">¶</a></h4>
<p>See "<a href="maven.html">Using Jena with Apache Maven</a>" for full details.</p>
<div class="codehilite"><pre><span class="nt"><dependency></span>
<span class="nt"><groupId></span>org.apache.jena<span class="nt"></groupId></span>
@@ -219,12 +230,12 @@ WAR file packaing) may be downloaded at:
</pre></div>
-<h4 id="source-code">Source code</h4>
+<h4 id="source-code">Source code<a class="headerlink" href="#source-code" title="Permanent link">¶</a></h4>
<p>The development codebase is available from git.</p>
<p><a href="https://git-wip-us.apache.org/repos/asf?p=jena.git">https://git-wip-us.apache.org/repos/asf?p=jena.git</a></p>
<p>This is mirrored on github:</p>
<p><a href="https://github.com/apache/jena">https://github.com/apache/jena</a></p>
-<h4 id="previous-releases">Previous releases</h4>
+<h4 id="previous-releases">Previous releases<a class="headerlink" href="#previous-releases" title="Permanent link">¶</a></h4>
<p>While previous releases are available, we strongly recommend that wherever
possible users use the latest official Apache releases of Jena in
preference to using any older versions of Jena.</p>
Modified: websites/staging/jena/trunk/content/download/maven.html
==============================================================================
--- websites/staging/jena/trunk/content/download/maven.html (original)
+++ websites/staging/jena/trunk/content/download/maven.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,13 +144,24 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Using Jena with Apache Maven</h1>
- <p><a href="http://maven.apache.org">Apache Maven</a> is a tool to help Java projects manage
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><a href="http://maven.apache.org">Apache Maven</a> is a tool to help Java projects manage
their dependencies on library code, such as Jena. By declaring a dependency on
the core of Jena in your project's <code>pom.xml</code> file, you will get the
consistent set of library files that Jena depends on automatically added too.</p>
<p>This page assumes you have Maven installed on your computer. If this is not the case,
please read and follow <a href="http://maven.apache.org/download.html#Installation">these instructions</a>.</p>
-<h3 id="repositories">Repositories</h3>
+<h3 id="repositories">Repositories<a class="headerlink" href="#repositories" title="Permanent link">¶</a></h3>
<p>Released maven artifacts are mirrored to the central maven repositories.
This can take a few days.</p>
<p>The Jena repositories at Apache are:</p>
@@ -161,7 +172,7 @@ This can take a few days.</p>
<p>Stable Jena releases are automatically mirrored by the central Maven
repositories, so there will normally be no need to add any extra
repositories to your <code>pom.xml</code> or <code>settings.xml</code>.</p>
-<h3 id="specifying-jena-as-a-dependency">Specifying Jena as a dependency</h3>
+<h3 id="specifying-jena-as-a-dependency">Specifying Jena as a dependency<a class="headerlink" href="#specifying-jena-as-a-dependency" title="Permanent link">¶</a></h3>
<p>This is how to specify in your pom.xml file the dependency
on a version of Jena:</p>
<div class="codehilite"><pre> <span class="nt"><dependency></span>
@@ -197,7 +208,7 @@ in the other artifacts.</p>
<p>Please check for the latest versions.</p>
-<h3 id="major-artifacts">Major Artifacts</h3>
+<h3 id="major-artifacts">Major Artifacts<a class="headerlink" href="#major-artifacts" title="Permanent link">¶</a></h3>
<p>Jena provides a number of maven artifacts as delivery points.<br />
There are also a number of maven artifacts used as part of
structuring Jena development.</p>
@@ -292,7 +303,7 @@ The full list can be seen by browsing Ma
<p>(This includes historic artifacts which are no longer active.)</p>
<p>You can run <code>mvn dependency:tree</code> to print the dependency
tree. </p>
-<h3 id="specifying-dependencies-on-snapshots">Specifying dependencies on SNAPSHOTs</h3>
+<h3 id="specifying-dependencies-on-snapshots">Specifying dependencies on SNAPSHOTs<a class="headerlink" href="#specifying-dependencies-on-snapshots" title="Permanent link">¶</a></h3>
<p>If you want to depend on Jena development snapshots, e.g. to get access
to recent bug fixes, you should add the following to your <code>pom.xml</code>:</p>
<div class="codehilite"><pre> <span class="nt"><repository></span>
@@ -308,7 +319,7 @@ to recent bug fixes, you should add the
</pre></div>
-<h3 id="build-and-install-artifacts-in-your-local-maven-repository">Build and install artifacts in your local Maven repository</h3>
+<h3 id="build-and-install-artifacts-in-your-local-maven-repository">Build and install artifacts in your local Maven repository<a class="headerlink" href="#build-and-install-artifacts-in-your-local-maven-repository" title="Permanent link">¶</a></h3>
<p>If you want you can checkout the Jena sources, build the artifacts and
install them in your local Maven repository, then you simply checkout the source
tree and build with maven
Modified: websites/staging/jena/trunk/content/download/osgi.html
==============================================================================
--- websites/staging/jena/trunk/content/download/osgi.html (original)
+++ websites/staging/jena/trunk/content/download/osgi.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
Modified: websites/staging/jena/trunk/content/getting_involved/index.html
==============================================================================
--- websites/staging/jena/trunk/content/getting_involved/index.html (original)
+++ websites/staging/jena/trunk/content/getting_involved/index.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,16 +144,27 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Getting involved in Apache Jena</h1>
- <p>We welcome your contribution towards making Jena a better platform for semantic web and linked data applications.
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>We welcome your contribution towards making Jena a better platform for semantic web and linked data applications.
We appreciate feature suggestions, bug reports and patches for code or documentation.</p>
<p>If you need help using Jena, please see our <a href="../help_and_support">getting help</a> page.</p>
-<h3 id="how-to-contribute">How to contribute</h3>
+<h3 id="how-to-contribute">How to contribute<a class="headerlink" href="#how-to-contribute" title="Permanent link">¶</a></h3>
<p>You can help us sending your suggestions, feature requests and bug reports (as well as patches) using the <a href="https://issues.apache.org/jira/browse/JENA">Jena issue tracker</a>.</p>
<p>You can discuss your contribution, before or after adding it to Jira, on the <a href="mailto:dev@jena.apache.org"><code>dev@jena.apache.org</code></a> mailing list.
You can also help other users by answering their questions on the <a href="mailto:users@jena.apache.org"><code>users@jena.apache.org</code></a> mailing list.
See the <a href="../help_and_support">subscription instructions</a> for details.</p>
<p>Please see the <a href="reviewing_contributions.html">Reviewing Contributions</a> page for details of what committers will be looking for when reviewing contributions.</p>
-<h4 id="improving-the-website">Improving the Website</h4>
+<h4 id="improving-the-website">Improving the Website<a class="headerlink" href="#improving-the-website" title="Permanent link">¶</a></h4>
<p>You can also help us improve the documentation on this website by making use of the Apache CMS which drives the website.</p>
<p>Please see <a href="http://www.apache.org/dev/cmsref#non-committer">I'm not a committer on $project, which uses the CMS. Can I still use the
CMS?</a> for guidance on how to do this. This process allows you to suggest
@@ -161,7 +172,7 @@ improvements to the project website as p
Contributions to documentation are always welcome and considered just as valuable as code contributions.</p>
<p>You can click the <span class="glyphicon glyphicon-pencil"></span><em>Improve this Page</em> button (top-right) on any page to instantly open the web based CMS editor. If prompted you
will need to use the username <code>anonymous</code> and a blank password to log in. Use the <em>[Diff]</em> and <em>[Mail Email]</em> links to submit your proposed changes to the Apache Jena committers.</p>
-<h3 id="snapshots">SNAPSHOTs</h3>
+<h3 id="snapshots">SNAPSHOTs<a class="headerlink" href="#snapshots" title="Permanent link">¶</a></h3>
<p>If you use Apache Maven and you are not afraid of being on the bleeding-edge, you can help us by testing our SNAPSHOTs which you can find in the <a href="https://repository.apache.org/content/repositories/snapshots/org/apache/jena/">Apache Maven repository</a>.</p>
<p>Here is, for example, how you can add TDB version X.Y.Z-SNAPSHOT to your project (please ask if you are unsure what the latest snapshot version number currently is):</p>
<div class="codehilite"><pre><span class="nt"><dependency></span>
@@ -176,7 +187,7 @@ will need to use the username <code>anon
<p>If you have problems with any of our SNAPSHOTs, <a href="/help_and_support/">let us know</a>.</p>
<p>You can check the state of each Jena development builds
on the <a href="https://builds.apache.org/pview/?match=Jena_.*">Apache Jenkins continuous integration server</a>.</p>
-<h3 id="git-repository">Git repository</h3>
+<h3 id="git-repository">Git repository<a class="headerlink" href="#git-repository" title="Permanent link">¶</a></h3>
<p>You can find the Jena source code in the Apache git repository:
<a href="https://git-wip-us.apache.org/repos/asf/jena.git">https://git-wip-us.apache.org/repos/asf/jena.git</a></p>
<p>There is also a read-only mirror of <a href="https://github.com/apache/jena">Jena on GitHub</a>:</p>
@@ -188,10 +199,10 @@ on the <a href="https://builds.apache.or
<p>You can <a href="https://github.com/apache/jena/fork">fork Jena on GitHub</a> and also submit <a href="https://github.com/apache/jena/pulls">pull requests</a> to
contribute your suggested changes to the code.</p>
-<h3 id="open-issues">Open issues</h3>
+<h3 id="open-issues">Open issues<a class="headerlink" href="#open-issues" title="Permanent link">¶</a></h3>
<p>You can find a list of the <a href="https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+JENA+AND+status+%3D+Open+ORDER+BY+priority+DESC&mode=hide">open issues</a> on JIRA (sorted by priority).
Or, you can look at the <a href="https://issues.apache.org/jira/secure/QuickSearch.jspa?searchString=jena+updated:-1w">last week activity</a> to get a sense of what people are working on.</p>
-<h3 id="submit-your-patches">Submit your patches</h3>
+<h3 id="submit-your-patches">Submit your patches<a class="headerlink" href="#submit-your-patches" title="Permanent link">¶</a></h3>
<p>You can develop new contributions and work on patches using either the
Apache-hosted git repository or the <a href="https://github.com/apache/jena">mirror on GitHub</a>. </p>
<p><a href="https://github.com/apache/jena/pulls">GitHub pull requests</a> are forwarded to the
@@ -213,9 +224,9 @@ select <code>Team > Create Patch</cod
</pre></div>
-<h3 id="irc-channel">IRC channel</h3>
+<h3 id="irc-channel">IRC channel<a class="headerlink" href="#irc-channel" title="Permanent link">¶</a></h3>
<p>Some Jena developers hang out on #jena on irc.freenode.net.</p>
-<h3 id="how-apache-software-foundation-works">How Apache Software Foundation works</h3>
+<h3 id="how-apache-software-foundation-works">How Apache Software Foundation works<a class="headerlink" href="#how-apache-software-foundation-works" title="Permanent link">¶</a></h3>
<p>To better understand how to get involved and how the Apache Software Foundation works we recommend you read:</p>
<ul>
<li><a href="http://www.apache.org/foundation/getinvolved.html">http://www.apache.org/foundation/getinvolved.html</a></li>
Modified: websites/staging/jena/trunk/content/getting_involved/reviewing_contributions.html
==============================================================================
--- websites/staging/jena/trunk/content/getting_involved/reviewing_contributions.html (original)
+++ websites/staging/jena/trunk/content/getting_involved/reviewing_contributions.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
Modified: websites/staging/jena/trunk/content/getting_started/fuseki.html
==============================================================================
--- websites/staging/jena/trunk/content/getting_started/fuseki.html (original)
+++ websites/staging/jena/trunk/content/getting_started/fuseki.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,14 +144,25 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Getting starting with serving RDF over HTTP</h1>
- <p><em>Please bear with us, we're in the process of updating this section of the site</em>.
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><em>Please bear with us, we're in the process of updating this section of the site</em>.
This section will shortly contain some example projects illustrating aspects of
using Jena for RDF processing. In the meantime, please see the following
resources for help:</p>
<ul>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
</ul>
-<h2 id="other-resources">Other resources</h2>
+<h2 id="other-resources">Other resources<a class="headerlink" href="#other-resources" title="Permanent link">¶</a></h2>
<p>Jena committer Paolo Castagna has listed some <a href="https://github.com/castagna/jena-examples">example programs</a>
using Jena on his GitHub site.</p>
</div>
Modified: websites/staging/jena/trunk/content/getting_started/index.html
==============================================================================
--- websites/staging/jena/trunk/content/getting_started/index.html (original)
+++ websites/staging/jena/trunk/content/getting_started/index.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Getting started with Apache Jena</h1>
- <p>Apache Jena (or Jena in short) is a free and open source Java
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Apache Jena (or Jena in short) is a free and open source Java
framework for building <a href="http://en.wikipedia.org/wiki/Semantic_Web">semantic web</a> and
<a href="http://linkeddata.org/">Linked Data</a> applications.
The framework is composed of different APIs interacting together to process RDF data. If you are new here, you might want to
Modified: websites/staging/jena/trunk/content/getting_started/rdf_api.html
==============================================================================
--- websites/staging/jena/trunk/content/getting_started/rdf_api.html (original)
+++ websites/staging/jena/trunk/content/getting_started/rdf_api.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">an overview of the Jena RDF API</h1>
- <p><em>Please bear with us, we're in the process of updating this section of the site</em>.
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><em>Please bear with us, we're in the process of updating this section of the site</em>.
This section will shortly contain some example projects illustrating aspects of
using Jena for RDF processing. In the meantime, please see the following
resources for help:</p>
@@ -153,7 +164,7 @@ resources for help:</p>
<li><a href="/tutorials/sparql.html">SPARQL tutorial</a></li>
<li><a href="/documentation/ontology">Ontology API overview</a></li>
</ul>
-<h2 id="other-resources">Other resources</h2>
+<h2 id="other-resources">Other resources<a class="headerlink" href="#other-resources" title="Permanent link">¶</a></h2>
<p>Jena committer Paolo Castagna has listed some <a href="https://github.com/castagna/jena-examples">example programs</a>
using Jena on his GitHub site.</p>
</div>
Modified: websites/staging/jena/trunk/content/getting_started/sparql.html
==============================================================================
--- websites/staging/jena/trunk/content/getting_started/sparql.html (original)
+++ websites/staging/jena/trunk/content/getting_started/sparql.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,14 +144,25 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Getting started with SPARQL queries</h1>
- <p><em>Please bear with us, we're in the process of updating this section of the site</em>.
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><em>Please bear with us, we're in the process of updating this section of the site</em>.
This section will shortly contain some example projects illustrating aspects of
using Jena for RDF processing. In the meantime, please see the following
resources for help:</p>
<ul>
<li><a href="/tutorials/sparql.html">SPARQL tutorial</a></li>
</ul>
-<h2 id="other-resources">Other resources</h2>
+<h2 id="other-resources">Other resources<a class="headerlink" href="#other-resources" title="Permanent link">¶</a></h2>
<p>Jena committer Paolo Castagna has listed some <a href="https://github.com/castagna/jena-examples">example programs</a>
using Jena on his GitHub site.</p>
</div>
Modified: websites/staging/jena/trunk/content/getting_started/tell_me_how.html
==============================================================================
--- websites/staging/jena/trunk/content/getting_started/tell_me_how.html (original)
+++ websites/staging/jena/trunk/content/getting_started/tell_me_how.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Tell me how to ...</h1>
- <p><em>Please bear with us, we're in the process of updating this section of the site</em>.
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p><em>Please bear with us, we're in the process of updating this section of the site</em>.
This section will shortly contain some example patterns and recipes for things we
have found Jena users commonly want to do. If you have a particular need that you
think would be usefully covered in this section, please <a href="https://issues.apache.org/jira/browse/JENA">file a Jira issue</a>