Author: buildbot
Date: Wed Feb 29 12:11:47 2012
New Revision: 806727
Log:
Staging update by buildbot for stanbol
Modified:
websites/staging/stanbol/trunk/ (props changed)
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/cmsadapter5min.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/index.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/contentenhancement.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/metaxaengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentitytaggingengine.html
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/index.html
Propchange: websites/staging/stanbol/trunk/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Feb 29 12:11:47 2012
@@ -1 +1 @@
-1292426
+1295071
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/cmsadapter5min.html
==============================================================================
---
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/cmsadapter5min.html
(original)
+++
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/cmsadapter5min.html
Wed Feb 29 12:11:47 2012
@@ -46,7 +46,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,10 +57,10 @@
<div id="content">
<h1 class="title"></h1>
- <h1 id="5_minutes_documentation_for_cms_adapter">5 Minutes Documentation
for CMS Adapter</h1>
-<p>CMS Adapter component acts as a bridge between content management systems
and the Apache Stanbol. Please note that all components of Apache Stanbol also
provides RESTful services which allow accesing them directly from outside. CMS
Adapter interacts with content management systems through JCR and CMIS
specifications. In other words, any content repository compliant with JCR or
CMIS specifications can make use of CMS Adapter functionalities. For the time
being, there are two main functionalities that CMS Adapter offers:
"Bidirectional Mapping" and "Contenthub Feed". </p>
+ <h1 id="5-minutes-documentation-for-cms-adapter">5 Minutes Documentation
for CMS Adapter</h1>
+<p>The CMS Adapter component acts as a bridge between content management
systems and the Apache Stanbol. Please note that all components of Apache
Stanbol also provides RESTful services which allow accessing them directly from
outside. CMS Adapter interacts with content management systems through JCR and
CMIS specifications. In other words, any content repository compliant with JCR
or CMIS specifications can make use of CMS Adapter functionalities. For the
time being, there are two main functionalities that CMS Adapter offers:
"Bidirectional Mapping" and "Contenthub Feed". </p>
<p><strong>Note</strong>: URLs given in the curl commands and link are valid
as long as full launcher of the Stanbol is launched with the default
configurations. In other words, it assumed that the root URL of the Stanbol is
<strong>http://localhost:8080</strong>.</p>
-<h2 id="session_management">Session Management</h2>
+<h2 id="session-management">Session Management</h2>
<p>To be able to use Contenthub features, it is necessary to get a session key
beforehand. While obtaining this key, CMS Adapter caches a JCR/CMIS session to
be used when the generated session key is passed in the subsequent operations
that require interaction with the content repository. A session can key can be
obtained through REST services as follows:</p>
<div class="codehilite"><pre><span class="n">curl</span> <span
class="o">-</span><span class="n">X</span> <span class="n">GET</span> <span
class="o">-</span><span class="n">H</span> <span class="s">"Accept:
text/plain"</span> <span
class="s">"http://localhost:8080/cmsadapter/session?repositoryURL=rmi://localhost:1099/crx&workspaceName=demo&username=admin&password=admin&connectionType=JCR"</span>
</pre></div>
@@ -68,7 +68,7 @@
<p>In this example a session key is obtained for a JCR compliant repository.
CMS Adapter use RMI protocol to get session from JCR repositories or it tries
to access repository via a URL. So, RMI endpoint or URL of the repository is
specified. Furthermore target workspace in the repository has been specified
together with the username and password to access it. While accessing CMIS
repositories AtomPub binding is used, so repository URL should be specified
considering this protocol.</p>
<p>Apart from the retrieval of session key by providing one by one as in the
RESTful example, Java API of CMS Adapter also allows obtaining a session key
with an already available session object through the SessionManager service.
Thus, this is a more convenient way while obtaining a session key using CMS
Adapter through its Java API.</p>
-<h2 id="bidirectional_mapping">Bidirectional Mapping</h2>
+<h2 id="bidirectional-mapping">Bidirectional Mapping</h2>
<p>This feature provides bidirectional mappings between JCR/CMIS compliant
content repositories and external RDF data. Using this feature it is possible
to generate RDF data from content repository or populate content repository
based on the external RDF data.</p>
<p>The functionality described in this feature is realized by a two-step
process. This process includes sequential execution of RDFBridge and RDFMapper
services of CMS Adapter. Considering the update of content repository based on
external RDF data, in the first step the given raw RDF data is annotated with
standard terms by RDFBridge. There are a few terms that are described in the
<strong>CMS Vocabulary</strong> section. RDFMapper processes the annotated RDF
and update the content repository accordingly. From the other direction, in the
first step content repository structure is transformed into RDF annotated with
the CMS Vocabulary terms by RDFMappers. In the second step RDFBridges add
implementation specific annotations.</p>
<p>From one perspective, bidirectional mapping feature makes possible to
exploit open linked data, which is already available on the web, in content
management systems. Apart from the already available RDF data on the web, any
RDF data can be mapped to content repository. By mapping external RDF data
existing content repository items can be updated or new ones created. </p>
@@ -85,7 +85,7 @@
<p>Note that during the mapping process of bidirectional mappings the same RDF
Bridge configurations are used in both directions. Also,
<strong>baseURI</strong> is a mandatory parameter that is used as the base URI
of the RDF to be generated.</p>
<p>RDF representation of a content management system helps building semantic
services on top of the existing system. Contenthub component of Apache Stanbol
can be used to provide semantic indexing and search functionalities based on
the RDF representation of content repositories. That is, the RDF representation
is used as a resource that Contenthub uses to populate the underlying semantic
index.</p>
-<h2 id="contenthub_feed">Contenthub Feed</h2>
+<h2 id="contenthub-feed">Contenthub Feed</h2>
<p>Contenthub feed feature aims to manage content repository items within the
Contenthub component of Apache Stanbol. The management process includes only
two types of operations, submit and delete. </p>
<p>Submission and deletion operations can be done based on the identifiers of
path of the content repository items. During the submission process, properties
of content repository items are collected and they are stored along with the
actual content. This makes possible faceted search over the properties of
items.</p>
<p>RESTful API of CMS Adapter can be used submit content repository items to
Contenthub.</p>
@@ -98,9 +98,9 @@
</pre></div>
-<h2 id="cms_vocabulary">CMS Vocabulary</h2>
+<h2 id="cms-vocabulary">CMS Vocabulary</h2>
<p>This vocabulary aims to provide a standardized mapping between content
repositories and RDF data. This vocabulary includes a small number of essential
terms to map an RDF data to a content repository. As well as general terms that
are commonly used for both JCR and CMIS repositories there are also JCR or CMIS
specific terms.</p>
-<h3 id="general_terms">General Terms</h3>
+<h3 id="general-terms">General Terms</h3>
<ul>
<li>CMS_OBJECT: In a CMS vocabulary annotated RDF, if a resource has this URI
reference as value of its rdf:type property, the subject of that resource
represents a content repository item e.g a node in JCR compliant content
repositories or an object in CMIS compliant content repositories.</li>
<li>CMS_OBJECT_NAME: This URI reference represents the name of the content
repository item.</li>
@@ -108,12 +108,12 @@
<li>CMS_OBJECT_PARENT_REF: This URI reference represents the item to be
created as parent of the item having this property.</li>
<li>CMS_OBJECT_HAS_URI: This URI reference represents the URI which is
associated with the content repository item.</li>
</ul>
-<h3 id="jcr_specific_properties">JCR Specific Properties</h3>
+<h3 id="jcr-specific-properties">JCR Specific Properties</h3>
<ul>
<li>JCR_PRIMARY_TYPE: This URI reference represents primary node of the
content repository item associated with the resource within the RDF.</li>
<li>JCR_MIXIN_TYPES: This URI reference represents the mixin type of the
content repository item associated with the resource within the RDF.</li>
</ul>
-<h3 id="cmis_specific_properties">CMIS Specific Properties</h3>
+<h3 id="cmis-specific-properties">CMIS Specific Properties</h3>
<ul>
<li>CMIS_BASE_TYPE_ID: This URI reference represents the base type of the
content repository item associated with the resource within the RDF.</li>
</ul>
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/index.html
==============================================================================
---
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/index.html
(original)
+++
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/cmsadapter/index.html
Wed Feb 29 12:11:47 2012
@@ -20,7 +20,7 @@
-->
<link href="/stanbol/css/stanbol.css" rel="stylesheet" type="text/css">
- <title>Apache Stanbol - </title>
+ <title>Apache Stanbol - CMS Adapter</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="icon" type="image/png"
href="/stanbol/images/stanbol-logo/stanbol-favicon.png"/>
</head>
@@ -46,7 +46,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>
@@ -56,20 +56,19 @@
</div>
<div id="content">
- <h1 class="title"></h1>
- <h1 id="cms_adapter">CMS Adapter</h1>
-<p>CMS Adapter component acts as a bridge between content management systems
and the Apache Stanbol. Please note that all components of Apache Stanbol also
provides RESTful services which allow accesing them directly from outside. CMS
Adapter interacts with content management systems through JCR and CMIS
specifications. In other words, any content repository compliant with JCR or
CMIS specifications can make use of CMS Adapter functionalities. For the time
being, there are two main functionalities that CMS Adapter offers:
"Bidirectional Mapping" and "Contenthub Feed". </p>
-<h2 id="bidirectional_mapping">Bidirectional Mapping</h2>
+ <h1 class="title">CMS Adapter</h1>
+ <p>The CMS Adapter component acts as a bridge between content management
systems and the Apache Stanbol. Please note that all components of Apache
Stanbol also provides RESTful services which allow accessing them directly from
outside. CMS Adapter interacts with content management systems through JCR and
CMIS specifications. In other words, any content repository compliant with JCR
or CMIS specifications can make use of CMS Adapter functionalities. For the
time being, there are two main functionalities that CMS Adapter offers:
"Bidirectional Mapping" and "Contenthub Feed". </p>
+<h2 id="bidirectional-mapping">Bidirectional Mapping</h2>
<p>From one perspective, this feature enables content management systems to
represent their content repository structure in RDF format. This helps building
semantic services on top of the existing content management systems using their
RDF representation. </p>
<p>From the other perspective, bidirectional mapping feature makes possible to
exploit open linked data, which is already available on the web, in content
management systems. Apart from the already available data on the web, any RDF
data can be mapped to content repository. By mapping external RDF data existing
content repository items can be updated or new ones created. </p>
-<h2 id="contenthub_feed">Contenthub Feed</h2>
-<p>Contenthub feed feature of CMS Adapter provides managemet of content
repository items within Contenthub. The management process includes only two
types of operations, namely: submit and delete. By submitting content items to
Contenthub, you can make use of indexing and search functionalities of
Contenthub over the submitted items.</p>
-<h2 id="use_cases">Use Cases</h2>
-<h3 id="faceted_search">Faceted Search</h3>
+<h2 id="contenthub-feed">Contenthub Feed</h2>
+<p>Contenthub feed feature of CMS Adapter provides management of content
repository items within Contenthub. The management process includes only two
types of operations, namely: submit and delete. By submitting content items to
Contenthub, you can make use of indexing and search functionalities of
Contenthub over the submitted items.</p>
+<h2 id="use-cases">Use Cases</h2>
+<h3 id="faceted-search">Faceted Search</h3>
<p>As properties of content repository items are submitted to Contenthub along
with the actual content, it is possible to provide to obtain faceted search
facility for the content items managed within Contenthub. Furthermore, any kind
of Solr query can be executed on the index keeping the submitted content
items.</p>
-<h3 id="exploiting_linked_data">Exploiting Linked Data</h3>
+<h3 id="exploiting-linked-data">Exploiting Linked Data</h3>
<p>Chance of mapping any RDF data to content repository enables users making
use of <a href="http://linkeddata.org/";>open linked data</a> available on the
web. Current implementation is especially handy for hierarchical RDF data e.g.
category, topic hierarchies. Users can populate content repositories with
hierarchies in which further content items can be created.</p>
-<h2 id="building_and_launching">Building and Launching</h2>
+<h2 id="building-and-launching">Building and Launching</h2>
<p>Since CMS Adapter is included in the Full Launcher of Apache Stanbol it is
built with Apache Stanbol by default and can be launched under Apache Stanbol
Full Launcher. For detailed instructions to build and launch Apache Stanbol see
this README file.</p>
<p>CMS Adapter serves its features through its Java API together with the
corresponding RESTful services. Restful services can be accessed starting from
the root resource: http://localhost:8080/cmsadapter after launching the full
launcher with default configurations.</p>
<p>More detailed information can be found in <a href="cmsadapter5min">5-minute
documentation</a> of CMS Adapter.</p>
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/contentenhancement.html
==============================================================================
---
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/contentenhancement.html
(original)
+++
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/contentenhancement.html
Wed Feb 29 12:11:47 2012
@@ -46,7 +46,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 +60,8 @@
<p>For enhancing content you simply post plain text content to the
Enhancement Engines and you will get back enhancement data. The enhancement
process is stateless, so neither your content item, nor the enhancements will
be stored. </p>
<p>You can test this via the [web interface of the engines][stan-engines] or
from console via</p>
<div class="codehilite"><pre><span class="n">curl</span> <span
class="o">-</span><span class="n">X</span> <span class="n">POST</span> <span
class="o">-</span><span class="n">H</span> <span class="s">"Accept:
text/turtle"</span> <span class="o">-</span><span class="n">H</span> <span
class="s">"Content-type: text/plain"</span> <span class="o">\</span>
-<span class="o">--</span><span class="n">data</span> <span
class="s">"John Smith was born in London."</span> <span
class="n">http:</span><span class="sr">//</span><span
class="n">localhost:8080</span><span class="o">/</span><span
class="n">engines</span>
+<span class="o">--</span><span class="n">data</span> <span class="s">"The
Stanbol enhancer can detect famous cities such as Paris \</span>
+<span class="s">and people such as Bob Marley."</span> <span
class="n">http:</span><span class="sr">//</span><span
class="n">localhost:8080</span><span class="o">/</span><span
class="n">engines</span>
</pre></div>
@@ -73,7 +74,7 @@
<p>Content items in formats other than plain text can be tested via the [web
interface of contenthub][stan-contenthub] or via the console by attaching
files. (The Metaxa Engine needs to be activated).</p>
-<h2 id="using_the_enhancement_engines">Using the enhancement engines</h2>
+<h2 id="using-the-enhancement-engines">Using the enhancement engines</h2>
<p>Apache Stanbol starts with a number of active enhancement engines by
default. You can activate or deactivate engines as well as configure them to
your needs via the [OSGI administration console][stan-admin].</p>
<p>For the enhancement engines, a workflow for the enhancement process is
defined as pre-processing, content-extraction, extraction-enhancement, default
and post-processing. </p>
<p>The following pre-processing engines are available:</p>
@@ -109,7 +110,7 @@
<ul>
<li>The <strong>CachingDereferencerEngine</strong> is used for the Web UI and
fetches files such as images for locations from external sites and is used to
present the enhancement results. </li>
</ul>
-<h2 id="using_an_index_of_linked_open_data_locally">Using an index of linked
open data locally</h2>
+<h2 id="using-an-index-of-linked-open-data-locally">Using an index of linked
open data locally</h2>
<p>To use the pre-configured indexes you can download them from
[here][stan-download]. You will get two files for each index:</p>
<ul>
<li>org.apache.stanbol.data.site.{name}-{version}.jar </li>
@@ -125,75 +126,80 @@
<p>This bundle does not contain the indexed data but only the configuration
for the Solr Index.</p>
<p>If one has not copied the archive beforehand, the ZIP archive will be
requested by the Apache Stanbol Data File Provider after installing the Bundle.
To install the data you need copy this file to the "/sling/datafiles" folder
within the working directory of your Stanbol Server.</p>
<p><em>Note: {name} denotes to the value you configured for the "name"
property within the "indexing.properties" file.</em></p>
-<h2 id="enhancement_example">Enhancement Example</h2>
-<p>The text "John Smith was born in London." with a minimal configuration of
enhancement engines (<em>Named Entity Extraction Enhancement Engine</em> and
<em>Named Entity Tagging Engine</em>) together with a local index of dbpedia
entities will result in the following output graph of several <strong>Entity
Annotations</strong> and <strong>Text Annotations</strong>. </p>
-<p>Two of the relevant fragments for "London" are listed below in
Turtle-Syntax:</p>
-<h3 id="example_for_text_annotation">Example for Text Annotation</h3>
-<div class="codehilite"><pre><span
class="sr"><urn:enhancement-7af2e1a3-93fc-008f-fc6a-12accf05e58f></span>
- <span class="n">a</span> <span
class="sr"><http://fise.iks-project.eu/ontology/TextAnnotation></span>
<span class="p">,</span>
- <span
class="sr"><http://fise.iks-project.eu/ontology/Enhancement></span> <span
class="p">;</span>
+<h2 id="enhancement-example">Enhancement Example</h2>
+<p>The text "The Stanbol enhancer can detect famous cities such as Paris and
people such as Bob Marley." with the default configuration of enhancement
engines and with a local index of dbpedia entities will result in the following
output graph of several <strong>Entity Annotations</strong> and <strong>Text
Annotations</strong>. </p>
+<p>Two of the relevant fragments for "Paris" are listed below in
Turtle-Syntax:</p>
+<h3 id="example-for-text-annotation">Example for Text Annotation</h3>
+<div class="codehilite"><pre><span
class="sr"><urn:enhancement-4a2543d8-4d83-43ce-3a33-2924f457c872></span>
+ <span class="n">a</span> <span
class="sr"><http://fise.iks-project.eu/ontology/TextAnnotation></span>
<span class="p">,</span>
+ <span
class="sr"><http://fise.iks-project.eu/ontology/Enhancement></span> <span
class="p">;</span>
- <span
class="sr"><http://fise.iks-project.eu/ontology/confidence></span>
- <span class="s">"0.9973729691652052"</span><span
class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#double></span> <span
class="p">;</span>
+ <span
class="sr"><http://fise.iks-project.eu/ontology/confidence></span>
+ <span class="s">"0.9322403510215739"</span><span
class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#double></span> <span
class="p">;</span>
- <span class="sr"><http://fise.iks-project.eu/ontology/end></span>
- <span class="s">"29"</span><span class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#int></span> <span
class="p">;</span>
+ <span class="sr"><http://fise.iks-project.eu/ontology/end></span>
+ <span class="s">"59"</span><span class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#int></span> <span
class="p">;</span>
- <span
class="sr"><http://fise.iks-project.eu/ontology/extracted-from></span>
- <span
class="sr"><urn:content-item-sha1-88a2b5f6520df87e4567c06b48e742b7d1c71e9c></span>
<span class="p">;</span>
+ <span
class="sr"><http://fise.iks-project.eu/ontology/extracted-from></span>
+ <span
class="sr"><urn:content-item-sha1-37c8a8244041cf6113d4ee04b3a04d0a014f6e10></span>
<span class="p">;</span>
- <span
class="sr"><http://fise.iks-project.eu/ontology/selected-text></span>
- <span class="s">"London"</span><span class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#string></span> <span
class="p">;</span>
+ <span
class="sr"><http://fise.iks-project.eu/ontology/selected-text></span>
+ <span class="s">"Paris"</span><span
class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#string></span> <span
class="p">;</span>
- <span
class="sr"><http://fise.iks-project.eu/ontology/selection-context></span>
- <span class="s">"John Smith was born in London."</span><span
class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#string></span> <span
class="p">;</span>
+ <span
class="sr"><http://fise.iks-project.eu/ontology/selection-context></span>
+ <span class="s">"The Stanbol enhancer can detect famous cities
such as </span>
+<span class="s"> Paris and people such as Bob Marley."</span>
+ <span class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#string></span> <span
class="p">;</span>
- <span class="sr"><http://fise.iks-project.eu/ontology/start></span>
- <span class="s">"23"</span><span class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#int></span> <span
class="p">;</span>
+ <span class="sr"><http://fise.iks-project.eu/ontology/start></span>
+ <span class="s">"54"</span><span class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#int></span> <span
class="p">;</span>
- <span class="sr"><http://purl.org/dc/terms/created></span>
- <span class="s">"2011-06-29T14:43:24.291+02:00"</span><span
class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#dateTime></span> <span
class="p">;</span>
+ <span class="sr"><http://purl.org/dc/terms/created></span>
+ <span class="s">"2012-02-29T11:18:36.282Z"</span><span
class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#dateTime></span> <span
class="p">;</span>
- <span class="sr"><http://purl.org/dc/terms/creator></span>
- <span
class="s">"org.apache.stanbol.enhancer.engines.opennlp.impl.NEREngineCore"</span>
- <span class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#string></span> <span
class="p">;</span>
+ <span class="sr"><http://purl.org/dc/terms/creator></span>
+ <span
class="s">"org.apache.stanbol.enhancer.engines.opennlp.impl.NEREngineCore"</span>
+ <span class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#string></span> <span
class="p">;</span>
- <span class="sr"><http://purl.org/dc/terms/type></span>
- <span class="sr"><http://dbpedia.org/ontology/Place></span> <span
class="o">.</span>
+ <span class="sr"><http://purl.org/dc/terms/type></span>
+ <span class="sr"><http://dbpedia.org/ontology/Place></span>
<span class="o">.</span>
</pre></div>
-<h3 id="example_for_entity_annotation">Example for Entity Annotation</h3>
-<div class="codehilite"><pre><span
class="sr"><urn:enhancement-6fbf0996-b518-7130-92f8-00b4f7572031></span>
+<h3 id="example-for-entity-annotation">Example for Entity Annotation</h3>
+<div class="codehilite"><pre><span
class="sr"><urn:enhancement-b5e71f70-4978-a70b-7111-8d6e31283a58></span>
<span class="n">a</span> <span
class="sr"><http://fise.iks-project.eu/ontology/EntityAnnotation></span>
<span class="p">,</span>
<span
class="sr"><http://fise.iks-project.eu/ontology/Enhancement></span> <span
class="p">;</span>
- <span
class="sr"><http://fise.iks-project.eu/ontology/confidence></span>
- <span class="s">"183.53368"</span><span
class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#double></span> <span
class="p">;</span>
-
- <span
class="sr"><http://fise.iks-project.eu/ontology/entity-label></span>
- <span class="s">"London"</span><span class="nv">@en</span>
<span class="p">;</span>
+ <span
class="sr"><http://fise.iks-project.eu/ontology/confidence></span>
+ <span class="s">"1323049.5"</span><span
class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#double></span> <span
class="p">;</span>
- <span
class="sr"><http://fise.iks-project.eu/ontology/entity-reference></span>
- <span class="sr"><http://dbpedia.org/resource/London></span>
<span class="p">;</span>
+ <span
class="sr"><http://fise.iks-project.eu/ontology/entity-label></span>
+ <span class="s">"Paris"</span><span class="nv">@en</span>
<span class="p">;</span>
- <span
class="sr"><http://fise.iks-project.eu/ontology/entity-type></span>
- <span class="sr"><http://www.w3.org/2002/07/owl#Thing></span>
<span class="p">,</span> <span
class="sr"><http://www.opengis.net/gml/_Feature></span> <span
class="p">,</span>
- <span
class="sr"><http://dbpedia.org/ontology/Settlement></span> <span
class="p">,</span> <span
class="sr"><http://dbpedia.org/ontology/Place></span> <span
class="p">,</span>
- <span
class="sr"><http://dbpedia.org/ontology/PopulatedPlace></span> <span
class="p">;</span>
+ <span
class="sr"><http://fise.iks-project.eu/ontology/entity-reference></span>
+ <span class="sr"><http://dbpedia.org/resource/Paris></span>
<span class="p">;</span>
- <span
class="sr"><http://fise.iks-project.eu/ontology/extracted-from></span>
- <span
class="sr"><urn:content-item-sha1-88a2b5f6520df87e4567c06b48e742b7d1c71e9c></span>
<span class="p">;</span>
-
- <span class="sr"><http://purl.org/dc/terms/created></span>
- <span
class="s">"2011-06-29T14:43:24.295+02:00"</span><span
class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#dateTime></span> <span
class="p">;</span>
-
- <span class="sr"><http://purl.org/dc/terms/creator></span>
- <span
class="s">"org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine"</span>
- <span class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#string></span> <span
class="p">;</span>
+ <span
class="sr"><http://fise.iks-project.eu/ontology/entity-type></span>
+ <span class="sr"><http://www.w3.org/2002/07/owl#Thing></span>
<span class="p">,</span>
+ <span class="sr"><http://www.opengis.net/gml/_Feature></span>
<span class="p">,</span>
+ <span class="sr"><http://dbpedia.org/ontology/Place></span>
<span class="p">,</span>
+ <span
class="sr"><http://dbpedia.org/ontology/Settlement></span> <span
class="p">,</span>
+ <span
class="sr"><http://dbpedia.org/ontology/PopulatedPlace></span> <span
class="p">;</span>
+
+ <span
class="sr"><http://fise.iks-project.eu/ontology/extracted-from></span>
+ <span
class="sr"><urn:content-item-sha1-37c8a8244041cf6113d4ee04b3a04d0a014f6e10></span>
<span class="p">;</span>
+
+ <span class="sr"><http://purl.org/dc/terms/created></span>
+ <span class="s">"2012-02-29T11:18:36.320Z"</span>
+ <span class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#dateTime></span> <span
class="p">;</span>
+
+ <span class="sr"><http://purl.org/dc/terms/creator></span>
+ <span
class="s">"org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine"</span>
+ <span class="o">^^</span><span
class="sr"><http://www.w3.org/2001/XMLSchema#string></span> <span
class="p">;</span>
- <span class="sr"><http://purl.org/dc/terms/relation></span>
- <span
class="sr"><urn:enhancement-7af2e1a3-93fc-008f-fc6a-12accf05e58f></span>
<span class="o">.</span>
+ <span class="sr"><http://purl.org/dc/terms/relation></span>
+ <span
class="sr"><urn:enhancement-4a2543d8-4d83-43ce-3a33-2924f457c872></span>
<span class="o">.</span>
</pre></div>
</div>
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/metaxaengine.html
==============================================================================
---
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/metaxaengine.html
(original)
+++
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/metaxaengine.html
Wed Feb 29 12:11:47 2012
@@ -46,7 +46,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 +58,14 @@
<div id="content">
<h1 class="title">The Metaxa Enhancement Engine: extracting content and
metadata from various formats</h1>
<p>The <strong>Metaxa Enhancement Engine</strong> extracts embedded
metadata and textual content from a large variety of document types and
formats. The text extraction functionality also makes Metaxa suitable as a
pre-processor for other components, especially NLP processors and indexing for
search.</p>
-<h2 id="technical_description">Technical description</h2>
+<h2 id="technical-description">Technical description</h2>
<p>The engine is based on the <a
href="http://aperture.sourceforge.net/";>Aperture
framework</a> with new extensions to handling structured content embedded in
HTML web content, such as <a href="http://microformats.org/";>Microformats</a>
and <a href="http://www.w3.org/TR/rdfa-syntax/";>RDFa</a>.
Also some of the original extractors of Aperture were replaced by other
engines using different base libraries.
Metaxa introduces a single TextEnhancement instance that refers to the content
item by its <em>extracted-from</em> property. The specific metadata extracted
by Metaxa are ascribed directly to the content item/document since they
represent
document properties and not text annotations. Various ontologies are employed
to describe various types of metadata. An overview will be given below.</p>
<p>The general structure of the Metaxa annotations consists of three levels of
annotations illustrated in the following example:</p>
-<h4 id="the_top-level_tttextannotationtt_instance">The top-level
<tt>TextAnnotation</tt> instance</h4>
+<h4 id="the-top-level-wzxhzdk10textannotationwzxhzdk11-instance">The top-level
<tt>TextAnnotation</tt> instance</h4>
<div
class="codehilite"><pre><urn:enhancement-03c9e85e-2681-21b7-a5af-6da62d67ef6b>
a <http://fise.iks-project.eu/ontology/TextAnnotation> ,
<http://fise.iks-project.eu/ontology/Enhancement> ;
@@ -80,7 +80,7 @@ document properties and not text annotat
</pre></div>
-<h4
id="the_top-level_document_metadata_referenced_from_the_tttextannotationtt_instance_via_the_extracted-from_property">The
top-level document metadata, referenced from the <tt>TextAnnotation</tt>
instance via the <em>extracted-from</em> property:</h4>
+<h4
id="the-top-level-document-metadata-referenced-from-the-wzxhzdk12textannotationwzxhzdk13-instance-via-the-extracted-from-property">The
top-level document metadata, referenced from the <tt>TextAnnotation</tt>
instance via the <em>extracted-from</em> property:</h4>
<div
class="codehilite"><pre><http://localhost:8080/store/content/mf_example.htm>
a
<http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#HtmlDocument> ;
<http://www.semanticdesktop.org/ontologies/2007/01/19/nie#contains>
@@ -94,8 +94,8 @@ document properties and not text annotat
</pre></div>
-<p>NOTE: The extracted plain text is no longer added to the metadata of the
contentItem but stores in an own <a
href="../contentitem.html#content_parts">ContentPart</a> with the media type
"text/plain". Both the RESTful Service as the Java API allows to request this
data. See the according documentations for details.</p>
-<h4
id="embedded_tthcardtt_microformat_data_referenced_via_the_ttniecontainstt_property">Embedded
<tt>hCard</tt> microformat data referenced via the <tt>nie:contains</tt>
property:</h4>
+<p>NOTE: The extracted plain text is no longer added to the metadata of the
ContentItem but stores in an own <a
href="../contentitem.html#content_parts">ContentPart</a> with the media type
"text/plain". Both the RESTful Service as the Java API allows to request this
data. See the according documentations for details.</p>
+<h4
id="embedded-wzxhzdk14hcardwzxhzdk15-microformat-data-referenced-via-the-wzxhzdk16niecontainswzxhzdk17-property">Embedded
<tt>hCard</tt> microformat data referenced via the <tt>nie:contains</tt>
property:</h4>
<div class="codehilite"><pre><urn:rnd:-9e25553:12b3843df43:-7ffe>
a <http://www.w3.org/2006/vcard/ns#VCard> ;
<http://www.w3.org/2006/vcard/ns#adr>
@@ -142,7 +142,7 @@ document properties and not text annotat
</pre></div>
-<h3 id="supported_document_types">Supported document types</h3>
+<h3 id="supported-document-types">Supported document types</h3>
<p>The set of extraction engines for specific document types is defined by the
resource <em>extractionregistry.xml</em>. Each engine specifies what MIME types
it can handle. By default the extraction registry provides extractors for the
following set of document formats:</p>
<ul>
@@ -190,12 +190,13 @@ following set of document formats:</p>
<li>Plain Text</li>
<li>XML</li>
</ul>
-<h3 id="textual_content">Textual Content</h3>
+<h3 id="textual-content">Textual Content</h3>
<p>The extracted plain text is no longer added to the metadata of the
contentItem but stores in an own <a
href="../contentitem.html#content_parts">ContentPart</a> with the media type
"text/plain".</p>
<p>The following POST request to the Enhancer can be used to directly request
the plain text version of a parsed content</p>
<div class="codehilite"><pre>curl -v -X POST -H <span class="s2">"Accept:
text/plain"</span> <span class="se">\</span>
-H <span class="s2">"Content-type: text/html;
charset=UTF-8"</span> <span class="se">\</span>
- --data <span class="s2">"<html><body><p>John Smith
was born in London.</p></body></html>"</span> <span
class="se">\</span>
+ --data <span class="s2">"<html><body><p>The Stanbol
enhancer can detect \</span>
+<span class="s2"> famous cities such as Paris and people such as Bob
Marley.</p></body></html>"</span> <span
class="se">\</span>
<span
class="s2">"http://localhost:8080/enhancer/chain/language?omitMetadata=true"</span>
</pre></div>
@@ -204,7 +205,7 @@ following set of document formats:</p>
<p>NOTE: previous versions of this engine had stored the plain text version by
using the
"http://www.semanticdesktop.org/ontologies/2007/01/19/nie#plainTextContent";
property directly in the metadata of the ContentItem. This is no longer
supported.</p>
<h3 id="vocabularies">Vocabularies</h3>
<p>Metaxa uses a set of vocabularies ("ontologies") for structured data
representation.</p>
-<h4 id="aperture_core_ontologies">Aperture Core Ontologies</h4>
+<h4 id="aperture-core-ontologies">Aperture Core Ontologies</h4>
<p>These ontologies belong to the underlying Aperture subsystem, contained in
the
package</p>
<div class="codehilite"><pre>org.semanticdesktop.aperture.vocabulary
@@ -229,7 +230,7 @@ http://www.semanticdesktop.org/ontologie
</pre></div>
-<h4 id="html_microformat_extractors">HTML Microformat Extractors</h4>
+<h4 id="html-microformat-extractors">HTML Microformat Extractors</h4>
<p>The following table describes which vocabularies are used for representing
microformat data in Metaxa: </p>
<table border="1">
<tr>
@@ -309,7 +310,7 @@ http://www.semanticdesktop.org/ontologie
</tr>
</table>
-<h2 id="configuration_options">Configuration options</h2>
+<h2 id="configuration-options">Configuration options</h2>
<p>By default, Metaxa uses the extractors specified in the resource
"extractionregistry.xml", and for HTML pages, the resource "htmlregistry.xml".
Alternative configurations and extractors can be attached to Metaxa as
fragment bundles, specifying as host bundle</p>
<div class="codehilite"><pre>Fragment-Host:
org.apache.stanbol.enhancer.engines.metaxa
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.html
==============================================================================
---
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.html
(original)
+++
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentityextractionengine.html
Wed Feb 29 12:11:47 2012
@@ -46,7 +46,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>
@@ -59,23 +59,21 @@
<h1 class="title">The Named Entity Recognition Engine: detect Named
Entities from unstructured text content </h1>
<p>This engine is based on the NLP features of <a
href="http://incubator.apache.org/opennlp/";>Apache OpenNLP (incubating)</a>. It
uses its Maximum Entropy models to detect Persons, Names and Organizations.</p>
<p>(TODO: features, configuration if possible)</p>
-<h2 id="example_result">Example Result</h2>
-<p>This engine adds <strong>TextAnnotation-Enhancements</strong> for the text
"John Smith lives in London", (amongst other) the following information to the
enhancement graph, suggesting London (of type: Place) for the string London:</p>
+<h2 id="example-result">Example Result</h2>
+<p>This engine adds <strong>TextAnnotation-Enhancements</strong> for the text
"The Stanbol enhancer can detect famous cities such as Paris and people such as
Bob Marley.", (amongst other) the following information to the enhancement
graph, suggesting Bob Marley (of type: Person) for the string "Bob Marley":</p>
<div class="codehilite"><pre>{
- "@subject":
"<urn:enhancement-e6a08398-a49f-5bf6-c09f-6da5db63507e>",
- "@type": [
- "<enhancer:Enhancement>",
- "<enhancer:TextAnnotation>"
- ],
- "dc:created": "2011-10-04T12:36:50.670Z",
- "dc:creator":
"org.apache.stanbol.enhancer.engines.opennlp.impl.NEREngineCore",
- "dc:type": "<dbp-ont:Place>",
- "enhancer:confidence": 0.99691045,
- "enhancer:end": 26,
- "enhancer:extracted-from":
"<urn:content-item-sha1-ea97a3171fe123b27b02497f6eb08b2fca63e6ec>",
- "enhancer:selected-text": "London",
- "enhancer:selection-context": "John Smith lives in
London",
- "enhancer:start": 20
+ "@subject":
"urn:enhancement-b3d4617d-1760-0374-f471-e0e746003f4e",
+ "@type": [
"enhancer:Enhancement","enhancer:TextAnnotation"],
+ "dc:created": "2012-02-29T11:34:56.369Z",
+ "dc:creator":
"org.apache.stanbol.enhancer.engines.opennlp.impl.NEREngineCore",
+ "dc:type": "dbp-ont:Person",
+ "enhancer:confidence": 0.94647044,
+ "enhancer:end": 89,
+ "enhancer:extracted-from":
"urn:content-item-sha1-37c8a8244041cf6113d4ee04b3a04d0a014f6e10",
+ "enhancer:selected-text": "Bob Marley",
+ "enhancer:selection-context":
+ "The Stanbol enhancer can detect famous cities such as Paris and
people such as Bob Marley.",
+ "enhancer:start": 79
}
</pre></div>
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentitytaggingengine.html
==============================================================================
---
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentitytaggingengine.html
(original)
+++
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/engines/namedentitytaggingengine.html
Wed Feb 29 12:11:47 2012
@@ -46,7 +46,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>
@@ -70,130 +70,50 @@
<li>Place Type {<empty>, dbp-ont:Place}: The rdf:type used to search for
Places. If empty Entities of any type are accepted.*</li>
<li>Label Field {<empty>, rdfs:label}: The field used to search for Entities
with a label similar to the selected text of the Text Annotation. If empty
rdfs:label is used as default*</li>
</ul>
-<h2 id="example_result">Example Result</h2>
-<p>For the sentence "John Smith lives in London", you will get several
EntityAnnotations for the terms "London", "John Smith" form your linking target
resource (in this case DBpedia) together with a confidence value, which can be
used to sort the suggestions.</p>
+<h2 id="example-result">Example Result</h2>
+<p>For the sentence "The Stanbol enhancer can detect famous cities such as
Paris and people such as Bob Marley.", you will get several EntityAnnotations
for the terms "Paris" and "Bob Marley" from your linking target resource (in
this case DBpedia) together with a confidence value, which can be used to sort
the suggestions, e.g.:</p>
<div class="codehilite"><pre>{
- "@subject":
"<urn:enhancement-2ec0662c-3a10-f8f5-43b4-cf7403e4c39d>",
- "@type": [
- "<enhancer:Enhancement>",
- "<enhancer:EntityAnnotation>"
- ],
- "dc:created": "2011-10-06T07:45:04.175Z",
- "dc:creator":
"org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine",
- "dc:relation":
"<urn:enhancement-0218c6fa-7376-8c9f-c4ed-e973ff72194c>",
- "enhancer:confidence": 5147829.5,
- "enhancer:entity-label": "\"London\"@en",
- "enhancer:entity-reference":
"<http://dbpedia.org/resource/London>",
- "enhancer:entity-type": "<owl:Thing>",
- "enhancer:extracted-from":
"<urn:content-item-sha1-ea97a3171fe123b27b02497f6eb08b2fca63e6ec>"
-},
-{
- "@subject":
"<urn:enhancement-44ccea73-639d-394a-8660-fad46795a772>",
- "@type": [
- "<enhancer:Enhancement>",
- "<enhancer:EntityAnnotation>"
- ],
- "dc:created": "2011-10-06T07:45:06.809Z",
- "dc:creator":
"org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine",
- "dc:relation":
"<urn:enhancement-4b7b010e-efcc-8752-f055-b73620270295>",
- "enhancer:confidence": 4.471743,
- "enhancer:entity-label": "\"John L.
Smith\"@en",
- "enhancer:entity-reference":
"<http://dbpedia.org/resource/John_L._Smith>",
- "enhancer:entity-type": "<dbp-ont:CollegeCoach>",
- "enhancer:extracted-from":
"<urn:content-item-sha1-ea97a3171fe123b27b02497f6eb08b2fca63e6ec>"
-},
-{
- "@subject":
"<urn:enhancement-4b7b010e-efcc-8752-f055-b73620270295>",
- "@type": [
- "<enhancer:Enhancement>",
- "<enhancer:TextAnnotation>"
- ],
- "dc:created": "2011-10-06T07:44:52.318Z",
- "dc:creator":
"org.apache.stanbol.enhancer.engines.opennlp.impl.NEREngineCore",
- "dc:type": "<dbp-ont:Person>",
- "enhancer:confidence": 0.66891855,
- "enhancer:end": 10,
- "enhancer:extracted-from":
"<urn:content-item-sha1-ea97a3171fe123b27b02497f6eb08b2fca63e6ec>",
- "enhancer:selected-text": "John Smith",
- "enhancer:selection-context": "John Smith lives in
London",
- "enhancer:start": 0
-},
-{
- "@subject":
"<urn:enhancement-708bfdae-c104-19bd-c423-f5c10a11ae55>",
- "@type": [
- "<enhancer:Enhancement>",
- "<enhancer:EntityAnnotation>"
- ],
- "dc:created": "2011-10-06T07:45:04.216Z",
- "dc:creator":
"org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine",
- "dc:relation":
"<urn:enhancement-0218c6fa-7376-8c9f-c4ed-e973ff72194c>",
- "enhancer:confidence": 2543.5994,
- "enhancer:entity-label": "\"London,
Ontario\"@en",
- "enhancer:entity-reference":
"<http://dbpedia.org/resource/London,_Ontario>",
- "enhancer:entity-type":
"<http://www.opengis.net/gml/_Feature>",
- "enhancer:extracted-from":
"<urn:content-item-sha1-ea97a3171fe123b27b02497f6eb08b2fca63e6ec>"
-},
-{
- "@subject":
"<urn:enhancement-73dce2ac-72b6-b0f4-7c5c-e9c30aec9263>",
- "@type": [
- "<enhancer:Enhancement>",
- "<enhancer:EntityAnnotation>"
- ],
- "dc:created": "2011-10-06T07:45:04.216Z",
- "dc:creator":
"org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine",
- "dc:relation":
"<urn:enhancement-0218c6fa-7376-8c9f-c4ed-e973ff72194c>",
- "enhancer:confidence": 7709.837,
- "enhancer:entity-label": "\"City of
London\"@en",
- "enhancer:entity-reference":
"<http://dbpedia.org/resource/City_of_London>",
- "enhancer:entity-type":
"<http://www.opengis.net/gml/_Feature>",
- "enhancer:extracted-from":
"<urn:content-item-sha1-ea97a3171fe123b27b02497f6eb08b2fca63e6ec>"
-},
-{
- "@subject":
"<urn:enhancement-c428cb67-cdce-4396-96b8-ac3a8465730a>",
- "@type": [
- "<enhancer:Enhancement>",
- "<enhancer:TextAnnotation>"
- ],
- "dc:created": "2011-10-06T07:44:39.064Z",
- "dc:creator":
"org.apache.stanbol.enhancer.engines.langid.LangIdEnhancementEngine",
- "dc:language": "\"fi\"",
- "enhancer:extracted-from":
"<urn:content-item-sha1-ea97a3171fe123b27b02497f6eb08b2fca63e6ec>"
-},
-{
- "@subject":
"<urn:enhancement-c6ffb5f4-a224-9b7d-9854-7eaa101b2ebe>",
- "@type": [
- "<enhancer:Enhancement>",
- "<enhancer:EntityAnnotation>"
- ],
- "dc:created": "2011-10-06T07:45:06.809Z",
- "dc:creator":
"org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine",
- "dc:relation":
"<urn:enhancement-4b7b010e-efcc-8752-f055-b73620270295>",
- "enhancer:confidence": 15.735652,
- "enhancer:entity-label": "\"John Maynard
Smith\"@en",
- "enhancer:entity-reference":
"<http://dbpedia.org/resource/John_Maynard_Smith>",
- "enhancer:entity-type": "<dbp-ont:Scientist>",
- "enhancer:extracted-from":
"<urn:content-item-sha1-ea97a3171fe123b27b02497f6eb08b2fca63e6ec>"
-},
-{
- "@subject":
"<urn:enhancement-eeaf0331-5988-5231-493c-f934a2602200>",
- "@type": [
- "<enhancer:Enhancement>",
- "<enhancer:EntityAnnotation>"
- ],
- "dc:created": "2011-10-06T07:45:06.809Z",
- "dc:creator":
"org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine",
- "dc:relation":
"<urn:enhancement-4b7b010e-efcc-8752-f055-b73620270295>",
- "enhancer:confidence": 4.4515367,
- "enhancer:entity-label": "\"John T.
Smith\"@en",
- "enhancer:entity-reference":
"<http://dbpedia.org/resource/John_T._Smith>",
- "enhancer:entity-type": "<owl:Thing>",
- "enhancer:extracted-from":
"<urn:content-item-sha1-ea97a3171fe123b27b02497f6eb08b2fca63e6ec>"
-}
-]
+ "@subject":
"urn:enhancement-b98283ae-845d-6666-d68b-f649852a7959",
+ "@type":
["enhancer:Enhancement","enhancer:EntityAnnotation"],
+ "dc:created": "2012-02-29T11:34:56.383Z",
+ "dc:creator":
"org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine",
+ "dc:relation":
"urn:enhancement-b3d4617d-1760-0374-f471-e0e746003f4e",
+ "enhancer:confidence": 16641.191,
+ "enhancer:entity-label":
+ {
+ "@literal": "Bob Marley",
+ "@language": "en"
+ },
+ "enhancer:entity-reference":
"http://dbpedia.org/resource/Bob_Marley",
+ "enhancer:entity-type":
+ ["dbp-ont:MusicalArtist", "foaf:Person",
"dbp-ont:Artist",
+ "dbp-ont:Person", "owl:Thing"],
+ "enhancer:extracted-from":
"urn:content-item-sha1-37c8a8244041cf6113d4ee04b3a04d0a014f6e10"
+ },
</pre></div>
-<p>}</p>
+<p>or </p>
+<div class="codehilite"><pre>{
+ "@subject":
"urn:enhancement-785a4c4f-dc7d-aa46-91a2-aef840542ae2",
+ "@type":
["enhancer:Enhancement","enhancer:EntityAnnotation"],
+ "dc:created": "2012-02-29T11:34:56.383Z",
+ "dc:creator":
"org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine",
+ "dc:relation":
"urn:enhancement-c176f1bf-a1dd-830e-df7d-deecdfdc8375",
+ "enhancer:confidence": 1323049.5,
+ "enhancer:entity-label":
+ {
+ "@literal": "Paris",
+ "@language": "en"
+ },
+ "enhancer:entity-reference":
"http://dbpedia.org/resource/Paris",
+ "enhancer:entity-type":
+ ["dbp-ont:PopulatedPlace","dbp-ont:Settlement",
+ "http://www.opengis.net/gml/_Feature",
+ "dbp-ont:Place","owl:Thing"],
+ "enhancer:extracted-from":
"urn:content-item-sha1-37c8a8244041cf6113d4ee04b3a04d0a014f6e10"
+ }
+</pre></div>
</div>
<div id="footer">
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
Feb 29 12:11:47 2012
@@ -46,7 +46,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 +58,7 @@
<div id="content">
<h1 class="title">Documentation</h1>
<p>This documentation of Apache Stanbol targets at Content Management
System (CMS) developers and integrators, who want to use and integrate Apache
Stanbol RESTful services into their CMS. Secondly, it is for Apache Stanbol
contributors, which are developing Apache Stanbol components and engines.</p>
-<h2 id="documentation_for_cms_developers">Documentation for CMS Developers</h2>
+<h2 id="documentation-for-cms-developers">Documentation for CMS Developers</h2>
<ul>
<li><a href="scenarios.html">Usage Scenarios</a></li>
<li><a href="components.html">Overview on components and engines</a></li>
@@ -66,15 +66,14 @@
<li>Demos</li>
</ul>
<p><em>Note</em>: In addition to the documentation on this site, every Apache
Stanbol instance provides you with live documentation when pointing your
browser to the Apache Stanbol start page. It contains further descriptions and
the most up-to-date documenation for each component and its RESTful API.
Additional technical notes for each component can be found within various
README files within the <a
href="http://svn.apache.org/repos/asf/incubator/stanbol/trunk/";>source
code</a>.</p>
-<h2
id="documentation_for_apache_stanbol_for_developers_and_contributors">Documentation
for Apache Stanbol for Developers and Contributors</h2>
+<h2
id="documentation-for-apache-stanbol-for-developers-and-contributors">Documentation
for Apache Stanbol for Developers and Contributors</h2>
<ul>
-<li>Java API for developers</li>
+<li>Detailed documentation on the <a href="enhancer">Enhancer</a> and <a
href="enhancer/engines">Enhancement Engines</a>: develop a new engine!</li>
<li>How to contribute to software development</li>
<li>How to work and update documentation</li>
<li>Proposals for further developments</li>
-<li>How to build an engine </li>
</ul>
-<h2 id="how_to_get_involved">How to get involved</h2>
+<h2 id="how-to-get-involved">How to get involved</h2>
<ul>
<li>
<p>Subscribe to the Apache Stanbol Developers mailinglist by sending an email
to <code>stanbol-dev-subscribe AT incubator.apache.org</code>.</p>
