Pierre-Antoine Champin

@AdamSobieski @spaceribs the [Media WG](https://www.w3.org/media-wg/) is currently being rechartered. Have a look at the [proposed charter](https://www.w3.org/2021/05/charter-media-wg.html), I think some of the deliverables will address several of the points raised above.

> Slight concern might be that the predicates would then be relative to the document themselves, so therefore, no two predicates would in theory match, unless using inferencing I consider...

Your example answers the original question, but in a very different way than @gkellogg's example [above](https://github.com/json-ld/json-ld.org/issues/719#issuecomment-632888397). More precisely, running your example through [toRdf](https://www.w3.org/TR/json-ld11-api/#dom-jsonldprocessor-tordf) produces (among others), the following triples, which...

> In my particular use case, I wanted objects with references to BOTH ancestors and descendants, but `@reverse` discarded the inverse predicate. Indeed. JSON-LD's expansion maps every JSON key to...

From what I remember of our Berlin discussion, we also considered a new JSON-LD keyword `@object` (working title), which would allow to express the following Turtle* ``` ex:certainty 0.9 ....

Darn, I was not entirely sure it was supposed to work, but I was too lazy to go back to the algorithm, and just checked on the Ruby distiller, which...

For me the problem was a missing space after title: ``` --- title:I forgot the space after the colon date: 2020-09-14 15:30 tags: [foo] --- ``` Now that I know...

Comments: * this could of course be optionally enabled/disabled in the settings * the colon (`:`) character is just a suggestion here; probably, this could also be customizable

I stumbled upon this old issue because I had the same problem. I was disappointed to find no solution here, but [Stackoverflow had one](https://stackoverflow.com/a/58146865/1235487). The cause (at least for me)...

I also have the issue, with the same config as @jontis