- From: Reto Gmür <reto@factsmission.com>
- Date: Mon, 2 Apr 2018 12:07:46 +0000
- To: Antoine Zimmermann <antoine.zimmermann@emse.fr>
- CC: Gregg Kellogg <gregg@greggkellogg.net>, Axel Polleres <axel@polleres.net>, "semantic-web@w3.org" <semantic-web@w3.org>
> > On Mar 30, 2018, at 1:29 AM, Antoine Zimmermann > <antoine.zimmermann@emse.fr> wrote: > > > > Axel, > > > > > > Adding a valid @context to an existing JSON file will make a valid JSON-LD > file, and therefore yield an RDF graph, but in all but the simplest cases, it will > not be the graph you want. > > > > From my experience, any non trivial data integration task with JSON and RDF > will require a change in the structure of the JSON tree that cannot be emulated > with any @context construction. > > > > For such cases, you need a more expressive way to map JSON to RDF, either > by programming a dedicated application or using a generic purpose mapping > language, such as RML [1] or SPARQL-Generate [2] (or maybe XSPARQL?). JARQL provides an approach that seems very similar to SPARQL Generate but specific to JSON (like TARQL for CVS). We found this approach of using SPARQL CONSTRUCT queries to convert JSON to the desired RDF to be far easier than RML. Cheers, Reto
Received on Monday, 2 April 2018 12:08:24 UTC