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

Rupert Westenthaler commented on STANBOL-1234:
----------------------------------------------

While this would allow to use Sesame to serialize TripleCollections (e.g. for 
Enhancement Requests) it would still not solve this issue. Here the problem is 
with the JAX-RS writer for Entityhub Representation. Changes in this Issue do 
allow the trunk version to use Representation implementation specific writers. 

To give some examples:

1. if e.g. a Clerezza backed Representation implementation is serialized to a 
RDF format the Clerezza serializer is used.  The Serializer can directly access 
the backing TripleCollection and serialize it

2. If a Sesmae Model backed  Representation is serialized the Sesame specific 
serializer would directly access the Sesame Model and serialize it

3. In the case of the in-memory Representation the data of the Representation 
need to first to be converted to RDF. In that case both the Sesmae and Clerezza 
serializer could be used. In this case the one with the higher service.ranking 
would be used.

Adding Sesame Serializers to Clerezza will not help because for ex. (2) one 
would still need to convert the RDF data in the Sesame Model to a Clerezza 
TripleCollection.

But again for the Stanbol Enhancer this would for sure be a nice addition.

> Allow the Entityhub to use native Sesame RDF serializers
> --------------------------------------------------------
>
>                 Key: STANBOL-1234
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1234
>             Project: Stanbol
>          Issue Type: Sub-task
>          Components: Entityhub
>            Reporter: Rupert Westenthaler
>            Assignee: Rupert Westenthaler
>             Fix For: 1.0.0
>
>
> With the current available serializes instances of the Sesame based Entityhub 
> Model implementation would be (1) converted to the Clerezza based Model 
> instance and (2) get serialized by using the Jena serializes via the 
> Clerezza/Jena model adapter.
> This will 
> * improve/extend the Entityhub to select Serializer based on the native type 
> of the used model
> * provide Serializer for Sesame model implementation
> It needs also to be checked if this extension can be back ported to 0.12.0 as 
> this branch uses a considerable different architecture.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to