Author: ito
Date: Wed Dec 16 08:23:09 2009
New Revision: 891155
URL: http://svn.apache.org/viewvc?rev=891155&view=rev
Log:
CLEREZZA-35: tutorials replaced
Modified:
incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/overview.xhtml
incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/scb-triaxrs-tutorial.xhtml
incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/tutorial_1.xhtml
Modified:
incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/overview.xhtml
URL:
http://svn.apache.org/viewvc/incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/overview.xhtml?rev=891155&r1=891154&r2=891155&view=diff
==============================================================================
---
incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/overview.xhtml
(original)
+++
incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/overview.xhtml
Wed Dec 16 08:23:09 2009
@@ -31,21 +31,21 @@
<p>Contributor: Reto Bachmann-Gmür - clerezza.org</p>
<h2>Introduction</h2>
<p>
- Smart Content Binding (SCB) is an open source framework
developed by
- clerezza.org aiming primarily at providing a java
implementation of the
- graph data model specified by W3C RDF [<a
href="#ref1">1</a>] and
- functionalities to operate on that data model. SCB
offers a service
- interface to access multiple named graphs and it can
use various
- providers to manage RDF graphs in a technology specific
manner, e.g.,
- using Jena [<a href="#ref2">2</a>] (TBD) or Sesame [<a
href="#ref3">3</a>].
- It also provides façades that allow an application to
use Jena or Sesame (TBD)
+ Smart Content Binding (SCB) is an open source framework
developed by
+ clerezza.org aiming primarily at providing a java
implementation of the
+ graph data model specified by W3C RDF [<a
href="#ref1">1</a>] and
+ functionalities to operate on that data model. SCB
offers a service
+ interface to access multiple named graphs and it can
use various
+ providers to manage RDF graphs in a technology specific
manner, e.g.,
+ using Jena [<a href="#ref2">2</a>] (TBD) or Sesame [<a
href="#ref3">3</a>].
+ It also provides façades that allow an application to
use Jena or Sesame (TBD)
APIs to process RDF graphs (note that the choice of a
façade is independent of
the chosen backend; you can for example use the Jena
façade to write
your code against the Jena API while using the Sesame
provider to store
- your data in a Sesame store).
- Furthermore, SCB offers a serialization and a parsing
service to convert
- a graph into a certain representation (format) and vice
versa. In order
- to support ontologies usage, SCB provides a tool to
convert ontologies
+ your data in a Sesame store).
+ Furthermore, SCB offers a serialization and a parsing
service to convert
+ a graph into a certain representation (format) and vice
versa. In order
+ to support ontologies usage, SCB provides a tool to
convert ontologies
defined in various formats including RDF/XML into Java
classes.
</p>
@@ -67,43 +67,43 @@
<br/><i>Figure 1: SCB Architecture</i>
</p>
<p>
- The Core contains interface definitions of the RDF
graph data model and its
- implementation. The three main classes are
<code>Graph</code>, <code>MGraph</code>,
- and <code>TripleCollection</code>. The class
<code>Graph</code> represents an
- immutable RDF Graph, as such its identity criterion is
defined in terms of
- graph-isomorphism. The class <code>MGraph</code>
represents a mutable RDF Graph,
- which enables triples to be added to or removed from a
graph. The class
- <code>TripleCollection</code> is the super class of
both the class <code>Graph</code>
- and <code>MGraph</code>.
- SCB Core provides three services:
<code>TcManager</code> [<a href="#ref4">4</a>] allows access to
- the various <code>TripleCollection</code>s,
<code>Parser</code> [<a href="#ref5">5</a>] and
- <code>Serializer</code> [<a href="#ref6">6</a>] to
allow reading and writing graphs from and to
- various formats. In an OSGi environment these services
are accessed using the
- service registry or injected using OSGi Declarative
Services. In a non OSGi environment
- static factory methods are used to return an instance.
- The <code>TcManager</code> delegates actual processing
tasks to a specific Storage Provider
- chosen from a set of Storage Providers based on their
priority number (weight).
- Storage Providers can be dynamically bound to or
unbound from the Core.
- The functionality required by the Parser and Serializer
is delegated to registered
- Parsing and Serializing Providers respectively,
according to their capability
+ The Core contains interface definitions of the RDF
graph data model and its
+ implementation. The three main classes are
<code>Graph</code>, <code>MGraph</code>,
+ and <code>TripleCollection</code>. The class
<code>Graph</code> represents an
+ immutable RDF Graph, as such its identity criterion is
defined in terms of
+ graph-isomorphism. The class <code>MGraph</code>
represents a mutable RDF Graph,
+ which enables triples to be added to or removed from a
graph. The class
+ <code>TripleCollection</code> is the super class of
both the class <code>Graph</code>
+ and <code>MGraph</code>.
+ SCB Core provides three services:
<code>TcManager</code> [<a href="#ref4">4</a>] allows access to
+ the various <code>TripleCollection</code>s,
<code>Parser</code> [<a href="#ref5">5</a>] and
+ <code>Serializer</code> [<a href="#ref6">6</a>] to
allow reading and writing graphs from and to
+ various formats. In an OSGi environment these services
are accessed using the
+ service registry or injected using OSGi Declarative
Services. In a non OSGi environment
+ static factory methods are used to return an instance.
+ The <code>TcManager</code> delegates actual processing
tasks to a specific Storage Provider
+ chosen from a set of Storage Providers based on their
priority number (weight).
+ Storage Providers can be dynamically bound to or
unbound from the Core.
+ The functionality required by the Parser and Serializer
is delegated to registered
+ Parsing and Serializing Providers respectively,
according to their capability
(supported formats). Later registered providers shadow
previous ones for the same format.
</p>
<p>
- The current implementation of SCB includes a Jena
Façade. The Jena Façade allows an
- application to use Jena API to manipulate a TC.
+ The current implementation of SCB includes a Jena
Façade. The Jena Façade allows an
+ application to use Jena API to manipulate a TC.
</p>
<p>
- In order to ease operations on a resource in a TC, the
Utilities component provides
- a class with a set of useful methods, e.g., to delete
all triples (statements) with
- the resource as subject and a specified predicate.
+ In order to ease operations on a resource in a TC, the
Utilities component provides
+ a class with a set of useful methods, e.g., to delete
all triples (statements) with
+ the resource as subject and a specified predicate.
</p>
<p>
- Finally, the Ontologies Tool contains a standalone
application called SchemaGen to
+ Finally, the Ontologies Tool contains a standalone
application called SchemaGen to
generate the Java source code with constants from an
ontology description.
</p>
<h2>Artifacts</h2>
<p>
- Each architectural component described above comprises
one or more artifacts as
+ Each architectural component described above comprises
one or more artifacts as
listed in Table 1.
<br/><br/><i>Table 1: Artifacts of each architectural
components</i><br/>
</p>
@@ -115,67 +115,67 @@
</tr>
<tr>
<td rowspan="2">Core</td>
- <td>org.apache.clerezza.rdf.core</td>
+ <td>org.clerezza.rdf.core</td>
<td>Jar and OSGi bundle</td>
</tr>
<tr>
- <td>org.apache.clerezza.rdf.core.test</td>
+ <td>org.clerezza.rdf.core.test</td>
<td>Jar and OSGi bundle</td>
</tr>
<tr>
<td>Façades</td>
- <td>org.apache.clerezza.rdf.jena.facade</td>
+ <td>org.clerezza.rdf.jena.facade</td>
<td>Jar and OSGi bundle</td>
</tr>
<tr>
<td>Utilities</td>
- <td>org.apache.clerezza.rdf.utils</td>
+ <td>org.clerezza.rdf.utils</td>
<td>Jar and OSGi bundle</td>
</tr>
<tr>
<td rowspan="2">Storage Providers</td>
- <td>org.apache.clerezza.rdf.sesame.storage</td>
+ <td>org.clerezza.rdf.sesame.storage</td>
<td>Jar and OSGi bundle</td>
</tr>
<tr>
- <td>org.apache.clerezza.rdf.jena.storage</td>
+ <td>org.clerezza.rdf.jena.storage</td>
<td>Jar and OSGi bundle</td>
</tr>
<tr>
<td>Parsing Providers</td>
- <td>org.apache.clerezza.rdf.jena.parser</td>
+ <td>org.clerezza.rdf.jena.parser</td>
<td>Jar and OSGi bundle</td>
</tr>
<tr>
<td>Serializing Providers</td>
- <td>org.apache.clerezza.rdf.jena.serializer</td>
+ <td>org.clerezza.rdf.jena.serializer</td>
<td>Jar and OSGi bundle</td>
</tr>
<tr>
<td>Ontologies Tool</td>
- <td>org.apache.clerezza.rdf.tool.schemagen</td>
+ <td>org.clerezza.rdf.tool.schemagen</td>
<td>Executable jar</td>
</tr>
</table>
<h2>Building SCB</h2>
<p>
- If you want to build SCB from its sources, you need JDK
version 1.6 to compile.
+ If you want to build SCB from its sources, you need JDK
version 1.6 to compile.
Maven version 2.0.9 has been used to build SCB.
</p>
<h2>Developing Applications using SCB</h2>
<p>
- To develop an application on top of SCB, you need to
have the Core and optionally
+ To develop an application on top of SCB, you need to
have the Core and optionally
Utilities and Façades.
</p>
<h2>Deploying an Application Requiring SCB</h2>
<p>
- To deploy an application which uses SCB, Java(TM) SE
Runtime Environment 6 or
- higher is needed. If the application does not use OSGi,
then the SCB Core,
- the jars required for compilation, as well as the
needed implementations
- (typically one provider for storage, serialization, and
parsing) must be in
- the classpath. If the application uses OSGi, these jars
are loaded as bundles,
- and to run in OSGi, Declarative Services must be
enabled (see the documentation
- of your OSGi container).
+ To deploy an application which uses SCB, Java(TM) SE
Runtime Environment 6 or
+ higher is needed. If the application does not use OSGi,
then the SCB Core,
+ the jars required for compilation, as well as the
needed implementations
+ (typically one provider for storage, serialization, and
parsing) must be in
+ the classpath. If the application uses OSGi, these jars
are loaded as bundles,
+ and to run in OSGi, Declarative Services must be
enabled (see the documentation
+ of your OSGi container).
</p>
<p>
The use of SCB in an OSGi environment has been tested
with Apache Felix [<a href="#ref7">7</a>]
@@ -183,11 +183,11 @@
</p>
<h2>Extending and Customizing SCB</h2>
<p>
- Since SCB applies a Service Oriented Architecture
approach, following components
- can be easily extended: Storage Providers, Parsing
Providers, and Serializing
- Providers. Using OSGi, new bundles just need to
implement the required service
- interfaces. To be located outside an OSGi environment,
they should also provide
- files in "META-INF/services" for the services they
expose. Consult the SCB JavaDoc
+ Since SCB applies a Service Oriented Architecture
approach, following components
+ can be easily extended: Storage Providers, Parsing
Providers, and Serializing
+ Providers. Using OSGi, new bundles just need to
implement the required service
+ interfaces. To be located outside an OSGi environment,
they should also provide
+ files in "META-INF/services" for the services they
expose. Consult the SCB JavaDoc
for more information [<a href="#ref9">9</a>].
</p>
<h2>References</h2>
@@ -197,21 +197,20 @@
</p>
<p id="ref3">[3] <a
href="http://www.openrdf.org/";>http://www.openrdf.org/</a>
</p>
- <p id="ref4">[4] <a
href="http://clerezza.org/projects/org.apache.clerezza.rdf.core/apidocs/index.html?org/apache/clerezza/rdf/core/access/TcManager.html";>
-
http://clerezza.org/projects/org.apache.clerezza.rdf.core/apidocs/index.html?org/apache/clerezza/rdf/core/access/TcManager.html</a>
+ <p id="ref4">[4] <a
href="http://clerezza.org/projects/org.clerezza.rdf.core/apidocs/index.html?org/clerezza/rdf/core/access/TcManager.html";>
+
http://clerezza.org/projects/org.clerezza.rdf.core/apidocs/index.html?org/clerezza/rdf/core/access/TcManager.html</a>
</p>
- <p id="ref5">[5] <a
href="http://clerezza.org/projects/org.apache.clerezza.rdf.core/apidocs/org/apache/clerezza/rdf/core/serializedform/Parser.html";>
-
http://clerezza.org/projects/org.apache.clerezza.rdf.core/apidocs/org/apache/clerezza/rdf/core/serializedform/Parser.html</a>
+ <p id="ref5">[5] <a
href="http://clerezza.org/projects/org.clerezza.rdf.core/apidocs/org/clerezza/rdf/core/serializedform/Parser.html";>
+
http://clerezza.org/projects/org.clerezza.rdf.core/apidocs/org/clerezza/rdf/core/serializedform/Parser.html</a>
</p>
- <p id="ref6">[6] <a
href="http://clerezza.org/projects/org.apache.clerezza.rdf.core/apidocs/org/apache/clerezza/rdf/core/serializedform/Serializer.html";>
-
http://clerezza.org/projects/org.apache.clerezza.rdf.core/apidocs/org/apache/clerezza/rdf/core/serializedform/Serializer.html</a>
+ <p id="ref6">[6] <a
href="http://clerezza.org/projects/org.clerezza.rdf.core/apidocs/org/clerezza/rdf/core/serializedform/Serializer.html";>
+
http://clerezza.org/projects/org.clerezza.rdf.core/apidocs/org/clerezza/rdf/core/serializedform/Serializer.html</a>
</p>
<p id="ref7">[7] <a
href="http://felix.apache.org/site/index.html";>http://felix.apache.org/site/index.html</a>
</p>
<p id="ref8">[8] <a
href="http://www.eclipse.org/equinox/";>http://www.eclipse.org/equinox/</a>
</p>
- <p id="ref9">[9] <a
href="http://clerezza.org/projects/org.apache.clerezza.rdf.core/apidocs/index.html";>http://clerezza.org/projects/org.apache.clerezza.rdf.core/apidocs/index.html</a>
+ <p id="ref9">[9] <a
href="http://clerezza.org/projects/org.clerezza.rdf.core/apidocs/index.html";>http://clerezza.org/projects/org.clerezza.rdf.core/apidocs/index.html</a>
</p>
</body>
-</html>
-
+</html>
\ No newline at end of file
Modified:
incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/scb-triaxrs-tutorial.xhtml
URL:
http://svn.apache.org/viewvc/incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/scb-triaxrs-tutorial.xhtml?rev=891155&r1=891154&r2=891155&view=diff
==============================================================================
---
incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/scb-triaxrs-tutorial.xhtml
(original)
+++
incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/scb-triaxrs-tutorial.xhtml
Wed Dec 16 08:23:09 2009
@@ -54,14 +54,14 @@
<h2 id="introduction">1. Introduction</h2>
<p>
REST [<a href="#ref1">1</a>] is a software architecture
style
- applicable to the World Wide Web. With the advent of
the Semantic Web
- this resource oriented design shows its strength. The
web of documents
+ applicable to the World Wide Web. With the advent of
the Semantic Web
+ this resource oriented design shows its strength. The
web of documents
evolves seamlessly to a web of data and knowledge.
</p>
<p>
- RESTful Web applications are designed based on a set of
REST
- principles. In this introductory tutorial you'll learn
how to develop
- a RESTful application that delivers human readable
semantic content
+ RESTful Web applications are designed based on a set of
REST
+ principles. In this introductory tutorial you'll learn
how to develop
+ a RESTful application that delivers human readable
semantic content
which is stored in a triple store.
</p>
<p>
@@ -72,11 +72,11 @@
</p>
<h2 id="setting">2. Setting up the project</h2>
<p>
- Create a maven project with the following parent and
dependencies
- (see the Triaxrs Tutorial 1 (Developing a RESTful Web
Application
+ Create a maven project with the following parent and
dependencies
+ (see the Triaxrs Tutorial 1 (Developing a RESTful Web
Application
for OSGi Runtime Environment) for more detail [<a
href="#ref4">4</a>]):
</p>
-
+
<p>First configure the repositories as follows:</p>
<blockcode>
<repositories>
@@ -92,20 +92,20 @@
<url>http://repo.trialox.org/snapshot</url>
<layout>default</layout>
</repository>
-</repositories>
+</repositories>
</blockcode>
<blockcode>
<parent>
<artifactId>org.clerezza.parent</artifactId>
<groupId>org.clerezza</groupId>
- <version>0.11-SNAPSHOT</version> //check <a
href="http://repo.trialox.org/release/org/clerezza/org.clerezza.parent/";>here</a>
for the newest release version or
+ <version>0.1-SNAPSHOT</version> //check <a
href="http://repo.trialox.org/release/org/clerezza/org.clerezza.parent/";>here</a>
for the newest release version or
<a
href="http://repo.trialox.org/snapshot/org/clerezza/org.clerezza.parent/";>here</a>
for newest snapshot version</parent> </blockcode>
<p>It in not necessary to define the <code>version</code> parameter of
each dependency because they are specified in the parents pom file.</p>
<blockcode>
<dependency>
<groupId>org.clerezza</groupId>
<artifactId>org.clerezza.jaxrs.rdf.providers</artifactId>
-</dependency>
+</dependency>
<dependency>
<groupId>org.clerezza</groupId>
<artifactId>org.clerezza.platform.typerendering.seedsnipe</artifactId>
@@ -113,22 +113,22 @@
<dependency>
<groupId>org.clerezza</groupId>
<artifactId>org.clerezza.triaxrs</artifactId>
-</dependency>
+</dependency>
</blockcode>
<p>Also set packaging to <code>bundle</code></p>
<p class="note">
By default the <code>maven-bundle-plugin</code> will
export the
package named <groupId>.<artifactId> and its
subpackages,
- so the exposed components must be defined in a package
named that way.
+ so the exposed components must be defined in a package
named that way.
In our example we use <code>org.example.clerezza</code>
as
groupId and <code>combined.tutorial</code> as
artifactId.
</p>
<h2 id="accessible">3. Creating an accessible service</h2>
<p>
- Like in the Triaxrs Tutorial 1 [<a href="#ref4">4</a>]
we create a
- JAX-RS class to get information about persons. To have
some data to
- play with, we will add an RDF file encoded in the
Turtle format into
+ Like in the Triaxrs Tutorial 1 [<a href="#ref4">4</a>]
we create a
+ JAX-RS class to get information about persons. To have
some data to
+ play with, we will add an RDF file encoded in the
Turtle format into
the resource tree of our project. Thus, we create the
file
src/main/resources/org/example/clerezza/combined/tutorial/data.turtle
with the following content:</p>
@@ -150,7 +150,7 @@
</blockcode>
<p>
- The JAX-RS resource class mentioned above is called in
this tutorial
+ The JAX-RS resource class mentioned above is called in
this tutorial
<code>TutorialApp</code> and looks as follows:
</p>
<blockcode>
@@ -194,17 +194,17 @@
@Path("/foaf")
public class TutorialApp {
-
+
/**
* @scr.reference
*/
TcManager tcManager;
-
+
/**
* @scr.reference
*/
private RenderletManager renderletManager;
-
+
private UriRef graphName = new UriRef("http://localhost.mygraph";);
@GET
@@ -237,12 +237,12 @@
/**
* The activate method is called when SCR activates the component
configuration.
* This method gets the system graph or create a new one if it doesn't
exist.
- *
+ *
* @param componentContext
*/
protected void activate(ComponentContext componentContext) {
-
- URL templateURL = getClass().getResource("tutorial.xhtml");
+
+ URL templateURL = getClass().getResource("tutorial.xhtml");
try {
renderletManager.registerRenderlet(SeedsnipeRenderlet.class
.getName(), new
UriRef(templateURL.toURI().toString()),
@@ -266,69 +266,69 @@
</blockcode>
<p>
- The resource class above provides two resource methods
to process
- GET requests specifying the path /foaf/find. The JAX-RS
annotation
- @Path on TutorialApp sets the path of the resource to
â/foafâ,
+ The resource class above provides two resource methods
to process
+ GET requests specifying the path /foaf/find. The JAX-RS
annotation
+ @Path on TutorialApp sets the path of the resource to
â/foafâ,
while the JAX-RS annotation @Path on the resource
methods
<code>getPersonRdf</code> and
<code>getPersonHtml</code> defines
- the subpath "find". Furthermore, the JAX-RS annotation
@Produces
- defines the list of media types that a Java type or a
method
+ the subpath "find". Furthermore, the JAX-RS annotation
@Produces
+ defines the list of media types that a Java type or a
method
can produce. A media type corresponds with the
representation of a
resource. In this tutorial <code>getPersonRdf</code>
should produce
- "application/rdf+xml", whereas
<code>getPersonHtml</code> should
- produce "application/xhtml+xml". Both methods accept a
parameter,
- whose value is obtained from the GET request parameter
called mbox.
- This is defined through the JAX-RS annotation
@QueryParam.
+ "application/rdf+xml", whereas
<code>getPersonHtml</code> should
+ produce "application/xhtml+xml". Both methods accept a
parameter,
+ whose value is obtained from the GET request parameter
called mbox.
+ This is defined through the JAX-RS annotation
@QueryParam.
</p>
<p>
- A resource can have multiple representations. For
example, a web page
- can be represented as html, pdf, plain text, or other
representations.
- The HTTP defines a mechanism known as content
negotiation to allow a
- client (e.g., a web browser) to specify which
representation it would
- like to get from the server. Using JAX-RS we can define
a
- <code>MessageBodyWriter</code> which maps a Java type
to a
- representation. In this tutorial
<code>getPersonRdf</code> returns
- a Graph, whereas <code>getPersonHtml</code> returns a
GraphNode,
+ A resource can have multiple representations. For
example, a web page
+ can be represented as html, pdf, plain text, or other
representations.
+ The HTTP defines a mechanism known as content
negotiation to allow a
+ client (e.g., a web browser) to specify which
representation it would
+ like to get from the server. Using JAX-RS we can define
a
+ <code>MessageBodyWriter</code> which maps a Java type
to a
+ representation. In this tutorial
<code>getPersonRdf</code> returns
+ a Graph, whereas <code>getPersonHtml</code> returns a
GraphNode,
which represents a node in the context of a graph. The
clerezza
- platform provides for either resources Graph and
GraphNode a
+ platform provides for either resources Graph and
GraphNode a
corresponding <code>MessageBodyWriter</code>.
</p>
<p>
- The clerezza platform's
<code>TemplatingMessageBodyWriter</code>
- produces a representation of the format
"application/xhtml+xml"
+ The clerezza platform's
<code>TemplatingMessageBodyWriter</code>
+ produces a representation of the format
"application/xhtml+xml"
from a <code>GraphNode</code>, whereas the
<code>GraphWriter</code>
produces "application/rdf+xml" from a
<code>Graph</code>.
- <code>GraphWriter</code> is implemented in the maven
project
+ <code>GraphWriter</code> is implemented in the maven
project
org.clerezza.jaxrs.rdf.providers.
The <code>TemplatingMessageBodyWriter</code> uses a
templating engine
- to render a <code>GraphNode</code> based on a
predefined template file.
- In order to allow a different <code>GraphNode</code> to
be rendered
- using a different template, each <code>GraphNode</code>
and template
+ to render a <code>GraphNode</code> based on a
predefined template file.
+ In order to allow a different <code>GraphNode</code> to
be rendered
+ using a different template, each <code>GraphNode</code>
and template
is bound to a specific RDF type.
</p>
<p>
- For the purpose of registering a template, a
+ For the purpose of registering a template, a
<code>RenderletManager</code> service is made
available. In this tutorial,
- a template (obtained from the file "tutorial.xhtml") is
registered
- for the RDF type FOAF.Person
(http://xmlns.com/foaf/0.1/Person).
- This is done in the <code>activate</code> method using
the
+ a template (obtained from the file "tutorial.xhtml") is
registered
+ for the RDF type FOAF.Person
(http://xmlns.com/foaf/0.1/Person).
+ This is done in the <code>activate</code> method using
the
<code>RenderletManager</code> service.
</p>
<p>
- In the <code>activate</code> method we also use the
<code>TcManager</code> to get
- the <code>MGraph</code> called
"http://localhost.mygraph";. If this
- graph doesn't exist, a
<code>NoSuchEntityException</code> is thrown.
- In this latter case, we catch this exception and create
an
- <code>MGraph</code>. Afterwards we add the triples from
the file
- mentioned above into the graph.
- </p>
-
- <p>
- The following template renders a FOAF.Person. For
easier readability
- namespaces can be defined. Statements which should be
interpreted by
- the templating engine starts with the character
<code>$</code>.
- The templating language allows loops and conditions.
More examples
- are available on the project website of the templating
engine
+ In the <code>activate</code> method we also use the
<code>TcManager</code> to get
+ the <code>MGraph</code> called
"http://localhost.mygraph";. If this
+ graph doesn't exist, a
<code>NoSuchEntityException</code> is thrown.
+ In this latter case, we catch this exception and create
an
+ <code>MGraph</code>. Afterwards we add the triples from
the file
+ mentioned above into the graph.
+ </p>
+
+ <p>
+ The following template renders a FOAF.Person. For
easier readability
+ namespaces can be defined. Statements which should be
interpreted by
+ the templating engine starts with the character
<code>$</code>.
+ The templating language allows loops and conditions.
More examples
+ are available on the project website of the templating
engine
(<a
href="http://clerezza.org/projects/org.clerezza.templating.seedsnipe/documentation/overview.xhtml";
target="_blank"
>http://clerezza.org/projects/org.clerezza.templating.seedsnipe/documentation/overview.xhtml</a>
</p>
<blockcode>
@@ -367,9 +367,9 @@
<h2 id="install">5. Installing the bundle in the Clerezza
Platform</h2>
<p>
- Download the latest clerezza platform launcher from
+ Download the latest clerezza platform launcher from
<a
href="http://repo.trialox.org/snapshot/org/clerezza/org.clerezza.platform.launcher.sesame/";
target="_blank" >
-
http://repo.trialox.org/snapshot/org/clerezza/org.clerezza.platform.launcher.sesame/</a>
and start it.
+
http://repo.trialox.org/snapshot/org/clerezza/org.clerezza.platform.launcher.sesame/</a>
and start it.
Go to <a
href="http://localhost:8080/user/admin/control-panel"; target="_blank"
>http://localhost:8080/user/admin/control-panel</a> (enter username: admin,
password; admin) and upload your bundle.
</p>
<h2 id="test">Test your bundle</h2>
Modified:
incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/tutorial_1.xhtml
URL:
http://svn.apache.org/viewvc/incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/tutorial_1.xhtml?rev=891155&r1=891154&r2=891155&view=diff
==============================================================================
---
incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/tutorial_1.xhtml
(original)
+++
incubator/clerezza/issues/CLEREZZA-35/org.apache.clerezza.rdf.core/src/site/xsite/content/tutorial_1.xhtml
Wed Dec 16 08:23:09 2009
@@ -224,18 +224,18 @@
</blockcode>
<p>
- The two dependencies are implementations of rdf parsers
and
+ The two dependencies are implementations of rdf parsers
and
serializers for various formats. They are based on the
Jena Framework
[<a href="#ref4">4</a>] but you don't have to care
about this.
</p>
-
+
<p>
Almost forgot, maven defaults to some rather old java
version, to fix
- this we should add the following to configure the
- <code>maven-compiler-plugin</code> to use java 6, the
+ this we should add the following to configure the
+ <code>maven-compiler-plugin</code> to use java 6, the
<code>build</code> element is a child of
<code>project</code>.
</p>
- <blockcode>
+ <blockcode>
<build>
<plugins>
<plugin>
@@ -459,9 +459,9 @@
mGraph = tcManager.createMGraph(mGraphName);
}
</blockcode>
- <p>If anything is unclear or you'd like to take it even
further, discuss
- about it on <a
href="http://forum.clerezza.org/scb-smart-content-binding-f6/";>
- http://forum.clerezza.org/scb-smart-content-binding-f6/</a></p>
+ <p>If anything is unclear or you'd like to take it even
further, ask
+ about it on our mailing list <a
href="http://lists.trialox.org/mailman/listinfo/users";>
+ http://lists.trialox.org/mailman/listinfo/users/</a></p>
<h2 id="references">8. References</h2>
<p id="ref1">[1] W3C: Resource Description Framework (RDF):
Concepts and Abstract Syntax; 2004,
<a
href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/";>http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/</a>
@@ -480,5 +480,4 @@
Conference 2005 Poster Track</p>
<p id="ref8">[8] Sesame, <a
href="http://openrdf.com/";>http://openrdf.com/</a></p>
</body>
-</html>
-
+</html>
\ No newline at end of file
