You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by al...@apache.org on 2011/12/22 18:29:06 UTC
svn commit: r1222363 - in /incubator/stanbol/site/trunk/content/stanbol/docs/trunk: ontologymanager.mdtext ontologymanager/ontonet.mdtext ontologymanager/ontonet/

Author: alexdma
Date: Thu Dec 22 17:29:06 2011
New Revision: 1222363

URL: http://svn.apache.org/viewvc?rev=1222363&view=rev
Log:
Added some OntoNet documentation.

Added:
    incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/ontonet/
    incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/ontonet.mdtext
Modified:
    incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager.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=1222363&r1=1222362&r2=1222363&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager.mdtext Thu Dec 22 17:29:06 2011
@@ -2,19 +2,9 @@ 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.
 
-## 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 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) 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).
-
-* 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
+   - [OntoNet](ontologymanager/ontonet.html)     - 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.
 

Added: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/ontonet.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/ontonet.mdtext?rev=1222363&view=auto
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/ontonet.mdtext (added)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/ontologymanager/ontonet.mdtext Thu Dec 22 17:29:06 2011
@@ -0,0 +1,33 @@
+Title: Ontology Network Manager (OntoNet)
+=========================================
+
+## 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 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) 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).
+
+* 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.
+
+## Service Endpoints
+--------------------
+
+The OntoNet RESTful API is structured as follows:
+
+_(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)_
+
+### Scopes ("/ontonet/ontology")
+* The endpoint @ [/ontonet/ontology](http://localhost:8080/ontonet/ontology) shows an overview (as an RDF graph or HTML document) of all registered ontology scopes.
+* An Ontology Scope @ /ontonet/ontology/{scopeId} provides the de-referenceable OWL form of the ontology scope _scopeId_, inclusive of OWL import statements for the spaces and ontologies therein.
+
+### Sessions ("/ontonet/session")
+* The endpoint @ [/ontonet/session](http://localhost:8080/ontonet/session) shows an overview (as an RDF graph or HTML document) of all open OntoNet sessions.
+* A Session @ /ontonet/session/{sessionId} provides the de-referenceable OWL form of the OntoNet Session _sessionId_, inclusive of OWL import statements for the ontologies therein.
+
+### Managed Ontologies ("ontonet/{ontologyId}")
+* A Managed Ontology @ /ontonet/{ontologyId}, where _ontologyId_ is the full logical IRI that identifies the ontology, provides the RDF form of the ontology with that ID, if that ontology has been stored and is managed by OntoNet.
+
+____
+_[Back to Ontology Manager](../ontologymanager.html)_
\ No newline at end of file