Author: buildbot
Date: Mon Jan 16 12:09:21 2012
New Revision: 802736
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/ontonet.html
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components.html
(original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/components.html
Mon Jan 16 12:09:21 2012
@@ -81,7 +81,7 @@
<p>The <a href="reasoners.html">Reasoners</a> can be used to automatically
infer additional knowledge. It is used to obtain new facts in the knowledge
base, e.g. if your enhanced content tells you about a shop located in
"Montparnasse", you can infer via a "located-in" relation that the same shop is
located in "Paris", in the "Ãle-de-France" and in "France".</p>
</li>
<li>
-<p>The <a href="ontologymanager.html">Ontology Manager</a> has the facility to
manage your ontologies. Ontologies are used to define the knowledge models that
describe the content's metadata. Additionally, the semantic of you metadata can
be defined through an ontology.</p>
+<p>The <a href="ontologymanager.html">Ontology Manager</a> is the facility
that manages your ontologies. Ontologies are used to define the knowledge
models that describe the metadata of content. Additionally, the semantics of
your metadata can be defined through an ontology.</p>
</li>
<li>
<p>The <a href="cmsadapter.html">CMS Adapter</a> can be used to map
(bidirectionally) existing node structures from content repositories (CMIS) to
RDF models.</p>
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/ontonet.html
==============================================================================
---
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/ontonet.html
(original)
+++
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/ontonet.html
Mon Jan 16 12:09:21 2012
@@ -57,8 +57,7 @@
<div id="content">
<h1 class="title">Ontology Network Manager (OntoNet)</h1>
- <p>=========================================</p>
-<h2 id="terminology">Terminology</h2>
+ <h2 id="terminology">Terminology</h2>
<p>Stanbol OntoNet implements the API section for managing OWL and OWL2
ontologies, in order to prepare them for consumption by reasoning services,
refactorers, rule engines and the like. Ontology management in OntoNet is
sparse and not connected: once loaded internally from their remote locations,
ontologies live and are known within the realm they were loaded in. This allows
loose-coupling and (de-)activation of ontologies in order to scale the data
sets for reasoners to process and optimize them for efficiency. The following
concepts have been introduced with OntoNet:</p>
<ul>
<li>
@@ -71,8 +70,38 @@
<p>Session: a container of (supposedly volatile) semantic data which need to
be intercrossed with one or more Scopes, for stateful management of ontology
networks. It can be used to load instances and reason on them using different
models (one per scope). An OntoNet Session is not equivalent to an HTTP session
(since it can live persistently across multiple HTTP sessions), although its
behaviour can reflect the one of the HTTP session that created it, if required
by the implementation.</p>
</li>
</ul>
-<h2 id="service_endpoints">Service Endpoints</h2>
<hr />
+<h2 id="usage">Usage</h2>
+<p>Given the entire knowledge base managed by your CMS, OntoNet allows the
construction and management of ontology networks, programmatically via its Java
API or RESTful Web Services <em>(see next section for details on the
latter)</em>. A criterion for choosing the appropriate API can be as
follows:</p>
+<ul>
+<li>
+<p>Stanbol plugins or server software that incorporates Stanbol (e.g. larger
OSGi platforms) should use the Java API.</p>
+</li>
+<li>
+<p>Client applications, non-Java CMSs or services decoupled from Stanbol
should use the RESTful API.</p>
+</li>
+<li>
+<p>Java-based CMSs can use either API.</p>
+</li>
+</ul>
+<h3 id="java_api">Java API</h3>
+<p>First and foremost, the concept of <strong>ontology network</strong> is
implicit in the OntoNet API. There is no such thing as an
<code>OntologyNetwork</code> type. What you do is create
<code>OntologyScope</code> and <code>Session</code> objects and link them
together at creation time or when launching a process.</p>
+<h4 id="accessing_the_managers">Accessing the managers.</h4>
+<p>First and foremost let us obtain references to the main OntoNet manager
classes. In an OSGi environment they can be obtained by reference:</p>
+<div class="codehilite"><pre><span class="nv">@Reference</span>
+<span class="n">ONManager</span> <span class="n">onMgr</span><span
class="p">;</span>
+
+<span class="nv">@Reference</span>
+<span class="n">SessionManager</span> <span class="n">sesMgr</span><span
class="p">;</span>
+</pre></div>
+
+
+<p>In a non-OSGi environment they must be instantiated as POJOs (Plain Old
Java Objects):</p>
+<div class="codehilite"><pre><span class="n">TODO</span>
+</pre></div>
+
+
+<h3 id="service_endpoints">Service Endpoints</h3>
<p>The OntoNet RESTful API is structured as follows:</p>
<p><em>(Please note, that the following links to the actual service endpoints
link to a running instance of Apache Stanbol. If you use other domains or ports
than "localhost:8080", then please change accordingly)</em></p>
<h3 id="scopes_ontonetontology">Scopes ("/ontonet/ontology")</h3>
