Dear all, The specification is clear about the use of a link header to provide a context for JSON to upgrade to JSON-LD when a document is being retrieved via HTTP GET: http://www.w3.org/TR/json-ld/#interpreting-json-as-json-ld Can, and if so should, this pattern also be available when accepting *requests* via PUT, POST or PATCH where the entity body's content-type is specified to be application/json? In other words, should a well-behaved application also look for a link header on requests giving a context, rather than assuming it will be in the JSON itself? My assumption is Yes, but it would be nice to hear if that is the group consensus :) Many thanks, Rob -- Rob Sanderson Information Standards Advocate Digital Library Systems and Services Stanford, CA 94305Received on Thursday, 5 March 2015 22:35:25 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:44 UTC