- From: Dave Longley <dlongley@digitalbazaar.com>
- Date: Tue, 11 Oct 2016 11:19:08 -0400
- To: Gregg Kellogg <gregg@greggkellogg.net>, George Svarovsky <gsvarovsky@idbs.com>
- Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, Linked JSON <public-linked-json@w3.org>
On 10/10/2016 06:50 PM, Gregg Kellogg wrote: >> On Oct 10, 2016, at 2:32 AM, George Svarovsky <gsvarovsky@idbs.com> wrote: >> >> Hi Markus & Gregg & everyone > > Hi George, glad to have you! Please consider joining the Community Group [1], which simplifies IP issues. > >> I've worked with JSON-LD since 2013, for IDBS internal POC work, including prototype APIs and indexing in elasticsearch. I'd like to make it the lingua franca of our foundational APIs going forward. So although I'm not currently a 'heavy user', I'd like to become one! and I'd be very happy to be involved in the new wave of progress. >> >> I have a particular interest in framing, and I concur with Markus that what I actually want is (some degree of) graph query. I have some thoughts, which I'll write out in a new thread. > > I think there are several ways we could go: > > 1) Improve framing based on the existing algorithms which provide some degree of manipulating and limiting the framed data based on existing relationships. > 2) Consider a way to include a variable syntax, and how this might be used for both matching and constructing data > 3) Consider the implications of using SPARQL via de-serialization from JSON-LD to the RDF data model, performing a SPARQL query operation, and re-serializing back to JSON-LD and framing using some variation of the existing algorithms. > > I’m certainly interested in hearing suggestions on other approaches, along with some use cases/examples. I don't have any use cases/examples at the moment, but wanted to mention that some sort of compatibility with GraphQL may be quite desirable. -- Dave Longley CTO Digital Bazaar, Inc. http://digitalbazaar.com
Received on Tuesday, 11 October 2016 15:19:41 UTC