Re: the necessity of describing responses in-band

Hi Ruben
 
>
> In an ideal situation, the headers (besides Content-Type) should be the same
> regardless of the body. Putting things inside of the body for HTML,
> but in the headers for RDF, just seems a clumsy and unnecessary workaround.
 
For HTML would also be fair to say that much of the metadata is put in the
<head> element of the message body.
 
Speaking of HTML I'm pretty interested in these new HTML Imports and see these
as a potentially neat way put pull out the surrounding context (headers,
footers, navigation) into separate resources in the same way that one doesn't
tend to embed the base64 of an image into the HTML representation.
This reduces the 'boilerplate' that need to be sent in each resource and makes
it easier to track changes to, for example, the site navigation as a separate
'thing'.
 
Makes sense to me to apply similar approach to an API.
Moreover should be easy to do with RDF.

>
> Best,
>
> Ruben
 
John
 
p.s. in your first Turtle snippet of the post, why not go the whole hog and make
the item URIs into blank nodes ;-)

Received on Tuesday, 6 October 2015 15:58:59 UTC