YAML-LD: A Missed Opportunity for a "Lightweight JSON-LD"

Dear JSON-LD Community and Working Group,

Having some experience implementing JSON-LD processor and encountering
issues that many users face, I wanted to share some thoughts on potential
directions for a lightweight alternative.

I see YAML-LD as a missed opportunity, not in syntax, but in design. A
simpler variant of the JSON-LD context, let's say a subset of JSON-LD
context expressivity, could enable straightforward, intuitive syntax,
faster processing, and even better support for streaming. This would make
it more approachable for developers and easier to use in constrained
environments.

Isomorphic mapping would also greatly help ensure contexts can be processed
safely and efficiently.

In practice, most use cases can function without features like scoped or
inline contexts, reverse properties, nesting, etc. Simplifying in this way
could drastically reduce implementation complexity and lower the learning
curve for developers and users.

Please don’t let this opportunity slip by. What is the current value of
YAML-LD? Is it mainly syntactic sugar? I would be very interested to hear
the community’s and working group’s perspective.

Best regards,
Filip
https://www.linkedin.com/in/filipkolarik/