Re: versioning from László Lajos Jánszky on 2014-09-19 (public-hydra@w3.org from September 2014)

From: László Lajos Jánszky <laszlo.janszky@gmail.com>
Date: Sat, 20 Sep 2014 01:31:34 +0200
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Cc: "public-hydra@w3.org" <public-hydra@w3.org>
Message-ID: <CA+=RcCpt5zD7saumiKNR47hBsUUQoai0YpSbtW32hC4r+9MEEQ@mail.gmail.com>

> Can you think of an use case that can't be addressed by these mechanisms?

HTTP headers typically break if you want to describe an embedded
resource with them. So for example if you represent an embedded
resource along with a PUT or PATCH link, then the etag header is
related to the original resource and not to the embedded resource. So
you cannot extract the etag of the embedded resource from the headers,
you have to send it in the message body. And since it is in the
message body, it has to be annotated with metadata.

Received on Friday, 19 September 2014 23:32:01 UTC