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 was pleased to learn about this effort to facilitate encoding of LD with YAML... i enjoy writing yaml in my editor. what i don't enjoy is making special syntactic adjustments because of special symbols introduced that require quotes around keys like '@context' or '@graph'. why not just use context: or graph: ? make these reserved symbols, and keep the writing simple.
The text was updated successfully, but these errors were encountered:
After discussion, the current idea is for a Best Practices document to encourage using a Convenience Context that defines the bare-word equivalents of the @ keywords.
There are a number of other vocabularies (e.g., schema.org) that define equivalents. In general because of the potential for stepping on another namespace, we cannot categorically just do away with @ keywords, in either JSON-LD or YAML-LD.
I was pleased to learn about this effort to facilitate encoding of LD with YAML... i enjoy writing yaml in my editor. what i don't enjoy is making special syntactic adjustments because of special symbols introduced that require quotes around keys like '@context' or '@graph'. why not just use context: or graph: ? make these reserved symbols, and keep the writing simple.
The text was updated successfully, but these errors were encountered: