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/14 14:52:15 UTC

svn commit: r958279 [6/6] - in /websites/staging/jena/trunk/content: ./ about_jena/ documentation/ documentation/csv/ documentation/hadoop/ documentation/inference/ documentation/io/ documentation/jdbc/ documentation/notes/ documentation/ontology/ docu...

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 Tue Jul 14 12:52:14 2015
@@ -144,7 +144,18 @@
     <div class="col-md-12">
     <div id="breadcrumbs"></div>
     <h1 class="title">Jena schemagen HOWTO</h1>
-  <p>The <code>schemagen</code> provided with Jena is used to convert an OWL or RDFS vocabulary into a Java class file that contains static
+  <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>The <code>schemagen</code> provided with Jena is used to convert an OWL or RDFS vocabulary into a Java class file that contains static
 constants for the terms in the vocabulary. This documents outlines
 the use of schemagen, and the various options and templates that
 may be used to control the output.</p>
@@ -159,12 +170,12 @@ or by RDF information read from a config
 other options are defined, and these are described in detail below.
 Note that the <code>CLASSPATH</code> environment variable must be set to
 include the Jena <code>.jar</code> libraries.</p>
-<h2 id="summary-of-configuration-options">Summary of configuration options</h2>
+<h2 id="summary-of-configuration-options">Summary of configuration options<a class="headerlink" href="#summary-of-configuration-options" title="Permanent link">&para;</a></h2>
 <p>For quick reference, here is a list of all of the schemagen options
 (both command line and configuration file). The use of these
 options is explained in detail below.</p>
 <p>Table 1: schemagen options</p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th>Command line option</th>
@@ -365,7 +376,7 @@ options is explained in detail below.</p
 </tr>
 </tbody>
 </table>
-<h2 id="what-does-schemagen-do">What does schemagen do?</h2>
+<h2 id="what-does-schemagen-do">What does schemagen do?<a class="headerlink" href="#what-does-schemagen-do" title="Permanent link">&para;</a></h2>
 <p>RDFS and OWL provide a very convenient means to define a
 controlled vocabulary or ontology. For general ontology processing,
 Jena provides various API's to allow the source files to be read in
@@ -383,7 +394,7 @@ file. Schemagen automates the production
 correspond to terms in an ontology document. By automating the step
 from source vocabulary to Java constants, a source of error and
 inconsistency is removed.</p>
-<h3 id="example">Example</h3>
+<h3 id="example">Example<a class="headerlink" href="#example" title="Permanent link">&para;</a></h3>
 <p>Perhaps the easiest way to explain the detail of what schemagen
 does is to show an example. Consider the following mini-RDF
 vocabulary:</p>
@@ -414,7 +425,7 @@ vocabulary:</p>
 to produce the following generated class:</p>
 <div class="codehilite"><pre><span class="cm">/* CVS $Id: schemagen.html,v 1.16 2010-06-11 00:08:23 ian_dickinson Exp $ */</span>
 
-<span class="kn">import</span> <span class="nn">com</span><span class="p">.</span><span class="n">hp</span><span class="p">.</span><span class="n">hpl</span><span class="p">.</span><span class="n">jena</span><span class="p">.</span><span class="n">rdf</span><span class="p">.</span><span class="n">model</span><span class="p">.</span><span class="o">*</span><span class="p">;</span>
+<span class="kn">import</span> <span class="nn">org</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">jena</span><span class="p">.</span><span class="n">rdf</span><span class="p">.</span><span class="n">model</span><span class="p">.</span><span class="o">*</span><span class="p">;</span>
 
 <span class="cm">/**</span>
 <span class="cm"> * Vocabulary definitions from deputy.rdf</span>
@@ -463,8 +474,8 @@ to <code>owl:Class</code>, and invoke
 to get:</p>
 <div class="codehilite"><pre><span class="cm">/* CVs $Id: schemagen.html,v 1.16 2010-06-11 00:08:23 ian_dickinson Exp $ */</span>
 
-<span class="kn">import</span> <span class="nn">com</span><span class="p">.</span><span class="n">hp</span><span class="p">.</span><span class="n">hpl</span><span class="p">.</span><span class="n">jena</span><span class="p">.</span><span class="n">rdf</span><span class="p">.</span><span class="n">model</span><span class="p">.</span><span class="o">*</span><span class="p">;</span>
-<span class="kn">import</span> <span class="nn">com</span><span class="p">.</span><span class="n">hp</span><span class="p">.</span><span class="n">hpl</span><span class="p">.</span><span class="n">jena</span><span class="p">.</span><span class="n">ontology</span><span class="p">.</span><span class="o">*</span><span class="p">;</span>
+<span class="kn">import</span> <span class="nn">org</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">jena</span><span class="p">.</span><span class="n">rdf</span><span class="p">.</span><span class="n">model</span><span class="p">.</span><span class="o">*</span><span class="p">;</span>
+<span class="kn">import</span> <span class="nn">org</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">jena</span><span class="p">.</span><span class="n">ontology</span><span class="p">.</span><span class="o">*</span><span class="p">;</span>
 <span class="cm">/**</span>
 <span class="cm"> * Vocabulary definitions from deputy.rdf</span>
 <span class="cm"> * @author Auto-generated by schemagen on 01 May 2003 22:03</span>
@@ -495,7 +506,7 @@ to get:</p>
 </pre></div>
 
 
-<h2 id="general-principles">General principles</h2>
+<h2 id="general-principles">General principles<a class="headerlink" href="#general-principles" title="Permanent link">&para;</a></h2>
 <p>In essence, schemagen will load a single vocabulary file,
 and generate a Java
 class that contains static constants for the named classes,
@@ -510,11 +521,11 @@ line and RDF option specification is per
 option is specified both in an RDF file and on the command line,
 the command line setting takes precedence. Thus the options in the
 RDF file can be seen as defaults.</p>
-<h3 id="specifying-command-line-options">Specifying command line options</h3>
+<h3 id="specifying-command-line-options">Specifying command line options<a class="headerlink" href="#specifying-command-line-options" title="Permanent link">&para;</a></h3>
 <p>To specify a command line option, add its name (and optional value)
 to the command line when invoking the schemagen tool. E.g:
 <code>Java jena.schemagen -i myvocab.owl --ontology --uppercase</code></p>
-<h3 id="specifying-options-in-an-rdf-file">Specifying options in an RDF file</h3>
+<h3 id="specifying-options-in-an-rdf-file">Specifying options in an RDF file<a class="headerlink" href="#specifying-options-in-an-rdf-file" title="Permanent link">&para;</a></h3>
 <p>To specify an option in an RDF file, create a resource of type
 <code>sgen:Config</code>, with properties corresponding to the option names
 listed in Table 1. The following fragment shows a small options
@@ -530,7 +541,7 @@ command line option. If there is no <cod
 look for a node of type <code>rdf:type sgen:Config</code>. If there are
 multiple such nodes in the model, it is indeterminate which one
 will be used.</p>
-<h3 id="using-templates">Using templates</h3>
+<h3 id="using-templates">Using templates<a class="headerlink" href="#using-templates" title="Permanent link">&para;</a></h3>
 <p>We have several times referred to a template being used to
 construct part of the generated file. What is a template? Simply
 put, it is a fragment of output file. Some templates will be used
@@ -545,7 +556,7 @@ keyword bindings stay the same throughou
 file, and some are dependent on the language element being
 processed. The substitutions are:</p>
 <p>Table 2: Substitutable keywords in templates</p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th>Keyword</th>
@@ -611,7 +622,7 @@ processed. The substitutions are:</p>
 </tr>
 </tbody>
 </table>
-<h2 id="details-of-schemagen-options">Details of schemagen options</h2>
+<h2 id="details-of-schemagen-options">Details of schemagen options<a class="headerlink" href="#details-of-schemagen-options" title="Permanent link">&para;</a></h2>
 <p>We now go through each of the configuration options in detail.</p>
 <p><strong>Note</strong>: for brevity, we assume a standard prefix <code>sgen</code> is
 defined for resource URI's in the schemagen namespace. The
@@ -621,7 +632,7 @@ expansion for <code>sgen</code> is:
 </pre></div>
 
 
-<h3 id="note-on-legal-java-identifiers">Note on legal Java identifiers</h3>
+<h3 id="note-on-legal-java-identifiers">Note on legal Java identifiers<a class="headerlink" href="#note-on-legal-java-identifiers" title="Permanent link">&para;</a></h3>
 <p>Schemagen will attempt to ensure that all generated code will
 compile as legal Java. Occasionally, this means that identifiers
 from input documents, which are legal components of RDF URI
@@ -640,8 +651,8 @@ are typically made distinct for clarity
 ontology users, so the use of the disambiguation tactic is rare.
 Indeed, it may be taken as a hint that refactoring the ontology
 itself is desirable.</p>
-<h3 id="specifying-the-configuration-file">Specifying the configuration file</h3>
-<table>
+<h3 id="specifying-the-configuration-file">Specifying the configuration file<a class="headerlink" href="#specifying-the-configuration-file" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -673,8 +684,8 @@ error.</p>
 configuration file is implied by the filename/ULRL suffix: ".n3"
 means N3, ".nt" means NTRIPLES, ".rdf" and ".owl" mean "RDF/XML".
 By default it assumes RDF/XML.</p>
-<h3 id="specifying-the-configuration-root-in-the-configuration-file">Specifying the configuration root in the configuration file</h3>
-<table>
+<h3 id="specifying-the-configuration-root-in-the-configuration-file">Specifying the configuration root in the configuration file<a class="headerlink" href="#specifying-the-configuration-root-in-the-configuration-file" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -712,8 +723,8 @@ the configuration file. For example:</p>
 </pre></div>
 
 
-<h3 id="specifying-the-input-document">Specifying the input document</h3>
-<table>
+<h3 id="specifying-the-input-document">Specifying the input document<a class="headerlink" href="#specifying-the-input-document" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -739,8 +750,8 @@ by specifying the input document in the
 schemagen can easily be invoked with the minimum of command line
 typing. For other means of automating schemagen, see
 <a href="#ant">using schemagen with Ant</a>.</p>
-<h3 id="specifying-the-output-location">Specifying the output location</h3>
-<table>
+<h3 id="specifying-the-output-location">Specifying the output location<a class="headerlink" href="#specifying-the-output-location" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -772,7 +783,7 @@ path name will be overwritten.</p>
 <p>By default, schemagen will create files that have the Unix
 convention for line-endings (i.e. '\n'). To switch to DOS-style
 line endings, use <code>--dos</code>.</p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -790,8 +801,8 @@ line endings, use <code>--dos</code>.</p
 </tr>
 </tbody>
 </table>
-<h3 id="specifying-the-class-name">Specifying the class name</h3>
-<table>
+<h3 id="specifying-the-class-name">Specifying the class name<a class="headerlink" href="#specifying-the-class-name" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -821,7 +832,7 @@ given.</p>
 distinguished by a common suffix, for example <code>xyzSchema.java</code> or
 <code>xyzVocabs.java</code>. This can be achieved by the classname-suffix
 option:</p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -841,8 +852,8 @@ option:</p>
 </table>
 <p>See also the <a href="#java-ids">note on legal Java identifiers</a>, which
 applies to generated class names.</p>
-<h3 id="specifying-the-vocabulary-namespace">Specifying the vocabulary namespace</h3>
-<table>
+<h3 id="specifying-the-vocabulary-namespace">Specifying the vocabulary namespace<a class="headerlink" href="#specifying-the-vocabulary-namespace" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -876,7 +887,7 @@ the configuration file.</p>
 primary namespace per generated Java class. However, constants from
 namespaces other than the primary namespace may be included in the
 generated Java class by the include option:</p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -905,7 +916,7 @@ the individual itself is not in that nam
 <code>strictIndividuals</code> is set, individuals are <strong>only</strong> included if
 they have a URI that is in the permitted namespaces for the
 vocabulary.</p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -923,8 +934,8 @@ vocabulary.</p>
 </tr>
 </tbody>
 </table>
-<h3 id="specifying-the-syntax-encoding-of-the-input-document">Specifying the syntax (encoding) of the input document</h3>
-<table>
+<h3 id="specifying-the-syntax-encoding-of-the-input-document">Specifying the syntax (encoding) of the input document<a class="headerlink" href="#specifying-the-syntax-encoding-of-the-input-document" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -949,8 +960,8 @@ a document <code>xyz.n3</code> will be p
 extension is non-obvious the default is RDF/XML. The encoding, and
 hence the parser, to use on the input document may be specified by
 the encoding configuration option.</p>
-<h3 id="choosing-the-style-of-the-generated-class-ontology-or-plain-rdf">Choosing the style of the generated class: ontology or plain RDF</h3>
-<table>
+<h3 id="choosing-the-style-of-the-generated-class-ontology-or-plain-rdf">Choosing the style of the generated class: ontology or plain RDF<a class="headerlink" href="#choosing-the-style-of-the-generated-class-ontology-or-plain-rdf" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -980,7 +991,7 @@ OWL (the default), and RDFS, it is neces
 which language is being processed. This will affect both the
 parsing of the input documents, and the language profile selected
 for the constants in the generated Java class.</p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -998,7 +1009,7 @@ for the constants in the generated Java
 </tr>
 </tbody>
 </table>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -1026,7 +1037,7 @@ asserted in the input model. From Jena 2
 now <strong>off by default</strong>. If correct handling of an input document by
 schemagen requires the use of inference rules, this must be
 specified by the <code>inference</code> option. </p>
-<table>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -1044,8 +1055,8 @@ specified by the <code>inference</code>
 </tr>
 </tbody>
 </table>
-<h3 id="specifying-the-java-package">Specifying the Java package</h3>
-<table>
+<h3 id="specifying-the-java-package">Specifying the Java package<a class="headerlink" href="#specifying-the-java-package" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -1069,8 +1080,8 @@ Java package name. <strong>Change from J
 Setting the package name will affect the directory into which the
 generated class will be written: directories will be appended to
 the <a href="#output">output directory</a> to match the Java package.</p>
-<h3 id="additional-decorations-on-the-main-class-declaration">Additional decorations on the main class declaration</h3>
-<table>
+<h3 id="additional-decorations-on-the-main-class-declaration">Additional decorations on the main class declaration<a class="headerlink" href="#additional-decorations-on-the-main-class-declaration" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -1094,8 +1105,8 @@ the class implements a given interface (
 <code>java.lang.Serializable</code>). Any string given as the value of the
 class-declaration option will be written immediately after
 "<code>public class &lt;i&gt;ClassName&lt;/i&gt;</code>".</p>
-<h3 id="adding-general-declarations-within-the-generated-class">Adding general declarations within the generated class</h3>
-<table>
+<h3 id="adding-general-declarations-within-the-generated-class">Adding general declarations within the generated class<a class="headerlink" href="#adding-general-declarations-within-the-generated-class" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -1123,8 +1134,8 @@ constants. The value of the option shoul
 on the code). Although this option can be declared as a command
 line option, it is typically easier to specify as a value in a
 configuration options file.</p>
-<h3 id="omitting-sections-of-the-generated-vocabulary">Omitting sections of the generated vocabulary</h3>
-<table>
+<h3 id="omitting-sections-of-the-generated-vocabulary">Omitting sections of the generated vocabulary<a class="headerlink" href="#omitting-sections-of-the-generated-vocabulary" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -1149,8 +1160,8 @@ the corresponding <em>noXYZ</em> configu
 specifying <code>--noproperties</code> means that the generated class will not
 contain any constants corresponding to predicate names from the
 ontology, irrespective of what is in the input document.</p>
-<h3 id="section-header-comments">Section header comments</h3>
-<table>
+<h3 id="section-header-comments">Section header comments<a class="headerlink" href="#section-header-comments" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -1174,8 +1185,8 @@ arbitrary Java code, though typically th
 at the head of the sections of class constant declarations,
 datatype constant declarations, property constant declarations,
 and individual constant declarations.</p>
-<h3 id="include-vocabulary-source-code">Include vocabulary source code</h3>
-<table>
+<h3 id="include-vocabulary-source-code">Include vocabulary source code<a class="headerlink" href="#include-vocabulary-source-code" title="Permanent link">&para;</a></h3>
+<table class="table">
 <thead>
 <tr>
 <th></th>
@@ -1209,7 +1220,7 @@ will:</p>
 <p>Note that Java compilers typically impose some limit on the size of a Java source file (or, more
 specifically, on the size of <code>.class</code> file they will generate. Loading a particularly large
 vocabulary with <code>--includeSource</code> may risk breaching that limit.</p>
-<h2 id="using-schemagen-with-maven">Using schemagen with Maven</h2>
+<h2 id="using-schemagen-with-maven">Using schemagen with Maven<a class="headerlink" href="#using-schemagen-with-maven" title="Permanent link">&para;</a></h2>
 <p><a href="http://maven.apache.org/">Apache Maven</a> is a build automation tool typically used for Java.  You can use <code>exec-maven-plugin</code> and <code>build-helper-maven-plugin</code> to run <code>schemagen</code> as part of the <code>generate-sources</code> goal of your project.  The following example shows one way of performing this task.  The developer should customize command-line options or use a configuration file instead as needed.</p>
 <div class="codehilite"><pre>  <span class="nt">&lt;build&gt;</span>
     <span class="nt">&lt;plugins&gt;</span>
@@ -1259,7 +1270,7 @@ vocabulary with <code>--includeSource</c
 
 
 <p>At this point you can run <code>mvn generate-sources</code> in your project to cause <code>schemagen</code> to run and create your Java source (note that this goal is run automatically from <code>mvn compile</code> or <code>mvn install</code>, so there really isn't any reason to to run it manually unless you wish to just generate the source).  The source file is placed in the maven standard <code>target/generated-sources/java</code> directory, which is added to the project classpath by <code>build-helper-maven-plugin</code>.</p>
-<h2 id="using-schemagen-with-ant">Using schemagen with Ant</h2>
+<h2 id="using-schemagen-with-ant">Using schemagen with Ant<a class="headerlink" href="#using-schemagen-with-ant" title="Permanent link">&para;</a></h2>
 <p><a href="http://ant.apache.org/">Apache Ant</a> is a tool for automating build
 steps in Java (and other language) projects. For example, it is the
 tool used to compile the Jena sources to the jena.jar file, and to
@@ -1312,7 +1323,7 @@ and those that are specified in the conf
 necessarily the "right" way to use schemagen from Ant, but if it
 points readers in the appropriate direction to produce a custom
 target for their own application it will have served its purpose.</p>
-<h2 id="appendix-a-complete-example-configuration-file">Appendix A: Complete example configuration file</h2>
+<h2 id="appendix-a-complete-example-configuration-file">Appendix A: Complete example configuration file<a class="headerlink" href="#appendix-a-complete-example-configuration-file" title="Permanent link">&para;</a></h2>
 <p>The source of this example is provided in the Jena download as
 <code>etc/schemagen.rdf</code>. For clarity, RDF/XML text is highlighted in
 blue.</p>

Modified: websites/staging/jena/trunk/content/tutorials/rdf_api.html
==============================================================================
--- websites/staging/jena/trunk/content/tutorials/rdf_api.html (original)
+++ websites/staging/jena/trunk/content/tutorials/rdf_api.html Tue Jul 14 12:52:14 2015
@@ -763,7 +763,7 @@ adding a whole group of mappings at once
 
 <p>Jena is a Java API for semantic web applications.  The key RDF package for
 the application developer is
-<code>com.hp.hpl.jena.rdf.model</code>. The API has been defined
+<code>org.apache.jena.rdf.model</code>. The API has been defined
 in terms of interfaces so that application code can work with different
 implementations without change. This package contains interfaces for
 representing models, resources, properties, literals, statements and all the
@@ -772,10 +772,10 @@ application code remains independent of
 the implementation, it is best if it uses interfaces wherever possible, not
 specific class implementations.</p>
 
-<p>The <code>com.hp.hpl.jena.tutorial</code> package contains the
+<p>The <code>org.apache.jena.tutorial</code> package contains the
 working source code for all the examples used in this tutorial.</p>
 
-<p>The <code>com.hp.hpl.jena...impl</code> packages contains
+<p>The <code>org.apache.jena...impl</code> packages contains
 implementation classes which may be common to many implementations. For
 example, they defines classes <code>ResourceImpl</code>,
 <code>PropertyImpl</code>, and <code>LiteralImpl</code> which may be
@@ -935,7 +935,7 @@ method <code>model.listStatements(Select
 iterator over all the statements in the model 'selected' by <code>s</code>.
 The selector interface is designed to be extensible, but for now, there is
 only one implementation of it, the class <code>SimpleSelector</code> from the
-package <code>com.hp.hpl.jena.rdf.model</code>.  Using
+package <code>org.apache.jena.rdf.model</code>.  Using
 <code>SimpleSelector </code>is one of the rare occasions in Jena when it is
 necessary to use a specific class rather than an interface.  The
 <code>SimpleSelector</code> constructor takes three arguments:</p>
@@ -1137,9 +1137,9 @@ should be reasonably clear that the Mode
 intersection and difference of the Models can be computed in a similar
 manner, using the methods <code>.intersection(Model)</code> and
 <code>.difference(Model)</code>; see the
-<a href="/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#difference(com.hp.hpl.jena.rdf.model.Model)">difference</a>
+<a href="/documentation/javadoc/jena/org/apache/jena/rdf/model/Model.html#difference(org.apache.jena.rdf.model.Model)">difference</a>
 and
-<a href="/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#intersection(com.hp.hpl.jena.rdf.model.Model)">intersection</a>
+<a href="/documentation/javadoc/jena/org/apache/jena/rdf/model/Model.html#intersection(org.apache.jena.rdf.model.Model)">intersection</a>
 Javadocs for more details.
 </p>
 

Modified: websites/staging/jena/trunk/content/tutorials/rdf_api_pt.html
==============================================================================
--- websites/staging/jena/trunk/content/tutorials/rdf_api_pt.html (original)
+++ websites/staging/jena/trunk/content/tutorials/rdf_api_pt.html Tue Jul 14 12:52:14 2015
@@ -144,7 +144,18 @@
     <div class="col-md-12">
     <div id="breadcrumbs"></div>
     <h1 class="title">Uma Introdução a RDF e à API RDF de Jena</h1>
-  <h2>Prefácio</h2>
+  <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>
+<h2>Prefácio</h2>
 
 <p>Este é um tutorial introdutório ao framework de descrição de recursos (RDF)
 e Jena, uma API Java para RDF. Ele é escrito para programadores que 
@@ -590,11 +601,11 @@ Você verá que os prefixos da entra
 <h2 id="ch-Jena RDF Packages">Pacotes Jena RDF</h2>
 
 <p>Jena é uma API JAVA para aplicações de web semântica. O pacote RDF chave para o desenvolvedor é
-<code>com.hp.hpl.jena.rdf.model</code>. A API  tem sido definida em termos de interfaces, logo o código da aplicação pode trabalhar com diferentes implementações sem causar mudanças. Esse pacote contém interfaces para representar modelos, recursos, propriedades, literais, sentenças e todos os outros conceitos chaves de RDF, e um ModelFactory para criação de modelos. Portanto, o código da aplicação permanece independente da implementação, o melhor é usar interfaces onde for possível e não implementações específicas de classes.</p>
+<code>org.apache.jena.rdf.model</code>. A API  tem sido definida em termos de interfaces, logo o código da aplicação pode trabalhar com diferentes implementações sem causar mudanças. Esse pacote contém interfaces para representar modelos, recursos, propriedades, literais, sentenças e todos os outros conceitos chaves de RDF, e um ModelFactory para criação de modelos. Portanto, o código da aplicação permanece independente da implementação, o melhor é usar interfaces onde for possível e não implementações específicas de classes.</p>
 
-<p>O pacote <code>com.hp.hpl.jena.tutorial</code> contém o código fonte funcional de todos os exemplos usados neste tutorial.</p>
+<p>O pacote <code>org.apache.jena.tutorial</code> contém o código fonte funcional de todos os exemplos usados neste tutorial.</p>
 
-<p>Os pacotes <code>com.hp.hpl.jena...impl</code> contêm a implementação de classes que podem ser comuns a várias implementações. Por exemplo, eles definem as classes <code>ResourceImpl</code>,
+<p>Os pacotes <code>org.apache.jena...impl</code> contêm a implementação de classes que podem ser comuns a várias implementações. Por exemplo, eles definem as classes <code>ResourceImpl</code>,
 <code>PropertyImpl</code>, e <code>LiteralImpl</code> que podem ser usadas diretamente ou então herdadas por diferentes implementações. As aplicações devem raramente usar essas classes diretamente. Por exemplo, em vez de criar um nova instância de  <code>ResourceImpl</code>, é melhor usar o método <code>createResource</code> do modelo que estiver sendo usado. Desta forma, se a implementação do modelo usar uma implementação otimizada de <code>Resource</code>, então não serão necessárias conversões entre os dois tipos.</p>
 
 
@@ -692,7 +703,7 @@ while (iter.hasNext()) {
 }</code></pre>
 </blockquote>
 
-<p>Todos esses métodos de consulta são acuçar sintático sobre o método primitivo de consulta <code>model.listStatements(Selector s)</code>. Esse método retorna um iterador sobre todas as sentenças no modelo 'selecionado' por <code>s</code>. A interface de selector foi feita para ser extensível, mas por hora, só há uma implementação dela, a classe  <code>SimpleSelector</code> do pacote <code>com.hp.hpl.jena.rdf.model</code>. Usar <code>SimpleSelector </code> é uma das raras ocasiões em Jena onde é necessário usar uma classe especifica em vez de uma interface. O construtor de <code>SimpleSelector</code> recebe três argumentos:</p>
+<p>Todos esses métodos de consulta são acuçar sintático sobre o método primitivo de consulta <code>model.listStatements(Selector s)</code>. Esse método retorna um iterador sobre todas as sentenças no modelo 'selecionado' por <code>s</code>. A interface de selector foi feita para ser extensível, mas por hora, só há uma implementação dela, a classe  <code>SimpleSelector</code> do pacote <code>org.apache.jena.rdf.model</code>. Usar <code>SimpleSelector </code> é uma das raras ocasiões em Jena onde é necessário usar uma classe especifica em vez de uma interface. O construtor de <code>SimpleSelector</code> recebe três argumentos:</p>
 
 <blockquote>
   <pre><code>Selector selector = new SimpleSelector(subject, predicate, object)
@@ -866,9 +877,9 @@ model.write(system.out, "RDF/XML-ABBREV"
 
 <p>Mesmo que você não seja familiarizado com  os detalhes da sintaxe RDF/XML, deve ser relativamente claro que os modelos foram unidos como esperado A interseção e a diferença de modelos podem ser computados de maneira semelhante, usando os métodos <code>.intersection(Model)</code> e
 <code>.difference(Model)</code>; veja a documentação de
-<a href="/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#difference(com.hp.hpl.jena.rdf.model.Model)">difference</a>
+<a href="/documentation/javadoc/jena/org/apache/jena/rdf/model/Model.html#difference(org.apache.jena.rdf.model.Model)">difference</a>
 e
-<a href "/documentation/javadoc/jena/com/hp/hpl/jena/rdf/model/Model.html#intersection(com.hp.hpl.jena.rdf.model.Model)">intersection</a>
+<a href "/documentation/javadoc/jena/org/apache/jena/rdf/model/Model.html#intersection(org.apache.jena.rdf.model.Model)">intersection</a>
 para mais detalhes.
 </p>
 

Modified: websites/staging/jena/trunk/content/tutorials/using_jena_with_eclipse_pt.html
==============================================================================
--- websites/staging/jena/trunk/content/tutorials/using_jena_with_eclipse_pt.html (original)
+++ websites/staging/jena/trunk/content/tutorials/using_jena_with_eclipse_pt.html Tue Jul 14 12:52:14 2015
@@ -144,7 +144,18 @@
     <div class="col-md-12">
     <div id="breadcrumbs"></div>
     <h1 class="title">Usando Jena com o Eclipse</h1>
-  <p><strong>Original credits to: <a href="http://www.iandickinson.me.uk/articles/jena-eclipse-helloworld/">Ian dickinson</a></strong></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><strong>Original credits to: <a href="http://www.iandickinson.me.uk/articles/jena-eclipse-helloworld/">Ian dickinson</a></strong></p>
 <p>Eu com certa frequência recebo emails da seguinte forma:</p>
 <blockquote>
 <div class="codehilite"><pre><span class="n">Prezado</span> <span class="n">Sr</span><span class="o">/</span><span class="n">Dr</span><span class="o">/</span><span class="n">Prof</span> <span class="n">Dickinson</span>
@@ -158,7 +169,7 @@
 <p>•   Instruções sobre <a href="http://www.cs.umd.edu/class/spring2006/cmsc132/EclipseTutorial/install.html">instalação do Eclipse</a></p>
 <p>•   Um <a href="http://jena.sourceforge.net/tutorial/RDF_API/">tutorial de Jena</a></p>
 <p>Em vez disto, meus objetivos para este artigo são mostrar a você como fazer um programa Jena bem básico no Eclipse. Em outras palavras, o equivalente em Jena do <a href="http://en.wikipedia.org/wiki/Hello_world_program">hello world</a>.</p>
-<h2 id="preambulo">Preâmbulo</h2>
+<h2 id="preambulo">Preâmbulo<a class="headerlink" href="#preambulo" title="Permanent link">&para;</a></h2>
 <p>Jena é uma API (application programming interface) de programação para aplicações
  de web semântica em Java. Ele não é um programa ou ferramenta que você “roda” –
  se é isto que você está procurando, eu sugiro <a href="http://www.topbraidcomposer.com/">TopBraid Composer</a> como uma boa 
@@ -167,7 +178,7 @@ opção. Desta forma, o principal us
  como meu ambiente de programação Java, existem outros ambientes disponíveis,
  mas eu não os uso e, portanto, 
 a experiência que eu posso passar é baseada no Eclipse.</p>
-<h2 id="pre-requesitos">Pré-requesitos</h2>
+<h2 id="pre-requesitos">Pré-requesitos<a class="headerlink" href="#pre-requesitos" title="Permanent link">&para;</a></h2>
 <p>Você precisará:</p>
 <ol>
 <li>Baixar em instalar o <a href="http://www.eclipse.org/">eclipse</a>. Este artigo foi escrito com o Eclipse 3.3.1, mas o número exato da versão não deveria importar já que a interface principal do Eclipse tem sido estável já há algum tempo.</li>
@@ -182,11 +193,11 @@ Settings\ijd</code> como diretório pa
 geralmente é uma boa ideia evitar caminhos de diretórios com espaços entre 
 eles, se você puder. Então, a instalação do meu Jena está em: <code>c:\home\ijd\projects\jena2</code>.
  Em qualquer lugar que você vê este caminho de diretório neste tutorial, substitua-o pelo lugar onde você instalou o seu Jena.</p>
-<h2 id="guia-passo-a-passo">Guia passo a passo</h2>
+<h2 id="guia-passo-a-passo">Guia passo a passo<a class="headerlink" href="#guia-passo-a-passo" title="Permanent link">&para;</a></h2>
 <p>Este tutorial é realmente para os novatos no Eclipse, então vou fazer um 
 passo por vez. Se você já tem alguma experiência com Eclipse, sinta-se à 
 vontade para pular alguns passos.  </p>
-<h2 id="passo-1-cria-um-java-project">Passo 1 – Cria um Java Project</h2>
+<h2 id="passo-1-cria-um-java-project">Passo 1 – Cria um Java Project<a class="headerlink" href="#passo-1-cria-um-java-project" title="Permanent link">&para;</a></h2>
 <p>Eclipse organiza arquivos em projetos (<em>projects</em>), então nós vamos precisar de um projeto neste tutorial. Dependendo dos plugins instalados, o Eclipse pode mostrar um grande número de diferentes tipos de projetos. Um projeto simples em Java é o suficiente para uma aplicação simples em Jena.  Se ao invés disso, você quisesse desenvolver um servlet Java que usa Jena, então use um tipo de projeto adequado. 
 Por clareza, eu vou começar com um workspace vazio no Eclipse:</p>
 <p align="center">
@@ -216,7 +227,7 @@ faz parte ou sua instituição educa
 <p align="center">
 <img border="0" src="figures/jhw_fig5.png"></p>
 
-<h2 id="passo-2-crie-uma-classe-hello-world">Passo 2: crie uma classe “hello world”</h2>
+<h2 id="passo-2-crie-uma-classe-hello-world">Passo 2: crie uma classe “hello world”<a class="headerlink" href="#passo-2-crie-uma-classe-hello-world" title="Permanent link">&para;</a></h2>
 <p>O código de Java fica em arquivos que correspondem à declaração de
  uma classe Java, então eu preciso criar uma classe para o meu exemplo
  de “hello world”. No <em>project explorer</em> (que fica no lado esquerdo por padrão,
@@ -229,11 +240,11 @@ faz parte ou sua instituição educa
 <p align="center">
 <img border="0" src="figures/jhw_fig7.png"></p>
 
-<h2 id="passo-3-adicionando-as-bibliotecas-de-jena">Passo 3: adicionando as bibliotecas de Jena</h2>
+<h2 id="passo-3-adicionando-as-bibliotecas-de-jena">Passo 3: adicionando as bibliotecas de Jena<a class="headerlink" href="#passo-3-adicionando-as-bibliotecas-de-jena" title="Permanent link">&para;</a></h2>
 <p>OK, agora vamos escrever algum código em Jena. 
 A primeira coisa que eu precisarei para trabalhar é um <code>Model</code> (modelo):
  um container para comandos RDF. A classe <code>Model</code> está no pacote (<em>package</em>)
- <code>com.hp.hpl.jena.rdf.model</code>, então primeiro eu irei importar (<em>import</em>) a 
+ <code>org.apache.jena.rdf.model</code>, então primeiro eu irei importar (<em>import</em>) a 
 classe e só então criar uma instância dela. </p>
 <p align="center">
 <img border="0" src="figures/jhw_fig8.png"></p>
@@ -241,7 +252,7 @@ classe e só então criar uma instÃ
 <p>Certo, então por que o código está sublinhando em vermelho? Este é o jeito do
  Eclipse de indicar que existe um problema no código. Se eu tentasse compilar
  este código usando <code>javac</code> na linha de comando, eu receberia uma mensagem de
- erro dizendo que o pacote <code>com.hp.hpl.jena.rdf.model</code>  não pôde ser encontrado,
+ erro dizendo que o pacote <code>org.apache.jena.rdf.model</code>  não pôde ser encontrado,
  e que a classe <code>Model</code> não foi definida. Na linha de comando, eu consertaria
  isto configurando o <code>Java classpath</code>. Essencialmente, isso é o que eu faço no
  Eclipse também, mas o Eclipse torna isto muito mais fácil. Note que eu não 
@@ -313,7 +324,7 @@ use este recurso aqui. </p>
 
 <p>Com a biblioteca de usuário Jena configurada, eu clico em Ok para fechar a 
 caixa de diálogo de configurações de biblioteca.  </p>
-<h2 id="passo-4-finalizando-o-programa-hello-world">Passo 4: Finalizando o programa “hello world”</h2>
+<h2 id="passo-4-finalizando-o-programa-hello-world">Passo 4: Finalizando o programa “hello world”<a class="headerlink" href="#passo-4-finalizando-o-programa-hello-world" title="Permanent link">&para;</a></h2>
 <p>Agora eu posso voltar ao meu projeto e configurar o <em>build path</em> de Java para 
 a biblioteca que eu acabei de criar. Para começar, clico com o botão direito 
 no nó do projeto no <em>Explorer window</em> para abrir o menu de propriedades do
@@ -368,7 +379,7 @@ Aqui está o programa <em>hello world<
 <p align="center">
 <img border="0" src="figures/jhw_fig24.png"></p>
 
-<h2 id="passo-5-rodando-o-programa-hello-world">Passo 5: rodando o programa “hello world”</h2>
+<h2 id="passo-5-rodando-o-programa-hello-world">Passo 5: rodando o programa “hello world”<a class="headerlink" href="#passo-5-rodando-o-programa-hello-world" title="Permanent link">&para;</a></h2>
 <p>Para rodar este programa a partir do Eclipse, eu uso o menu <em>run</em>, acessado a
  partir do botão mostrando um triângulo branco dentro de um círculo verde. 
 Dado que eu ainda não tinha rodado nenhum código, eu tenho que dizer ao