You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Didac (Jira)" <ji...@apache.org> on 2020/09/02 13:09:00 UTC
[jira] [Updated] (JENA-1959) Json-LD to Rdf
[ https://issues.apache.org/jira/browse/JENA-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Didac updated JENA-1959:
------------------------
Description:
When converting from DataSet to JSON-LD there is a way to override the JsonLDOptions (provided by Json-LD Java) as described [in this example|https://github.com/apache/jena/blob/master/jena-arq/src-examples/arq/examples/riot/Ex_WriteJsonLD.java#L291]
However I don't see the same being used for the other conversion (JSON-LD document to DataSet). From the [following code line|https://github.com/apache/jena/blob/bfce1741cb12f9cf544235d32fba6598bc7341b5/jena-arq/src/main/java/org/apache/jena/riot/lang/JsonLDReader.java#L157], the JsonLdOptions gets created right there instead of being read from the Jena Context object. It seems just the base field gets read from the Context.
Why there isn't coherence between the way JsonLdOptions can be provided in both conversions?
JsonLdOptions can be used for things like [providing a DocumentLoader|https://github.com/jsonld-java/jsonld-java#loading-contexts-from-a-string], which will affect the conversion Json-LD -> DataSet
was:
When converting from DataSet to JSON-LD there is a way to override the JsonLDOptions (provided by Json-LD Java) as described [in this example|[https://github.com/apache/jena/blob/master/jena-arq/src-examples/arq/examples/riot/Ex_WriteJsonLD.java#L291]]
However I don't see the same being used for the other conversion (JSON-LD document to DataSet). From the [following code line|[https://github.com/apache/jena/blob/bfce1741cb12f9cf544235d32fba6598bc7341b5/jena-arq/src/main/java/org/apache/jena/riot/lang/JsonLDReader.java#L157]], the JsonLdOptions gets created right there instead of being read from the Jena Context object. It seems just the base field gets read from the Context.
Why there isn't coherence between the way JsonLdOptions can be provided in both conversions?
JsonLdOptions can be used for things like [providing a DocumentLoader|[https://github.com/jsonld-java/jsonld-java#loading-contexts-from-a-string]], which will affect the conversion Json-LD -> DataSet
> Json-LD to Rdf
> --------------
>
> Key: JENA-1959
> URL: https://issues.apache.org/jira/browse/JENA-1959
> Project: Apache Jena
> Issue Type: Wish
> Components: RIOT
> Reporter: Didac
> Priority: Major
>
> When converting from DataSet to JSON-LD there is a way to override the JsonLDOptions (provided by Json-LD Java) as described [in this example|https://github.com/apache/jena/blob/master/jena-arq/src-examples/arq/examples/riot/Ex_WriteJsonLD.java#L291]
> However I don't see the same being used for the other conversion (JSON-LD document to DataSet). From the [following code line|https://github.com/apache/jena/blob/bfce1741cb12f9cf544235d32fba6598bc7341b5/jena-arq/src/main/java/org/apache/jena/riot/lang/JsonLDReader.java#L157], the JsonLdOptions gets created right there instead of being read from the Jena Context object. It seems just the base field gets read from the Context.
> Why there isn't coherence between the way JsonLdOptions can be provided in both conversions?
> JsonLdOptions can be used for things like [providing a DocumentLoader|https://github.com/jsonld-java/jsonld-java#loading-contexts-from-a-string], which will affect the conversion Json-LD -> DataSet
--
This message was sent by Atlassian Jira
(v8.3.4#803005)