You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Marco Brandizi (JIRA)" <ji...@apache.org> on 2017/11/22 21:28:01 UTC
[jira] [Updated] (COMMONSRDF-72) Pointers to containers (Graph/RDF)
[ https://issues.apache.org/jira/browse/COMMONSRDF-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marco Brandizi updated COMMONSRDF-72:
-------------------------------------
Description:
I'm writing a few utilities to ease the use of commons RDF, starting from a library I already have for Jena ([here|https://github.com/marco-brandizi/rdfutils/blob/master/rdfutils-core/src/main/java/info/marcobrandizi/rdfutils/GraphUtils.java] the interface).
It would be quite useful to have container links in interfaces like Graph (Graph.getRDF()) or RDFTerm (RDFTerm.getGraph()). Methods that need to go back to their container to do something (e.g., add some property/value statement to a given IRI object, using the graph it comes from) wouldn't need to receive too many parameters (new triples would be added to subject.getGraph() and new IRI properties would be generated using subject.getGraph().getRDF() ).
Jena uses this approach (e.g., RDFNode has getModel() ).
was:
I'm writing a few utilities to ease the use of commons RDF, starting from a library I already have for Jena ([here|https://github.com/marco-brandizi/rdfutils/blob/master/rdfutils-core/src/main/java/info/marcobrandizi/rdfutils/GraphUtils.java] the interface).
It would be quite useful to have container links in interfaces like Graph (Graph.getRDF()) or RDFTerm (RDFTerm.getGraph()). Methods that need to go back to their container to do something (e.g., add some property/value statement to a given IRI object, using the graph it comes from) wouldn't need to receive too many parameters (new triples would be added to subject.getGraph() and new IRI properties would be generated using subject.getGraph().getRDF() ).
> Pointers to containers (Graph/RDF)
> ----------------------------------
>
> Key: COMMONSRDF-72
> URL: https://issues.apache.org/jira/browse/COMMONSRDF-72
> Project: Apache Commons RDF
> Issue Type: New Feature
> Components: api
> Reporter: Marco Brandizi
>
> I'm writing a few utilities to ease the use of commons RDF, starting from a library I already have for Jena ([here|https://github.com/marco-brandizi/rdfutils/blob/master/rdfutils-core/src/main/java/info/marcobrandizi/rdfutils/GraphUtils.java] the interface).
> It would be quite useful to have container links in interfaces like Graph (Graph.getRDF()) or RDFTerm (RDFTerm.getGraph()). Methods that need to go back to their container to do something (e.g., add some property/value statement to a given IRI object, using the graph it comes from) wouldn't need to receive too many parameters (new triples would be added to subject.getGraph() and new IRI properties would be generated using subject.getGraph().getRDF() ).
> Jena uses this approach (e.g., RDFNode has getModel() ).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)