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 2011/02/28 22:52:10 UTC
svn commit: r786249 -
/websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/stanbolenhancementstructure.html
Author: buildbot
Date: Mon Feb 28 21:52:09 2011
New Revision: 786249
Log:
Staging update by buildbot
Modified:
websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/stanbolenhancementstructure.html
Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/stanbolenhancementstructure.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/stanbolenhancementstructure.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/stanbolenhancementstructure.html Mon Feb 28 21:52:09 2011
@@ -89,7 +89,7 @@ To express that it will need to combine
</ul>
<p>Notations used by this specification:</p>
<ul>
-<li><strong><{code}></strong> elements do refer to an instance identified by the URI {code}. To improve the readability {codes} that refer to instances of concepts defined by the Stanbol enhancement structure will use short forms (<ci> for a ContentItem instance, <a> for anAnnotation instance ...).</li>
+<li><strong><{code}></strong> elements do refer to an instance identified by the URI {code}. To improve the readability {codes} that refer to instances of concepts defined by the Stanbol enhancement structure will use short forms (<ci> for a ContentItem instance, <a> for anAnnotation instance ...).</li>
<li><strong>{prefix}:{localname}</strong> is used as short form for <{namespace+localname}>. The namespace -> prefix mappings are defined in the above list</li>
<li><strong>{value}^^dataType</strong> The (xsd) dataType required by the value e.g. xsd:float, xsd:anyUri, The default is xsd:string</li>
<li><strong>?{var}</strong> represent a resource that is unknown by the Stanbol Enhancer. Usually a resource of the Users knowledge model that is not necessarily parsed to the Stanbol<br />
@@ -102,8 +102,8 @@ To express that it will need to combine
<li>In case of <{code}> the URI identifies a resource that is created/defined by the enhancement results - meaning that the returned knowledge contains all information about that resource</li>
<li>{value}^^xsd:anyURI indicates that enhancement results will not provide additional knowledge about this resource. If the consumer needs more information about such resources he need to use other services to retrieve such knowledge or parse special parameters to tell Stanbol to explicitly include such knowledge in the response.</li>
</ul>
-<h3 id="contentitem_ci">ContentItem <ci></h3>
-<p>The ContentItem <ci> represents a content enhanced by the Stanbol Enhancer. It is the central resource used to link all the enhancements created by the EnhancementEngines.
+<h3 id="contentitem_ltci">ContentItem <ci></h3>
+<p>The ContentItem <ci> represents a content enhanced by the Stanbol Enhancer. It is the central resource used to link all the enhancements created by the EnhancementEngines.
The Stanbol Enhancement Structure does not force client to distinguish between content (data) and contentItem (interpretation of the data). Within the Stanbol Enhancer only the contentItem is needed, because the Content is accessed via the Java API. Client are free to use markup to explicitly identify these parts of documents that need to be interpreted as content (e.g. an element in the DOM tree). An example is provided below. </p>
<div class="codehilite"><pre><span class="sr"><ci></span> <span class="n">rdf:type</span> <span class="n">sb:ContentItem</span>
<span class="p">[</span><span class="sr"><ci></span> <span class="n">rdf:type</span> <span class="n">sioc:Item</span><span class="p">]</span>
@@ -112,7 +112,7 @@ The Stanbol Enhancement Structure does n
</pre></div>
-<p>The ContentItem itself does not define any properties however it is used as domain (target type) of some properties within the Stanbol Enhancement structure. Information extracted from metadata parsed with the content (e.g. Dublin Core, EXIF, ID3 ...) can be added directly to the ContentItem <ci>.</p>
+<p>The ContentItem itself does not define any properties however it is used as domain (target type) of some properties within the Stanbol Enhancement structure. Information extracted from metadata parsed with the content (e.g. Dublin Core, EXIF, ID3 ...) can be added directly to the ContentItem <ci>.</p>
<p><em>TODO:</em> Describe here how to deal with embedded knowledge (e.g. RDFa, MicroFormats â¦). Last time the discussion was to write such knowledge into an own Graph and do not add it to the returned Enhancement Structure. However this was only an suggestion and need to be reviewed.</p>
<p>The usage of SIOC (Semantically-Interlinked Online Communities) is optionally and usually added by the client to embed information (e.g. as RDFa) to the content itself. However when parsing HTML with such markup to the Stanbol Enhancer such markup MUST BE used as default to determine those parts of the content that need to be enhanced.</p>
<p><em>TODO</em>: Move this to an own section about RDFa support!</p>
@@ -150,8 +150,8 @@ The Stanbol Enhancement Structure does n
</pre></div>
-<p>The presence of the statement "<e> rdf:type sd:Enhancement" statement indicated that enhancement metadata are present for the resource <e>. This also means that if there is some configuration set to exclude such information, than all the above properties MUST be removed from the results of the enhancement process.
-The optional rdf:types sb:Annotation and sb:Occurrent do only indicate, that typically any enhancement resource <e> is also of type sb:Annotation and/or sb:Occurrent. See the according sections and the usage examples for more information.</p>
+<p>The presence of the statement "<e> rdf:type sd:Enhancement" statement indicated that enhancement metadata are present for the resource <e>. This also means that if there is some configuration set to exclude such information, than all the above properties MUST be removed from the results of the enhancement process.
+The optional rdf:types sb:Annotation and sb:Occurrent do only indicate, that typically any enhancement resource <e> is also of type sb:Annotation and/or sb:Occurrent. See the according sections and the usage examples for more information.</p>
<p>All of the metadata used to describe the enhancement process do use the DCterms vocabulary. </p>
<ul>
<li>dc:creator and dc:contributor link to the EnhancementEngine(s) involved in creating the Enhancement. </li>
@@ -161,7 +161,7 @@ The optional rdf:types sb:Annotation an
<p><em>NOTE</em>: With this version of the enhancement structure it is no longer expected from users to process dc:relation and dc:requires relations as it was the case with the FISE enhancement structure to query for EntityAnnotations for TextAnnotations.</p>
<h3 id="annotations">Annotations</h3>
<p>The concept "Annotation" provides metadata about the extracted feature. This information are important both for the enhancement process and the users of the Stanbol Enhancer.
-The following code segment shows the knowledge typically provided by an Annotation <a>. A description of the properties is provided below:</p>
+The following code segment shows the knowledge typically provided by an Annotation <a>. A description of the properties is provided below:</p>
<div class="codehilite"><pre><span class="sr"><a></span> <span class="n">rdf:type</span> <span class="n">sb:Annotation</span>
<span class="p">[</span><span class="sr"><a></span> <span class="n">rdf:type</span> <span class="n">sb:Enhancement</span><span class="p">,</span> <span class="n">sb:Occurrence</span><span class="p">]</span>
<span class="sr"><a></span> <span class="n">sb:extracted</span><span class="o">-</span><span class="n">from</span> <span class="sr"><ci></span>
@@ -175,7 +175,7 @@ The following code segment shows the kno
</pre></div>
-<p>The following properties are defined for Annotations <a></p>
+<p>The following properties are defined for Annotations <a></p>
<ul>
<li><strong>rdf:type sb:Annotation</strong>: This states that someone can expect the resource to provide all the information as defined by this specification</li>
<li><strong>sb:extracted-from</strong>: This links the annotation describing an feature with the content item this feature is extracted from.</li>