[
https://issues.apache.org/jira/browse/JENA-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630152#comment-16630152
]
A. Soroka commented on JENA-1608:
---------------------------------
The JSON-LD playground is _not_ authoritative (although of course it is
extremely useful). The specifications are, and Jena relies on
[json-ld-java|https://github.com/jsonld-java/jsonld-java] to implement them. We
can check to see if there is an error here or in how Jena is moving information
to json-ld-java, but the code that is generating JSON-LD is not part of Jena's
codebase so there may be a limited amount we can do.
> 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)
