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
There are no plans to just unreserve that character.
It might get used in the future as a prefix for something like function calls. We only have two reserved chars, they are too precious to just unreserve them :)
While it's understandable to reserve such characters for future needs, it's crucial to recognize the potential of @ as a versatile and potentially language-independent annotation mechanism for both metadata and functions. It's also just too valuable leave it untouched without a clear plan for its use.
YAML-LD initiative, looking forward to express JSON-LD vocabulary in YAML, forces to write something like this:
The @-keywords have to be quoted because the
@
character is reserved.Is there any plan to perhaps unreserve that character? Or perhaps there are particular plans how to use it? Thank you!
The text was updated successfully, but these errors were encountered: