This project has retired. For details please refer to its Attic page.

• Getting Started
• Documentation
  • Usage Scenarios
  • Components
  • Production Mode
• Development
  • Mailing Lists
  • Issue Tracker
  • Source Code
  • Development Practices

Downloads

• Overview
  • Releases
  • Launchers

Project

• Team
• License
• Privacy Policy

Archived Docs

• 0.9.0-incubating

The ASF

• Apache Software Foundation
• Thanks
• Become a Sponsor
• Security

Apache Stanbol Components

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. The components are implemented as OSGi components based on Apache Felix.

This page gives an overview of the major features of various Apache Stanbol components. Figure 1 depicts the main Apache Stanbol components and their arrangement within the Apache Stanbol architecture. Additionally, we have documented some usage scenarios.


We will shortly describe the components from top to bottom and link to their detailed descriptions.

• The Enhancer component together with its Enhancement Engines provides you with the ability to post content to Apache Stanbol and get suggestions for possible entity annotation in return. The enhancements are provided via natural language processing, metadata extraction and linking named entities to public or private entity repositories. Furthermore, Apache Stanbol provides a machinery to further process this data and add additional knowledge and links via applying rules and reasoning. Technically, the enhancements are stored in a triple-graph that is maintained by Apache Clerezza.

• The 'Sparql endpoint' gives access to the semantic enhancements form the Apache Stanbol Enhancer.

• 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 component provides you with the means to re-factor knowledge graphs, e.g. for supporting the schema.org vocabulary for Search Engine Optimization.

• The Reasoners 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".

• The Ontology Manager is the facility that manages your ontologies. Ontologies are used to define the knowledge models that describe the metadata of content. Additionally, the semantics of your metadata can be defined through an ontology.

• The CMS Adapter CMS Adapter component acts as a bridge between JCR/CMIS compliant content management systems and the Apache Stanbol. It can be used to map existing node structures from JCR/CMIS content repositories to RDF models or vica versa. It also provides services for the management of content repository items as Content Items within Contenthub.

• The Entityhub is the component, which lets you cache and manage local indexes of repositories such as dbpedia but also custom data (e.g. product descriptions, contact data, specialized topic thesauri).

• The Contenthub is the component which provides persistent document store whose back-end is Apache Solr. On top of the store, it enables semantic indexing facilities during text based document submission and semantic search together with faceted search capability on the documents.

• The FactStore is a component that let's use store relations between entities identified by their URIs. This relation between two entities is called a fact.

---

Back to Documentation