svn commit: r1213798 - in /incubator/stanbol/site/trunk/content/stanbol/docs/trunk: ontologymanager.mdtext ontologymanager/registry.mdtext

[al...@apache.org]

Author: alexdma
Date: Tue Dec 13 17:32:03 2011
New Revision: 1213798

URL: http://svn.apache.org/viewvc?rev=1213798&view=rev
Log:
STANBOL-402 : updated OntoNet terminology

Modified:
    incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager.mdtext
    incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/registry.mdtext

Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager.mdtext?rev=1213798&r1=1213797&r2=1213798&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager.mdtext Tue Dec 13 17:32:03 2011
@@ -2,25 +2,21 @@ Title: Ontology Manager
 
 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.
 
-## RESTful API
+## Terminology
 
-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 ONM 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 the ONM:
+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:
 
 * 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.
 
-* 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) exactly one core space, which contains the immutable set of essential ontologies that describe the scope; (b) exactly 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); (c) zero or more session spaces, which extend the custom space with additional models provided by end-users (e.g. the set of individuals that 'populate' a scope may be fed to OntoNet via a session space). Session spaces are mapped one-to-one with KReS sessions (see below).
+* 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).
 
-* OntoNet session: a container of session spaces for all affected scopes, for stateful management of ontology networks. It 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.
+* 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.
 
 ### Sub-Components
 
-   - 'ontonet'     - allows to construct subsets of the knowledge base 
-                     managed by Stanbol into OWL/OWL2 ontology networks
-   - [Registry](ontologymanager/registry.html)  - manages ontology libraries for bootstrapping the network
-                     using both external and internal ontologies
-   - 'store'       - create, read, update and modify operations on single
-                     ontologies stored in Stanbol
-   - 'web'         - the RESTful Web Service interface for OntoNet
+   - OntoNet     - allows to construct subsets of the knowledge base managed by Stanbol into OWL/OWL2 ontology networks
+   - [Registry](ontologymanager/registry.html)  - manages ontology libraries for bootstrapping the network using both external and internal ontologies
+   - Store       - create, read, update and delete operations on single ontologies stored in Stanbol. These operations can be performed on entities, axioms, and whole ontologies.
 
 ## Examples
 

Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/registry.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/registry.mdtext?rev=1213798&r1=1213797&r2=1213798&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/registry.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/registry.mdtext Tue Dec 13 17:32:03 2011
@@ -2,7 +2,7 @@ Title: Ontology Registry Manager
 
 Registry management is a facility for Stanbol __administrators__ to pre-configure sets of ontologies that Stanbol should load and store, or simply be aware of, _before_ they are included in a part of the ontology network (e.g. a scope or session). Via the registry manager, it is possible to configure whether these ontologies should be loaded immediately when Stanbol is initialized, or only when explicitly requested. The Ontology Registry Manager is essentially an ontology bookmarker with caching support. It is also possible to cache multiple versions of the same ontology if needed.
 
-## Glossary
+## Terminology
 
 * A __Library__ is a collection of references to ontologies, which can be located anywhere on the Web. CMS administrators and knowledge managers can create a library by any criterion, e.g. a library of all _W3C ontologies_, a library of all the ontologies that describe a _social network_ (which can include [SIOC](http://sioc-project.org/ontology), [FOAF](http://xmlns.com/foaf/spec) etc.), a library of _ontology alignments_ (which includes ontologies that align DBPedia to Schema.org, GeoNames to DBPedia, or a custom product ontology to GoodRelations).
 * A __Registry__ is an RDF resource (i.e. an ontology itself) that describes one or more libraries. It is the physical object that has to be accessed to gain knowledge about libraries.