Author: florent
Date: Sun Dec 11 22:14:51 2011
New Revision: 1213091
URL: http://svn.apache.org/viewvc?rev=1213091&view=rev
Log:
little typo corrections. One to confirm is : if a user would except an
suggestion ==> if a user would accept a suggestion
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/ses_annotationontology.mdtext
Modified:
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/ses_annotationontology.mdtext
URL:
http://svn.apache.org/viewvc/incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/ses_annotationontology.mdtext?rev=1213091&r1=1213090&r2=1213091&view=diff
==============================================================================
---
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/ses_annotationontology.mdtext
(original)
+++
incubator/stanbol/site/trunk/content/stanbol/docs/trunk/enhancer/ses_annotationontology.mdtext
Sun Dec 11 22:14:51 2011
@@ -43,13 +43,13 @@ The following Figure gives an overview a
> Image Credit: Annotation-Ontology
> [Link](http://annotation-ontology.googlecode.com/svn/trunk/images/Document%20Annotation%20-%20AO%20Annotation%20Ontology%20-%20by%20Paolo%20Ciccarese.png)
-## Stanbol Enhancement Strucutre
+## Stanbol Enhancement Structure
-The following sections describe how the Stanbol Enhancement Structure can
utilize the Annotation-Ontology to encode knowledge extracted form analyzed
Content Items.
+The following sections describe how the Stanbol Enhancement Structure can
utilize the Annotation-Ontology to encode knowledge extracted from analyzed
Content Items.
### ContentItems
-Within the FISE Enhancement Structure the enhanced ContentItems where only
referenced by the **fise:extracted-form** property. There was no specification
on how to further define properties of the ContentItem. The Annotation-Ontology
defines a much richer vocabulary for that.
+Within the FISE Enhancement Structure the enhanced ContentItems where only
referenced by the **fise:extracted-from** property. There was no specification
on how to further define properties of the ContentItem. The Annotation-Ontology
defines a much richer vocabulary for that.
First an most important the Annotation-Ontology distinguished between the:
@@ -70,9 +70,9 @@ The possibility to distinguish between t
### Content Selectors
-The FISE Enhancement Structure defined a single "Content Selector" the *FISE
Text Annotation*. The Annotation-Ontology uses a much richer Structure that
even provides the possibility to extensions for defining specific selections
different content types.
+The FISE Enhancement Structure defined a single "Content Selector" the *FISE
Text Annotation*. The Annotation-Ontology uses a much richer Structure that
even provides the possibility to extensions for defining specific selections on
different content types.
-With the Annotation-Ontology each Selector can link to both a the *Annotated
Document* and the *Source Document*. In the following an Example for an Image
Selection
+With the Annotation-Ontology each Selector can link to both the *Annotated
Document* and the *Source Document*. In the following an Example for an Image
Selection
> 
@@ -80,15 +80,15 @@ With the Annotation-Ontology each Select
#### Text Selectors
-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 ->
Seletor" model or the Annotation-Ontology all Annotation related properties of
the FISE TextAnnotation must be separated from the properties describing the
selection.
+The currently used FISE TextAnnotation differs from text selects of the
Annotation-Ontology mainly in that it defines both the actual annotation AND
the selection within the text. Therefore when adopting the "Annotation ->
Selector" model or the Annotation-Ontology all Annotation related properties of
the FISE TextAnnotation must be separated from the properties describing the
selection.
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.
-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".
+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".
#### Multi Media Selectors and the Media Fragments Standard
-The [Media Fragments Working
Group](http://www.w3.org/2008/WebVideo/Fragments/) of the W3C is currently
working on a Recommendion on how to encode Fragments of Resources within so
called [Media Fragments
URIs](http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/).
+The [Media Fragments Working
Group](http://www.w3.org/2008/WebVideo/Fragments/) of the W3C is currently
working on a Recommendation on how to encode Fragments of Resources within so
called [Media Fragments
URIs](http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/).
This specification defines how to encode the
[Temporal](http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/#naming-time),
[Spatial](http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/#naming-space),
[Track](http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/#naming-track)
and
[ID](http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-spec/#naming-id)
dimensions within Document URIs but also defines processing rules (e.g. for
Browsers) and the semantics.
@@ -104,11 +104,11 @@ Annotations as defined by the Annotation
* The Annotation-Resource may be linked to an Selector with the **ao:context**
property. If no such link is present the Annotation-Resource is about the whole
Document. It is also possible to link multiple Selectors with an annotation.
* Each Annotation-Resource MUST BE linked to the *Annotated Document* by using
the **ao:annotatesResource** property. The *Source Document* can be referenced
by using the **ao:onSourceDocument**. It is also possible to link multiple
Documents with an annotation.
-The following sub-sections will provide an overview how Text Annotations ,
Entity Annotations and Category Annotations as used by Stanbol can be expressed
using the Annotation-Ontology
+The following sub-sections will provide an overview how Text Annotations,
Entity Annotations and Category Annotations as used by Stanbol can be expressed
using the Annotation-Ontology
#### Text Annotations
-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.
+Text Annotations are Annotations as typically created by NER (Named Entity
Recognition) engines. Such Annotations select a part of a Text and assign a
type (Person, Organization, Place ...) to that.
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.
@@ -150,17 +150,17 @@ With the FISE Enhancement Structure this
Expressing the same based on the Annotation-Ontology would be possible by
* An Annotation Set that links to the following Annotations (by the *ao:item*
property):
-* An TextAnnotaion uses an stanbol:TextSelector to define the actual selected
position of the selected text within the document
+* A TextAnnotation uses a stanbol:TextSelector to define the actual selected
position of the selected text within the document
* One EntityAnnotation (extends ao:Qualifier) per suggested Entities.
* In addition the Annotation Set also includes metadata such the the Engine
that created the suggestions
**OPTIONS**
-* 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 *Coreference
Suggestions*)
+* 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 accept a suggestion for one TextAnnotation but
reject the same for an other. In addition Users might even accept different
suggestions for different included TextAnnotation. (see also *Coreference
Suggestions*)
#### Category Suggestions
-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.)
+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).
#### Coreference Suggestion
