Re: Hydra metadata for non-RDF resources

>> Another option is to negotiate for application/ld+json,
>> in response to which the server can send a 303 to an about resource.
> 
> Would 303 be appropriate here if the first resource is a (binary) information resource?

It seems so:

"A 303 response to a GET request indicates that the origin server does
   not have a representation of the target resource that can be
   transferred by the server over HTTP.  However, the Location field
   value refers to a resource that is descriptive of the target
   resource, such that making a retrieval request on that other resource
   might result in a representation that is useful to recipients without
   implying that it represents the original target resource."
— https://tools.ietf.org/html/rfc7231#section-6.4.4

Best,

Ruben

Received on Wednesday, 11 November 2015 20:39:38 UTC