svn commit: r799382 - /websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/ses_annotationontology.html

[bu...@apache.org]

Author: buildbot
Date: Mon Nov 28 07:20:58 2011
New Revision: 799382

Log:
Staging update by buildbot

Modified:
    websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/ses_annotationontology.html

Modified: websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/ses_annotationontology.html
==============================================================================
--- websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/ses_annotationontology.html (original)
+++ websites/staging/stanbol/trunk/content/stanbol/docs/trunk/enhancer/ses_annotationontology.html Mon Nov 28 07:20:58 2011
@@ -46,12 +46,7 @@
   
   <div id="content">
     <h1 class="title">The Stanbol Enhancement Structure (PROPOSAL)</h1>
-    <p>Please NOTE: This is a proposal for the future version of the Enhancement Structure used by the Stanbol Enhancer. </p>
-<p><strong>NOTES:</strong> </p>
-<ul>
-<li>This <strong>DOES NOT</strong> describe the Enhancement Structure used by the current version of the Stanbol Enhancer! </li>
-<li>There is also an <a href="stanbolenhancementstructure.html">older Proposal</a> that might still contain some information that are not yet contained in this version.</li>
-</ul>
+    <p>Please NOTE: This is a proposal for the future version of the Enhancement Structure used by the Stanbol Enhancer. This <strong>DOES NOT</strong> describe the Enhancement Structure used by the current version of the Stanbol Enhancer!</p>
 <h2 id="background">Background</h2>
 <p>This proposal is aimed to define the "Stanbol Enhancement Structure" intended to be used by future version of the Stanbol Enhancer to encode Knowledge extracted from analyzed Documents.</p>
 <p>Currently the Stanbol Enhancer still uses the <a href="http://wiki.iks-project.eu/index.php/EnhancementStructure">FISE Enhancement Structure</a> that dates back before the incubation of Stanbol to Apache. This proposal now suggest to base the "Stanbol Enhancement Structure" on the existing <a href="http://code.google.com/p/annotation-ontology/wiki/Homepage">Annotation-Ontology</a>.</p>
@@ -108,8 +103,9 @@
 <p>Image Credits: Annotation-Ontology <a href="http://annotation-ontology.googlecode.com/svn/trunk/images/Image%20InitEndCorner%20Selector%20-%20AO%20Annotation%20Ontology%20-%20by%20Paolo%20Ciccarese.png">Link</a>.</p>
 </blockquote>
 <h4 id="text_selectors">Text Selectors</h4>
-<p>The "PrefixPostfixSelector" as defined by the Text-Annotation Ontology differs from the currently used FISE Text Annotation. It does not define the character indexes and uses prefix and postfix instead of the surrounding context.</p>
-<p>Regarding backward compatibility The suggestion is to adopt the "PrefixPostfixSelector" but keep the start and end positions of the current Text Annotation. The prefix/posfix model of the "PrefixPostfixSelector" is definitely better than the used context of the FISE Text Annotation, because it allows to clearly identify the selected text even if it occurs several times in a given context.</p>
+<p>The currently used FISE TextAnnotation differs form text selects of the Annotation-Ontology mainly in that, that it defines bot the actual annotation AND the selection within the text. Therefore when adopting the "Anootation -&gt; Seletor" model or the Annotation-Ontology all Annotation related properties of the FISE TextAnnotation must be separated from the properties describing the selection.</p>
+<p>The Annotation-Ontology defines two text selectors: (1) the "OffsetRangeSelector" that uses char offset within the text to define a selection and (2) the "PrefixPostfixSelector" that uses a prefix, suffix and the selected text to define the selection based on the context. The Stanbol Enhancer currently uses both (context and offset) to define selection. However currently only single property "context" is used instead of the prefix, suffix model of the "PrefixPostfixSelector". In general the prefix, postfix based context definition as used by the Annotation-Ontology is better, because is allows to uniquely determine the selected part of the text even if the selected text appears multiple times within a given context. With the currently used model it is not possible to do that if the selected text appears several times in the provided context. </p>
+<p>The suggestion is to keep both (offset and context) based definition of text selection but switch to the prefix, suffix model for defining the context . Therefore stanbol:TextSelector will be defined as sub-class of both "OffsetRangeSelector" and "PrefixPostfixSelector".</p>
 <h4 id="multi_media_selectors_and_the_media_fragments_standard">Multi Media Selectors and the Media Fragments Standard</h4>
 <p>The <a href="http://www.w3.org/2008/WebVideo/Fragments/">Media Fragments Working Group</a> of the W3C is currently working on a Recommendion on how to encode Fragments of Resources within so called <a href="http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/">Media Fragments URIs</a>.</p>
 <p>This specification defines how to encode the <a href="http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/#naming-time">Temporal</a>, <a href="http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/#naming-space">Spatial</a>, <a href="http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/#naming-track">Track</a> and <a href="http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/#naming-id">ID</a> dimensions within Document URIs but also defines processing rules (e.g. for Browsers) and the semantics.</p>
@@ -126,8 +122,17 @@
 <h4 id="text_annotations">Text Annotations</h4>
 <p>Text Annotations are Annotations as typically created by NER (Named Entity Recognition) engines. Such Annotations select a part of a Text and assign an type (Person, Organization, Place ...) to that.</p>
 <p>The text selection can be expressed by using an "PrefixPostfixSelector". The type and the confidence of the detected named entity need to be properties of the Annotation class.</p>
+<div class="codehilite"><pre><span class="err">stanbol:TextAnnotation</span> <span class="err">rdfs:subClassOf</span> <span class="err">ao:Annotation</span>
+<span class="err">stanbol:TextAnnotation</span> <span class="err">stanbol:named-entity-type</span> <span class="err">{schema:Perosn,</span> <span class="err">schema:Organization,</span> <span class="err">schema:Place,</span> <span class="err">…}</span>
+</pre></div>
+
+
 <h4 id="entity_annotations">Entity Annotations</h4>
 <p>Entity Annotations are similar to "Qualifier" annotations as defined to the Annotaiton-Ontology. The <em>ao:hasTopic</em> relation is used to link the annotation with the related topic.</p>
+<div class="codehilite"><pre><span class="err">stanbol:EntityAnnotation</span> <span class="err">rdfs:subClassof</span> <span class="err">aot:Qualifier,</span> <span class="err">ao:Annotation</span>
+</pre></div>
+
+
 <h4 id="category_anotations">Category Anotations</h4>
 <p>Category Annotations are typically about the whole or an specific section of an Document. Normal Selectors can be used for defining the categorized Section. If no Selector is present the categorization applies to the whole document. The "Qualifier" annotation could also be used as a base class for categorizations.</p>
 <h3 id="annotation_sets">Annotation Sets</h3>
@@ -145,12 +150,19 @@
 <p>Expressing the same based on the Annotation-Ontology would be possible by</p>
 <ul>
 <li>An Annotation Set that links to the following Annotations (by the <em>ao:item</em> property):</li>
-<li>An TextAnnotaion including the PrefixPostfixSelector selector defining the actual position of the selected text within the document</li>
+<li>An TextAnnotaion uses an stanbol:TextSelector to define the actual selected position of the selected text within the document</li>
 <li>One EntityAnnotation (extends ao:Qualifier) per suggested Entities.</li>
 <li>In addition the Annotation Set also includes metadata such the the Engine that created the suggestions</li>
 </ul>
+<p><strong>OPTIONS</strong></p>
+<ul>
+<li>Allow multiple TextAnnotations: This would allow to suggest the same set of Entities to all TextAnnotations. However it would make it also more difficult to express if a user would except an suggestion for on TextAnnotation but reject the same for an other. In addition Users might even accept different suggestions for different included TextAnnotation. (see also <em>Coreference Suggestions</em>)</li>
+</ul>
 <h4 id="category_suggestions">Category Suggestions</h4>
 <p>Typically categorizations can provide more than a single Category. So grouping such suggestions within an AnnotationSet gives Users the possibility to accept/reject one or more of such suggestions. In addition it would also allow to distinguish sets of categorizations calculated based on disjoint sets of categories (e.g. a categorization based on a UserProfile with a categorization based on general topics or a spatial categorization.)</p>
+<h4 id="coreference_suggestion">Coreference Suggestion</h4>
+<p>This would allow to link several Text Annotations to suggest a co-reference between those two. This kind of AnnotationSet is expected to be used by NLP (Natural Language Processing) frameworks that can detect co-references. It might be also of interest for Engines that suggest Entities but keep an Annotation Context and therefore want to link persons only referred by the given or family name to an other occurrence that uses both.</p>
+<p>The type of the coreference could be captured by an special property of this annotation set type.</p>
   </div>
   
   <div id="footer">