Author: fchrist
Date: Fri Jan 6 08:47:29 2012
New Revision: 801892
Log:
Minor changes and typos in documentation start page.
Added:
websites/production/stanbol/content/stanbol/docs/trunk/ontologymanager/ontonet.html
- copied unchanged from r801891,
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/ontonet.html
Modified:
websites/production/stanbol/ (props changed)
websites/production/stanbol/content/stanbol/docs/trunk/index.html
websites/production/stanbol/content/stanbol/docs/trunk/ontologymanager.html
Propchange: websites/production/stanbol/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Fri Jan 6 08:47:29 2012
@@ -1 +1 @@
-/websites/staging/stanbol/trunk:779452-800784
+/websites/staging/stanbol/trunk:779452-801891
Modified: websites/production/stanbol/content/stanbol/docs/trunk/index.html
==============================================================================
--- websites/production/stanbol/content/stanbol/docs/trunk/index.html (original)
+++ websites/production/stanbol/content/stanbol/docs/trunk/index.html Fri Jan
6 08:47:29 2012
@@ -51,7 +51,7 @@
<div id="content">
<h1 class="title">Documentation</h1>
- <p>This documentation of Apache Stanbol targets at CMS developers and
integrators, who want to use and integrate Stanbol RESTful Services into a
content management system and secondly for Stanbol contributors, which are
developing Stanbol Components and Engines.</p>
+ <p>This documentation of Apache Stanbol targets at Content Management
System (CMS) developers and integrators, who want to use and integrate Stanbol
RESTful services into their CMS. Secondly, it is for Stanbol contributors,
which are developing Stanbol components and engines.</p>
<h2 id="documentation_for_cms_developers">Documentation for CMS Developers</h2>
<ul>
<li><a href="scenarios.html">Usage Scenarios</a></li>
@@ -59,7 +59,7 @@
<li><a href="faq.html">FAQ</a></li>
<li>Demos</li>
</ul>
-<p><em>Note: In addition to the documentation on this site, every running
Stanbol server provides you with further descriptions of its RESTful web
services for each component. The most detailed technical documentation can be
found within various Readme.files within the <a
href="http://svn.apache.org/repos/asf/incubator/stanbol/trunk/";>source
code</a>.</em></p>
+<p><em>Note</em>: In addition to the documentation on this site, every Stanbol
instance provides you with live documentation when pointing your browser to the
Stanbol start page. It contains further descriptions and the most up-to-date
documenation for each component and its RESTful API. Additional technical notes
for each component can be found within various README files within the <a
href="http://svn.apache.org/repos/asf/incubator/stanbol/trunk/";>source
code</a>.</p>
<h2 id="documentation_for_stanbol_contributors">Documentation for Stanbol
Contributors</h2>
<ul>
<li>Java API for developers</li>
Modified:
websites/production/stanbol/content/stanbol/docs/trunk/ontologymanager.html
==============================================================================
--- websites/production/stanbol/content/stanbol/docs/trunk/ontologymanager.html
(original)
+++ websites/production/stanbol/content/stanbol/docs/trunk/ontologymanager.html
Fri Jan 6 08:47:29 2012
@@ -52,22 +52,9 @@
<div id="content">
<h1 class="title">Ontology Manager</h1>
<p>The Stanbol Ontology Manager provides a controlled environment for
managing ontologies, ontology networks and user sessions for semantic data
modeled after them. It provides full access to ontologies stored into the
Stanbol persistence layer.</p>
-<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>
-<p>Ontology scope: a "logical realm" for all the ontologies that encompass a
certain CMS-related set of concepts (such as "User", "ACL", "Event", "Content",
"Domain", "Reengineering", "Community", "Travelling" etc.). Scopes never
inherit from each other, though they can load the same ontologies if need
be.</p>
-</li>
-<li>
-<p>Ontology space: an access-restricted container for synchronized access to
ontologies within a scope. The ontologies in a scope are loaded within its set
of spaces. An ontology scope contains: (a) one core space, which contains the
immutable set of essential ontologies that describe the scope; (b) one
(possibly empty) custom space, which extends the core space according to
specific CMS needs (e.g. the core space for the User scope may contains
alignments to FOAF).</p>
-</li>
-<li>
-<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>
<h3 id="sub-components">Sub-Components</h3>
<ul>
-<li>OntoNet - allows to construct subsets of the knowledge base managed by
Stanbol into OWL/OWL2 ontology networks</li>
+<li><a href="ontologymanager/ontonet.html">OntoNet</a> - allows to
construct subsets of the knowledge base managed by Stanbol into OWL/OWL2
ontology networks</li>
<li><a href="ontologymanager/registry.html">Registry</a> - manages ontology
libraries for bootstrapping the network using both external and internal
ontologies</li>
<li>Store - create, read, update and delete operations on single
ontologies stored in Stanbol. These operations can be performed on entities,
axioms, and whole ontologies.</li>
</ul>
