[
https://issues.apache.org/jira/browse/COMMONSRDF-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555231#comment-15555231
]
ASF GitHub Bot commented on COMMONSRDF-35:
------------------------------------------
Github user stain commented on the issue:
https://github.com/apache/incubator-commonsrdf/pull/24
Thanks for the great and thorough review, @ansell! I think this helped get
a better shape of the interfaces.
I used some of the feedback also on the `jena` module, which now also
reduced most of the `UUID` exposure.
RDF4J is interesting because of the difference in semantics around datasets
- I think one value of Commons RDF is that we give a (hopefully) unified view
of semantics between the implementations - and then of course users can
"upgrade" to native RDF4J if they want other semantics or more functionalities.
I'll raise in Jira the remaining issues I am afraid I don't have time to
look at right now, and go ahead to merge this to `master`.
Once merged we can see if we can normalize the converter method names
between the factories.
Then add the integration tests, and roll for a `0.3.0-incubating` release.
Cheers!
> rdf4j integration
> -----------------
>
> Key: COMMONSRDF-35
> URL: https://issues.apache.org/jira/browse/COMMONSRDF-35
> Project: Apache Commons RDF
> Issue Type: New Feature
> Reporter: Stian Soiland-Reyes
> Assignee: Stian Soiland-Reyes
> Labels: integration, rdf4j, sesame
> Fix For: 0.3.0
>
>
> Add a new rdf4j module with implementation for Eclipse rdf4j
> See https://github.com/apache/incubator-commonsrdf/tree/rdf4j/rdf4j
> A legacy sesame branch could then be added by mainly copy/paste and change
> the import
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
