Gregg Kellogg
Gregg Kellogg
This issue was discussed in [today's meeting](https://json-ld.org/minutes/2022-07-20/).
> @ericprud -- Please edit your [#19 (comment)](https://github.com/json-ld/yaml-ld/issues/19#issuecomment-1179545426) to put a code fence around `@context` so that GitHub user doesn't get pinged every time this issue is updated. I took...
The JSON-LD WG discussed this and decided that work can proceed on the editor's draft, so this can be merged.
You could have different entities making the same assertion, but just using different anchor/aliases and verify that it results in only a single triple.
Step 9 of the JSON-LD `expand()` API entry says the following: > Resolve the promise with expanded output transforming expanded output from the [internal representation](https://www.w3.org/TR/json-ld11-api/#dfn-internal-representation) to a JSON serialization. It...
Something for @davidlehn to comment on. Serialization may be handled just outside the API call. Ruby is probably similar. But, the API definitions between JSON-LD and YAML-LD should be symmetric.
Very nice diagram and work plan!
Presumably, YAML-LD should not require anything specific to support -star; it should follow from the generalized support for JSON-LD representation in YAML. Being too explicit would require regular maintenance of...
That certainly is an interesting capability, but also contradicts #8 and other concerns about round-trip ability, at least at the syntactic level.
Looks like a good approach to me.