- From: Dave Longley <dlongley@digitalbazaar.com>
- Date: Wed, 30 Mar 2016 10:48:30 -0400
- To: james anderson <james@dydra.com>, Linked JSON <public-linked-json@w3.org>
On 03/29/2016 08:05 AM, james anderson wrote:
> good morning;
>
> the output for test 14 notes includes an object for
>
> "ex:sees": { "@id": "_:b0", "ex:remember_me": "This value should not
> disappear." }
>
> even though the object’s type specification does not conform to that
> of the frame. does this indicate that the passage regarding matched
> subjects should be understood to apply to the top-level sequence
> only. that is, embedded objects are included without regard to type
> constraint - even if the embedded member definition includes its own
> frame definition?
Yes. Framing is a mechanism for organizing a graph into tree structures
according to some filter. It will find nodes from the graph that match
the filter and place them as roots of the output trees. Any other nodes
that are related to the matching nodes will be, by default, embedded
within the matching nodes and appear as leaves in the trees.
You can further explore the behavior of framing (and probably find bugs
for us! :P) by using the json-ld playground:
http://json-ld.org/playground
The embed behavior can be modified using the options described here:
https://github.com/json-ld/json-ld.org/issues/377
The framing spec is sorely out-of-date and does not include options like
those specified in that issue.
--
Dave Longley
CTO
Digital Bazaar, Inc.
http://digitalbazaar.com
Received on Wednesday, 30 March 2016 14:48:54 UTC