[
https://issues.apache.org/jira/browse/JENA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178222#comment-13178222
]
Andy Seaborne commented on JENA-182:
------------------------------------
Laurent,
I agree - two (or more?) different writers. For old (=current) Tutle writing,
it tries to reuse the same code but this is actually inefficient because
writing in blocks of same-subject triples does not require any pre-processing
of the graph to be written.
(new, mostly finished, untested) TurtleWriterBlocks is this style - it's a
streaming write of the data with no special list of nested object forms.
>From the point of view efficiency, using the proto-Trig with
>TurtleWriterBlocks might be interesting to you. TriGWriter can choose the
>Turtle writer. The prefixes need sorting out.
A non-TriG way of transferring datasets is to use BindingIO streams. These
compress by avoiding sending terms in the previous row.
> Add TriG support to RiotWriter
> ------------------------------
>
> Key: JENA-182
> URL: https://issues.apache.org/jira/browse/JENA-182
> Project: Jena
> Issue Type: New Feature
> Components: RIOT
> Reporter: Paolo Castagna
> Priority: Minor
> Labels: trig
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> RIOT has the ability to parse TriG
> (http://www4.wiwiss.fu-berlin.de/bizer/TriG/) files but not to serialize RDF
> datasets in that format.
> When working with named graphs people would probably find it easier to look
> at TriG files rather than N-Quads (same as Turtle and N-Triples).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
