[ 
https://issues.apache.org/jira/browse/JENA-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rob Vesse closed JENA-675.
--------------------------

    Resolution: Not a Problem

Closing as Not a Problem

I've experimented with the {{StreamRDF}} approach as suggested and it is a much 
cleaner way of doing things since I can re-use the pre-existing 
{{WriterStreamRDFBlocks}} to do much of the work for me

> Add and use a WriterProfile API
> -------------------------------
>
>                 Key: JENA-675
>                 URL: https://issues.apache.org/jira/browse/JENA-675
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: ARQ, RIOT
>    Affects Versions: Jena 2.11.1
>            Reporter: Rob Vesse
>            Assignee: Andy Seaborne
>         Attachments: DevFragWrite.java
>
>
> Currently we have a {{ParserProfile}} which allows specifying certain aspects 
> of input behaviour such as Prologue and Label to Node ID
> However we don't have a corresponding {{WriterProfile}} API, we actually have 
> a class called {{OutputProfile}} but this is never actually used anywhere.
> This would be particularly useful for languages that rely on the 
> {{NodeFormatter}} API where we can find comments such as the following:
> {quote}
> // Replace with a single "OutputPolicy"
> {quote}
> The lack of this API means we don't provide users any ability to do things 
> like control how blank node IDs are allocated.  And existing functionality we 
> do give them like providing a set of namespaces and base URI to use for 
> serialisation needs to be folded into this API.
> I know of two places where this is currently causing issues:
> * In the incoming Hadoop RDF Tools code (JENA-666) many output formats 
> currently mangle the data when outputting blank nodes because they can't 
> share a {{NodeToLabel}} instance over multiple writer runs.
> * In an internal bug at Cray we're seeing a situation where different code 
> paths lead to different presentation of blank nodes and we have no APIs to 
> allow us to control this presentation.



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

Reply via email to