There's no way (as far as I know) right now to propose a particular context (or other profile information) via HTTP when
accepting JSON-LD:
https://github.com/json-ld/json-ld.org/issues/491
Or is your expectation that Jena would somehow figure out to do what you want unhinted? If you can define a very clear
and specific algorithm by which Jena could conservatively guess at the right way to build a @context, it might be
implementable.
ajs6f
Laura Morales wrote on 10/7/17 10:21 AM:
The problem is that Fuseki (when I select JSON-LD output format) creates a
@context with as many properties as there are URIs. For example
"@context" : {
"name" : {
"@id" : "example.org/vocab/name",
"@type" : ...
},
"surname" : {
"@id" : "example.org/vocab/surname",
"@type" : ...
},
"age" : {
"@id" : "example.org/vocab/age",
"@type" : ...
},
"ex": "example.org/vocab/"
}
whereas all I want is
"@context" : {
"ex": "example.org/vocab/"
}
Sent: Saturday, October 07, 2017 at 12:37 PM
From: "Andy Seaborne" <a...@apache.org>
To: users@jena.apache.org
Subject: Re: Change DESCRIBE @context
The result Model from DESCRIBE has the prefixes of the data and the
query. There can be multiple prefixes for the same URI.
How that gets processed by JSON-LD is another matter and I don't know
the details.
Andy
