Ability to re-route JSON-LD "@context" within EDG?

[Fan Li]

I understand that it is possible to define an external graph URI for a given ontology so that owl:import will be re-routed accordingly. Is there a similar feature to deal with JSON-LD @context? Thanks!

[Holger Knublauch]

No there is no such feature, yet. As a paying customer you could use the TSM system to enter a feature request where we could discuss details, starting with your use case. I am not familiar with the capabilities of the JSON-LD writer bundled with Jena that we are using, to judge how much is possible.

Regards,
Holger

On 7/08/2019 22:04, Fan Li wrote:

I understand that it is possible to define an external graph URI for a given ontology so that owl:import will be re-routed accordingly. Is there a similar feature to deal with JSON-LD @context? Thanks!

--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/0f8ddbac-d4a8-4aaa-8bbb-629066f52c21%40googlegroups.com.

[Rob Atkinson]

+1 to this.

also, AFAICT there seem no reason we couldnt also add a JSON-schema. 

Both of these could be derived from shapes for a graph - and i think each exported graph would need some mix of the following:

1) a context derived from the graphQL schema used in the case of a graphQL export

2) a context derived from the EDG project type (i.e. any known, assumed  available context such as RDF, OWL, SHACL etc) 

3) a context derived from imports of graphs containing SHACL shapes

4) a context specified by graph metadata (this graph conforms to the profile X)

in general these can be just annotations at the top of vanilla JSON - but JSON-LD with canonical object identifiers added  is still a good thing to consider.

On Thursday, 8 August 2019 09:04:07 UTC+10, Holger Knublauch wrote:

No there is no such feature, yet. As a paying customer you could use the TSM system to enter a feature request where we could discuss details, starting with your use case. I am not familiar with the capabilities of the JSON-LD writer bundled with Jena that we are using, to judge how much is possible.

Regards,
Holger

On 7/08/2019 22:04, Fan Li wrote:

I understand that it is possible to define an external graph URI for a given ontology so that owl:import will be re-routed accordingly. Is there a similar feature to deal with JSON-LD @context? Thanks!

--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to topbrai...@googlegroups.com.

[Fan Li]

Holger, thanks. Currently I only have one use case: when I import a JSON-LD document in EDG, the import will fail as it cannot resolve the "@context" uri. It would be convenient if I can store the context document in EDG and have EDG automatically re-route like how it behaves for owl:import.

If this makes sense, I am happy to submit a feature request. Or if there is an alternative please let me know.

[Fan Li]

Rob - I definitely support the idea of generating JSON-Schema based on shapes, if that is what you mean and feasible.

On Wednesday, August 7, 2019 at 9:55:06 PM UTC-4, Rob Atkinson wrote: