You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by bu...@apache.org on 2013/05/19 19:58:34 UTC
svn commit: r862442 - in /websites/staging/jena/trunk/content: ./
tutorials/rdf_api.html
Author: buildbot
Date: Sun May 19 17:58:34 2013
New Revision: 862442
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/tutorials/rdf_api.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun May 19 17:58:34 2013
@@ -1 +1 @@
-1484091
+1484323
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 Sun May 19 17:58:34 2013
@@ -663,11 +663,11 @@ prefixes other than the standard ones:</
</blockquote>
<p>We see that the rdf namespace is declared automatically, since it
-is required for tags such as <code><RDF:rdf></code> and
-<code><rdf:resource></code>. Namespace declarations are also
+is required for tags such as <code><rdf:RDF></code> and
+<code><rdf:resource></code>. XML namespace declarations are also
needed for using the two properties P and Q, but since their
-namespaces have not been introduced to the model, they get invented
-namespace names: <code>j.0</code> and <code>j.1</code>.</p>
+prefixes have not been introduced to the model in this example,
+they get invented namespace names: <code>j.0</code> and <code>j.1</code>.</p>
<p>The method <code>setNsPrefix(String prefix, String URI)</code>
declares that the namespace <code>URI</code> may be abbreviated
by <code>prefix</code>. Jena requires that <code>prefix</code> be