jena-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r949654 - in /websites/staging/jena/trunk/content: ./ documentation/assembler/assembler-howto.html documentation/migrate_jena2_jena3.html
Date Wed, 29 Apr 2015 21:33:10 GMT
Author: buildbot
Date: Wed Apr 29 21:33:10 2015
New Revision: 949654

Log:
Staging update by buildbot for jena

Modified:
    websites/staging/jena/trunk/content/   (props changed)
    websites/staging/jena/trunk/content/documentation/assembler/assembler-howto.html
    websites/staging/jena/trunk/content/documentation/migrate_jena2_jena3.html

Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Apr 29 21:33:10 2015
@@ -1 +1 @@
-1675847
+1676866

Modified: websites/staging/jena/trunk/content/documentation/assembler/assembler-howto.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/assembler/assembler-howto.html (original)
+++ websites/staging/jena/trunk/content/documentation/assembler/assembler-howto.html Wed Apr
29 21:33:10 2015
@@ -323,69 +323,6 @@ interpretation.</p>
 resources. The subgraphs rooted at those resources (using the
 algorithm from <code>ResourceUtils.reachableClosure()</code>) are added to the
 content.</p>
-<h3 id="file-models">File models</h3>
-<p>A FileModel specification builds a memory model that is backed by a
-file. By "backed", we mean that the model is loaded from that file
-and written back to the file when (if) it is closed. Furthermore,
-the model (weakly) supports transactions.</p>
-<div class="codehilite"><pre><span class="n">eg</span><span class="o">:</span><span
class="n">fileModel</span><span class="o">-</span><span class="n">example</span><span
class="o">-</span><span class="mi">1</span>
-    <span class="n">ja</span><span class="o">:</span><span class="n">directory</span>
<span class="o">&lt;</span><span class="n">file</span><span
class="o">:///</span><span class="n">tmp</span><span class="o">&gt;</span>
<span class="o">;</span>
-    <span class="n">ja</span><span class="o">:</span><span class="n">modelName</span>
<span class="s2">&quot;simple&quot;</span>
-    <span class="o">.</span>
-</pre></div>
-
-
-<p>Here, the model is read from (and written to) the file
-<code>/tmp/simple</code>. Directory names are given as resources (not
-literals) and of course file names are system dependent -- this is
-what one might see on a Unix system. If the directory name is to be
-shared by several different FileModels, it can be useful to give it
-a namespace prefix so that it can be changed in one place as
-necessary.</p>
-<div class="codehilite"><pre><span class="n">eg</span><span class="o">:</span><span
class="n">fileModel</span><span class="o">-</span><span class="n">example</span><span
class="o">-</span><span class="mi">2</span>
-    <span class="n">ja</span><span class="o">:</span><span class="n">directory</span>
<span class="o">&lt;</span><span class="n">file</span><span
class="o">:////</span><span class="n">home</span><span class="sr">/kers/projects/jena2/doc/assembler/</span><span
class="n">FileModels</span><span class="o">&gt;</span> <span class="o">;</span>
-    <span class="n">ja</span><span class="o">:</span><span class="n">mapName</span>
<span class="n">ja</span><span class="o">:</span><span class="kc">true</span>
<span class="o">;</span>
-    <span class="n">ja</span><span class="o">:</span><span class="n">modelName</span>
<span class="s2">&quot;http://somewhere.org/stuff.n3&quot;</span>
-    <span class="o">.</span>
-</pre></div>
-
-
-<p>Model names can be <em>mapped</em> to allow them to be URIs without
the /s
-in URIs being taken as directory separators. Here, the base file
-name will be <code>FileModels/http_C_S_Ssomewhere.org_Sstuff.n3</code>. The
-encoding is not pretty, but is sufficient for simple URIs.</p>
-<div class="codehilite"><pre><span class="n">ja</span><span class="o">:</span><span
class="n">FileModel</span> <span class="n">a</span> <span class="n">rdfs</span><span
class="o">:</span><span class="n">Class</span> <span class="o">;</span>
-  <span class="n">rdfs</span><span class="o">:</span><span class="n">subClassOf</span>
<span class="o">[</span><span class="n">owl</span><span class="o">:</span><span
class="n">onProperty</span> <span class="n">ja</span><span class="o">:</span><span
class="n">mapName</span><span class="o">;</span> <span class="n">owl</span><span
class="o">:</span><span class="n">maxCardinality</span> <span class="mi">1</span><span
class="o">]</span> <span class="o">;</span>
-  <span class="n">rdfs</span><span class="o">:</span><span class="n">subClassOf</span>
<span class="o">[</span><span class="n">owl</span><span class="o">:</span><span
class="n">onProperty</span> <span class="n">ja</span><span class="o">:</span><span
class="n">directory</span><span class="o">;</span> <span class="n">owl</span><span
class="o">:</span><span class="n">maxCardinality</span> <span class="mi">1</span><span
class="o">]</span> <span class="o">;</span>
-  <span class="n">rdfs</span><span class="o">:</span><span class="n">subClassOf</span>
<span class="o">[</span><span class="n">owl</span><span class="o">:</span><span
class="n">onProperty</span> <span class="n">ja</span><span class="o">:</span><span
class="n">fileEncoding</span><span class="o">;</span> <span class="n">owl</span><span
class="o">:</span><span class="n">maxCardinality</span> <span class="mi">1</span><span
class="o">]</span> <span class="o">;</span>
-  <span class="n">rdfs</span><span class="o">:</span><span class="n">subClassOf</span>
<span class="n">ja</span><span class="o">:</span><span class="n">NamedModel</span>
-<span class="o">.</span>
-<span class="n">ja</span><span class="o">:</span><span class="n">fileEncoding</span>
<span class="n">a</span> <span class="n">rdf</span><span class="o">:</span><span
class="n">Property</span> <span class="o">;</span>
-  <span class="n">rdfs</span><span class="o">:</span><span class="n">domain</span>
<span class="n">ja</span><span class="o">:</span><span class="n">FileModel</span>
-<span class="o">.</span>
-<span class="n">ja</span><span class="o">:</span><span class="n">directory</span>
<span class="n">a</span> <span class="n">rdf</span><span class="o">:</span><span
class="n">Property</span> <span class="o">;</span>
-  <span class="n">rdfs</span><span class="o">:</span><span class="n">domain</span>
<span class="n">ja</span><span class="o">:</span><span class="n">FileModel</span>
-<span class="o">.</span>
-<span class="n">ja</span><span class="o">:</span><span class="n">mapName</span>
<span class="n">a</span> <span class="n">rdf</span><span class="o">:</span><span
class="n">Property</span> <span class="o">;</span>
-  <span class="n">rdfs</span><span class="o">:</span><span class="n">domain</span>
<span class="n">ja</span><span class="o">:</span><span class="n">FileModel</span>
-<span class="o">.</span>
-</pre></div>
-
-
-<p>The <code>ja:directory</code> property specifies the directory in which
the
-model file is located. The <code>ja:modelName</code> property specifies the
-name of the file within that directory.</p>
-<p>The optional unique property <code>ja:fileEncoding</code> has as its
value a
-string which is the name of the encoding language of the model (ie
-one of RDF/XML or N3, etc). If it is omitted, the language is
-guessed from the suffix of the filename (as per
-<code>FileUtils.guessLang()</code>).</p>
-<p>If the optional unique property <code>ja:mapName</code> has the value
-<code>ja:true</code>, then the name of the model is <em>mapped</em>
by replacing any
-_, /, or : characters by the escape sequences __, _S, or _C.
-This translation (which is the same one done by <code>FileGraphMaker</code>
-for <code>FileModelMaker</code>) allows URIs to be used as model names without
-conflicting with the filesystems use of / characters.</p>
 <h3 id="inference-models-and-reasoners">Inference models and reasoners</h3>
 <p>Inference models are specified by supplying a description of the
 reasoner that is used by the model and (optionally) a base model to

Modified: websites/staging/jena/trunk/content/documentation/migrate_jena2_jena3.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/migrate_jena2_jena3.html (original)
+++ websites/staging/jena/trunk/content/documentation/migrate_jena2_jena3.html Wed Apr 29
21:33:10 2015
@@ -146,6 +146,12 @@
     <h1 class="title">Migrating from Jena2 to Jena3</h1>
   <p>Apache Jena3 is a major version release for Jena - it is not binary compatibly
with
 Jena2. The migration consists of package renaming and database reloading.</p>
+<blockquote>
+<p>@@ Logger name chnages
+@@ java:
+@@ assemblers
+@@ version numbers</p>
+</blockquote>
 <h2 id="key-changes">Key Changes</h2>
 <ul>
 <li><a href="#packaging">Package renaming</a></li>
@@ -202,6 +208,9 @@ tag.</p>
 <p>For data stored in <a href="tdb/">TDB</a> and <a href="sdb/">SDB</a>,
it is advisable to reload data.</p>
 <p>Data that does not use explicit <code>xsd:string</code> should be safe
but it is still
 recommended that data is reloaded at a convenient time.</p>
+<h2 id="other">Other</h2>
+<p>Gone:
+ModelFactory.createFileModelMaker // JA.FileModel</p>
   </div>
 </div>
 



Mime
View raw message