Closed kuzdogan closed 1 year ago
Definitely odd behavior. The Ruby implementation also doesn't seem to honor "@omitGraph": false
. Not sure why it is included when you first open it; @davidlehn may have some idea.
In the case of the Ruby implementation (and I expect pyld and jsonld.js) it never actually looks for the @omitGraph
keyword in the frame, only in either the invocation options, or based on the processorMode which defaults to json-ld1.1
, so assumes "@omitGraph": false
.
Also, looks like a couple of tests for @omitGraph
would be in order.
Actually, looking further at the spec, there is no actual @omitGraph
keyword defined. It is mentioned in the title of example 41, but it is only defined as a processor option, which takes a default value based on the processing mode.
Although the playground behavior is odd, the best correction is an editorial change to the title of Example 41.
It would be useful if the playground allowed this (and other options) to be set.
Summary:
Updated label on Example 41 to use omitGraph
instead of @omitGraph
, as omitGraph
is an API option, not a framing keyword.
Example 41 on the document has the following description:
EXAMPLE 41: Framed library objects with @omitGraph set to false
, which indeed has the correct result output on the document.However, upon clicking on "Open in playground" the frame does not contain the property
@omitGraph
. Interestingly the result is correct, i.e. contains@graph
.The playground has the following frame, note that
@omitGraph
is missing:and the following output:
But if one touches the frame and initiates a recompilation e.g. by adding a space and removing, the output does not have
@graph
anymore. So the following output is generated:I wasn't also able to apply the
@omitGraph
rule by manually adding it to the frame. I might be placing the property in the wrong place but the following frame produced an output without a@graph
.