You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "andrew u frank (JIRA)" <ji...@apache.org> on 2018/09/27 09:43:00 UTC
[jira] [Commented] (JENA-1608) different output when processing
json-ld in the playground and in riot
[ https://issues.apache.org/jira/browse/JENA-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630068#comment-16630068 ]
andrew u frank commented on JENA-1608:
--------------------------------------
I found that the problem is solved in 3.8.0 - sorry to bother and thank you for json-ld support! any plans to switch to json-ld 1.1?
> different output when processing json-ld in the playground and in riot
> ----------------------------------------------------------------------
>
> Key: JENA-1608
> URL: https://issues.apache.org/jira/browse/JENA-1608
> Project: Apache Jena
> Issue Type: Bug
> Components: RIOT
> Affects Versions: Jena 3.6.0
> Reporter: andrew u frank
> Priority: Minor
> Labels: newbie
> Attachments: problem.jsonld, problem.ttl, problem_output_playground.txt
>
>
> I have the json-ld document [^problem.jsonld] processed on the json-ld playground (which I assume is authoritative) and get the result [^problem_output_playground.txt]. if I process the same file with RIOT the result is different, namely [^problem.ttl].
> The difference is simply that RIOT does not include the rdf-objects which are not using a blank node as identifier. If a line
> "@base": "http://gerastree.at/lit_2014#"
> is added to the context, the output seems to conform to what is produced by the playground.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)