W3C home > Mailing lists > Public > public-linked-json@w3.org > August 2015

best practices in "reasoning" or "querying" with JSON-LD

From: Herman Bruyninckx <Herman.Bruyninckx@mech.kuleuven.be>
Date: Wed, 26 Aug 2015 07:30:10 +0200 (CEST)
To: public-linked-json@w3.org
cc: Herman Bruyninckx <Herman.Bruyninckx@mech.kuleuven.be>
Message-ID: <alpine.DEB.2.11.1508260719520.24028@pma-15-011>
I am part of a group who is experimenting with using JSON-LD as the formal
language to represent the domain knowledge of robotics; starting with the
mathematical models of robots, to modelling their control and perception
capabiities, as well as the requirements in the tasks the robots are
expected to execute. All of these sub-domains get their own JSON-LD models,
with some structures linking between them.

We are now confronted with how we should best "query" such linked data models,
to represent "reasoning" questions, such as:
  "Which robots can perform this task?"
  "How should the robot move to see that object in the scene?"
  "Where was this robot yesterday at noon?"
  "Which robot has performed a similar task already?"
Etc.

Inside one model, querying reduces to graph search, for which we find quite
some "best practices" out there, such as GraphQL from Facebook, ReQL from
RethinkDB, or Cypher from Neo4J. But our main problem is how to follow the
"@context" links in JSON-LD during queries that have to cross the boundary
between models. We imagine that some sort of context-dependent
"if-then-elses" must be integrated into the query answering, but we have
not yet found any examples of such queries.

We would be grateful to receive pointers to already existing similar
solutions, feedback on the above-mentioned query languages, or just
insights about how we should realise the reasoning we're after.

Thanks!

Best regards,

Herman Bruyninckx
KU Leuven --- TU Eindhoven
Received on Wednesday, 26 August 2015 09:32:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:45 UTC