The @vocab prefix is dropped by Jena when parsing JsonLD.
An empty prefix is correctly translated into @vocab during serialization, but
is lost during deserialization.
Below code demonstrates the point.
public static void main(String... args) {
String base = "http://www.ns.com/base/";
Adam,
In the first instance, this seems like something to raise with the
jsonld-java team to find out if that is intentional. Could you open a
discussion issue there?
IIRC empty prefix and the base are mixed up in JSON-LD.
Andy
On 04/01/18 03:34, Adam Jacobs wrote:
The @vocab prefix is
Do you know where jsonld discussions are at?
I'm having trouble finding a mailing list.
From: Andy Seaborne
Sent: Thursday, January 4, 2018 2:34 PM
To: dev@jena.apache.org
Subject: Re: JsonLD @vocab
Adam,
In the first instance, this seems
Andy Seaborne
Sent: Thursday, January 4, 2018 2:34 PM
To: dev@jena.apache.org
Subject: Re: JsonLD @vocab
Adam,
In the first instance, this seems like something to raise with the
jsonld-java team to find out if that is intentional. Could you open a
discussion issue there?
IIRC empty prefix and the
Github user afs commented on the issue:
https://github.com/apache/jena/pull/235
I've pulled this into the work general cleaning up RIOT (PR#234). It'll get
included when that is merged.
Does this complete JENA-1292?
---
If your project is set up for it, you can reply to thi
Github user fpservant commented on the issue:
https://github.com/apache/jena/pull/235
> Does this complete JENA-1292?
yes.
In JENA-1292's discussion I had suggested a way to automatically remove
from the @context the properties that belong to the @vocab, but it is not
GitHub user fpservant opened a pull request:
https://github.com/apache/jena/pull/235
jsonld: @vocab in @context for "" ns prefix
"" prefix are not allowed in jsonld's @context. "" ns prefix defined in a
model were therefore ignored. This pull req
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/235
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enable
