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
IMHO you shouldn't bundle the schema.org context but just refer to it.
That way clients can cache the schema context and your context separately, which will provide better opportunities for caching.
If bundled, you risk outdated schema context, or need for more often caching (when either of the two changes).
Thanks, we bundle the schema.org context because we add some additional requirements to some of the schema.org properties. For instance the schema.org context doesn't specify if the value of some properties should be a @list or @set but for some properties we do (e.g here). I guess we could still just link to the schema.org context and overwrite those property definitions right after.
IMHO you shouldn't bundle the schema.org context but just refer to it.
That way clients can cache the schema context and your context separately, which will provide better opportunities for caching.
If bundled, you risk outdated schema context, or need for more often caching (when either of the two changes).
(related to #24)
The text was updated successfully, but these errors were encountered: