svn commit: r786250 - /websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/stanbolenhancementstructure.html

[bu...@apache.org]

Author: buildbot
Date: Mon Feb 28 21:55:28 2011
New Revision: 786250

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:55:28 2011
@@ -225,7 +225,7 @@ The following code segment shows the kno
 <p>By default detected Features are considered to be extracted from the whole content. While this assumption is appropriate for things like Categorizations and keywords for a lot of cases it is possible to specify the exact occurrence of features within the content and/or the metadata of the content.</p>
 <p>Typically Occurrences are used together with sb:Annotations and sb:Enhancement in cases an EnhancementEngine whats to describe the position of the extracted Feature within the analyzed content. So propertied defined by this two context should be considered when reading this section.</p>
 <p>Different Occurrence descriptions are needed to describe the position of a feature within different types of content or within the parsed metadata.</p>
-<h4 id="textoccurrence">TextOccurrence:</h4>
+<p><strong>TextOccurrence:</strong> </p>
 <p>Describe the occurrence of a feature within an textual content.</p>
 <div class="codehilite"><pre><span class="sr">&lt;o&gt;</span> <span class="n">rdf:type</span> <span class="n">sb:TextOccurrence</span>
     <span class="n">sb:TextOccurrence</span> <span class="n">rdfs:subClassOf</span> <span class="n">sb:Occurrence</span>
@@ -245,7 +245,7 @@ The following code segment shows the kno
 <li><strong>sb:context</strong>: The context (e.g. the sentence) used to extract the selected text.</li>
 <li><strong>sb:occurrence-within-context</strong>: Defines the n-th occurrence of the selected text with the context. Together with the sb:context this can be used to locate the selected text even if the sb:start/sb:end positions are no longer valid (e.g. when the original content was transformed to an other format).</li>
 </ul>
-<h4 id="metadataoccurrence">MetadataOccurrence:</h4>
+<p><strong>MetadataOccurrence:</strong> </p>
 <p>Describes the occurrence of an feature within the metadata of the parsed content. This are extremely useful to link entities for literal values provided by metadata standards such as creator information for Dublin Core, Artist, Album, Label ... information provided by ID3 or Camera Model information as present in EXIF metadata. Also geo-point to City, Region, Country enhancements could be done by using this type of occurrences. </p>
 <div class="codehilite"><pre><span class="sr">&lt;o&gt;</span> <span class="n">rdf:type</span> <span class="n">sb:MetadataOccurrence</span>
     <span class="n">sb:MetadataOccurrence</span> <span class="n">rdfs:subClassOf</span> <span class="n">sb:Occurrence</span>
@@ -260,7 +260,7 @@ The following code segment shows the kno
 <li><strong>rdf:field</strong>: The field of the metadata standard used. Multiple values describe that the feature occurs in several fields</li>
 <li><strong>rdf:value</strong>: The value that hints the described feature. The property is related to the properties dc:title - in case the value is a literal - and the sb:entity - in case the value is an URI - of sb:Annotation.</li>
 </ul>
-<h4 id="other_occurrence_types">Other Occurrence Types</h4>
+<p><strong>Other Occurrence Types</strong></p>
 <ul>
 <li>TimeBasedMediaOccurrence: This would define a temporal section within a time based media (e.g. a Sound File)</li>
 <li>VisualOccurrence: This would define a section within a media that can be presented on a screen</li>