You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by fc...@apache.org on 2012/07/16 14:51:10 UTC
svn commit: r1362011 - /incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components.mdtext

Author: fchrist
Date: Mon Jul 16 12:51:10 2012
New Revision: 1362011

URL: http://svn.apache.org/viewvc?rev=1362011&view=rev
Log:
Minor format fix

Modified:
    incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components.mdtext

Modified: incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components.mdtext
URL: http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components.mdtext?rev=1362011&r1=1362010&r2=1362011&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components.mdtext Mon Jul 16 12:51:10 2012
@@ -7,11 +7,12 @@ Apache Stanbol is built as a modular set
 
 Components do not depend on each other. However they can be easily combined if needed as shown by the different [Usage Scenarios](scenarios.html). This ensures that the list of used components depend on the specific usage scenario and not on the Stanbol architecture.
 
-All components are implemented as [OSGi](http://www2.osgi.org/Specifications/HomePage) bundles, components and services. By default Apache Stanbol uses [Apache Felix](http://felix.apache.org) as OSGI environment. However generally we try to avoid the use of Felix specific features. If you need to run Stanbol in an other OSGI environment an encounter problems tell us by opening a [JIRA issue](https://issues.apache.org/jira/browse/STANBOL) and/or asking about it on the Stanbol Developer [mailing list](mailinglists.html).
+All components are implemented as [OSGi](http://www2.osgi.org/Specifications/HomePage) bundles, components and services. By default Apache Stanbol uses [Apache Felix](http://felix.apache.org) as OSGi environment. However generally we try to avoid the use of Felix specific features. If you need to run Stanbol in an other OSGi environment an encounter problems tell us by opening a [JIRA issue](https://issues.apache.org/jira/browse/STANBOL) and/or asking about it on the Stanbol Developer [mailing list](mailinglists.html).
 
-For deployment Stanbol uses the [Apache Sling](http://sling.apache.org) launcher. While the Stanbol Community maintains different launcher options including run-able JARs and WAR files we expect users to configure their custom launchers optimized for their usage scenario. However it os also possible to us Stanbol with other launchers (such as [Apache Karaf](http://karaf.apache.org/)) or to add its bundles to any existing OSGI environment.
+For deployment Stanbol uses the [Apache Sling](http://sling.apache.org) launcher. While the Stanbol Community maintains different launcher options including run-able JARs and WAR files we expect users to configure their custom launchers optimized for their usage scenario. However it os also possible to us Stanbol with other launchers (such as [Apache Karaf](http://karaf.apache.org/)) or to add its bundles to any existing OSGi environment.
 
 Figure 2 depicts the main Apache Stanbol components and their arrangement within the Apache Stanbol architecture.
+
 ![Apache Stanbol Components](images/stanbol-architecture.png "Apache Stanbol Components")
 <figcaption>Figure 2: Apache Stanbol Architecture</figcaption>
 
@@ -21,7 +22,7 @@ Figure 2 depicts the main Apache Stanbol
 
 * The 'EnhancerVIE' is a stateful interface to submit content to analyze and store the results on the server. It is then possible to browse the resulting enhanced content items.
 
-* The [Rules](rules.html) component provides you with the means to re-factor knowledge graphs, e.g. for supporting the schema.org vocabulary for Search Engine Optimization. 
+* The [Rules](rules.html) component provides you with the means to refactor knowledge graphs, e.g. for supporting the schema.org vocabulary for search engine optimization. 
   
 * The [Reasoners](reasoners.html) 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".