From 85cdd64da7c6fe39cf547ead975fcca6bce67694 Mon Sep 17 00:00:00 2001
From: Pierre-Antoine Champin application/ld+json
representation. The profile
parameter MAY be used by
clients to express their preferences in the content negotiation process.
If the profile parameter is given, a server SHOULD return a document that
- honors the profiles in the list which are recognized by the server.
+ honors the profiles in the list which it recognizes,
+ and MUST ignore the profiles in the list which it does not recognize.
It is RECOMMENDED that profile URIs are dereferenceable and provide
useful documentation at that URI. For more information and background
please refer to [[RFC6906]].
Other specifications may publish additional profile parameter - URIs with their own defined sematics.
+ URIs with their own defined sematics. + However, all URIs starting withhttp://www.w3.org/ns/json-ld
+ are reserved for future use by JSON-LD specifications.
When used as a media type parameter [[RFC4288]]
in an HTTP Accept header [[RFC7231]],
From 6ea443ed780650e4330c39b8c1c6c798000bdd39 Mon Sep 17 00:00:00 2001
From: Pierre-Antoine Champin Other specifications may publish additional profile parameter
- URIs with their own defined sematics.
- However, all URIs starting with All other URIs starting with Other specifications may publish additional profile parameter
+ URIs with their own defined sematics.
When used as a media type parameter [[RFC4288]]
in an HTTP Accept header [[RFC7231]],
application/ld+json
http://www.w3.org/ns/json-ld#framed
http://www.w3.org/ns/json-ld
+ http://www.w3.org/ns/json-ld
are reserved for future use by JSON-LD specifications.