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 2012/03/22 18:35:01 UTC
svn commit: r809594 [3/9] - in /websites/staging/jena/trunk/content: ./
jena/ jena/about_jena/ jena/documentation/ jena/documentation/assembler/
jena/documentation/inference/ jena/documentation/io/
jena/documentation/javadoc/ jena/documentation/larq/ j...
Modified: websites/staging/jena/trunk/content/jena/documentation/larq/index.html
==============================================================================
--- websites/staging/jena/trunk/content/jena/documentation/larq/index.html (original)
+++ websites/staging/jena/trunk/content/jena/documentation/larq/index.html Thu Mar 22 17:34:58 2012
@@ -47,7 +47,7 @@
</div>
<div id="navigation" class="clear">
- <h1 id="quick_links">Quick links</h1>
+ <h1 id="quick-links">Quick links</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/download/index.html">Downloads</a></li>
@@ -57,7 +57,7 @@
<li><a href="/jena/getting_involved/index.html">Getting involved</a></li>
<li><a href="/jena/documentation/">Documentation</a></li>
</ul>
-<h1 id="about_jena">About Jena</h1>
+<h1 id="about-jena">About Jena</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/about_jena/about.html">About Jena</a></li>
@@ -72,12 +72,12 @@
<li><a href="/jena/download/maven.html">Using Maven</a></li>
<li><a href="/jena/download/osgi.html">Using OSGi</a></li>
</ul>
-<h1 id="help_and_support">Help and support</h1>
+<h1 id="help-and-support">Help and support</h1>
<ul>
<li><a href="/jena/help_and_support/index.html">Getting help</a></li>
<li><a href="/jena/help_and_support/bugs_and_suggestions.html">Bugs and suggestions</a></li>
</ul>
-<h1 id="getting_started">Getting Started</h1>
+<h1 id="getting-started">Getting Started</h1>
<ul>
<li><a href="/jena/getting_started/index.html">A first Jena project</a></li>
<li><a href="/jena/getting_started/rdf_api.html">RDF API overview</a></li>
@@ -108,7 +108,7 @@
</ul>
</li>
<li><a href="/jena/documentation/sdb/index.html">SDB</a></li>
-<li><a href="/jena/documentation/larq/index.html">LARQ</a></li>
+<li><a href="/jena/documentation/larq/index.html">LARQ: Free Text Search</a></li>
<li><a href="/jena/documentation/serving_data/index.html">Fuseki: Serving Data</a></li>
<li><a href="/jena/documentation/ontology/index.html">Ontology</a></li>
<li><a href="/jena/documentation/inference/index.html">Inference</a></li>
@@ -139,11 +139,11 @@
</ul>
</li>
</ul>
-<h1 id="getting_involved">Getting Involved</h1>
+<h1 id="getting-involved">Getting Involved</h1>
<ul>
<li><a href="/jena/getting_involved/index.html">Contributing to Jena</a></li>
</ul>
-<h1 id="asf_links">ASF links</h1>
+<h1 id="asf-links">ASF links</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
@@ -159,7 +159,7 @@
<p>Some example code is available here: <a href="https://svn.apache.org/repos/asf/incubator/jena/Jena2/LARQ/trunk/src/test/java/org/apache/jena/larq/examples/">https://svn.apache.org/repos/asf/incubator/jena/Jena2/LARQ/trunk/src/test/java/org/apache/jena/larq/examples/</a>.</p>
<p>Two helper commands are provided: <code>larq.larqbuilder</code> and <code>larq.larq</code> used respectively for updating and querying LARQ indexes.</p>
<p>A full description of the free text query language syntax is given in the <a href="http://lucene.apache.org/java/3_0_0/queryparsersyntax.html">Lucene query syntax</a> document.</p>
-<h2 id="usage_patterns">Usage Patterns</h2>
+<h2 id="usage-patterns">Usage Patterns</h2>
<p>There are three basic usage patterns supported:</p>
<ul>
<li>Pattern 1 : index string literals. The index will return the literals matching the Lucene search pattern.</li>
@@ -168,16 +168,16 @@
</ul>
<p>Patterns 1 and 2 have the indexed content in the graph. Both 1 and 2 can be modified by specifying a property so that only values of a given property are indexed. Pattern 2 is less flexible as <a href="#query_using_a_lucene_index">discussed below</a>. Pattern 3 is covered in the <a href="#external_content">external content</a> section below.</p>
<p>LARQ can be used in other ways as well but the classes for these patterns are supplied. In both patterns 1 and 2, strings are indexed, being plain strings, string with any language tag or any literal with datatype XSD string.</p>
-<h2 id="index_creation">Index Creation</h2>
+<h2 id="index-creation">Index Creation</h2>
<p>There are many ways to use Lucene, which can be set up to handle particular features or languages. The creation of the index is done outside of the ARQ query system proper and only accessed at query time. LARQ includes some platform classes and also utility classes to create indexes on string literals for the use cases above. Indexing can be performed as the graph is read in, or to built from an existing graph.</p>
-<h3 id="index_builders">Index Builders</h3>
+<h3 id="index-builders">Index Builders</h3>
<p>An index builder is a class to create a Lucene index from RDF data.</p>
<ul>
<li><code>IndexBuilderString</code>: This is the most commonly used index builder. It indexes plain literals (with or without language tags) and XSD strings and stores the complete literal. Optionally, a property can be supplied which restricts indexing to strings in statements using that property.</li>
<li><code>IndexBuilderSubject</code>: Index the subject resource by a string literal, an store the subject resource, possibly restricted by a specified property.</li>
</ul>
<p>Lucene has many ways to create indexes and the index builder classes do not attempt to provide all possible Lucene features. Applications may need to extend or modify the standard index builders provided by LARQ.</p>
-<h3 id="index_creation_1">Index Creation</h3>
+<h3 id="index-creation_1">Index Creation</h3>
<p>An index can be built while reading RDF into a model:</p>
<div class="codehilite"><pre><span class="sr">//</span> <span class="o">--</span> <span class="n">Read</span> <span class="ow">and</span> <span class="nb">index</span> <span class="n">all</span> <span class="n">literal</span> <span class="n">strings</span><span class="o">.</span>
<span class="n">IndexBuilderString</span> <span class="n">larqBuilder</span> <span class="o">=</span> <span class="k">new</span> <span class="n">IndexBuilderString</span><span class="p">()</span> <span class="p">;</span>
@@ -206,7 +206,7 @@
</pre></div>
-<h2 id="index_registration">Index Registration</h2>
+<h2 id="index-registration">Index Registration</h2>
<p>Next the index is made available to ARQ. This can be done globally:</p>
<div class="codehilite"><pre><span class="sr">//</span> <span class="o">--</span> <span class="n">Make</span> <span class="n">globally</span> <span class="n">available</span>
<span class="n">LARQ</span><span class="o">.</span><span class="n">setDefaultIndex</span><span class="p">(</span><span class="nb">index</span><span class="p">)</span> <span class="p">;</span>
@@ -221,7 +221,7 @@
<p>In both these cases, the default index is set, which is the one expected by property function <code>pf:textMatch</code>. Use of multiple indexes in the same query can be achieved by introducing new properties. The application can subclass the search class <code>org.apache.jena.larq.LuceneSearch</code> to set different indexes with different property names.</p>
-<h2 id="query_using_a_lucene_index">Query using a Lucene index</h2>
+<h2 id="query-using-a-lucene-index">Query using a Lucene index</h2>
<p>Query execution is as usual using the property function pf:textMatch. "textMatch" can be thought of as an implied relationship in the data. Note the prefix ends in ".".</p>
<div class="codehilite"><pre><span class="n">String</span> <span class="n">queryString</span> <span class="o">=</span> <span class="n">StringUtils</span><span class="o">.</span><span class="nb">join</span><span class="p">(</span><span class="s">"\n"</span><span class="p">,</span> <span class="k">new</span> <span class="n">String</span><span class="o">[]</span><span class="p">{</span>
<span class="s">"PREFIX pf: <http://jena.hpl.hp.com/ARQ/property#>"</span><span class="p">,</span>
@@ -246,7 +246,7 @@
<p>This is a more flexible way of achieving the effect of using a <code>IndexBuilderSubject</code>. <code>IndexBuilderSubject</code> can be more compact when there are many large literals (it stores the subject not the literal) but does not work for blank node subjects without extremely careful co-ordination with a persistent model. Looking the literal up in the model does not have this complication.</p>
-<h2 id="accessing_the_lucene_score">Accessing the Lucene Score</h2>
+<h2 id="accessing-the-lucene-score">Accessing the Lucene Score</h2>
<p>The application can get access to the Lucene match score by using a list argument for the subject of <code>pf:textMatch</code>. The list must have two arguments, both unbound variables at the time of the query.</p>
<div class="codehilite"><pre><span class="n">PREFIX</span> <span class="n">pf:</span> <span class="sr"><http://jena.hpl.hp.com/ARQ/property#></span>
<span class="n">SELECT</span> <span class="p">?</span><span class="n">doc</span> <span class="p">?</span><span class="n">score</span>
@@ -257,7 +257,7 @@
</pre></div>
-<h2 id="limiting_the_number_of_matches">Limiting the number of matches</h2>
+<h2 id="limiting-the-number-of-matches">Limiting the number of matches</h2>
<p>When used with just a query string, pf:textMatch returns all the Lucene matches. In many applications, the application is only interested in the first few matches (Lucene returns matches in order, highest scoring first), or only matches above some score threshold. The query argument that forms the object of the pf:textMatch property can also be a list, including a score threshold and a total limit on the number of results matched.</p>
<div class="codehilite"><pre><span class="p">?</span><span class="n">lit</span> <span class="n">pf:textMatch</span> <span class="p">(</span> <span class="s">'+text'</span> <span class="mi">100</span> <span class="p">)</span> <span class="o">.</span> <span class="c1"># Limit to at most 100 hits</span>
@@ -267,7 +267,7 @@
</pre></div>
-<h2 id="direct_application_use">Direct Application Use</h2>
+<h2 id="direct-application-use">Direct Application Use</h2>
<p>The IndexLARQ class provides the ability to search programmatically, not just from ARQ. The searchModelByIndex method returns an iterator over RDFNodes.</p>
<div class="codehilite"><pre><span class="sr">//</span> <span class="o">--</span> <span class="n">Create</span> <span class="n">the</span> <span class="n">access</span> <span class="nb">index</span>
<span class="n">IndexLARQ</span> <span class="nb">index</span> <span class="o">=</span> <span class="n">larqBuilder</span><span class="o">.</span><span class="n">getIndex</span><span class="p">()</span> <span class="p">;</span>
@@ -281,14 +281,14 @@
</pre></div>
-<h2 id="external_content">External Content</h2>
+<h2 id="external-content">External Content</h2>
<ul>
<li>Pattern 3: index graph nodes based on strings not present in the graph.</li>
</ul>
<p>Sometimes, the index needs to be created based on external material and the index gives nodes in the graph. This can be done by using <code>IndexBuilderNode</code> which is a helper class to relate external material to some RDF node.</p>
<p>Here, the indexed content is not in the RDF graph at all. For example, the indexed content may come from HTML.XHTML, PDFs or XML documents and the RDF graph only holds the metadata about these content items. </p>
<p>The <a href="http://lucene.apache.org/java/3_4_0/contributions.html#Lucene%20Document%20Converters">Lucene contributions page</a> lists some content converters.</p>
-<h2 id="getting_help_and_getting_involved">Getting Help and Getting Involved</h2>
+<h2 id="getting-help-and-getting-involved">Getting Help and Getting Involved</h2>
<p>If you have a problem with LARQ, make sure you read the <a href="../../help_and_support/index.html">Getting help with Jena</a> page and post a message on the <a href="mailto:jena-users@incubator.apache.org">jena-users@incubator.apache.org</a> mailing list.
You can also search the jena-users mailing list archives <a href="http://markmail.org/search/?q=larq+list%3Aorg.apache.incubator.jena-users">here</a>.</p>
<p>If you use LARQ and you want to get involved, make sure you read the <a href="../../getting_involved/index.html">Getting Involved</a> page. You can help us making LARQ better by:</p>
Modified: websites/staging/jena/trunk/content/jena/documentation/notes/concurrency-howto.html
==============================================================================
--- websites/staging/jena/trunk/content/jena/documentation/notes/concurrency-howto.html (original)
+++ websites/staging/jena/trunk/content/jena/documentation/notes/concurrency-howto.html Thu Mar 22 17:34:58 2012
@@ -47,7 +47,7 @@
</div>
<div id="navigation" class="clear">
- <h1 id="quick_links">Quick links</h1>
+ <h1 id="quick-links">Quick links</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/download/index.html">Downloads</a></li>
@@ -57,7 +57,7 @@
<li><a href="/jena/getting_involved/index.html">Getting involved</a></li>
<li><a href="/jena/documentation/">Documentation</a></li>
</ul>
-<h1 id="about_jena">About Jena</h1>
+<h1 id="about-jena">About Jena</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/about_jena/about.html">About Jena</a></li>
@@ -72,12 +72,12 @@
<li><a href="/jena/download/maven.html">Using Maven</a></li>
<li><a href="/jena/download/osgi.html">Using OSGi</a></li>
</ul>
-<h1 id="help_and_support">Help and support</h1>
+<h1 id="help-and-support">Help and support</h1>
<ul>
<li><a href="/jena/help_and_support/index.html">Getting help</a></li>
<li><a href="/jena/help_and_support/bugs_and_suggestions.html">Bugs and suggestions</a></li>
</ul>
-<h1 id="getting_started">Getting Started</h1>
+<h1 id="getting-started">Getting Started</h1>
<ul>
<li><a href="/jena/getting_started/index.html">A first Jena project</a></li>
<li><a href="/jena/getting_started/rdf_api.html">RDF API overview</a></li>
@@ -108,7 +108,7 @@
</ul>
</li>
<li><a href="/jena/documentation/sdb/index.html">SDB</a></li>
-<li><a href="/jena/documentation/larq/index.html">LARQ</a></li>
+<li><a href="/jena/documentation/larq/index.html">LARQ: Free Text Search</a></li>
<li><a href="/jena/documentation/serving_data/index.html">Fuseki: Serving Data</a></li>
<li><a href="/jena/documentation/ontology/index.html">Ontology</a></li>
<li><a href="/jena/documentation/inference/index.html">Inference</a></li>
@@ -139,11 +139,11 @@
</ul>
</li>
</ul>
-<h1 id="getting_involved">Getting Involved</h1>
+<h1 id="getting-involved">Getting Involved</h1>
<ul>
<li><a href="/jena/getting_involved/index.html">Contributing to Jena</a></li>
</ul>
-<h1 id="asf_links">ASF links</h1>
+<h1 id="asf-links">ASF links</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
@@ -210,7 +210,7 @@ be other application threads reading the
iterators must be assumed to be iterating over the data-structures
in the model or graph implementation itself. It is not possible to
safely pass these out of critical sections.</p>
-<h2 id="sparql_query">SPARQL Query</h2>
+<h2 id="sparql-query">SPARQL Query</h2>
<p>SPARQL query results are iterators and no different from other
iterators in Jena for concurrency purposes. The default query
engine does not give thread safety and the normal requirements on
Modified: websites/staging/jena/trunk/content/jena/documentation/notes/event-handler-howto.html
==============================================================================
--- websites/staging/jena/trunk/content/jena/documentation/notes/event-handler-howto.html (original)
+++ websites/staging/jena/trunk/content/jena/documentation/notes/event-handler-howto.html Thu Mar 22 17:34:58 2012
@@ -47,7 +47,7 @@
</div>
<div id="navigation" class="clear">
- <h1 id="quick_links">Quick links</h1>
+ <h1 id="quick-links">Quick links</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/download/index.html">Downloads</a></li>
@@ -57,7 +57,7 @@
<li><a href="/jena/getting_involved/index.html">Getting involved</a></li>
<li><a href="/jena/documentation/">Documentation</a></li>
</ul>
-<h1 id="about_jena">About Jena</h1>
+<h1 id="about-jena">About Jena</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/about_jena/about.html">About Jena</a></li>
@@ -72,12 +72,12 @@
<li><a href="/jena/download/maven.html">Using Maven</a></li>
<li><a href="/jena/download/osgi.html">Using OSGi</a></li>
</ul>
-<h1 id="help_and_support">Help and support</h1>
+<h1 id="help-and-support">Help and support</h1>
<ul>
<li><a href="/jena/help_and_support/index.html">Getting help</a></li>
<li><a href="/jena/help_and_support/bugs_and_suggestions.html">Bugs and suggestions</a></li>
</ul>
-<h1 id="getting_started">Getting Started</h1>
+<h1 id="getting-started">Getting Started</h1>
<ul>
<li><a href="/jena/getting_started/index.html">A first Jena project</a></li>
<li><a href="/jena/getting_started/rdf_api.html">RDF API overview</a></li>
@@ -108,7 +108,7 @@
</ul>
</li>
<li><a href="/jena/documentation/sdb/index.html">SDB</a></li>
-<li><a href="/jena/documentation/larq/index.html">LARQ</a></li>
+<li><a href="/jena/documentation/larq/index.html">LARQ: Free Text Search</a></li>
<li><a href="/jena/documentation/serving_data/index.html">Fuseki: Serving Data</a></li>
<li><a href="/jena/documentation/ontology/index.html">Ontology</a></li>
<li><a href="/jena/documentation/inference/index.html">Inference</a></li>
@@ -139,11 +139,11 @@
</ul>
</li>
</ul>
-<h1 id="getting_involved">Getting Involved</h1>
+<h1 id="getting-involved">Getting Involved</h1>
<ul>
<li><a href="/jena/getting_involved/index.html">Contributing to Jena</a></li>
</ul>
-<h1 id="asf_links">ASF links</h1>
+<h1 id="asf-links">ASF links</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
@@ -223,7 +223,7 @@ see all the statements.</p>
through the Model API will be presented to the listener; any
Triples added to its underlying Graph will also be presented to the
listener as statements.</p>
-<h2 id="utility_classes">Utility classes</h2>
+<h2 id="utility-classes">Utility classes</h2>
<p>The full Listener API is rather chunky and it can be inconvenient
to use, especially for the creation of inline classes. There are
four utility classes in <em>com.hp.hpl.jena.rdf.listeners:</em>
@@ -243,7 +243,7 @@ four utility classes in <em>com.hp.hpl.j
- <em>ObjectListener</em>. This class translates all the listener calls
into <em>added(Object)</em> or <em>removed(Object)</em> as appropriate; it is
left to the user code to distinguish among the types of argument.</p>
-<h2 id="when_listeners_are_called">When listeners are called</h2>
+<h2 id="when-listeners-are-called">When listeners are called</h2>
<p>In the current implementation, listener methods are called
immediately the additions or removals are made, in the same thread
as the one making the update. If a model has multiple listeners
@@ -253,7 +253,7 @@ throws an exception, that exception is t
call, and other listeners may not be informed of the update.
Hence listener code should be brief and exception-free if at all
possible.</p>
-<h2 id="registering_and_unregistering">Registering and unregistering</h2>
+<h2 id="registering-and-unregistering">Registering and unregistering</h2>
<p>A listener may be registered with the same model multiple times. If
so, it will be invoked as many times as it is registered for each
update event on the model.</p>
@@ -263,7 +263,7 @@ happens.</p>
<p>If a listener is registered multiple times with the same model,
each <code>unregister()</code> for that listener will remove just one of the
registrations.</p>
-<h2 id="transactions_and_databases">Transactions and databases</h2>
+<h2 id="transactions-and-databases">Transactions and databases</h2>
<p>In the current design, listeners are not informed of transaction
boundaries, and all events are fed to listeners as soon as they
happen.
Modified: websites/staging/jena/trunk/content/jena/documentation/notes/file-manager.html
==============================================================================
--- websites/staging/jena/trunk/content/jena/documentation/notes/file-manager.html (original)
+++ websites/staging/jena/trunk/content/jena/documentation/notes/file-manager.html Thu Mar 22 17:34:58 2012
@@ -47,7 +47,7 @@
</div>
<div id="navigation" class="clear">
- <h1 id="quick_links">Quick links</h1>
+ <h1 id="quick-links">Quick links</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/download/index.html">Downloads</a></li>
@@ -57,7 +57,7 @@
<li><a href="/jena/getting_involved/index.html">Getting involved</a></li>
<li><a href="/jena/documentation/">Documentation</a></li>
</ul>
-<h1 id="about_jena">About Jena</h1>
+<h1 id="about-jena">About Jena</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/about_jena/about.html">About Jena</a></li>
@@ -72,12 +72,12 @@
<li><a href="/jena/download/maven.html">Using Maven</a></li>
<li><a href="/jena/download/osgi.html">Using OSGi</a></li>
</ul>
-<h1 id="help_and_support">Help and support</h1>
+<h1 id="help-and-support">Help and support</h1>
<ul>
<li><a href="/jena/help_and_support/index.html">Getting help</a></li>
<li><a href="/jena/help_and_support/bugs_and_suggestions.html">Bugs and suggestions</a></li>
</ul>
-<h1 id="getting_started">Getting Started</h1>
+<h1 id="getting-started">Getting Started</h1>
<ul>
<li><a href="/jena/getting_started/index.html">A first Jena project</a></li>
<li><a href="/jena/getting_started/rdf_api.html">RDF API overview</a></li>
@@ -108,7 +108,7 @@
</ul>
</li>
<li><a href="/jena/documentation/sdb/index.html">SDB</a></li>
-<li><a href="/jena/documentation/larq/index.html">LARQ</a></li>
+<li><a href="/jena/documentation/larq/index.html">LARQ: Free Text Search</a></li>
<li><a href="/jena/documentation/serving_data/index.html">Fuseki: Serving Data</a></li>
<li><a href="/jena/documentation/ontology/index.html">Ontology</a></li>
<li><a href="/jena/documentation/inference/index.html">Inference</a></li>
@@ -139,11 +139,11 @@
</ul>
</li>
</ul>
-<h1 id="getting_involved">Getting Involved</h1>
+<h1 id="getting-involved">Getting Involved</h1>
<ul>
<li><a href="/jena/getting_involved/index.html">Contributing to Jena</a></li>
</ul>
-<h1 id="asf_links">ASF links</h1>
+<h1 id="asf-links">ASF links</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
@@ -159,7 +159,7 @@
There is a standard global FileManager and applications may also
define specific ones by constructing addition FileManagers.</p>
<p>The LocationMapper provides alternative locations for RDF data.</p>
-<h2 id="the_file_manager">The File Manager</h2>
+<h2 id="the-file-manager">The File Manager</h2>
<p>Files are named by a string, according to the conventions of their
storage system. Typically this is by URI. There are a number of
storage system adapters provided:</p>
@@ -192,7 +192,7 @@ by name extension:</p>
<li><code>.nt</code> : N-Triples</li>
<li>Anything else: RDF/XML</li>
</ul>
-<h2 id="the_locationmapper_configuration_file">The LocationMapper configuration file</h2>
+<h2 id="the-locationmapper-configuration-file">The LocationMapper configuration file</h2>
<p>This example uses the RDF subset of
<a href="http://www.w3.org/2000/10/swap/Primer">N3</a>. Jena has an RDF reader
and RDF writer for N3. This is nearly the same as
@@ -252,7 +252,7 @@ original URI, not the alternative locati
<p>Using log4j, set the logging level of the classes:
com.hp.hpl.jena.util.FileManager=ALL
com.hp.hpl.jena.util.LocationManager=ALL</p>
-<h3 id="see_also">See also</h3>
+<h3 id="see-also">See also</h3>
<p>Javadoc:
<a href="/jena/documentation/javadoc/jena/com/hp/hpl/jena/util/FileManager.html">FileManager</a>
<a href="/jena/documentation/javadoc/jena/com/hp/hpl/jena/util/LocationMapper.html">LocationMapper</a></p>
Modified: websites/staging/jena/trunk/content/jena/documentation/notes/index.html
==============================================================================
--- websites/staging/jena/trunk/content/jena/documentation/notes/index.html (original)
+++ websites/staging/jena/trunk/content/jena/documentation/notes/index.html Thu Mar 22 17:34:58 2012
@@ -47,7 +47,7 @@
</div>
<div id="navigation" class="clear">
- <h1 id="quick_links">Quick links</h1>
+ <h1 id="quick-links">Quick links</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/download/index.html">Downloads</a></li>
@@ -57,7 +57,7 @@
<li><a href="/jena/getting_involved/index.html">Getting involved</a></li>
<li><a href="/jena/documentation/">Documentation</a></li>
</ul>
-<h1 id="about_jena">About Jena</h1>
+<h1 id="about-jena">About Jena</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/about_jena/about.html">About Jena</a></li>
@@ -72,12 +72,12 @@
<li><a href="/jena/download/maven.html">Using Maven</a></li>
<li><a href="/jena/download/osgi.html">Using OSGi</a></li>
</ul>
-<h1 id="help_and_support">Help and support</h1>
+<h1 id="help-and-support">Help and support</h1>
<ul>
<li><a href="/jena/help_and_support/index.html">Getting help</a></li>
<li><a href="/jena/help_and_support/bugs_and_suggestions.html">Bugs and suggestions</a></li>
</ul>
-<h1 id="getting_started">Getting Started</h1>
+<h1 id="getting-started">Getting Started</h1>
<ul>
<li><a href="/jena/getting_started/index.html">A first Jena project</a></li>
<li><a href="/jena/getting_started/rdf_api.html">RDF API overview</a></li>
@@ -108,7 +108,7 @@
</ul>
</li>
<li><a href="/jena/documentation/sdb/index.html">SDB</a></li>
-<li><a href="/jena/documentation/larq/index.html">LARQ</a></li>
+<li><a href="/jena/documentation/larq/index.html">LARQ: Free Text Search</a></li>
<li><a href="/jena/documentation/serving_data/index.html">Fuseki: Serving Data</a></li>
<li><a href="/jena/documentation/ontology/index.html">Ontology</a></li>
<li><a href="/jena/documentation/inference/index.html">Inference</a></li>
@@ -139,11 +139,11 @@
</ul>
</li>
</ul>
-<h1 id="getting_involved">Getting Involved</h1>
+<h1 id="getting-involved">Getting Involved</h1>
<ul>
<li><a href="/jena/getting_involved/index.html">Contributing to Jena</a></li>
</ul>
-<h1 id="asf_links">ASF links</h1>
+<h1 id="asf-links">ASF links</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
Modified: websites/staging/jena/trunk/content/jena/documentation/notes/iri.html
==============================================================================
--- websites/staging/jena/trunk/content/jena/documentation/notes/iri.html (original)
+++ websites/staging/jena/trunk/content/jena/documentation/notes/iri.html Thu Mar 22 17:34:58 2012
@@ -47,7 +47,7 @@
</div>
<div id="navigation" class="clear">
- <h1 id="quick_links">Quick links</h1>
+ <h1 id="quick-links">Quick links</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/download/index.html">Downloads</a></li>
@@ -57,7 +57,7 @@
<li><a href="/jena/getting_involved/index.html">Getting involved</a></li>
<li><a href="/jena/documentation/">Documentation</a></li>
</ul>
-<h1 id="about_jena">About Jena</h1>
+<h1 id="about-jena">About Jena</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/about_jena/about.html">About Jena</a></li>
@@ -72,12 +72,12 @@
<li><a href="/jena/download/maven.html">Using Maven</a></li>
<li><a href="/jena/download/osgi.html">Using OSGi</a></li>
</ul>
-<h1 id="help_and_support">Help and support</h1>
+<h1 id="help-and-support">Help and support</h1>
<ul>
<li><a href="/jena/help_and_support/index.html">Getting help</a></li>
<li><a href="/jena/help_and_support/bugs_and_suggestions.html">Bugs and suggestions</a></li>
</ul>
-<h1 id="getting_started">Getting Started</h1>
+<h1 id="getting-started">Getting Started</h1>
<ul>
<li><a href="/jena/getting_started/index.html">A first Jena project</a></li>
<li><a href="/jena/getting_started/rdf_api.html">RDF API overview</a></li>
@@ -108,7 +108,7 @@
</ul>
</li>
<li><a href="/jena/documentation/sdb/index.html">SDB</a></li>
-<li><a href="/jena/documentation/larq/index.html">LARQ</a></li>
+<li><a href="/jena/documentation/larq/index.html">LARQ: Free Text Search</a></li>
<li><a href="/jena/documentation/serving_data/index.html">Fuseki: Serving Data</a></li>
<li><a href="/jena/documentation/ontology/index.html">Ontology</a></li>
<li><a href="/jena/documentation/inference/index.html">Inference</a></li>
@@ -139,11 +139,11 @@
</ul>
</li>
</ul>
-<h1 id="getting_involved">Getting Involved</h1>
+<h1 id="getting-involved">Getting Involved</h1>
<ul>
<li><a href="/jena/getting_involved/index.html">Contributing to Jena</a></li>
</ul>
-<h1 id="asf_links">ASF links</h1>
+<h1 id="asf-links">ASF links</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
@@ -170,7 +170,7 @@ Gives the main interface for IRIs.</p>
Gives the main class for creating IRIs, including specifying
which specifications you wish to be using, and with what degree of
force.</p>
-<h2 id="minimal_documentation">Minimal Documentation</h2>
+<h2 id="minimal-documentation">Minimal Documentation</h2>
<p>Unfortunately this version of the IRI Library has badly incomplete
documentation, any help in producing good documentation would be
appreciated.</p>
Modified: websites/staging/jena/trunk/content/jena/documentation/notes/jena-internals.html
==============================================================================
--- websites/staging/jena/trunk/content/jena/documentation/notes/jena-internals.html (original)
+++ websites/staging/jena/trunk/content/jena/documentation/notes/jena-internals.html Thu Mar 22 17:34:58 2012
@@ -47,7 +47,7 @@
</div>
<div id="navigation" class="clear">
- <h1 id="quick_links">Quick links</h1>
+ <h1 id="quick-links">Quick links</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/download/index.html">Downloads</a></li>
@@ -57,7 +57,7 @@
<li><a href="/jena/getting_involved/index.html">Getting involved</a></li>
<li><a href="/jena/documentation/">Documentation</a></li>
</ul>
-<h1 id="about_jena">About Jena</h1>
+<h1 id="about-jena">About Jena</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/about_jena/about.html">About Jena</a></li>
@@ -72,12 +72,12 @@
<li><a href="/jena/download/maven.html">Using Maven</a></li>
<li><a href="/jena/download/osgi.html">Using OSGi</a></li>
</ul>
-<h1 id="help_and_support">Help and support</h1>
+<h1 id="help-and-support">Help and support</h1>
<ul>
<li><a href="/jena/help_and_support/index.html">Getting help</a></li>
<li><a href="/jena/help_and_support/bugs_and_suggestions.html">Bugs and suggestions</a></li>
</ul>
-<h1 id="getting_started">Getting Started</h1>
+<h1 id="getting-started">Getting Started</h1>
<ul>
<li><a href="/jena/getting_started/index.html">A first Jena project</a></li>
<li><a href="/jena/getting_started/rdf_api.html">RDF API overview</a></li>
@@ -108,7 +108,7 @@
</ul>
</li>
<li><a href="/jena/documentation/sdb/index.html">SDB</a></li>
-<li><a href="/jena/documentation/larq/index.html">LARQ</a></li>
+<li><a href="/jena/documentation/larq/index.html">LARQ: Free Text Search</a></li>
<li><a href="/jena/documentation/serving_data/index.html">Fuseki: Serving Data</a></li>
<li><a href="/jena/documentation/ontology/index.html">Ontology</a></li>
<li><a href="/jena/documentation/inference/index.html">Inference</a></li>
@@ -139,11 +139,11 @@
</ul>
</li>
</ul>
-<h1 id="getting_involved">Getting Involved</h1>
+<h1 id="getting-involved">Getting Involved</h1>
<ul>
<li><a href="/jena/getting_involved/index.html">Contributing to Jena</a></li>
</ul>
-<h1 id="asf_links">ASF links</h1>
+<h1 id="asf-links">ASF links</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
@@ -157,10 +157,10 @@
<h1 class="title">Notes on Jena internals</h1>
<p><strong>Note:</strong> These notes are quite old now, but may still be of some interest in the design
and architecture of Jena.</p>
-<h2 id="enhanced_nodes">Enhanced Nodes</h2>
+<h2 id="enhanced-nodes">Enhanced Nodes</h2>
<p>This note is a development of the original note on the enhanced
node and graph design of Jena 2.</p>
-<h3 id="key_objectives_for_the_enhanced_node_design">Key objectives for the enhanced node design</h3>
+<h3 id="key-objectives-for-the-enhanced-node-design">Key objectives for the enhanced node design</h3>
<p>One problem with the Jena 1 design was that both the DAML layer and
the RDB layer independently extended Resource with domain-specific
information. That made it impossible to have a DAML-over-RDB
@@ -226,7 +226,7 @@ implementation
that present a given enhanced node according to a given type. For
example, an alt implementation can produce a sub-class of enhanced
node that provides accessors for the members of the alt.</p>
-<h4 id="key_points">Key points</h4>
+<h4 id="key-points">Key points</h4>
<p>Some key features of the design are:</p>
<ul>
<li>every enhanced graph has a single graph personality, which
@@ -239,8 +239,8 @@ implementation
<li>enhanced nodes wrap information in the graph, but keep no
independant state; they may be discarded and regenerated at whim.</li>
</ul>
-<h3 id="how_an_enhanced_node_is_created">How an enhanced node is created</h3>
-<h4 id="creation_from_another_enhanced_node">Creation from another enhanced node</h4>
+<h3 id="how-an-enhanced-node-is-created">How an enhanced node is created</h3>
+<h4 id="creation-from-another-enhanced-node">Creation from another enhanced node</h4>
<p>If <code>en</code> is an enhanced node representing some resource we wish to
be able to view as being of some (Java) class/interface <code>T</code>, the
expression <code>en.as(T.class)</code> will either deliver an EnhNode of type
@@ -248,7 +248,7 @@ expression <code>en.as(T.class)</code> w
<p>To check if the conversion is allowed, without having to catch
exceptions, the expression <code>en.canAs(T.class)</code> delivers <code>true</code> iff
the conversion is possible.</p>
-<h4 id="creation_from_a_base_node">Creation from a base node</h4>
+<h4 id="creation-from-a-base-node">Creation from a base node</h4>
<p>Somehow, some seed enhanced node must be created, otherwise <code>as()</code>
would have nothing to work on. Subclasses of enhanced node provide
constructors (perhaps hidden behind factories) which wrap plain
@@ -257,7 +257,7 @@ constructor
<code>EnhNode(Node,EnhGraph)</code></p>
<p>It's up to the constructors for the enhanced node subclasses to
ensure that they are called with appropriate arguments.</p>
-<h4 id="internal_operation_of_the_conversion">internal operation of the conversion</h4>
+<h4 id="internal-operation-of-the-conversion">internal operation of the conversion</h4>
<p><code>as(Class T)</code> is defined on EnhNode to invoke <code>asInternal(T)</code> in
<code>Polymorphic</code>. If the original enhanced node <code>en</code>is already a valid
instance of <code>T</code>, it is returned as the result. Validity is checked
@@ -275,7 +275,7 @@ type to an <code>Implementation</code> o
<code>wrap</code> method which takes a (plain) node and an enhanced graph and
delivers the new enhanced node after checking that its conditions
apply. The new enhanced node is then linked into the sibling ring.</p>
-<h3 id="how_to_build_an_enhanced_node__graph">How to build an enhanced node & graph</h3>
+<h3 id="how-to-build-an-enhanced-node-graph">How to build an enhanced node & graph</h3>
<p>What you have to do to define an enhanced node/graph
implementation:</p>
<ol>
@@ -296,7 +296,7 @@ implementation:</p>
graph.</li>
</ol>
<p>For an example, see the code for <code>ReifiedStatementImpl</code>.</p>
-<h2 id="reification_api">Reification API</h2>
+<h2 id="reification-api">Reification API</h2>
<h3 id="introduction">Introduction</h3>
<p>This document describes the reification API in Jena2, following
discussions based on the 0.5a document. The essential decision made
@@ -345,7 +345,7 @@ The goal of reification support in the J
<li>enable a complete standard compliant implementation, but not
necessarily as default</li>
</ul>
-<h3 id="presentation_api">Presentation API</h3>
+<h3 id="presentation-api">Presentation API</h3>
<p><em>Statement</em> will no longer be a subclass of <em>Resource</em>. Thus a
statement may not be used where a resource is expected. Instead, a
new interface <em>ReifiedStatement</em> will be defined:</p>
@@ -455,7 +455,7 @@ reification <em>rs</em> from the model b
Other reified statements with different resources will remain.</p>
<p><em>removeAllReifications(Statement st)</em> will remove all the
reifications in this model which reify <em>st</em>.</p>
-<h3 id="input_and_output">Input and output</h3>
+<h3 id="input-and-output">Input and output</h3>
<p>The writers will have access to the complete set of <em>Statement</em>s
and will be able to write out the quad components.</p>
<p>The readers need have no special machinery, but it would be
@@ -473,7 +473,7 @@ the <em>Statement</em>.</p>
<p><em>createReifiedStatement</em> is expected to bypass the construction and
detection of the quad components, so that in the "usual case" they
will never come into existance.</p>
-<h2 id="the_reification_spi">The Reification SPI</h2>
+<h2 id="the-reification-spi">The Reification SPI</h2>
<h3 id="introduction_1">Introduction</h3>
<p>This document describes the reification SPI, the mechanisms by
which the Graph family supports the Model API reification
@@ -493,24 +493,24 @@ So there are three kinds of <code>Graph<
<p>Graphs that do no reification;
Graphs that only do explicit reficiation;
Graphs that do implicit reification.</p>
-<h3 id="graph_operations_for_reification">Graph operations for reification</h3>
+<h3 id="graph-operations-for-reification">Graph operations for reification</h3>
<p>The primary reification operation on graphs is to extract their
<code>Reifier</code> instance. Handing reification off to a different class
allows reification to be handled independantly of other Graph
issues, eg query handling, bulk update.</p>
-<h4 id="graphgetreifier_-_reifier">Graph.getReifier() -> Reifier</h4>
+<h4 id="graphgetreifier-62-reifier">Graph.getReifier() -> Reifier</h4>
<p>Returns the <code>Reifier</code> for this <code>Graph</code>. Each graph has a single
reifier during its lifetime. The reifier object need not be
allocated until the first call of <code>getReifier()</code>.</p>
-<h3 id="addtriple_deletetriple">add(Triple), delete(Triple)</h3>
+<h3 id="addtriple-deletetriple">add(Triple), delete(Triple)</h3>
<p>These two operations may defer their triples to the graph's reifier
using <code>handledAdd(Triple)</code> and <code>handledDelete(Triple)</code>; see below
for details.</p>
-<h3 id="interface_reifier">Interface Reifier</h3>
+<h3 id="interface-reifier">Interface Reifier</h3>
<p>Instances of <code>Reifier</code> handle reification requests from their
<code>Graph</code> and from the API level code (issues by the API class
<code>ModelReifier</code>.</p>
-<h4 id="reifiergethiddentriples_-_graph">reifier.getHiddenTriples() -> Graph</h4>
+<h4 id="reifiergethiddentriples-62-graph">reifier.getHiddenTriples() -> Graph</h4>
<p>The reifier may keep reification triples to itself, coded in some
special way, rather than having them stored in the parent <code>Graph</code>.
This method exposes those triples as another <code>Graph</code>. This is a
@@ -519,14 +519,14 @@ However, it is read-only; triples cannot
from it.
The <code>SimpleReifier</code> implementation currently does not implement a
dynamic graph. This is a bug that will need fixing.</p>
-<h4 id="reifiergetparentgraph_-_graph">reifier.getParentGraph() -> Graph</h4>
+<h4 id="reifiergetparentgraph-62-graph">reifier.getParentGraph() -> Graph</h4>
<p>Get the <code>Graph</code> that this reifier serves; the result is never
<code>null</code>. (Thus the observable relationship between graphs and
reifiers is 1-1.)</p>
-<h4 id="class_alreadyreifiedexception">class AlreadyReifiedException</h4>
+<h4 id="class-alreadyreifiedexception">class AlreadyReifiedException</h4>
<p>This class extends <code>RDFException</code>; it is the exception that may be
thrown by <code>reifyAs</code>.</p>
-<h3 id="reifierreifyas_triple_t_node_n__-_node">reifier.reifyAs( Triple t, Node n ) -> Node</h3>
+<h3 id="reifierreifyas-triple-t-node-n-62-node">reifier.reifyAs( Triple t, Node n ) -> Node</h3>
<p>Record the <code>t</code> as reified in the parent <code>Graph</code> by the given <code>n</code>
and returns <code>n</code>. If <code>n</code> already reifies a different <code>Triple</code>, throw
a <code>AlreadyReifiedException</code>.
@@ -537,44 +537,44 @@ Calling <code>reifyAs(t,n)</code> is lik
<code>n rdf:object t.getObject()</code>
to the associated Graph; however, it is intended that it is
efficient in both time and space.</p>
-<h4 id="reifierhastriple_triple_t__-_boolean">reifier.hasTriple( Triple t ) -> boolean</h4>
+<h4 id="reifierhastriple-triple-t-62-boolean">reifier.hasTriple( Triple t ) -> boolean</h4>
<p>Returns true iff some <code>Node n</code> reifies <code>t</code> in this <code>Reifier</code>,
typically by an unretracted call of <code>reifyAs(t,n)</code>.
The intended (and actual) use for <code>hasTriple(Triple)</code> is in the
implementation of <code>isReified(Statement)</code> in <code>Model</code>.</p>
-<h4 id="reifiergettriple_node_n__-_triple">reifier.getTriple( Node n ) -> Triple</h4>
+<h4 id="reifiergettriple-node-n-62-triple">reifier.getTriple( Node n ) -> Triple</h4>
<p>Get the single <code>Triple</code> associated with <code>n</code>, if there is one. If
there isn't, return <code>null</code>.
A node reifies at most one triple. If <code>reifyAs</code>, with its explicit
check, is bypassed, and extra reification triples are asserted into
the parent graph, then <code>getTriple()</code> will simply return <code>null</code>.</p>
-<h3 id="reifierallnodes_-_extendediterator">reifier.allNodes() -> ExtendedIterator</h3>
+<h3 id="reifierallnodes-62-extendediterator">reifier.allNodes() -> ExtendedIterator</h3>
<p>Returns an (extended) iterator over all the nodes that (still)
reifiy something in this reifier.
This is intended for the implementation of <code>listReifiedStatements</code>
in <code>Model</code>.</p>
-<h4 id="reifierallnodes_triple_t__-_closableiterator">reifier.allNodes( Triple t ) -> ClosableIterator</h4>
+<h4 id="reifierallnodes-triple-t-62-closableiterator">reifier.allNodes( Triple t ) -> ClosableIterator</h4>
<p>Returns an iterator over all the nodes that (still) reify the
triple _t_.</p>
-<h3 id="reifierremove_node_n_triple_t_">reifier.remove( Node n, Triple t )</h3>
+<h3 id="reifierremove-node-n-triple-t">reifier.remove( Node n, Triple t )</h3>
<p>Remove the association between <code>n</code> and the triple<code>t</code>. Subsequently,
<code>hasNode(n)</code> will return false and <code>getTriple(n)</code> will return
<code>null</code>.
This method is used to implement <code>removeReification(Statement)</code> in
<code>Model</code>.</p>
-<h4 id="reifierremove_triple_t_">reifier.remove( Triple t )</h4>
+<h4 id="reifierremove-triple-t">reifier.remove( Triple t )</h4>
<p>Remove all the associations between any node <code>n</code> and <code>t</code>; ie, for
all <code>n</code> do <code>remove(n,t)</code>.
This method is used to implement <code>removeAllReifications</code> in
<code>Model</code>.</p>
-<h4 id="handledadd_triple_t__-_boolean">handledAdd( Triple t ) -> boolean</h4>
+<h4 id="handledadd-triple-t-62-boolean">handledAdd( Triple t ) -> boolean</h4>
<p>A graph doing reification may choose to monitor the triples being
added to it and have the reifier handle reification triples. In
this case, the graph's <code>add(t)</code> should call <code>handledAdd(t)</code> and
only proceed with its add if the result is <code>false</code>.
A graph that does not use <code>handledAdd()</code> [and <code>handledDelete()</code>]
can only use the explict reification supplied by its reifier.</p>
-<h4 id="handledremove_triple_t_">handledRemove( Triple t )</h4>
+<h4 id="handledremove-triple-t">handledRemove( Triple t )</h4>
<p>As for <code>handledAdd(t)</code>, but applied to <code>delete</code>.</p>
<h3 id="simplereifier">SimpleReifier</h3>
<p><code>SimpleReifier</code> is an implementation of <code>Reifier</code> suitable for
Modified: websites/staging/jena/trunk/content/jena/documentation/notes/model-factory.html
==============================================================================
--- websites/staging/jena/trunk/content/jena/documentation/notes/model-factory.html (original)
+++ websites/staging/jena/trunk/content/jena/documentation/notes/model-factory.html Thu Mar 22 17:34:58 2012
@@ -47,7 +47,7 @@
</div>
<div id="navigation" class="clear">
- <h1 id="quick_links">Quick links</h1>
+ <h1 id="quick-links">Quick links</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/download/index.html">Downloads</a></li>
@@ -57,7 +57,7 @@
<li><a href="/jena/getting_involved/index.html">Getting involved</a></li>
<li><a href="/jena/documentation/">Documentation</a></li>
</ul>
-<h1 id="about_jena">About Jena</h1>
+<h1 id="about-jena">About Jena</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/about_jena/about.html">About Jena</a></li>
@@ -72,12 +72,12 @@
<li><a href="/jena/download/maven.html">Using Maven</a></li>
<li><a href="/jena/download/osgi.html">Using OSGi</a></li>
</ul>
-<h1 id="help_and_support">Help and support</h1>
+<h1 id="help-and-support">Help and support</h1>
<ul>
<li><a href="/jena/help_and_support/index.html">Getting help</a></li>
<li><a href="/jena/help_and_support/bugs_and_suggestions.html">Bugs and suggestions</a></li>
</ul>
-<h1 id="getting_started">Getting Started</h1>
+<h1 id="getting-started">Getting Started</h1>
<ul>
<li><a href="/jena/getting_started/index.html">A first Jena project</a></li>
<li><a href="/jena/getting_started/rdf_api.html">RDF API overview</a></li>
@@ -108,7 +108,7 @@
</ul>
</li>
<li><a href="/jena/documentation/sdb/index.html">SDB</a></li>
-<li><a href="/jena/documentation/larq/index.html">LARQ</a></li>
+<li><a href="/jena/documentation/larq/index.html">LARQ: Free Text Search</a></li>
<li><a href="/jena/documentation/serving_data/index.html">Fuseki: Serving Data</a></li>
<li><a href="/jena/documentation/ontology/index.html">Ontology</a></li>
<li><a href="/jena/documentation/inference/index.html">Inference</a></li>
@@ -139,11 +139,11 @@
</ul>
</li>
</ul>
-<h1 id="getting_involved">Getting Involved</h1>
+<h1 id="getting-involved">Getting Involved</h1>
<ul>
<li><a href="/jena/getting_involved/index.html">Contributing to Jena</a></li>
</ul>
-<h1 id="asf_links">ASF links</h1>
+<h1 id="asf-links">ASF links</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
@@ -171,7 +171,7 @@ API, which had proved unsatisfactory.)</
<p>This note is an introduction, not an exhaustive description. As
usual consult the Javadoc for details of the methods and classes to
use.</p>
-<h2 id="simple_model_creation">Simple model creation</h2>
+<h2 id="simple-model-creation">Simple model creation</h2>
<p>The simplest way to create a model (if not the shortest) is to call
<code>ModelFactory.createDefaultModel()</code>. This [by default] delivers a
plain RDF model, stored in-memory, that does no inference and has
@@ -209,7 +209,7 @@ returns that model.</p>
over create <em>vs</em> open, closing the maker, and looking names up; for
those consult the
<a href="/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/ModelMaker.html">ModelMaker JavaDoc</a>.</p>
-<h3 id="file-based_models">File-based models</h3>
+<h3 id="file-based-models">File-based models</h3>
<p>The method <code>ModelFactory.createFileModelMaker(String)</code> returns a
<code>ModelMaker</code> which attaches models to filing-system files. The
<code>String</code> argument is the <em>fileBase</em>. When a file-ModelMaker opens a
@@ -223,10 +223,10 @@ to avoid confusion with significant char
systems. In the current implementation,</p>
<ul>
<li>colon : is converted to \_C</li>
-<li>slash / is converted to \_S</li>
+<li>slash \/ is converted to \_S</li>
<li>underbar _ is converted to \_U</li>
</ul>
-<h2 id="reification_styles">Reification styles</h2>
+<h2 id="reification-styles">Reification styles</h2>
<p>Jena models have different <em>reification styles</em>, which are
described in more detail in the
<a href="reification.html">reification howto</a>. <code>ModelFactory</code> provides
@@ -255,7 +255,7 @@ specified reification style.</p>
<p>Reification styles also appear in other Modelfactory methods,
although they are not required. We shall not discuss them further
in this document; consult the Javadoc for appropriate details.</p>
-<h2 id="database_model_creation">Database model creation</h2>
+<h2 id="database-model-creation">Database model creation</h2>
<p>Jena allows models to be created within databases. For an extensive
discussion of the available options and controls, see the
<a href="../DB/index.html">database howto documents</a>. The current
@@ -289,7 +289,7 @@ from <strong>jena.db.password</strong>,
<p>Details of these fields can be found in the database documentation,
as well as direct ways to construct connections if required, and
additional operations on RDB Models that may be useful.</p>
-<h2 id="inference_model_creation">Inference model creation</h2>
+<h2 id="inference-model-creation">Inference model creation</h2>
<p>An important feature of Jena is support for different kinds of
inference over RDF-based models (used for RDFS, OWL, and DAML).
Inference models are constructed by applying <em>reasoners</em> to
@@ -343,7 +343,7 @@ some predefined access methods for well-
sub-property closure.</p>
</li>
</ul>
-<h2 id="ontology_model_creation">Ontology model creation</h2>
+<h2 id="ontology-model-creation">Ontology model creation</h2>
<p>An <em>ontology model</em> is one that presents RDF as an ontology -
classes, individuals, different kinds of properties, and so forth.
Jena supports RDFS, OWL, and DAML ontologies through <em>profiles</em>.
@@ -384,7 +384,7 @@ additional inferences</p>
the full OWL Lite inference</p>
</li>
</ul>
-<h2 id="creating_models_from_assembler_descriptions">Creating models from Assembler descriptions</h2>
+<h2 id="creating-models-from-assembler-descriptions">Creating models from Assembler descriptions</h2>
<p>A new feature of Jena since Jena 2.4 is the use of
<em>assembler descriptions</em>, documented in the
<a href="../assembler/assembler-howto.html">assembler howto</a>. Access to the
Modified: websites/staging/jena/trunk/content/jena/documentation/notes/rdf-frames.html
==============================================================================
--- websites/staging/jena/trunk/content/jena/documentation/notes/rdf-frames.html (original)
+++ websites/staging/jena/trunk/content/jena/documentation/notes/rdf-frames.html Thu Mar 22 17:34:58 2012
@@ -47,7 +47,7 @@
</div>
<div id="navigation" class="clear">
- <h1 id="quick_links">Quick links</h1>
+ <h1 id="quick-links">Quick links</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/download/index.html">Downloads</a></li>
@@ -57,7 +57,7 @@
<li><a href="/jena/getting_involved/index.html">Getting involved</a></li>
<li><a href="/jena/documentation/">Documentation</a></li>
</ul>
-<h1 id="about_jena">About Jena</h1>
+<h1 id="about-jena">About Jena</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/about_jena/about.html">About Jena</a></li>
@@ -72,12 +72,12 @@
<li><a href="/jena/download/maven.html">Using Maven</a></li>
<li><a href="/jena/download/osgi.html">Using OSGi</a></li>
</ul>
-<h1 id="help_and_support">Help and support</h1>
+<h1 id="help-and-support">Help and support</h1>
<ul>
<li><a href="/jena/help_and_support/index.html">Getting help</a></li>
<li><a href="/jena/help_and_support/bugs_and_suggestions.html">Bugs and suggestions</a></li>
</ul>
-<h1 id="getting_started">Getting Started</h1>
+<h1 id="getting-started">Getting Started</h1>
<ul>
<li><a href="/jena/getting_started/index.html">A first Jena project</a></li>
<li><a href="/jena/getting_started/rdf_api.html">RDF API overview</a></li>
@@ -108,7 +108,7 @@
</ul>
</li>
<li><a href="/jena/documentation/sdb/index.html">SDB</a></li>
-<li><a href="/jena/documentation/larq/index.html">LARQ</a></li>
+<li><a href="/jena/documentation/larq/index.html">LARQ: Free Text Search</a></li>
<li><a href="/jena/documentation/serving_data/index.html">Fuseki: Serving Data</a></li>
<li><a href="/jena/documentation/ontology/index.html">Ontology</a></li>
<li><a href="/jena/documentation/inference/index.html">Inference</a></li>
@@ -139,11 +139,11 @@
</ul>
</li>
</ul>
-<h1 id="getting_involved">Getting Involved</h1>
+<h1 id="getting-involved">Getting Involved</h1>
<ul>
<li><a href="/jena/getting_involved/index.html">Contributing to Jena</a></li>
</ul>
-<h1 id="asf_links">ASF links</h1>
+<h1 id="asf-links">ASF links</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
@@ -199,7 +199,7 @@ an ontology or schema. The purpose of th
mechanisms built-in to Jena to support a frame-like view of
resources, while remaining correct with respect to RDF (and OWL)
semantics.</p>
-<h2 id="basic_principles_the_properties_of_a_class">Basic principles: the properties of a class</h2>
+<h2 id="basic-principles-the-properties-of-a-class">Basic principles: the properties of a class</h2>
<p>Since any RDF property can be applied to any RDF resource, we
require a definition of the properties of a given class that
respects RDF semantics. Consider the following RDF fragment:</p>
@@ -231,7 +231,7 @@ for the purposes of this HOWTO we define
<em>properties of a class</em> as just those properties that don't entail
any new type information when applied to resources that are already
known to be of that class.</p>
-<h2 id="sub-classes_and_more_complex_class_expressions">Sub-classes, and more complex class expressions</h2>
+<h2 id="sub-classes-and-more-complex-class-expressions">Sub-classes, and more complex class expressions</h2>
<p>Given these basic principles, now consider the following RDF
fragment:</p>
<div class="codehilite"><pre> <span class="nt"><rdfs:Class</span> <span class="na">rdf:ID=</span><span class="s">"LivingThing"</span> <span class="nt">/></span>
@@ -276,7 +276,7 @@ property of <code>B</code>.</p>
both <code>A</code> and <code>B</code> will have <code>p</code> as a property, since an occurrence
of, say <code>x p y</code> does not allow us to conclude that either
<code>x rdf:type A</code> or <code>x rdf:type B</code>.</p>
-<h2 id="property_hierarchies">Property hierarchies</h2>
+<h2 id="property-hierarchies">Property hierarchies</h2>
<p>Since sub-properties inherit the domain constraints of their parent
property, the properties of a class will include the closure over
the sub-property hierarchy. Extending the previous example, the
@@ -297,7 +297,7 @@ domain constraints from the axioms asser
Whether or not all of these possible deductions are present in any
given RDF model depends on the power and completeness of the
reasoner bound to that model.</p>
-<h2 id="global_properties">Global properties</h2>
+<h2 id="global-properties">Global properties</h2>
<p>Under the principled definition that we propose here, properties
which do not express a domain value are <em>global</em>, in the sense that
they can apply to any resource. They do not, by definition, entail
@@ -336,7 +336,7 @@ restriction. Since there were problems w
heuristic, and ensuring correct behaviour (especially with
inference models), we have dropped the use of this heuristic from
Jena 2.2 onwards.</p>
-<h2 id="the_java_api">The Java API</h2>
+<h2 id="the-java-api">The Java API</h2>
<p>Support for frame-like views of classes and properties is provided
through the <a href="../ontology/index.html">ontology API</a>. The following
methods are used to access the properties of a class, and the
@@ -385,7 +385,7 @@ difference is illustrated by the followi
<p>Iterator <code>i1</code> will return <code>p</code> and <code>q</code>, while <code>i0</code> will return only
<code>p</code>.</p>
-<h2 id="summary_of_changes_from_jena_22-beta-2_and_older">Summary of changes from Jena 2.2-beta-2 and older</h2>
+<h2 id="summary-of-changes-from-jena-22-beta-2-and-older">Summary of changes from Jena 2.2-beta-2 and older</h2>
<p>For users updating code that uses <code>listDeclaredProperties</code> from
versions of Jena prior to 2.2-final, the following changes should
be noted:</p>
Modified: websites/staging/jena/trunk/content/jena/documentation/notes/reification.html
==============================================================================
--- websites/staging/jena/trunk/content/jena/documentation/notes/reification.html (original)
+++ websites/staging/jena/trunk/content/jena/documentation/notes/reification.html Thu Mar 22 17:34:58 2012
@@ -47,7 +47,7 @@
</div>
<div id="navigation" class="clear">
- <h1 id="quick_links">Quick links</h1>
+ <h1 id="quick-links">Quick links</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/download/index.html">Downloads</a></li>
@@ -57,7 +57,7 @@
<li><a href="/jena/getting_involved/index.html">Getting involved</a></li>
<li><a href="/jena/documentation/">Documentation</a></li>
</ul>
-<h1 id="about_jena">About Jena</h1>
+<h1 id="about-jena">About Jena</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/about_jena/about.html">About Jena</a></li>
@@ -72,12 +72,12 @@
<li><a href="/jena/download/maven.html">Using Maven</a></li>
<li><a href="/jena/download/osgi.html">Using OSGi</a></li>
</ul>
-<h1 id="help_and_support">Help and support</h1>
+<h1 id="help-and-support">Help and support</h1>
<ul>
<li><a href="/jena/help_and_support/index.html">Getting help</a></li>
<li><a href="/jena/help_and_support/bugs_and_suggestions.html">Bugs and suggestions</a></li>
</ul>
-<h1 id="getting_started">Getting Started</h1>
+<h1 id="getting-started">Getting Started</h1>
<ul>
<li><a href="/jena/getting_started/index.html">A first Jena project</a></li>
<li><a href="/jena/getting_started/rdf_api.html">RDF API overview</a></li>
@@ -108,7 +108,7 @@
</ul>
</li>
<li><a href="/jena/documentation/sdb/index.html">SDB</a></li>
-<li><a href="/jena/documentation/larq/index.html">LARQ</a></li>
+<li><a href="/jena/documentation/larq/index.html">LARQ: Free Text Search</a></li>
<li><a href="/jena/documentation/serving_data/index.html">Fuseki: Serving Data</a></li>
<li><a href="/jena/documentation/ontology/index.html">Ontology</a></li>
<li><a href="/jena/documentation/inference/index.html">Inference</a></li>
@@ -139,11 +139,11 @@
</ul>
</li>
</ul>
-<h1 id="getting_involved">Getting Involved</h1>
+<h1 id="getting-involved">Getting Involved</h1>
<ul>
<li><a href="/jena/getting_involved/index.html">Contributing to Jena</a></li>
</ul>
-<h1 id="asf_links">ASF links</h1>
+<h1 id="asf-links">ASF links</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
@@ -195,7 +195,7 @@ statement it reifies. The method</p>
<p>returns the <code>Statement</code> that the resource is reifying. All the
other <code>Resource</code> methods, of course, may be applied to a
<code>ReifiedStatement</code>.</p>
-<h2 id="converting_resources_to_reified_statements">Converting resources to reified statements</h2>
+<h2 id="converting-resources-to-reified-statements">Converting resources to reified statements</h2>
<p>If a resource <code>R</code> is associated with a reified statement, but might
not itself be a <code>ReifiedStatement</code> object, the conversion method
<code>RDFNode::as(Class)</code> can be used to find (or create) a
@@ -217,7 +217,7 @@ properties.)</p>
<code>Statement</code> even if some (or all) of the original quadlets are
removed from the model. This is a feature of the current
implementation that might go away; do not rely on it.</p>
-<h2 id="testing_statements_for_reification">Testing statements for reification</h2>
+<h2 id="testing-statements-for-reification">Testing statements for reification</h2>
<p>You may wish to know if some <code>Statement</code> is reified. The methods
<code>Statement::isReified()</code> and <code>Model::isreified(Statement)</code> return
true if (and only if) the statement has been reified in the model.
@@ -225,7 +225,7 @@ Note that the <code>Statement</code> met
reified in its own model, and the model method tests to see if the
<code>Statement</code> is reified in <em>that</em> model; there is no test to see if
a <code>Statement</code> is reified in any other models.</p>
-<h2 id="listing_reified_statements">Listing reified statements</h2>
+<h2 id="listing-reified-statements">Listing reified statements</h2>
<p>Just as <code>listStatements</code> is used to find the statements present in
some model, there are methods for finding the reified statements of
a model. Each of them returns a <code>RSIterator</code> object, which is an
@@ -238,7 +238,7 @@ suitably-cast reified statement.
in this model.
- <code>Model::listReifiedStatements(Statement s)</code> - all the reified
statements reifiying <code>s</code> in this model.</p>
-<h2 id="creating_reified_statements_directly">Creating reified statements directly</h2>
+<h2 id="creating-reified-statements-directly">Creating reified statements directly</h2>
<p>You do not have to create reified statements by asserting their
quads into a <code>Model</code>; they can be created directly from their
<code>Statement</code>s using one of the methods:
@@ -260,7 +260,7 @@ an <code>AlreadyReifiedException</code>.
<p>The additional method <code>Model::getAnyReifiedStatement(Statement)</code>
returns some reification of the supplied <code>Statement</code>; an existing
one if possible, otherwise a fresh one (reified by a fresh bnode).</p>
-<h2 id="reification_and_modeladdmodel">Reification and Model::add(Model)</h2>
+<h2 id="reification-and-modeladdmodel">Reification and Model::add(Model)</h2>
<p>When one model is added to another, as well as the ordinary
statements of the model being added, the reified statements are
copied across. If this is not desired, there is a two-argument
@@ -269,7 +269,7 @@ form:
<p>If <code>suppress</code> is <code>true</code>, then the reified statements are not
copied. (This choice arose from comments on earlier versions of the
Jena 2 API; users expected the reified statements to be copied.)</p>
-<h2 id="removing_reified_statements">Removing reified statements</h2>
+<h2 id="removing-reified-statements">Removing reified statements</h2>
<p>There are two methods which remove all the reifications of a
<code>Statement</code> in some <code>Model</code>:
- <code>Statement::removeReification()</code>
@@ -282,7 +282,7 @@ a particular reified statement only, use
<code>model.remove(Model m)</code> will remove all the reified statements of
<code>m</code> from <code>model</code>, and the two-argument form <code>model.remove(m,true)</code>
will not.</p>
-<h2 id="reification_styles">Reification styles</h2>
+<h2 id="reification-styles">Reification styles</h2>
<p>By default and as you might expect, Jena models allow reification
quads to be manifested as <code>ReifiedStatement</code>s. Similarly,
explicitly created <code>ReifiedStatement</code>s are visible as statement
Modified: websites/staging/jena/trunk/content/jena/documentation/notes/sse.html
==============================================================================
--- websites/staging/jena/trunk/content/jena/documentation/notes/sse.html (original)
+++ websites/staging/jena/trunk/content/jena/documentation/notes/sse.html Thu Mar 22 17:34:58 2012
@@ -47,7 +47,7 @@
</div>
<div id="navigation" class="clear">
- <h1 id="quick_links">Quick links</h1>
+ <h1 id="quick-links">Quick links</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/download/index.html">Downloads</a></li>
@@ -57,7 +57,7 @@
<li><a href="/jena/getting_involved/index.html">Getting involved</a></li>
<li><a href="/jena/documentation/">Documentation</a></li>
</ul>
-<h1 id="about_jena">About Jena</h1>
+<h1 id="about-jena">About Jena</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/about_jena/about.html">About Jena</a></li>
@@ -72,12 +72,12 @@
<li><a href="/jena/download/maven.html">Using Maven</a></li>
<li><a href="/jena/download/osgi.html">Using OSGi</a></li>
</ul>
-<h1 id="help_and_support">Help and support</h1>
+<h1 id="help-and-support">Help and support</h1>
<ul>
<li><a href="/jena/help_and_support/index.html">Getting help</a></li>
<li><a href="/jena/help_and_support/bugs_and_suggestions.html">Bugs and suggestions</a></li>
</ul>
-<h1 id="getting_started">Getting Started</h1>
+<h1 id="getting-started">Getting Started</h1>
<ul>
<li><a href="/jena/getting_started/index.html">A first Jena project</a></li>
<li><a href="/jena/getting_started/rdf_api.html">RDF API overview</a></li>
@@ -108,7 +108,7 @@
</ul>
</li>
<li><a href="/jena/documentation/sdb/index.html">SDB</a></li>
-<li><a href="/jena/documentation/larq/index.html">LARQ</a></li>
+<li><a href="/jena/documentation/larq/index.html">LARQ: Free Text Search</a></li>
<li><a href="/jena/documentation/serving_data/index.html">Fuseki: Serving Data</a></li>
<li><a href="/jena/documentation/ontology/index.html">Ontology</a></li>
<li><a href="/jena/documentation/inference/index.html">Inference</a></li>
@@ -139,11 +139,11 @@
</ul>
</li>
</ul>
-<h1 id="getting_involved">Getting Involved</h1>
+<h1 id="getting-involved">Getting Involved</h1>
<ul>
<li><a href="/jena/getting_involved/index.html">Contributing to Jena</a></li>
</ul>
-<h1 id="asf_links">ASF links</h1>
+<h1 id="asf-links">ASF links</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
@@ -224,9 +224,9 @@ no operations, no <em>push</em>, <em>pop
between cooperating machines. The structures are not completely
self-representing. But we do discuss a way to express in RDF that does
give a self-describing nature through the use of tagged structures.</p>
-<h2 id="design_intent">Design Intent</h2>
+<h2 id="design-intent">Design Intent</h2>
<ul>
-<li>Concise (=> for people to write conveniently) format for data
+<li>Concise (=> for people to write conveniently) format for data
structures</li>
<li>RDF-centric</li>
</ul>
@@ -240,7 +240,7 @@ give a self-describing nature through th
<li>Concise syntax for RDF terms</li>
<li>Datastructures</li>
</ul>
-<h2 id="other_approaches">Other Approaches</h2>
+<h2 id="other-approaches">Other Approaches</h2>
<h3 id="rdf">RDF</h3>
<p>RDF is "map-centric" but not all data structures are conveniently
expressible in maps. RDF has lists, and these lists have convenient
@@ -264,7 +264,7 @@ Query Results in
JSON</a>
shows how JSON might be used. It describes how RDF terms are encoded
into further substructures. Alternatively, we could put encoded terms in
-strings like "<http://w3.org/>" and have a parser-within-a-parser. But
+strings like "<http://w3.org/>" and have a parser-within-a-parser. But
both these approaches do not make the writing of RDF terms as easy as it
could be.</p>
<h2 id="design">Design</h2>
@@ -341,10 +341,10 @@ non-distinguished variable.</p>
form.</p>
<p>Almost any sequence of characters which is not an RDF term or variable
is a symbol that can be given special meaning by processing software.</p>
-<h3 id="sse_comments">SSE Comments</h3>
+<h3 id="sse-comments">SSE Comments</h3>
<p><code>#</code> or <code>;</code> introduce comments, which run to the end of line, including
the end-of-line characters.</p>
-<h3 id="sse_escapes">SSE Escapes</h3>
+<h3 id="sse-escapes">SSE Escapes</h3>
<p><code>\u</code> and <code>\U</code> escape sequences for arbitrary Unicode codepoints. These
apply to the input character stream before parsing. They don't, for
example, permit a space in a symbol.</p>
@@ -361,7 +361,7 @@ a string</p>
<p>A list of 2 elements: a symbol (<code>bgp</code>) and a list of 3 elements. Both
<code>()</code> and <code>[]</code> delimit lists; they must match but otherwise it's a free
choice. Convention is that compact lists use <code>[]</code>; large lists use <code>()</code>.</p>
-<h2 id="tagged_structures">Tagged Structures</h2>
+<h2 id="tagged-structures">Tagged Structures</h2>
<p>The basic syntax defines tokens and lists. Higher level processing
happens on this basic syntax and can be extended by interpreting the
structure.</p>
@@ -380,7 +380,7 @@ a symbol and the elements of the data ob
<p>is tagged with symbol <code>triple</code></p>
-<h3 id="iri_resolution">IRI resolution</h3>
+<h3 id="iri-resolution">IRI resolution</h3>
<p>One such layer is IRI and prefix name resolution, using tags <code>base</code> and
<code>prefix</code>.</p>
<p>Basic syntax includes unresolved IRIs, (example <code><abc></code>) and prefixed
@@ -436,7 +436,7 @@ serialized as a strict tree and some for
<p>The link layer will produce an SSE structure without these tags, having
replaced all <code>name@</code> and <code>@link</code> with the shared structure <em>X</em>.</p>
<p><em><code>@</code> is a convention for referencing.</em></p>
-<h2 id="building_java_objects">Building Java Objects</h2>
+<h2 id="building-java-objects">Building Java Objects</h2>
<p>Builders are code classes that process the structure into Java objects.
Writing builders is straight-forward because low-level parsing details
have been taken care of in the basic syntax. A typical builder is a
@@ -467,7 +467,7 @@ on the default graph.</p>
<li>Filter expressions (in prefix notation <code>(+ 1 2)</code>)</li>
<li>Query solutions (Bindings) and tables.</li>
</ul>
-<h3 id="sse_factory">SSE Factory</h3>
+<h3 id="sse-factory">SSE Factory</h3>
<p>The class <code>SSE</code> in package <code>com.hp.hpl.jena.sparql.sse</code> provides many
convenience functions to call builders for RDF and SPARQL structures.</p>
<div class="codehilite"><pre><span class="n">Node</span> <span class="n">n</span> <span class="o">=</span> <span class="n">SSE</span><span class="o">.</span><span class="n">parseNode</span><span class="p">(</span><span class="s">"<http://example/node>"</span><span class="p">)</span> <span class="p">;</span>
@@ -482,7 +482,7 @@ be used without explicit prefix declarat
<p>There is a default prefix mapping with a few common prefixes: <code>rdf</code>,
<code>rdfs</code>, <code>owl</code>, <code>xsd</code> and <code>fn</code> (the XPath/XQuery functions and operators
namespace).</p>
-<h2 id="mapping_to_rdf">Mapping to RDF</h2>
+<h2 id="mapping-to-rdf">Mapping to RDF</h2>
<p>The syntax of SSE is very close to Turtle lists because the syntax for
IRIs and literals are the same.: to produce Turtle (outline):</p>
<ol>
@@ -495,7 +495,7 @@ IRIs and literals are the same.: to prod
<p>The result is an RDF model using only the properties <code>rdf:first</code> and
<code>rdf:rest</code> so it records the data structure, but not what hthe data
structure represents.</p>
-<h2 id="sse_files">SSE Files</h2>
+<h2 id="sse-files">SSE Files</h2>
<p>The file extension is <code>.sse</code> and all files are UTF-8.</p>
<p>A quick and pragmatic Emacs mode is given by:</p>
<div class="codehilite"><pre><span class="p">;;</span> <span class="o">====</span> <span class="n">SSE</span> <span class="n">mode</span>
@@ -513,8 +513,8 @@ structure represents.</p>
</pre></div>
-<h2 id="longer_examples">Longer Examples</h2>
-<h3 id="query_1">Query 1</h3>
+<h2 id="longer-examples">Longer Examples</h2>
+<h3 id="query-1">Query 1</h3>
<div class="codehilite"><pre><span class="n">PREFIX</span> <span class="n">foaf:</span> <span class="sr"><http://xmlns.com/foaf/0.1/></span>
<span class="n">SELECT</span> <span class="n">DISTINCT</span> <span class="p">?</span><span class="n">name</span> <span class="p">?</span><span class="n">nick</span>
<span class="p">{</span>
@@ -536,7 +536,7 @@ structure represents.</p>
</pre></div>
-<h3 id="complete_sparql_execution">Complete SPARQL Execution</h3>
+<h3 id="complete-sparql-execution">Complete SPARQL Execution</h3>
<p>The following is a complete query execution, data and query. There is an
inline dataset and a query of</p>
<div class="codehilite"><pre> <span class="n">PREFIX</span> <span class="p">:</span> <span class="sr"><http://example/></span>
@@ -572,7 +572,7 @@ context sorts out the different usages.<
</pre></div>
-<h2 id="sse_grammar">SSE Grammar</h2>
+<h2 id="sse-grammar">SSE Grammar</h2>
<p><em>@@ insert grammar here</em></p>
</div>
Modified: websites/staging/jena/trunk/content/jena/documentation/notes/typed-literals.html
==============================================================================
--- websites/staging/jena/trunk/content/jena/documentation/notes/typed-literals.html (original)
+++ websites/staging/jena/trunk/content/jena/documentation/notes/typed-literals.html Thu Mar 22 17:34:58 2012
@@ -47,7 +47,7 @@
</div>
<div id="navigation" class="clear">
- <h1 id="quick_links">Quick links</h1>
+ <h1 id="quick-links">Quick links</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/download/index.html">Downloads</a></li>
@@ -57,7 +57,7 @@
<li><a href="/jena/getting_involved/index.html">Getting involved</a></li>
<li><a href="/jena/documentation/">Documentation</a></li>
</ul>
-<h1 id="about_jena">About Jena</h1>
+<h1 id="about-jena">About Jena</h1>
<ul>
<li><a href="/jena/index.html">Home</a></li>
<li><a href="/jena/about_jena/about.html">About Jena</a></li>
@@ -72,12 +72,12 @@
<li><a href="/jena/download/maven.html">Using Maven</a></li>
<li><a href="/jena/download/osgi.html">Using OSGi</a></li>
</ul>
-<h1 id="help_and_support">Help and support</h1>
+<h1 id="help-and-support">Help and support</h1>
<ul>
<li><a href="/jena/help_and_support/index.html">Getting help</a></li>
<li><a href="/jena/help_and_support/bugs_and_suggestions.html">Bugs and suggestions</a></li>
</ul>
-<h1 id="getting_started">Getting Started</h1>
+<h1 id="getting-started">Getting Started</h1>
<ul>
<li><a href="/jena/getting_started/index.html">A first Jena project</a></li>
<li><a href="/jena/getting_started/rdf_api.html">RDF API overview</a></li>
@@ -108,7 +108,7 @@
</ul>
</li>
<li><a href="/jena/documentation/sdb/index.html">SDB</a></li>
-<li><a href="/jena/documentation/larq/index.html">LARQ</a></li>
+<li><a href="/jena/documentation/larq/index.html">LARQ: Free Text Search</a></li>
<li><a href="/jena/documentation/serving_data/index.html">Fuseki: Serving Data</a></li>
<li><a href="/jena/documentation/ontology/index.html">Ontology</a></li>
<li><a href="/jena/documentation/inference/index.html">Inference</a></li>
@@ -139,11 +139,11 @@
</ul>
</li>
</ul>
-<h1 id="getting_involved">Getting Involved</h1>
+<h1 id="getting-involved">Getting Involved</h1>
<ul>
<li><a href="/jena/getting_involved/index.html">Contributing to Jena</a></li>
</ul>
-<h1 id="asf_links">ASF links</h1>
+<h1 id="asf-links">ASF links</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/licenses/LICENSE-2.0">License</a></li>
@@ -155,7 +155,7 @@
<div id="content">
<h1 class="title">Typed literals how-to</h1>
- <h2 id="what_are_typed_literals">What are typed literals?</h2>
+ <h2 id="what-are-typed-literals">What are typed literals?</h2>
<p>In the original RDF specifications there were two types of literal
values defined - plain literals (which are basically strings with
an optional language tag) and XML literals (which are more or less
@@ -203,7 +203,7 @@ ontology definition.</p>
<p>In the new scheme of things well-formed XML literals are treated as
typed literals whose datatype is the special type
<code>rdf:XMLLiteral</code>.</p>
-<h2 id="basic_api_operations">Basic API operations</h2>
+<h2 id="basic-api-operations">Basic API operations</h2>
<p>Jena will correctly parse typed literals within RDF/XML, NTriple
and Turtle source files. The same Java object,
<a href="/jena/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Literal.html"><code>Literal</code></a>
@@ -263,7 +263,7 @@ attempts to parse the string of the plai
this example). These are for backward compatibility with earlier
versions of Jena and older datasets. In normal circumstances
<code>createTypedLiteral</code> is preferable.</p>
-<h3 id="equality_issues">Equality issues</h3>
+<h3 id="equality-issues">Equality issues</h3>
<p>There is a well defined notion of when two typed literals should be
equal, based on the equality defined for the datatype in question.
Jena2 implements this equality function by using the method
@@ -276,7 +276,7 @@ equality problems would have arisen beca
substitutable in the Java sense (for example they return different
values from a getDatatype() call). This would, for example, have
made it impossible to cache literals in a hash table.</p>
-<h2 id="how_datatypes_are_represented">How datatypes are represented</h2>
+<h2 id="how-datatypes-are-represented">How datatypes are represented</h2>
<p>Datatypes for typed literals are represented by instances of the
interface
<a href="/jena/documentation/javadoc/com/hp/hpl/jena/datatypes/RDFDatatype.html"><code>com.hp.hpl.jena.datatypes.RDFDatatype</code></a>.
@@ -288,7 +288,7 @@ XSD datatypes (see <a href="#xsd">below<
<p>In addition, it is possible for an application to define new
datatypes and register them against some URI (see
<a href="#userdef">below</a>).</p>
-<h3 id="error_detection">Error detection</h3>
+<h3 id="error-detection">Error detection</h3>
<p>When Jena parses a datatype whose lexical value is not legal for
the declared datatype is does not immediately throw an error. This
is because the RDFCore working group has defined that illegal
@@ -318,7 +318,7 @@ the full javadoc, not the API javadoc) b
regarded as stable. We plan to develop a cleaner way of setting
mode switches for Jena and these switches will migrate there in due
course, if they prove to be useful.</p>
-<h2 id="xsd_data_types">XSD data types</h2>
+<h2 id="xsd-data-types">XSD data types</h2>
<p>Jena includes prebuilt, and pre-registered, instances of
<code>RDFDatatype</code> for all of the relevant XSD types:</p>
<blockquote>
@@ -389,7 +389,7 @@ use to represent certain Java classes:</
When parsing an xsd:integer the Java value object used will be an
Integer, Long or BigInteger depending on the size of the specific
value being represented.</p>
-<h2 id="user_defined_xsd_data_types">User defined XSD data types</h2>
+<h2 id="user-defined-xsd-data-types">User defined XSD data types</h2>
<p>XML schema allows derived types to be defined in which a base type
is modified through some facet restriction such as limiting the
min/max of an integer or restricting a string to a regular
@@ -457,7 +457,7 @@ then tries to create and use two instanc
</pre></div>
-<h2 id="user_defined_non-xsd_data_types">User defined non-XSD data types</h2>
+<h2 id="user-defined-non-xsd-data-types">User defined non-XSD data types</h2>
<p>RDF allows any URI to be used as a datatype but provides no
standard for how to map the datatype URI to a datatype definition.</p>
<p>Within Jena2 we allow new datatypes to be created and registered by
@@ -531,7 +531,7 @@ rational numbers:</p>
defined literals will be perfectly legal a client application has
no standard way of looking up the datatype URI you have chosen.
This has to be done "out of band" as they say.</p>
-<h2 id="a_note_on_xmllang">A note on xml:Lang</h2>
+<h2 id="a-note-on-xmllang">A note on xml:Lang</h2>
<p>Plain literals have an xml:Lang tag as well as a string value. Two
plain literals with the same string but different Lang tags are not
equal.</p>