- From: David Booth <david@dbooth.org>
- Date: Wed, 12 Oct 2016 22:18:32 -0400
- To: public-linked-json@w3.org
First off, thanks to all of you for this thread, and for the renewed interest in JSON-LD Framing! >>>> Gregg >>> Additionally, the Framing algorithm [2] has proven to be important, but work on the specification was never complete, and >>> implementations have moved beyond what was documented in any case. >>>> Markus >> It is certainly handy but I'm not sure there's agreement on what exactly it should be. Initially it was just (or at least mostly) >>> about re-framing an existing graph... I think what a lot of people (myself included) actually want and need is to query a graph and control >>> the serialization of the result. Maybe we should start with a discussion on the role of framing!? I agree that there is often a need to query and then Frame the result, but I'm concerned that bundling both capabilities into one syntax/solution might be a mistake at this point. Framing seems hard enough by itself. Wouldn't it be better to just tackle Framing first, and later look at the possibility of bundling a query capability? David Booth
Received on Thursday, 13 October 2016 02:19:00 UTC