Re: Framing and Query

+1 to David. There's a very real need for framing of an existing graph into
a certain shape for serialization.  If we can solve that quickly everyone
would benefit, and then we can move onto exploring the query+serialization
space.

Rob

On Wed, Oct 12, 2016 at 7:18 PM, David Booth <david@dbooth.org> wrote:

> 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
>
>


-- 
Rob Sanderson
Semantic Architect
The Getty Trust
Los Angeles, CA 90049