You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jena.apache.org by "A. Soroka (JIRA)" <ji...@apache.org> on 2018/09/27 10:33:00 UTC

[jira] [Commented] (JENA-1608) different output when processing json-ld in the playground and in riot - solved in

    [ https://issues.apache.org/jira/browse/JENA-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630147#comment-16630147 ] 

A. Soroka commented on JENA-1608:
---------------------------------

Not before JSON-LD 1.1. is actually released as a W3C recommendation: [https://www.w3.org/2018/03/jsonld-wg-charter.html]

I am a Jena committer and a member of that working group, so Jena is fully apprised of what is happening there.

> different output when processing json-ld in the playground and in riot - solved in 
> -----------------------------------------------------------------------------------
>
>                 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, Jena 3.8.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)