[ 
https://issues.apache.org/jira/browse/STANBOL-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655476#comment-13655476
 ] 

Rupert Westenthaler commented on STANBOL-351:
---------------------------------------------

There are even other short comings like

* (Text)Selectors (fise:start, fise:end, fise:selected-text) should be an own 
resource. Currently those information are part of the fise:TextAnnotation. This 
makes is necessary to potentially generate different resource for the same 
section. This prevents to use an unique URI for the selected text and use e.g 
the W3C MediaFragment standard for generating URIs
* ContentParts are not represented in the Enhancement Structure. 
EnhancementEngine can not state that is extracted information from the plain 
text version of the parsed PDF document
* The EnhancementEngine.class.getName() value is used as creator instead of the 
URI of the EnhancementEgine in the RESTful API

The downside is that any change in the Enhancement Structure would make current 
clients incompatible. So as long as we do not provide our own client(s) such 
changes would generate a big pressure to all Stanbol users to update their 
clients. So while we can use this issue to discuss and decide on improvements 
to the EnhancementStructure the actual implementation will need some more 
thoughts / discussions and also a solution for backward compatibility. 
                
> Define Stanbol Enhancement Structure
> ------------------------------------
>
>                 Key: STANBOL-351
>                 URL: https://issues.apache.org/jira/browse/STANBOL-351
>             Project: Stanbol
>          Issue Type: Sub-task
>          Components: Enhancer
>            Reporter: Rupert Westenthaler
>              Labels: Enhancementstructure
>
> The Stanbol Enhancement Structure will replace the currently used schema that 
> was defined for FISE (see [1] for details).
> The current plan is to base the Stanbol Enhancement Structure an the 
> Annotation Ontology [2].
> planed steps include 
> 1. to take the current suggestion [3] and align it to the Annotation Ontology.
> 2. initiate an discussion about this proposal on the mailing list and get 
> into contact with the Annotation Ontology community
> 3. reach an agreement on the new schema (discussions -> vote)
> 4. implement utilities that help implementers of enhancement engines to use 
> the new schema
> 5. adapt existing Enhancement Engines to use the new utilities 
> [1] FISE enhancement structure: 
> http://wiki.iks-project.eu/index.php/EnhancementStructure
> [2] Annotation Ontology: http://code.google.com/p/annotation-ontology/
> [3] 
> http://incubator.apache.org/stanbol/docs/trunk/components/enhancer/enhancementstructure.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to