[
https://issues.apache.org/jira/browse/JENA-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282066#comment-16282066
]
ASF GitHub Bot commented on JENA-1430:
--------------------------------------
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/314
I'm saying that `ja:data` is now used for loading quads into two different
kinds of datasets, but loading triples into only one. That's confusing at best.
I want to make it clearer by getting rid of the second use, because we already
have `ja:graph`, and then what about `ja:content`? But I'm happy to hear other
ways to clarify the semantics-- I just think that we've made things more
powerful but more confusing with this PR. I want to keep the power (load quads
easily, which we just did) while not making it harder to understand how to
build assembler RDF (which I think we just did).
Re: deprecation: we can deprecate with comments and by throwing warnings
from inside the assembler code. And again, we have good reason (the mistake in
the docs that no one noticed enough to complain about) to think that it won't
be too disruptive.
> 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)
