[
https://issues.apache.org/jira/browse/JENA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284137#comment-16284137
]
ASF GitHub Bot commented on JENA-1430:
--------------------------------------
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/314
1. The two different datasets at TIM and general. The fact that the code
for the general dataset assembler doesn't mention `ja:data` is fine, but
because TIM's assembler does understand `ja:data` and some assembler RDF with
the general dataset type _can_ get shunted to TIM, `ja:data` can end up being
successfully used with well-defined semantics in assembler RDF with the general
dataset type.
This is what I mean by the whole thing having gotten a bit confusing!
:grin:
I agree fully that we need to be able to do what you clearly intend to do
with your example. I just want the the example to look like:
```
<#dataset> a ja:MemoryDataset ;
ja:data "File for the default graph - also data for dataset" ;
ja:namedGraph [ ja:graphName "http://example/graph1";; ja:graph "File for
graph1" ] ;
ja:namedGraph [ ja:graphName "http://example/graph2";; ja:graph "File for
graph2" ] ;
.
```
instead so that TIM and general look the same from the assembler POV.
I don't want to block 3.6.0 on this, so what do you say to your three
points above, plus (after 3.6.0)
4. We gracefully deprecate the use of `ja:data` for anything other than
loading quads into datasets and make TIM's assembler RDF look like the general
dataset assembler RDF modulo the dataset type.
Sound okay?
> Quad loading for in-memory assemblers
> -------------------------------------
>
> Key: JENA-1430
> URL: https://issues.apache.org/jira/browse/JENA-1430
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Reporter: A. Soroka
> Assignee: A. Soroka
> Fix For: Jena 3.6.0
>
>
> In-memory dataset Assemblers should support loading quad files.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
