You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by bu...@apache.org on 2012/04/11 10:56:16 UTC
svn commit: r812321 [3/4] - in /websites/staging/stanbol/trunk/content: ./
stanbol/ stanbol/docs/0.9.0-incubating/
stanbol/docs/0.9.0-incubating/cmsadapter/
stanbol/docs/0.9.0-incubating/contenthub/
stanbol/docs/0.9.0-incubating/enhancer/ stanbol/docs/...
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/entityhub/entityhubandlinkeddata.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/entityhub/entityhubandlinkeddata.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/entityhub/entityhubandlinkeddata.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -63,7 +66,7 @@
<h2 id="short-introduction-to-linked-data-and-proposed-linked-media-extensions">Short Introduction to Linked Data and proposed Linked Media extensions</h2>
<p>from <a href="http://linkeddata.org/faq">linkeddata.org</a> </p>
<blockquote>
-<h3 id="what_is_linked_data">What is Linked Data?</h3>
+<h3 id="what-is-linked-data">What is Linked Data?</h3>
<p>The Web enables us to link related documents. Similarly it enables us to link related data.
The term Linked Data refers to a set of best practices for publishing and connecting structured data on the Web.
Key technologies that support Linked Data are URIs (a generic means to identify entities or
@@ -83,7 +86,7 @@ structure and link data that describes t
<li>URI Aliases: If different providers publish information about the same Non-Information Resource (e.g a famous Person, a Country, ...) than "<a href="http://www.w3.org/TR/owl-ref/#sameAs-def">owl:sameAs</a>" relations are used to tell clients that two different Resource Identifiers (HTTP URIs) identify the same Resource.</li>
</ul>
<p>A more detailed overview is provided by the <a href="http://www4.wiwiss.fu-berlin.de/bizer/pub/LinkedDataTutorial/">Linked Data Tutorial</a>.</p>
-<h3 id="linked_media">Linked Media</h3>
+<h3 id="linked-media">Linked Media</h3>
<p>The <a href="http://lists.w3.org/Archives/Public/public-lod/2011May/0019.html">Linked Media proposal</a> tries to extend Linked Data by two features.</p>
<ol>
<li>Creating and updating of resources: Linked data currently covers only retrieval of information, which is sufficient for sites like <a href="http://dbpedia.org">DBpedia</a> or <a href="http://www.geonames.org">Geonames</a> where users are only able to consume data. When creating interactive (web) applications one needs to be able to create/update and remove information. Features that are currently not covered by linked data, but well defined for RESTful Services. The Linked Media proposal therefore suggest to use HTTP PUT, POST and DELETE request for this purpose.</li>
@@ -98,7 +101,7 @@ structure and link data that describes t
<li>it allows to define and manage network of referenced sites used to retrieve information about entities from. In addition the Entityhub also supports the use of local caches to speedup access and to get independency of the availability of remote services. </li>
<li>it manages an own (local) site that is used to manage local entities. Such entities can be created locally but it is also possible to import them form any referenced site. Typical examples of locally managed entities are customers, employees, concepts of a company thesaurus, offices, meeting rooms ... </li>
</ol>
-<h3 id="entity_model_of_the_entityhub">Entity Model of the Entityhub</h3>
+<h3 id="entity-model-of-the-entityhub">Entity Model of the Entityhub</h3>
<p>Entities managed by the entityhub define first an unique ID. In case the referenced site follows linked data principles this will be the HTTP URI of the Non-Information resource. However this might be any valid URI (including URNs). The URI prefix of locally managed entities are configureable. Therefore the URI type of locally managed entities depends on the configuration. The Entity itself represents a Non-Information Resource. Each Entity comes with a Representation. The representation holds all information known by the site about the entity. In Linked Data terminology the Representation is the Information Resource a User needs to be redirected when he requests the Entity (Non-Information Resource). Finally an Entity also links to the ID of the (referenced) site managing it. This allows users to track who is providing the information for an Entity.</p>
<p>Currently the Entityhub distinguish three different types of Entities:</p>
<ol>
@@ -114,7 +117,7 @@ structure and link data that describes t
<li>Content: All Representations about Entities</li>
<li>Metadata: Additional information about Representations such as license, copyrights, attributions as well as mappings to other entities.</li>
</ul>
-<h3 id="restful_services_of_the_entityhub">RESTful Services of the Entityhub</h3>
+<h3 id="restful-services-of-the-entityhub">RESTful Services of the Entityhub</h3>
<p>The Entityhub defines the following service endpoints:</p>
<ol>
<li>The (referenced) Site Manager: Provides retrieval and search over all referenced sites.</li>
@@ -147,9 +150,9 @@ structure and link data that describes t
<p>Based on this evaluation of the Model and the Services provided by the Entityhub the proposed Linked Media extension to the Linked Data principles would be sufficient to cover most of the functionalities exposed by the Entityhub as RESTful services. While for referenced Sites only the distinction between Metadata and Content is needed for locally managed Entities also the possibility to create, update and remove Entities, their Representation (content) and metadata is of central importance. The main functionalities not covered is the import of Entities from referenced sites. Also for functionalities like the creation of mappings and the management of the Entity workflow special additions to the generic Linked Media/Linked Data API would be useful.</p>
<h2 id="specific-considerations">Specific Considerations</h2>
<p>This section contains Entityhub specific considerations about some of the principles defined for Linked Data and Linked Media. </p>
-<h3 id="resource_identifier">Resource Identifier</h3>
+<h3 id="resource-identifier">Resource Identifier</h3>
<p>Linked data defines the principle to use HTTP URIs as Resource Indetifier so that one can retrieve data by directly accessing the URI of a resource. This does not work out for the Entityhub because it needs to also manage remote entities and also for local entities this will not always be an option. Because of that the RESTful interface needs also to support an alternative that allows to parse the URI of an entity as a parameter. This is also a requirement to don't affect the IDs of entities when the Entityhub is deployed on an different host of even by using localhost. In addition this allows to use use other URI types (mainly URNs but also other protocols such as LDAP) as identifiers for locally managed entities.</p>
-<h3 id="redirects_for_content_negotiation">Redirects for Content Negotiation</h3>
+<h3 id="redirects-for-content-negotiation">Redirects for Content Negotiation</h3>
<p>It is important to consider that Entities are Non-Information Resources and based on Linked Data Principles requests for Non-Information resources need to be answered with redirects ("303 See Other") to the URI of the Information Resource. In practice such redirects are for two things:</p>
<ol>
<li>
@@ -165,7 +168,7 @@ structure and link data that describes t
</ol>
<h2 id="redesigning-the-entityhub">Redesigning the Entityhub</h2>
<p>This section evaluates necessary changes to the Entityhub.</p>
-<h3 id="uri_scheme_for_resources">URI scheme for Resources</h3>
+<h3 id="uri-scheme-for-resources">URI scheme for Resources</h3>
<p>The support of Linked Data requires the use of a local URI. This is in contrast to the parameter based approach ("?id={remoteURI}") as currently used by the Entityhub. The goal is that the Entityhub allows both variants</p>
<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="sr">/entityhub/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="sr">/entity/</span><span class="p">{</span><span class="n">localname</span><span class="p">}</span> <span class="ow">and</span>
<span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="sr">/entityhub/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="o">/</span><span class="n">entity</span><span class="p">?</span><span class="n">uri</span><span class="o">=</span><span class="p">{</span><span class="n">uri</span><span class="p">}</span>
@@ -188,7 +191,7 @@ structure and link data that describes t
<p>For referenced entities such representations will be created by merging remote metadata with locally managed. Remote Metadata will be recognized by Resources with a <a href="http://xmlns.com/foaf/0.1/primaryTopic">foaf:primaryTopic</a> relation to the Entity. Local Metadata can include information known for the referenced site (e.g. license, copyright, attributions, information about the managing organization ...) as well as mappings to other (locally managed) entities.</p>
<p>For locally managed Entities the metadata will also include all the additional information as currently defined by the Symbol API (state, predecessors, successors).</p>
<p>Note that the URIs for Representations and Metadata are optional and will be omitted based on HTTP request headers in case redirects are disabled. However even in case that redirects are disabled it is still possible to use such URIs for requests.</p>
-<h3 id="uri_scheme_for_content_negotiation">URI scheme for Content Negotiation</h3>
+<h3 id="uri-scheme-for-content-negotiation">URI scheme for Content Negotiation</h3>
<p>To confirm with the Linked Data principles the Entityhub needs to provide unique HTTP URIs for any content type Information Resources (Content and Metadata Resoruces) can be serialized. As for the ".rep" and ".meta" extensions used to directly access Representations and their Metadata the proposal is also to use of file extensions to indicate the media type. In cases users wish to parse the remote URI as parameter it is also possible to parse the extension or the media type as parameter.</p>
<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="sr">/entityhub/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="sr">/entity/</span><span class="p">{</span><span class="n">localname</span><span class="p">}</span><span class="o">.</span><span class="p">{</span><span class="n">extension</span><span class="p">}</span> <span class="ow">or</span>
<span class="n">http:</span><span class="sr">//</span><span class="p">{</span><span class="n">host</span><span class="p">}</span><span class="sr">/entityhub/</span><span class="p">{</span><span class="n">site</span><span class="p">}</span><span class="o">/</span><span class="n">entity</span><span class="p">?</span><span class="n">uri</span><span class="o">=</span><span class="p">{</span><span class="n">uri</span><span class="p">}</span><span class="o">&</span><span class="nb">format</span><span class="o">=</span><span class="p">{</span><span class="n">extension</span><span class="p">}</span><span class="o">&</span><span class="n">mediaType</span><span class="o">=</span><span class="p">{</span><span class="n">mediatype</span><span class="p">}</span>
@@ -203,9 +206,9 @@ structure and link data that describes t
<p>Note that the URIs used for content negotiation are optional and will be omitted based on HTTP request headers in case redirects are disabled. However even in case that redirects are disabled it is still possible to use such URIs for requests.</p>
-<h3 id="http_requestresponse_headers_with_special_use">HTTP Request/Response Headers with special use</h3>
+<h3 id="http-requestresponse-headers-with-special-use">HTTP Request/Response Headers with special use</h3>
<p>This section provides information about header fields that are specially evaluated by the Entityhub. Normal evaluations of headers as specified by <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html">RFC2616 section 14</a> e.g. the use of Content-Type to read data parsed by PUT/POST requests are not described.</p>
-<h4 id="accept_headerhttpwwww3orgprotocolsrfc2616rfc2616-sec14htmlsec141"><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.1">Accept header</a></h4>
+<h4 id="accept-header"><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.1">Accept header</a></h4>
<p>The Accept header allows to specify the media type of the content as expected by the client in the response. The <a href="http://lists.w3.org/Archives/Public/public-lod/2011May/0019.html">Linked Media proposal</a> suggests to use the "rel" parameter to specify if the response should return the data or the metadata of the requested resource. The semantics of the "rel" parameter is defined for the Link header by <a href="http://www.ietf.org/rfc/rfc5988.txt">RFC5988</a>. An related example can be found on the <a href="http://www.w3.org/wiki/LinkHeader">LinkHeader</a> page on the W3C wiki.</p>
<p>The pattern useable for Accept header looks like</p>
<div class="codehilite"><pre><span class="n">Accept:</span> <span class="p">{</span><span class="n">media</span><span class="o">-</span><span class="n">type</span><span class="p">}[;</span> <span class="n">rel</span><span class="o">=</span><span class="n">meta</span><span class="p">]</span>
@@ -213,7 +216,7 @@ structure and link data that describes t
<p>If no "rel" pattern is specified the Entityhub will return the data (representation about the entity) as default. If users want to retrieve the the metadata they need to add "rel=meta". The {media-type} is always applied to the information selected by the "rel" parameter. </p>
-<h4 id="cache-controlhttpwwww3orgprotocolsrfc2616rfc2616-sec14htmlsec149"><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9">Cache-Control</a></h4>
+<h4 id="cache-control"><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9">Cache-Control</a></h4>
<p>The Entityhub supports the following cache-request-directives to allow clients some control about local caching of entities managed by remote sites. Note that the Stanbol OFFLINE mode has precedence over Cache-Control specifications<br />
</p>
<ul>
@@ -222,7 +225,7 @@ structure and link data that describes t
<li>no-transform: The Entityhub may be configured to transform/filter information from the remote site. This can be used to bypass this kind of transformations. In case transformations are used for the local cache, then this parameter will not work out if Stanbol is operates in OFFLINE mode</li>
<li>only-if-cached: Representations are only returned if they are available in the local cache.</li>
</ul>
-<h4 id="link_headerhttpwwwietforgrfcrfc5988txt"><a href="http://www.ietf.org/rfc/rfc5988.txt">Link Header</a></h4>
+<h4 id="link-header"><a href="http://www.ietf.org/rfc/rfc5988.txt">Link Header</a></h4>
<p>The Link header is central to Linked Data and Linked Media because it is used to expose internal structures defined in-between Resources (in-between Entities but also between Entities and there Representations and Metadata)</p>
<p>The principle Syntax of Link headers is as follows:</p>
<div class="codehilite"><pre><span class="n">Link:</span> <span class="o">&</span><span class="ow">lt</span><span class="p">;{</span><span class="n">uri</span><span class="p">}</span><span class="o">&</span><span class="ow">gt</span><span class="p">;;</span> <span class="n">rel</span><span class="o">=</span><span class="s">"{relation}"</span><span class="p">;</span> <span class="n">type</span><span class="o">=</span><span class="s">"{media-type}"</span>
@@ -255,7 +258,7 @@ structure and link data that describes t
<p>Link: {licenseURI}; rel=license</p>
</li>
</ul>
-<h3 id="entity_model">Entity Model</h3>
+<h3 id="entity-model">Entity Model</h3>
<p>This changes to the RESTful API should be also reflected in the Java API. Currently on the API level there are three types of Entities: Sign, Symbol and EntityMapping. The only differentiation between those Entities are a different set of metadata. However there is no plan to distinguish such types on the RESTful API level.</p>
<p>To streamline the domain model and to bring it more in line with the RESTful API the proposal is to drop the different Entity types. The Sign, Symbol and EnttiyMapping Interfaces will be replaced by a single Entity interface with the following Methods</p>
<div class="codehilite"><pre><span class="n">Entity</span>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/entityhub/index.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/entityhub/index.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/entityhub/index.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -60,9 +63,9 @@
<p>The Entityhub provides two main services. The Entityhub provides the connection to external linked open data sites as well as using indexes of them locally. Its services allow to manage a <strong>network of sites</strong> to consume entity information and to <strong>manage entities locally</strong>.<br />
</p>
<p>A small index of approx. 43k entities from dbpedia comes with the default installation.</p>
-<h2 id="service_endpoints">Service Endpoints</h2>
+<h2 id="service-endpoints">Service Endpoints</h2>
<p>The RESTful API of the Entityhub ist structured as follows:</p>
-<h3 id="entity_network_entityhubsite">Entity Network ("/entityhub/site*"):</h3>
+<h3 id="entity-network-entityhubsite">Entity Network ("/entityhub/site*"):</h3>
<ul>
<li>The Referenced Site Manager @ <a href="http://localhost:8080/entityhub/sites">/entityhub/sites</a> allows to manages sites and retrieve/search Entities in all sites of the Entity Network.</li>
<li>A Referenced Site @ /entityhub/site/{siteName} refers to a single site of the Referenced Site Manager and allows to retrieve all active sites. Referenced sites provide the same interface as the referenced site manager.</li>
@@ -83,7 +86,7 @@
</li>
</ul>
<p>Currently active referenced sites at the demo server are available and running for <a href="http://dev.iks-project.eu:8080/entityhub/site/dbpedia/">dbpedia</a>, <a href="http://dev.iks-project.eu:8080/entityhub/site/dblp/">dplp</a> and <a href="http://dev.iks-project.eu:8080/entityhub/site/geonames/">geonames</a>.</p>
-<h3 id="entityhub_entityhub">Entityhub ("/entityhub"):</h3>
+<h3 id="entityhub-entityhub">Entityhub ("/entityhub"):</h3>
<ul>
<li>Local Entities @/entityhub/entity: Full CRUD operations on Entities managed by the Entityhub</li>
<li>Entity Mappings @ /entityhub/mapping: Lookup mappings from local Entities to Entities managed by a Referenced Site</li>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/implementation.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/implementation.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/implementation.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -58,10 +61,10 @@
<div id="content">
<h1 class="title">FactStore Implementation Concept</h1>
<p>The <a href="specification.html">FactStore specification</a> is written with a certain kind of implementation in mind. Although the implementation of the specification is not pretended it might be useful to have a look at this simple implementation concept.</p>
-<h2 id="store_implementation">Store Implementation</h2>
+<h2 id="store-implementation">Store Implementation</h2>
<p>The store implementation is based on the well known concept of relational databases. Each fact schema is a table in a relational database. Creating a new fact schema is equivalent to creating a new table with a number of String attributes, because we store IRIs, according to the schema. For performance reasons the attributes should be indexed.
The store just needs to be able to create new schemata. It is not specified that a schema may be altered over time. This could be an improvement for the future.</p>
-<h2 id="query_implementation">Query Implementation</h2>
+<h2 id="query-implementation">Query Implementation</h2>
<p>The JSON-LD query structure is designed to be mapped directly to valid SQL statements. If the store is implemented in a relational database all queries can be transformed to SQL queries to this database. For security reasons it is important to keep hacks like SQL injection in mind when transforming the JSON-LD query to SQL.</p>
<p>As seen in the examples, queries may use attributes of entities to formulate the request. However, the FactStore does only store the IRIs of the entities not the entities with their attributes. Therefore, the FactStores needs an EntityHub to resolve entities specified by their attributes. The EntityHub must be able to query for entities by example.</p>
<p>Note: Depending on the number of entities returned by the EntityHub for a certain request this architecture may lead to performance problems. It has to be evaluated where the limit of this approach is in terms of performance. However, the assumption is that in many (or most) scenarios this will not become a problem. If it becomes a problem, the type of allowed queries may be restricted, e.g. don't allow queries that use entity attributes in the "where" clause, to avoid performance or memory problems.</p>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/index.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/index.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/index.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -98,7 +101,7 @@
<p>On success this will return a 201 (Created) and the URI of the newly created fact in the location header of the response. To retrieve a fact you can GET it from the returned URI.</p>
-<h2 id="rest_api_documentation">REST API Documentation</h2>
+<h2 id="rest-api-documentation">REST API Documentation</h2>
<p>To get the latest documentation you should start your copy of an Apache Stanbol launcher that includes the FactStore and navigate your browser to http://localhost:8080/factstore. There you will find more information and the documentation of the FactStore's REST API.</p>
</div>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/specification.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/specification.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/factstore/specification.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -67,9 +70,9 @@
<p>In the following, we will define the required interfaces for the FactStore plus the required query language.</p>
<p>''Note'': Interfaces will be defined as RESTful service APIs. The payload of service calls is specified using <a href="http://www.json-ld.org/spec/ED/20110507/JSON-LD">Specification version 20110507</a>.</p>
<p>''Note'': The FactStore does not provide any SPARQL endpoint so far. This could be part of an extended version.</p>
-<h2 id="store_interface">Store Interface</h2>
+<h2 id="store-interface">Store Interface</h2>
<p>The store interface allows clients to put new fact schemata and according facts (instances of that schemata) to the FactStore.</p>
-<h3 id="publish_a_new_fact_schema">Publish a New Fact Schema</h3>
+<h3 id="publish-a-new-fact-schema">Publish a New Fact Schema</h3>
<p>Allows clients to publish new fact schemata to the FactStore. Each fact is an n-tuple where each element of that tuple defines a certain type of entity. A fact schema defines which types of entities and their roles are part of instances of that fact.</p>
<p>Path: /factstore/facts/{fact-schema-name}</p>
<p>Method: PUT with data type application/json returns HTTP 201 (created) on success.</p>
@@ -112,7 +115,7 @@
<p>will create the new fact schema for "attendees" at the given URL which is in decoded representation: /factstore/facts/http://www.schema.org/Event.attendees.</p>
<p>''Note'': This fact schema uses the ability to define more than one possible type for a role. The role 'attendee' can be of type http://www.schema.org/Person or http://www.schema.org/Organization.</p>
-<h3 id="get_fact_schema">Get Fact Schema</h3>
+<h3 id="get-fact-schema">Get Fact Schema</h3>
<p>Allows clients to get the definition of an existing fact schema.</p>
<p>Path: /factstore/facts/{fact-schema-name}</p>
<p>Method: GET with data type application/json returns HTTP 200 on success.</p>
@@ -132,7 +135,7 @@
<p>Status: <strong>Implemented</strong></p>
-<h3 id="publish_new_facts">Publish New Facts</h3>
+<h3 id="publish-new-facts">Publish New Facts</h3>
<p>Allows clients to publish a new facts according to a defined fact schema that was previously published to the FactStore. Each new fact is an n-tuple according to its schema where each tuple element identifies an entity using its unique IRI.</p>
<p>Path: /factstore/facts</p>
<p>Method: POST with data type application/json returns HTTP 201 (created) on success.</p>
@@ -194,9 +197,9 @@
<p>creates two new facts. The first one of type http://iks-project.eu/ont/employeeof specifying that the person http://upb.de/persons/bnagel is employee of the organization defined by the IRI http://uni-paderborn.de. The second of type http://iks-project.eu/ont/friendOf specifying that http://upb.de/persons/fchrist is a friend of http://upb.de/persons/bnagel.</p>
<p>Status: <strong>Implemented</strong></p>
-<h2 id="query_interface">Query Interface</h2>
+<h2 id="query-interface">Query Interface</h2>
<p>The query interface allows clients to query for facts and combination of facts (reasoning). The JSON-LD query structure is inspired by SQL using SELECT FROM [JOIN] WHERE constructs. Depending on the implementation the JSON-LD queries may be transformed directly into valid SQL queries.</p>
-<h3 id="query_for_facts_of_a_certain_type">Query for Facts of a Certain Type</h3>
+<h3 id="query-for-facts-of-a-certain-type">Query for Facts of a Certain Type</h3>
<p>Allows clients to query stored facts of a specific type defined by the fact's schema. The clients specify the desired fact plus an arbitrary number of entities that play some role in the fact.</p>
<p>Path: /factstore/query</p>
<p>Method: POST with data type application/json returns application/json</p>
@@ -289,7 +292,7 @@
<p>Status: <strong>Example 2 is NOT Implemented, yet.</strong></p>
-<h3 id="query_for_combinations_of_facts">Query for Combinations of Facts</h3>
+<h3 id="query-for-combinations-of-facts">Query for Combinations of Facts</h3>
<p>Allows clients to query for combinations of facts.</p>
<p>Path: /factstore/query?q=</p>
<p>Method: GET with data type application/json returns application/json</p>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/faq.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/faq.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/faq.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -57,17 +60,17 @@
<div id="content">
<h1 class="title">FAQ for Apache Stanbol users </h1>
- <h2 id="can_i_update_the_default_dbpedia_index_with_a_bigger_one">Can I update the default DBpedia index with a bigger one?</h2>
+ <h2 id="can-i-update-the-default-dbpedia-index-with-a-bigger-one">Can I update the default DBpedia index with a bigger one?</h2>
<p>Yes, you can just copy such an index from <a href="http://dev.iks-project.eu/downloads/stanbol-indices/">here</a> into the sling/datafiles directory. It will be initialized automatically.</p>
-<h2 id="how_about_language_support_of_enhancement_engines">How about language support of enhancement engines?</h2>
+<h2 id="how-about-language-support-of-enhancement-engines">How about language support of enhancement engines?</h2>
<ul>
<li>The Named Entity Recognition Engine has support for English.</li>
<li>The Keyword Linking Engine has support for English, German, Danish, Dutch and Portuguese.
<em><a href="multilingual.html">Check "Working with multiple languages"</a></em></li>
</ul>
-<h2 id="can_i_use_my_own_vocabulary_as_linking_target">Can I use my own vocabulary as linking target?</h2>
+<h2 id="can-i-use-my-own-vocabulary-as-linking-target">Can I use my own vocabulary as linking target?</h2>
<p>Yes, Stanbol provides you with and indexing tool for creating appropriate indexes for any kind of RDF data, vCard or SKOS vocabularies. <em><a href="customvocabulary.html">Check "Using custom vocabulary"</a></em></p>
-<h2 id="can_i_use_existing_solr_indexes">Can I use existing SOLr indexes?</h2>
+<h2 id="can-i-use-existing-solr-indexes">Can I use existing SOLr indexes?</h2>
<p>Yes, just provide a link within the org.apache.stanbol.commons.solr.impl.DefaultSolrDirectoryManager.name Bundle to a local directory, where you host the SOLr indexes, in order to reuse.</p>
</div>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/features.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/features.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/features.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -57,7 +60,7 @@
<div id="content">
<h1 class="title">Apache Stanbol features</h1>
- <h2 id="stable_features">Stable features</h2>
+ <h2 id="stable-features">Stable features</h2>
<ul>
<li>NLP and Named Entity Recognition via <a href="http://incubator.apache.org/opennlp/">Apache OpenNLP</a></li>
<li>Enhancement engines linking to open data such as dbpedia, geonames, dplb.</li>
@@ -68,8 +71,8 @@
<li>Language Detection for European Languages</li>
<li>Extracting embedded metadata and textual content via <a href="http://aperture.sourceforge.net/">Aperture</a></li>
</ul>
-<h2 id="upcoming_features">Upcoming Features</h2>
-<h2 id="features_whishlist">Features whishlist</h2>
+<h2 id="upcoming-features">Upcoming Features</h2>
+<h2 id="features-whishlist">Features whishlist</h2>
<ul>
<li>Multilingual support</li>
</ul>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/index.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/index.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/index.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/mailinglists.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/mailinglists.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/mailinglists.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/multilingual.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/multilingual.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/multilingual.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -66,17 +69,17 @@
<li>Dutch</li>
<li>Portuguese</li>
</ul>
-<h2 id="configuration_steps">Configuration steps</h2>
+<h2 id="configuration-steps">Configuration steps</h2>
<ul>
<li>Have language labels in your target data and install the index</li>
<li>Add language models to your Stanbol instance</li>
<li>Activate the LangIdEnhancementEngine and the KeywordLinkingEngine</li>
<li>Configure the KeywordLinkingEngine</li>
</ul>
-<h3 id="install_your_index">Install your index</h3>
+<h3 id="install-your-index">Install your index</h3>
<p>In DBpedia, there exist language labels for many entities. In case you want to use an index of your custom vocabulary, first <a href="customvocabulary.html">create the index</a> from it and add the index to your stanbol instance. Simply paste the <code>{yourindex}.solr.zip</code> into your <code>{stanbol-root}/sling/datafiles</code> directory and install the respective OSGI bundle at your OSGI admin console.</p>
<p>Make sure, that this index contains language labels in all languages you want to work with and that they are properly indexed.</p>
-<h3 id="build_and_add_the_necessary_language_bundles">Build and add the necessary language bundles</h3>
+<h3 id="build-and-add-the-necessary-language-bundles">Build and add the necessary language bundles</h3>
<p>To build the language bundles go to "{stanbol-root}/data/" and call</p>
<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span> <span class="o">-</span><span class="n">P</span> <span class="n">opennlp</span>
</pre></div>
@@ -90,13 +93,13 @@
<p>The naming of the bundles is "org.apache.stanbol.data.opennlp.lang.{language}-*.jar".</p>
<p>Add the bundles via the OSGI admin console in the bundles tab. The language bundles will fetch and install the according <a href="http://dev.iks-project.eu/downloads/opennlp/models-1.5/">OpenNLP</a> models for the languages you want to use.</p>
-<h3 id="activate_langid_engine_and_keywordlinkingengine">Activate LangID engine and KeywordLinkingEngine</h3>
+<h3 id="activate-langid-engine-and-keywordlinkingengine">Activate LangID engine and KeywordLinkingEngine</h3>
<p>Go to the admin console and deactivate some of the available engines. Especially the standard NER engine and the Entity Linking Engines should be deactivated, as they do not support multiple languages. At least two engines need to be activated:</p>
<ul>
<li>The <a href="enhancer/engines/langidengine.html">Language Identification Engine</a> provides you with the language of the text you want to enhance, it creates a dc:terms languaage property. The </li>
<li>The <a href="enhancer/engines/keywordlinkingengine.html">Keyword Linking Engine</a> provides you with the TextAnnotations (selects potential parts of your text) as well as with EntitiyAnnotations (provides suggestions for links). Be aware, that the result (especially the recall) heavily depends on the amount of entities you have specified in your target data source.</li>
</ul>
-<h3 id="configure_the_keywordlinkingengine">Configure the KeywordLinkingEngine</h3>
+<h3 id="configure-the-keywordlinkingengine">Configure the KeywordLinkingEngine</h3>
<p>At the OSGI admin console, you can get the most relevant configuration options of the Keyword Linking Engine.</p>
<ul>
<li><strong>Referenced Site:</strong> The ID of the Entityhub Referenced Site holding the Controlled Vocabulary (e.g. a taxonomy or just a set of named entities) </li>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/index.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/index.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/index.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -58,12 +61,12 @@
<div id="content">
<h1 class="title">Ontology Manager</h1>
<p>The Stanbol Ontology Manager provides a <strong>controlled environment</strong> for managing ontologies, <strong>ontology networks</strong> and user sessions for semantic data modeled after them. It provides full access to ontologies stored into the Stanbol persistence layer. Managing an ontology network means that you can activate or deactivate parts of a complex model from time to time, so that your data can be viewed and classified under different "logical lenses". This is especially useful in <a href="reasoners.html">Reasoning</a> operations.</p>
-<h2 id="usage_scenarios">Usage Scenarios</h2>
-<h3 id="user_networks">User networks</h3>
+<h2 id="usage-scenarios">Usage Scenarios</h2>
+<h3 id="user-networks">User networks</h3>
<p>In your CMS, you might be interested in figuring out the trust and acquaintance network of its users. This can be a combination of the <em>asserted</em> network (i.e. what other users are included in the contact or friend list of a given user) with the <em>inferred</em> network (e.g. exclude those who are in the contact list of a blacklisted user). The latter can be derived from the user activities over the user-generated content of your CMS (e.g. blogs posts, forum posts, reviews, tweets, ratings). </p>
<p>Both types of networks can be modelled as ontologies. Models can be build on the <em>class</em> level, or <em>TBox</em> (e.g. everyone who is an Administrator is also a User, and collaborates with every other Administrator of the same system) and on the <em>instance</em> level, or <em>ABox</em> (e.g. John is a friend of Mary, who created blog post bp345263 on 3/10/2012 at 15:10). These models can all be stored using the Store facility of the Ontology Manager.</p>
<p>Using a <a href="reasoners.html">reasoner</a> you can classify all the knowledge loaded on Stanbol, but this can be a time-consuming process due to classifying knowledge we are not interested in for this task. <a href="ontologymanager/ontonet.html">OntoNet</a> allows you to select only the "interesting" parts of your knowledge base. For example, if the knowledge contains classifications of animal species, you may want to deactivate that model when reasoning on user networks. Likewise, you may want to consider the user profiles <em>today</em>, rather than who was a user's friend five years ago. Therefore, on the instance level you will exclude the profile history and only consider today's snapshot.</p>
-<h3 id="knowledge_within_content">Knowledge within content</h3>
+<h3 id="knowledge-within-content">Knowledge within content</h3>
<p>Hierarchical, tree-like structures are a tried-and-true mechanism for organizing documents, applications and in fact any content items. What users are required to do is select <em>one</em> set of criteria and organize the directory structure accordingly. For instance, if journalists were to classify the reserch papers on their file system, they could do as follows:</p>
<ul>
<li><code>articles/mine</code> (articles authored by the users)</li>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/ontonet/index.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/ontonet/index.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/ontonet/index.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -91,9 +94,9 @@
<p>Java-based CMSs can use either API.</p>
</li>
</ul>
-<h3 id="java_api">Java API</h3>
+<h3 id="java-api">Java API</h3>
<p>First and foremost, the concept of <strong>ontology network</strong> is implicit in the OntoNet API. There is no such thing as an <code>OntologyNetwork</code> type. What you do is create <code>OntologyScope</code> and <code>Session</code> objects and link them together at creation time or when launching a process.</p>
-<h4 id="accessing_the_managers">Accessing the managers.</h4>
+<h4 id="accessing-the-managers">Accessing the managers.</h4>
<p>First and foremost let us obtain references to the main OntoNet manager classes. In an OSGi environment they can be obtained by reference:</p>
<div class="codehilite"><pre><span class="nv">@Reference</span>
<span class="n">ONManager</span> <span class="n">onMgr</span><span class="p">;</span>
@@ -108,7 +111,7 @@
</pre></div>
-<h4 id="managing_an_ontology_scope">Managing an ontology scope.</h4>
+<h4 id="managing-an-ontology-scope">Managing an ontology scope.</h4>
<p>Let us now show an example of how to setup an ontology scope, which you should use for storing the models for a certain domain of your knowledge base. In this example we will refer to social networks and communities.</p>
<div class="codehilite"><pre><span class="n">ScopeRegistry</span> <span class="n">registry</span> <span class="o">=</span> <span class="n">onMgr</span><span class="o">.</span><span class="n">getScopeRegistry</span><span class="p">();</span>
<span class="n">OntologyScopeFactory</span> <span class="n">factory</span>
@@ -225,7 +228,7 @@
</pre></div>
-<h4 id="ontology_input_sources">Ontology input sources.</h4>
+<h4 id="ontology-input-sources">Ontology input sources.</h4>
<p>Note that when you add an ontology to a space or session, you pass it an <code>OntologyInputSource</code> object, or more precisely, an <code>OntologyInputSource<O,P></code>. This is because there can be several ways to obtain an ontology, and those most common are supported in Stanbol. For example, it can be obtained by defererencing a IRI and parsing its source code (in RDF/XML, Turtle, etc.), or by reading an input stream, or taking an already stored RDF graph in the Stanbol store; or it could be an ontology Java object created from scratch. An <strong>Ontology input source</strong> is an object that incorporates (1) the "method" by which an ontology should be accessed; (2) the type of Java object it should create to represent an ontology; (3) where it should store the ontology.</p>
<ul>
<li><strong><code>OWLOntology</code> input sources</strong> comply with the OWL API specification <a href="#ref1">[1]</a> and creates objects of type <code>OWLOntology</code> stored in an <em>in-memory</em> <code>OWLOntologyManager</code>. It will be stored persistently once added to an ontology network.<ul>
@@ -242,20 +245,20 @@ Loads the ontology source codeWraps an a
</ul>
</li>
</ul>
-<h3 id="service_endpoints">Service Endpoints</h3>
+<h3 id="service-endpoints">Service Endpoints</h3>
<p>The OntoNet RESTful API is structured as follows:</p>
<p><em>(Please note, that the following links to the actual service endpoints link to a running instance of Apache Stanbol. If you use domains or ports other than "localhost:8080", then please change accordingly)</em></p>
-<h4 id="scopes_ontonetontology">Scopes ("/ontonet/ontology")</h4>
+<h4 id="scopes-ontonetontology">Scopes ("/ontonet/ontology")</h4>
<ul>
<li>The endpoint @ <a href="http://localhost:8080/ontonet/ontology">/ontonet/ontology</a> shows an overview (as an RDF graph or HTML document) of all registered ontology scopes.</li>
<li>An Ontology Scope @ /ontonet/ontology/{scopeId} provides the de-referenceable OWL form of the ontology scope <em>scopeId</em>, inclusive of OWL import statements for the spaces and ontologies therein.</li>
</ul>
-<h4 id="sessions_ontonetsession">Sessions ("/ontonet/session")</h4>
+<h4 id="sessions-ontonetsession">Sessions ("/ontonet/session")</h4>
<ul>
<li>The endpoint @ <a href="http://localhost:8080/ontonet/session">/ontonet/session</a> shows an overview (as an RDF graph or HTML document) of all open OntoNet sessions.</li>
<li>A Session @ /ontonet/session/{sessionId} provides the de-referenceable OWL form of the OntoNet Session <em>sessionId</em>, inclusive of OWL import statements for the ontologies therein.</li>
</ul>
-<h4 id="managed_ontologies_ontonetontologyid">Managed Ontologies ("ontonet/{ontologyId}")</h4>
+<h4 id="managed-ontologies-ontonetontologyid">Managed Ontologies ("ontonet/{ontologyId}")</h4>
<ul>
<li>A Managed Ontology @ /ontonet/{ontologyId}, where <em>ontologyId</em> 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 (i.e. is in some scope or session).</li>
</ul>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/registry/index.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/registry/index.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/registry/index.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -63,7 +66,7 @@
<li>A <strong>Library</strong> is a collection of references to ontologies, which can be located anywhere on the Web. CMS administrators and knowledge managers can create a library by any criterion, e.g. a library of all <em>W3C ontologies</em>, a library of all the ontologies that describe a <em>social network</em> (which can include <a href="http://sioc-project.org/ontology">SIOC</a>, <a href="http://xmlns.com/foaf/spec">FOAF</a> etc.), a library of <em>ontology alignments</em> (which includes ontologies that align DBPedia to Schema.org, GeoNames to DBPedia, or a custom product ontology to GoodRelations).</li>
<li>A <strong>Registry</strong> is an RDF resource (i.e. an ontology itself) that describes one or more libraries. It is the physical object that has to be accessed to gain knowledge about libraries.</li>
</ul>
-<h2 id="usage_scenarios">Usage Scenarios</h2>
+<h2 id="usage-scenarios">Usage Scenarios</h2>
<p>Your CMS ca handle hundreds of vocabularies together for semantic annotation, but you do not want to clutter the system runtime by having all those vocabularies loaded altogether. You would like the ontology of a specific vocabulary to be loaded only when someone uses or requests it, and once it is loaded you would like it to be stored internally, rather than fetching it from the Web over and over again.</p>
<p>The Ontology Registry Manager can help you with that. With a simple RDF document that references these hundreds of ontologies, it is possible to organize them into libraries, e.g. by topic ("user profile", "product", "event") or by provenance ("W3C", "Industrial standards", "nonstandard" etc.). If a user decides to annotate a content item using <code>schema.org</code>, she can choose to do so and the Registry Manager will automatically figure out that it is referenced by libraries "Industrial standards", "user profile" and "product"). None of these libraries has been preloaded yet, so Stanbol will automatically choose the smallest one, say "Industrial standards", and load it. The <code>schema.org</code> ontology will be available from that point on.</p>
<h2 id="configuration">Configuration</h2>
@@ -75,15 +78,15 @@
<li>You can select one <strong>Caching policy</strong> between Centralised (default) and Distributed. In <em>Centralised</em> caching, all the libraries that reference an ontology with the same URI will share the very same version of that ontology. In <em>Distributed</em> caching, each library will reference its own version of each ontology. Centralised caching is generally recommended, as distributed caching allows multi-version ontology management, but occupies much more storage space, depending on the amount of ontologies in common.</li>
</ol>
<h2 id="usage">Usage</h2>
-<h3 id="setup_an_ontology_registry">Setup an Ontology Registry</h3>
+<h3 id="setup-an-ontology-registry">Setup an Ontology Registry</h3>
<p>To create a Registry, you simply need to make an OWL ontology with certain types of axioms. See <a href="language">Registry Language</a> for examples on how to create a Registry and add Library instances to it. </p>
<p>Then upload the ontology on the Web and add it to the <strong>Registry locations</strong> from the <a href="http://localhost:8080/system/console/configMgr/org.apache.stanbol.ontologymanager.registry.impl.RegistryManagerImpl">Felix console Configuration</a>.</p>
<p>Note that not only can a single registry describe multiple libraries, but also multiple registries can describe the same library, each adding information on the ontologies referenced by it. Library descriptions are <em>monotonic</em>, in that registries can only <em>add</em> information about libraries, never <em>remove</em> any.</p>
-<h3 id="access_a_cached_ontology">Access a cached ontology</h3>
+<h3 id="access-a-cached-ontology">Access a cached ontology</h3>
<p>A cached ontology does not need to be loaded into an OntoNet scope or session in order to be available. It can be accessed at <code>@/ontonet/{ontologyURI}</code>, where <code>{ontologyURI}</code> can be either the ontology ID, if the ontology is named, of the physical URI it was retrieved from.</p>
-<h3 id="load_a_library_into_ontonet">Load a library into OntoNet</h3>
+<h3 id="load-a-library-into-ontonet">Load a library into OntoNet</h3>
<p>One useful application of ontology libraries is that they can be used to populate an OntoNet ontology collector (space or session) with multiple ontologies with a single command. There are two ways to do so.</p>
-<h4 id="java_api">Java API</h4>
+<h4 id="java-api">Java API</h4>
<p>The Registry Manager is an OSGi service component. To obtain the service reference:</p>
<div class="codehilite"><pre><span class="nv">@Reference</span>
<span class="n">RegistryManager</span> <span class="n">registryManager</span><span class="p">;</span>
@@ -114,16 +117,16 @@
<p>Note that we called <code>addOntology()</code> although this resulted in adding multiple ontologies. This is because a <code>LibrarySource</code> "fools" OntoNet into thinking a single ontology is being loaded, i.e. the <em>root</em> ontology that depends on the library contents. It will still possible to access a single imported ontology, though.</p>
-<h4 id="rest_api">REST API</h4>
+<h4 id="rest-api">REST API</h4>
<p>When using the REST API, an ontology library can be loaded into a scope the very moment the scope is created.</p>
<p>To load the contents of library <code>http://stanbol.apache.org/ontologies/library/W3C_ontologies</code> into a <em>new</em> scope called <code>AnnotationStandards</code>:</p>
<div class="codehilite"><pre><span class="n">curl</span> <span class="o">-</span><span class="n">X</span> <span class="n">PUT</span> <span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="sr">/ontonet/o</span><span class="n">ntology</span><span class="sr">/AnnotationStandards?corereg=http://stanbol.apache.org/o</span><span class="n">ntologies</span><span class="sr">/library/</span><span class="n">W3C_ontologies</span>
</pre></div>
-<h3 id="load_selected_ontologies_from_library">Load selected ontologies from library</h3>
+<h3 id="load-selected-ontologies-from-library">Load selected ontologies from library</h3>
<p>We are working on that. Stay tuned.</p>
-<h3 id="service_endpoints">Service Endpoints</h3>
+<h3 id="service-endpoints">Service Endpoints</h3>
<p>Because the configuration of registries is a task for <strong>administrators</strong> and is performed through the Felix administration console, there are no RESTful services for modifying ontology registries. It is however possible to browse the known ontology <em>libraries</em>.</p>
<ul>
<li><a href="http://localhost:8080/ontonet/registry"><strong>Libraries</strong></a>. If called from a Web browser, shows a list of known ontology libraries, and for each of them the caching state and the number of referenced ontologies. <em>Note that this service does not provide information on the registries that describe these libraries; that is classified information for administrators.</em> This endpoint supports only GET with no parameters, and generates text/html only.</li>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/registry/language.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/registry/language.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/ontologymanager/registry/language.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/reasoners.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/reasoners.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/reasoners.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -111,7 +114,7 @@
<http://xmlns.com/foaf/0.1/Project> ;
[...]</pre>
This behaviour is equivalent if we use the method POST with the header <tt>Content-type: application/x-www-form-urlencoded</tt>. In addition, if the <tt>target</tt> parameter is provided, the service saves the output in the given graph in the triple store and does not return the RDF stream.</p>
-<h2 id="differences_between_the_reasoners">Differences between the reasoners</h2>
+<h2 id="differences-between-the-reasoners">Differences between the reasoners</h2>
<p>Let's give some example on the differences between the available reasoners (to try the example ontology snippets you can download them from <a href="https://github.com/enridaga/reasoners.examples/tree/master/enridaga.reasoners.examples" target="_blank">here</a>).</p>
<p>The first snippet uses rdfs:subClassOf to declare that any Article is a Document, which is in turn a ContentItem.
<pre>
@@ -293,7 +296,7 @@ The <tt>/owlmini</tt> implements the OWL
</pre>
<a href="https://raw.github.com/enridaga/reasoners.examples/master/enridaga.reasoners.examples/owl2/class-restrictions-owl2.xml" target="_blank">download it</a></p>
<p>The above differences depend on the semantic supported by the specific reasoner and from the implementation, which limit the power of the system in favour of a better efficiency (is the case of the <tt>/owlmini</tt> implementation of Jena, more efficient then the respective <tt>/owl</tt>). If you need to work with RDFS semantic, and don't need OWL for your inferences, just use the RDFS one.</p>
-<h2 id="build_and_install">Build and install</h2>
+<h2 id="build-and-install">Build and install</h2>
<p>Run Stanbol, for example:</p>
<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">java</span> <span class="o">-</span><span class="n">jar</span> <span class="o">-</span><span class="n">Xmx1g</span> <span class="n">org</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">stanbol</span><span class="o">.</span><span class="n">launchers</span><span class="o">.</span><span class="n">full</span><span class="o">-</span><span class="mf">0.9.0</span><span class="o">-</span><span class="n">incubating</span><span class="o">-</span><span class="n">SNAPSHOT</span><span class="o">.</span><span class="n">jar</span>
</pre></div>
@@ -307,7 +310,7 @@ Move to the <tt>/reasoners</tt> director
<p>for example</p>
<p>% mvn install -PinstallBundle http://localhost:8080/system/console</p>
-<h3 id="add_the_hermit_reasoner">Add the HermiT reasoner</h3>
+<h3 id="add-the-hermit-reasoner">Add the HermiT reasoner</h3>
<p>To enable HermiT as OWL2 reasoner you can download and install it from the Stanbol (Incubating) svn repository. The steps are the following:</p>
<div class="codehilite"><pre><span class="nv">$</span> <span class="nv">svn</span> <span class="n">co</span> <span class="n">https:</span><span class="sr">//s</span><span class="n">vn</span><span class="o">.</span><span class="n">apache</span><span class="o">.</span><span class="n">org</span><span class="sr">/repos/</span><span class="n">asf</span><span class="sr">/incubator/s</span><span class="n">tanbol</span><span class="sr">/trunk/</span><span class="n">reasoners</span><span class="o">/</span><span class="n">hermit</span> <span class="n">stanbol</span><span class="o">-</span><span class="n">hermit</span>
<span class="nv">$</span> <span class="nv">cd</span> <span class="n">stanbol</span><span class="o">-</span><span class="n">hermit</span>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -58,14 +61,14 @@
<div id="content">
<h1 class="title">Rules</h1>
<p>Stanbol Rules is a component that supports the construction and execution of inference rules. An <strong>inference rule</strong>, or transformation rule, is a syntactic rule or function which takes premises and returns a conclusion. Stanbol Rules allows to add a layer for expressing business logics by means of axioms, which encode the inference rules. These axioms can be organized into a container called <strong>recipe</strong>, which identifies a set of rules that share the same business logic and interpret them as a whole.</p>
-<h2 id="usage_scenarios">Usage Scenarios</h2>
-<h3 id="integrity_check_from_data_fusion">Integrity check from data fusion</h3>
+<h2 id="usage-scenarios">Usage Scenarios</h2>
+<h3 id="integrity-check-from-data-fusion">Integrity check from data fusion</h3>
<p>With Stanbol Rules the administrator can define integrity checks for data fetched from heterogeneous and external sources in order to prevent unwanted formats or inconsistent data.
In such a way the administrator is able to configure the CMS in order filter knowledge retrieved in Linked Data, e.g., via the <a href="enhancer.html">Enhancer</a>, that satisfies some integrity driven constraint. The constraint can be defined by means of Stanbol Rules.
For instance in a CMS which collects core knowledge about musicians it might possible to define integrity check rules which keep only entities that are typed as Musicians in DBpedia <a href="#dbpedia">[5]</a> and have an associated image, a birth place and the instrument played.
Any other entity not satisfying the constraints is discarded. <br />
</p>
-<h3 id="vocabulary_harmonization">Vocabulary harmonization</h3>
+<h3 id="vocabulary-harmonization">Vocabulary harmonization</h3>
<p>Supposing we want to use some dataset in Linked
Data as external knowledge bases for a generic CMS enhanced with Stanbol.
Now the problem how to use data from those datasets expressed with some external
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/language.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/language.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/language.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/refactor.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/refactor.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/refactor.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -64,8 +67,8 @@
<li><strong>Refactoring</strong> is the task aimed to perform the transformation of RDF graphs. The transformation is driven by refactoring rules, basically Stanbol Rules interpreted as SPARQL CONSTRUCT clauses.</li>
<li><strong>Reasoning</strong> is the activity of interpreting axioms for inferring new knowledge, classifying, checking the consistency of an ontology, etc...</li>
</ul>
-<h2 id="usage_scenarios">Usage Scenarios</h2>
-<h3 id="vocabulary_harmonization">Vocabulary harmonization</h3>
+<h2 id="usage-scenarios">Usage Scenarios</h2>
+<h3 id="vocabulary-harmonization">Vocabulary harmonization</h3>
<p>Supposing we want to use some dataset in Linked
Data as external knowledge bases for a generic CMS enhanced with Stanbol.
Now the problem how to use data from those datasets expressed with some
@@ -113,14 +116,14 @@ translated into the construct template,
<p>The SPARQL engines used internally by the Refactor for running rules is <a href="http://incubator.apache.org/jena/documentation/query/">Apache Jena ARQ</a></p>
<p>We remand any detail about the syntax and the expressivity of the Stanbole Rule language to its <a href="./language.html">section</a>.<br />
</p>
-<h2 id="service_endpoints">Service Endpoints</h2>
+<h2 id="service-endpoints">Service Endpoints</h2>
<p>The Refactor RESTful API is structured as follows:
<em>(Please note, that the following links to the actual service endpoint link to a running instance of Apache Stanbol. If you use other domains or ports than "localhost:8080", then please change accordingly)</em></p>
-<h3 id="refactor_engine_refactor">Refactor Engine ("/refactor"):</h3>
+<h3 id="refactor-engine-refactor">Refactor Engine ("/refactor"):</h3>
<ul>
<li>The Refactor Engine <strong>@/refactor</strong> performs a refactoring applying an existing recipe in the rule store to the provided RDF graph.</li>
</ul>
-<h3 id="refactor_engine_refactorapply">Refactor Engine ("/refactor/apply"):</h3>
+<h3 id="refactor-engine-refactorapply">Refactor Engine ("/refactor/apply"):</h3>
<ul>
<li>Refactor Engine <strong>@/refactor/apply</strong> performs a refactoring applying an recipe as string to the provided RDF graph as input source.</li>
</ul>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/store.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/store.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/rules/store.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -57,14 +60,14 @@
<div id="content">
<h1 class="title">Rule Store</h1>
- <h2 id="service_endpoints">Service Endpoints</h2>
+ <h2 id="service-endpoints">Service Endpoints</h2>
<p>The Rules RESTful API is structured as follows:
<em>(Please note, that the following links to the actual service endpoint link to a running instance of Apache Stanbol. If you use other domains or ports than "localhost:8080", then please change accordingly)</em></p>
-<h3 id="rule_manager_rulesrule">Rule Manager ("/rules/rule"):</h3>
+<h3 id="rule-manager-rulesrule">Rule Manager ("/rules/rule"):</h3>
<ul>
<li>The Rule Manager @ <a href="http://localhost:8080/rules/rule">/rules/rule</a> allows to manage and retrieve inference rules.</li>
</ul>
-<h3 id="recipe_manager_rulesrecipe">Recipe Manager ("/rules/recipe"):</h3>
+<h3 id="recipe-manager-rulesrecipe">Recipe Manager ("/rules/recipe"):</h3>
<ul>
<li>The Recipe Manager @ <a href="http://localhost:8080/rules/recipe">/rules/recipe</a> allows to manage, store and retrieve pre-defined rule sequences, or <strong>recipes</strong>.</li>
</ul>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/scenarios.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/scenarios.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/scenarios.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -58,10 +61,11 @@
<div id="content">
<h1 class="title">Usage Scenarios for Apache Stanbol</h1>
<p>Apache Stanbol is designed to bring semantic technologies to existing content management systems (CMS). If you have a CMS and you want to start using semantic technologies in combination with your content, Apache Stanbol is a good software candidate for you. To make the integration as easy and painless as possible all Apache Stanbol features are accessible via RESTful web services. All you need is to connect your CMS via HTTP to an instance of Apache Stanbol. Additionally, Apache Stanbol comes with a <a href="cmsadapter.html">CMS Adapter</a> component as a bridge between a CMIS/JCR compliant content repositories and the semantic metadata repository in Apache Stanbol. Figure 1 gives you an overview of using Apache Stanbol from a CMS.</p>
-<p><figure>
-<img alt="Traditional CMS using Apache Stanbol" src="../../images/stanbol-cms-scenario.png" />
+<figure>
+
<figcaption>Figure 1: Traditional CMS using Apache Stanbol via its HTTP RESTful interface.</figcaption>
-</figure></p>
+</figure>
+
<p>The following usage scenarios explain in more detail how to use various services from a CMS.</p>
<ul>
<li>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/services.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/services.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/services.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -60,7 +63,7 @@
<p>The web interface of your Apache Stanbol installation provides information for the main HTTP entry points. Each resource comes with a web view that documents the matching RESTful API for applications. </p>
<p>Depending on which launcher you use, you will get a different set of services. By choosing the <strong>full launcher</strong>, you will get everything including experimental components, if you choose the <strong>stable launcher</strong> you will get the most stable components only.</p>
<p><em>Note: all links on this page direct to <a href="http://dev.iks-project.eu">demo instances</a> of Apache Stanbol. To be able to configure all services to your needs, you have run your own installation.</em></p>
-<h2 id="stable_services">Stable Services</h2>
+<h2 id="stable-services">Stable Services</h2>
<ul>
<li><a href="http://dev.iks-project.eu:8080/engines">/engines</a></li>
</ul>
@@ -74,9 +77,9 @@
</ul>
<p>This is the OSGi administration console (for administrators and developers). The initial username / password is set to admin / admin. Use the console to add new bundles and activate, de-activate and configure components. The console can also be used to perform hot-(re)deployment of any OSGi bundles. </p>
<p>For instance to re-deploy a new version of this web interface, go to the <code>$STANBOL_HOME/enhancer/jersey</code> source folder and run the following command:</p>
-<p><code>$ mvn install -o -DskipTests -PinstallBundle
+<p><code>$ mvn install -o -DskipTests -PinstallBundle \
-Dsling.url=http://localhost:8080/system/console</code></p>
-<h2 id="services_in_the_lab">Services "in the Lab"</h2>
+<h2 id="services-in-the-lab">Services "in the Lab"</h2>
<ul>
<li>
<p><a href="http://dev.iks-project.eu:8081/sparql">/sparql</a>: This is the SPARQL endpoint for the Stanbol store. SPARQL is the standard query language the most commonly used to provide interactive access to semantic knowledge bases.</p>
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/tutorial.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/tutorial.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/tutorial.html Wed Apr 11 08:56:13 2012
@@ -32,7 +32,10 @@
<ul>
<li><a href="/stanbol/index.html">Home</a></li>
<li><a href="/stanbol/docs/trunk/tutorial.html">Tutorial</a></li>
-<li><a href="/stanbol/docs/trunk/">Documentation</a></li>
+<li><a href="/stanbol/docs/trunk/">Documentation</a><ul>
+<li><a href="/stanbol/doc/0.9.0-incubating/">0.9.0-incubating</a></li>
+</ul>
+</li>
<li><a href="/stanbol/docs/trunk/building.html">Building</a></li>
</ul>
<h1 id="project">Project</h1>
@@ -46,7 +49,7 @@
<ul>
<li><a href="/stanbol/docs/trunk/downloads.html">Overview</a></li>
</ul>
-<h1 id="the_asf">The ASF</h1>
+<h1 id="the-asf">The ASF</h1>
<ul>
<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -58,7 +61,7 @@
<div id="content">
<h1 class="title">Tutorial for Apache Stanbol - Enhancing content items</h1>
<p>This tutorial targets at content management system developers, who want to enrich unstructured textual content with "named entity" tags (locations, persons or organizations such as "Paris", "Barack Obama", "BBC"). Apache Stanbol can provide such enhancements together with links to public (e.g. DBpedia) or private (e.g. an enterprise specific terminology) repositories.</p>
-<h2 id="build_and_run_your_apache_stanbol_instance">Build and run your Apache Stanbol instance</h2>
+<h2 id="build-and-run-your-apache-stanbol-instance">Build and run your Apache Stanbol instance</h2>
<p>To build Apache Stanbol from source you need Java 6 and maven 2.2.1 + (version as defined in the pom). You probably need also:<br />
</p>
<div class="codehilite"><pre><span class="c">% export MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=128M"</span>
@@ -85,7 +88,7 @@
</pre></div>
-<h2 id="post_content_item_get_an_enhancement_graph">Post content item, get an enhancement graph</h2>
+<h2 id="post-content-item-get-an-enhancement-graph">Post content item, get an enhancement graph</h2>
<p>Goto the local HTTP web endpoint</p>
<div class="codehilite"><pre><span class="n">http:</span><span class="sr">//</span><span class="n">localhost:8080</span><span class="o">/</span><span class="n">enhancer</span>
</pre></div>
@@ -109,7 +112,7 @@
</ul>
<p>You can use the <a href="http://localhost:8080/">OSGI console (http://{yourdomain}:{port}/)</a> (user/pwd: admin/admin) of your running Stanbol instance to activate and configure additional engines. Additional engines provide support keyword extraction together with a better language support, for geonames, zemanta or opencalais. See the overview of available Apache Stanbol <a href="enhancer/engines/list.html">Enhancement Engines</a>.</p>
<p>Another feature of this Apache Stanbol version is to manage and locally cache external entity repositories such as DBpedia as well as the possibility to use custom vocabularies as linking target repositories. Read more about this scenario <a href="customvocabulary.html">using custom vocabularies</a>.</p>
-<h2 id="advanced_explore_apache_stanbol_full_launcher">Advanced: Explore Apache Stanbol "full" launcher</h2>
+<h2 id="advanced-explore-apache-stanbol-full-launcher">Advanced: Explore Apache Stanbol "full" launcher</h2>
<p>The full (including experimental) features of Apache Stanbol can be accessed via Apache Stanbol's "full launcher". See the <a href="components.html">list of all available components</a> and their features.</p>
<p>To start the full launcher, you just have to execute its JAR via the following command:</p>
<div class="codehilite"><pre><span class="c">% java -Xmx1g -jar full/target/org.apache.stanbol.launchers.full-{snapshot-version}-SNAPSHOT.jar</span>