Author: fchrist
Date: Mon Jul 16 13:22:11 2012
New Revision: 1362026
URL: http://svn.apache.org/viewvc?rev=1362026&view=rev
Log:
Fixed and added links
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/cmsadapter/cmsadapter5min.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/entityhub/index.mdtext
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/index.mdtext
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/cmsadapter/cmsadapter5min.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/cmsadapter/cmsadapter5min.mdtext?rev=1362026&r1=1362025&r2=1362026&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/cmsadapter/cmsadapter5min.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/cmsadapter/cmsadapter5min.mdtext
Mon Jul 16 13:22:11 2012
@@ -1,4 +1,4 @@
-#5 Minutes Documentation for CMS Adapter#
+Title: 5 Minutes Tutorial for CMS Adapter
The CMS Adapter component acts as a bridge between content management systems
and the Apache Stanbol. Please note that all components of Apache Stanbol also
provides RESTful services which allow accessing them directly from outside. CMS
Adapter interacts with content management systems through JCR and CMIS
specifications. In other words, any content repository compliant with JCR or
CMIS specifications can make use of CMS Adapter functionalities. For the time
being, there are two main functionalities that CMS Adapter offers:
"Bidirectional Mapping" and "Contenthub Feed".
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/entityhub/index.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/entityhub/index.mdtext?rev=1362026&r1=1362025&r2=1362026&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/entityhub/index.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/entityhub/index.mdtext
Mon Jul 16 13:22:11 2012
@@ -9,12 +9,12 @@ The main Features are the:
* __Entityhub__ (<code>/entityhub</code>): Allows to manage local entities as
well as import entities from Sites or to define mappings from local Entities to
Entities managed by Sites. An Apache Stanbol instance can only have a single
Entityhub so if you want to manage multiple controlled vocabularies you should
preferable use [ManagedSite](managedsite.html) instead.
* __Site Manager__ (<code>/entityhub/sites</code>): The SiteManager provides a
unified access to all currently active Sites - your Entity Network. Requests
sent to this endpoint will be forwarded to all currently active Sites. Users
should note that queries (requests to the <code>/entityhub/sites/find</code>
and <code>/entityhub/sites/query</code> endpoints) might be slow as remote
services might need to be called for answering those requests. Retrieval of
Entities (requests to the <code>/entityhub/sites/entity</code> endpoint) and
also LDpath requests should perform reasonable well.
* __Sites__ (<code>/entityhub/site/{siteId}</code>): Sites represent entity
sources that are integrated with the Stanbol Entityhub. There are two different
types of Sites
- * __ReferencedSite__: This site allows to refer remote services to
dereference (Entity id based retrieval) and query entities. It also supports
local caches and indexes. A local cache allows to locally store retrieved
Entity data to speed-up retrieval on subsequent requests. A local index is a
locally available index over all/some of the data of the remote dataset. If
such an index is available all requests will be processed using the index. The
remote services are only used as a fallback. Local Indexes are created by the
Entityhub Indexing tool. The usage scenario [Working with Custom
Vocabularies](../customvocabulary.html) provides a good overview on how to use
this feature.
+ * __ReferencedSite__: This site allows to refer remote services to
dereference (Entity id based retrieval) and query entities. It also supports
local caches and indexes. A local cache allows to locally store retrieved
Entity data to speed-up retrieval on subsequent requests. A local index is a
locally available index over all/some of the data of the remote dataset. If
such an index is available all requests will be processed using the index. The
remote services are only used as a fallback. Local Indexes are created by the
Entityhub Indexing tool. The usage scenario [Working with Custom
Vocabularies](../../customvocabulary.html) provides a good overview on how to
use this feature.
* __ManagedSite__: [ManagedSites](managedsite.html) allow users to manage
their own entity by using the RESTful API of the Entityhub. They are very
similar to the <code>/entityhub</code> endpoint but do not allow to manage
mappings are to import Entities from other Sites.
## RESTful services
-The documentation of the RESTful services provided by the Stanbol Entityhub is
served by the Web UI of your Stanbol instance. If you do not have a running
Stanbol server [this introduction](../tutorial.html) provides you with all
necessary information. You can also try to access the documentation on the
Stanbol demo server available on the [IKS development
server](http://dev.iks-project.eu/) at
[http://dev.iks-project.eu:8081/entityhub](http://dev.iks-project.eu:8081/entityhub).
+The documentation of the RESTful services provided by the Stanbol Entityhub is
served by the Web UI of your Stanbol instance. If you do not have a running
Stanbol server [this introduction](../../tutorial.html) provides you with all
necessary information. You can also try to access the documentation on the
Stanbol demo server available on the [IKS development
server](http://dev.iks-project.eu/) at
[http://dev.iks-project.eu:8081/entityhub](http://dev.iks-project.eu:8081/entityhub).
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/index.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/index.mdtext?rev=1362026&r1=1362025&r2=1362026&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/index.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/components/index.mdtext
Mon Jul 16 13:22:11 2012
@@ -3,9 +3,19 @@ Title: Apache Stanbol Components
<figcaption>Figure 1: The Apache Stanbol Components</figcaption>
+* Jump to
+ * [Enhancer](enhancer/) and [Enhancement Engines](enhancer/engines/)
+ * [Entityhub](entityhub/)
+ * [Contenthub](contenthub/)
+ * [Ontology Manager](ontologymanager/)
+ * [Rules](rules/)
+ * [Reasoners](reasoner/)
+ * [CMS Adapter](cmsadapter/)
+ * [FactStore](factstore/)
+
Apache Stanbol is built as a modular set of components. Each component is
accessible via its own RESTful web interface. From this viewpoint, all Apache
Stanbol features can be used via RESTful service calls.
-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.
+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 Apache 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).
