Roberto Polli

@anatoly-scherbakov I think it's worth discussing the above points in a dedicated document providing considerations about context independently on the serialization format.

Yes, something unrelated to YAML and instead, related to how managing contexts in different kinds of ecosystems.

> Wouldn't it be nice to "construct a smooth path" so you don't need to cross any boundaries, and can think more about your data model rather than the various...

In general, I think that this topic goes beyond the goal of yaml-ld and should probably addressed in JSON Schema and JSON-LD as a separate project (E.g. json-ld/restapi-ld-keywords).

@VladimirAlexiev This presentation I hope to present at the next APISpec explains my view on JSON-LD vs JSON Schema https://docs.google.com/presentation/d/175ZFBXkhaawtvD97lU7II9-G2R6_a6XAMo82_BaYr4c/edit#slide=id.g14b35179850_0_8 It's not a trivial explanation, though. I think a solution...

1. Why should we replace "@" with "$" ? 2. not sure the doc above is correct YAML

> because @-keywords need to be in quotes I think quoting is less problematic than changing parsers :) For example, the following document is both a valid YAML and JSON...

@VladimirAlexiev I am not sure that YAML does not already provide something like that. I am not sure that's the most readable form, but did you ask to YAML folks?...

@VladimirAlexiev YAML repo or https://app.element.io/#/room/#chat:yaml.io After a brief investigation, I understood there's no easy fix for that - at least if we want to include aliases/anchors.

> YAML C14N ... a spec to reference :+1: I think that the c14n discussion can be managed in the YAML community (e.g. via element). I think there's some interest...