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
It is possible to have multiple JSON-LD contexts applied to exactly the same model to generate different serializations with the same structure. Compare the CG's context with the current WG's context, for example. The protocol should specify how to request the annotation using a particular context. For Create and Update this is not relevant as the context can be part of the JSON-LD payload of the request.
Proposal:
There is a recommended best practice of using profile URIs [1] from RFC 7284 [2]. The WG would need to register a profile for the base context and frame/structure, and further communities would then register their own profiles to specify alternatives. The registered profile URI is then carried in the Link header [3] on the HTTP request/response with a rel of 'profile' [4]
It is possible to have multiple JSON-LD contexts applied to exactly the same model to generate different serializations with the same structure. Compare the CG's context with the current WG's context, for example. The protocol should specify how to request the annotation using a particular context. For Create and Update this is not relevant as the context can be part of the JSON-LD payload of the request.
Proposal:
There is a recommended best practice of using profile URIs [1] from RFC 7284 [2]. The WG would need to register a profile for the base context and frame/structure, and further communities would then register their own profiles to specify alternatives. The registered profile URI is then carried in the Link header [3] on the HTTP request/response with a rel of 'profile' [4]
Thus the header might look like:
[1] http://www.iana.org/assignments/profile-uris/profile-uris.xhtml
[2] http://tools.ietf.org/html/rfc7284
[3] http://tools.ietf.org/html/rfc5988
[4] http://tools.ietf.org/html/rfc6906
The text was updated successfully, but these errors were encountered: