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 think to be able to make JSON-LD forward-compatible we shouldn't allow terms that start with an @. We don't necessarily have to throw an exception at this point, but we make it clear that any term starting with an @ might be used in a future version of JSON-LD. If we don't do that, we won't be able to introduce new keywords without breaking stuff in the future.
RESOLVED: Terms MAY be defined as any valid JSON string. Terms starting with an '@' character SHOULD NOT be used as they may create forward-compatibility issues.
I think to be able to make JSON-LD forward-compatible we shouldn't allow terms that start with an
@
. We don't necessarily have to throw an exception at this point, but we make it clear that any term starting with an@
might be used in a future version of JSON-LD. If we don't do that, we won't be able to introduce new keywords without breaking stuff in the future.This came up while discussing fa8a035
The text was updated successfully, but these errors were encountered: