You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I enjoy the flexibility of JSON-LD, but I suspect that a lot of the tooling makes assumptions about structure that we haven't actually documented in the spec. Here are some suggestions that might help provide a simpler encoding format:
Ban @context anywhere except at a top level graph. JSON-LD supports adding @context almost anywhere, but this is confusing and complex to parse
Ban any keyword redefinition. JSON-LD 1.1 allows you to, for example:
I enjoy the flexibility of JSON-LD, but I suspect that a lot of the tooling makes assumptions about structure that we haven't actually documented in the spec. Here are some suggestions that might help provide a simpler encoding format:
@context
anywhere except at a top level graph. JSON-LD supports adding@context
almost anywhere, but this is confusing and complex to parse@id
, such as{"foo": "@id"}
(see 4.2.2.14 in the spec)@type
, such as{"bar": "@type"}
(see 4.2.2.4 in the spec)There are probably some others I haven't thought of yet, but this is a start.
The text was updated successfully, but these errors were encountered: