Author: rwesten
Date: Tue Jun 26 11:07:30 2012
New Revision: 1353942
URL: http://svn.apache.org/viewvc?rev=1353942&view=rev
Log:
moved detailed description about featuers from the index to the overview page
Added:
incubator/stanbol/site/trunk/content/stanbol/overview.mdtext
Modified:
incubator/stanbol/site/trunk/content/stanbol/index.mdtext
Modified: incubator/stanbol/site/trunk/content/stanbol/index.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/index.mdtext?rev=1353942&r1=1353941&r2=1353942&view=diff
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/index.mdtext (original)
+++ incubator/stanbol/site/trunk/content/stanbol/index.mdtext Tue Jun 26
11:07:30 2012
@@ -4,57 +4,28 @@ Apache Stanbol (currently in [incubating
<p style="text-align: center;">
</p>
-The Apache Stanbol [components](docs/trunk/components.html) are meant to be
accessed over RESTful services. Typically they are use to extend traditional
content management systems with semantic services. However Apache Stanbol is
not limited to CMS. Other possible use cases include direct usage from web
applications e.g. for tag suggestions or entity suggestion in search fields as
well as smart Email/Document processing based on extracted Entities/Topics.
-
-Apache Stanbol is by no meanprovides a set of RESTful services that aim to
extend traditional content management systems with semantic services. bring
semantic technologies to Content Management Systems.
+The Apache Stanbol [components](docs/trunk/components.html) are meant to be
accessed over RESTful services. Typically they are use to extend traditional
content management systems with semantic services. Other feasible use cases
include: Direct usage from web applications (e.g. for Tag
extraction/suggestion; or text completion in search fields), 'smart' Content
workflows or email routing based on extracted Entities/Topics, ...
Apache Stanbol's main features are:
+- **[Content Enhancement](docs/trunk/enhancer)**<br>
+ Services that add semantic information to ânon-semanticâ pieces of
content.
+- **[Reasoning](docs/trunk/reasoners.html)**<br>
+ Services that are able to retrieve additional semantic information about the
content based on the semantic information retrieved via content enhancement.
+- **[Knowledge Models](docs/trunk/ontologymanager)**<br>
+ Services that are used to define and manipulate the data models (e.g.
ontologies) that are used to store the semantic information.
+- **[Persistence](docs/trunk/contenthub)**<br>
+ Services that store (or cache) semantic information, i.e. enhanced content,
entities, facts, and make it searchable.
-### Content Enhancement
-
-<span style="float:right"> </span>
-
-The Stanbol Enhancer provides a [RESTful
API](docs/trunk/enhancer/enhancerrest.html) that allows to [extract semantic
information](docs/trunk/contentenhancement.html) from parsed Content. Results
are represented as RDF graph and can be used on the front end e.g. to improve
[Tagging](docs/trunk/enhancementusage.html#entity-tagging-use-tags-to-relate-you-content-to-persons-places-events)
or even [inline Content
Annotation](docs/trunk/enhancementusage.html#entity-checker-inline-editing-of-content-enhancements).
In the backend extracted information can be used to improve search and content
processing workflows.
-
-In more details the Stanbol Enhancer can enhancer Content in [multiple
languages](docs/trunk/multilingual.html). It can be configured to use [custom
vocabularies](docs/trunk/customvocabulary.html). This [List of Enhancement
Engines](docs/trunk/enhancer/engines/list.html) provides a good overview about
the different option. However users with special needs can also extend the
Stanbol Enhancers by implementing their own [Enhancement
Engine](docs/trunk/enhancer/engines/).
-
-### Manage your Domain Data
-
-<span style="float:right"> </span>
-
-Information (Data/Knowledge) about relevant Entities are key for any semantic
System. But those information may come from a variety of source. The Stanbol
Entityhub provides tools and services that allow you and the other Stanbol
components to access those data via RESTful services.
-
-The Entityhub allows you to create/manage your own local Entities. It also
provides a tool for [create local indexes](docs/trunk/customvocabulary.html) of
datasets. This is important for supporting fast local queries as required by
the Stanbol Enhancer. The Entityhub can also reference and cache remotely
hosted datasets. It directly supports [Linked Data](http://linkeddata.org)
protocols but can also be extended to work with services that use special
protocols and formats.
-
-The Apache Entityhub also implements the [Google
Refine](http://code.google.com/p/google-refine/) [Reconciliation
API](http://code.google.com/p/google-refine/wiki/ReconciliationServiceApi).
Google Refine is a powerful tool for working with messy data. The
reconciliation step allows to link those data with information of other data
sets - similar to the Stanbol Enhancer suggesting links within parsed content.
-
-### Knowledge Models and Reasoning
+See also [Overview](overview.html) page for a more compressive list about
features provided by Apache Stanbol. If you are a Developer you might also want
to look at the [Components](docs/trunk/components.html) page for further
technical details.
-<span style="float:right"> </span>
-
-TODO: Services that are used to define and manipulate the data models (e.g.
ontologies) that are used to store the semantic information.
-
-
-### Semantic Indexing and Search
-
-<span style="float:right"> </span>
-
-TODO: Services that store (or cache) semantic information, i.e. enhanced
content, entities, facts, and make it searchable
-
-
-### Used Technologies
+Used Technologies/Frameworks include:
- Features provided as **RESTful Services* returning results as
**[RDF](http://www.w3.org/RDF/)**(Resource Description Language) and
[JSON](http://www.json.org/). Stanbol also supports the use of
**[JSON-LD](http://json-ld.org/)**.
- Available as **Standalone application** (runable Jar) or **Web Archive**(WAR
file) deployable on any Servlet Container such as Apache Tomcat.
- Written in **Java** based on
**[OSGi](http://www2.osgi.org/Specifications/HomePage)** as component framework
- Implemented using frameworks such as [Apache
Solr](http://lucene.apache.org/solr/) - for semantic search; [Apache
Tika](http://tika.apache.org/) - for plain text and metadata extraction;
[Apache OpenNLP](http://opennlp.apache.org/) - for natural language processing;
[Apache Clerezza](http://incubator.apache.org/clerezza/) and [Apache
Jena](http://jena.apache.org/) - as RDF framework and Storage; [Apache
Felix](http://felix.apache.org) as default OSGI framework and [Apache
Sling](http://sling.apache.org) for deployment.
-Apache Stanbol [components](docs/trunk/components.html) are meant to be
accessed over RESTful interfaces to provide semantic services for content
management. Thus, one application is to extend traditional content management
systems with (internal or external) semantic services. Additionally, Apache
Stanbol let's you create new types of content management systems with semantics
at their core. The current code is written in Java and based on the
[OSGi](http://www2.osgi.org/Specifications/HomePage) component framework.
-
-
-Apache Stanbol features provide the basics to create content management
systems with semantically advanced user interfaces. Those user interfaces
benefit from the semantic information that can be handled by Apache Stanbol.
See the [documentation](docs/trunk/) pages for more details.
-
------------------------------------------------------------------------------------------------
The Apache Stanbol project was initiated by the European R&D project
[IKS](http://www.iks-project.eu) - Interactive Knowledge Stack for small to
medium CMS providers. Some people who are working on the project are
part-funded by the IKS project, as well as by several European SME CMS
providers, who are [adopting Apache
Stanbol](http://wiki.iks-project.eu/index.php/Participants).
Added: incubator/stanbol/site/trunk/content/stanbol/overview.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/overview.mdtext?rev=1353942&view=auto
==============================================================================
--- incubator/stanbol/site/trunk/content/stanbol/overview.mdtext (added)
+++ incubator/stanbol/site/trunk/content/stanbol/overview.mdtext Tue Jun 26
11:07:30 2012
@@ -0,0 +1,41 @@
+Title: Overview about Apache Stanbol (incubating)
+
+Apache Stanbol (currently in [incubating](http://incubator.apache.org))
provides a set of reusable components for semantic content management. For
users it is important to note that Stanbol is NOT a semantic CMS by it own. It
is designed to provide semantic services for existing content management.
+
+<p style="text-align: center;">
+</p>
+
+All the features described in the following sections are meant to be accessed
over RESTful services. Typically they are use to extend traditional content
management systems with semantic services. Other feasible use cases include:
Direct usage from web applications (e.g. for Tag extraction/suggestion; or text
completion in search fields), 'smart' Content workflows or email routing based
on extracted Entities/Topics, ...
+
+### Content Enhancement
+
+The Stanbol Enhancer provides a [RESTful
API](docs/trunk/enhancer/enhancerrest.html) that allows to [extract semantic
information](docs/trunk/contentenhancement.html) from parsed Content.
+
+<p style="text-align: center;"></p>
+
+Results are represented as RDF graph and can be used on the front end e.g. to
improve
[Tagging](docs/trunk/enhancementusage.html#entity-tagging-use-tags-to-relate-you-content-to-persons-places-events)
or even [inline Content
Annotation](docs/trunk/enhancementusage.html#entity-checker-inline-editing-of-content-enhancements).
In the backend extracted information can be used to improve search and content
processing workflows.
+
+In more details the Stanbol Enhancer can enhancer Content in [multiple
languages](docs/trunk/multilingual.html). It can be configured to use [custom
vocabularies](docs/trunk/customvocabulary.html). This [List of Enhancement
Engines](docs/trunk/enhancer/engines/list.html) provides a good overview about
the different option. However users with special needs can also extend the
Stanbol Enhancers by implementing their own [Enhancement
Engine](docs/trunk/enhancer/engines/).
+
+### Manage your Domain Data
+
+Information (Data/Knowledge) about relevant Entities are key for any semantic
System. But those information may come from a variety of source. The Stanbol
Entityhub provides tools and services that allow you and the other Stanbol
components to access those data via RESTful services.
+
+<p style="text-align: center;"> </p>
+
+The Entityhub allows you to create/manage your own local Entities. It also
provides a tool for [create local indexes](docs/trunk/customvocabulary.html) of
datasets. This is important for supporting fast local queries as required by
the Stanbol Enhancer. The Entityhub can also reference and cache remotely
hosted datasets. It directly supports [Linked Data](http://linkeddata.org)
protocols but can also be extended to work with services that use special
protocols and formats.
+
+The Apache Entityhub also implements the [Google
Refine](http://code.google.com/p/google-refine/) [Reconciliation
API](http://code.google.com/p/google-refine/wiki/ReconciliationServiceApi).
Google Refine is a powerful tool for working with messy data. The
reconciliation step allows to link those data with information of other data
sets - similar to the Stanbol Enhancer suggesting links within parsed content.
+
+### Knowledge Models and Reasoning
+
+<p style="text-align: center;"> </p>
+
+TODO: Services that are used to define and manipulate the data models (e.g.
ontologies) that are used to store the semantic information.
+
+
+### Semantic Indexing and Search
+
+<p style="text-align: center;"> </p>
+
+TODO: Services that store (or cache) semantic information, i.e. enhanced
content, entities, facts, and make it searchable
