- From: László Lajos Jánszky <laszlo.janszky@gmail.com>
- Date: Fri, 19 Sep 2014 12:51:50 +0200
- To: "McBennett, Pat" <McBennettP@dnb.com>
- Cc: Ruben Verborgh <ruben.verborgh@ugent.be>, "public-hydra@w3.org" <public-hydra@w3.org>
> So should the spec somehow allude to the point that the concept of > versioning needs to be reconsidered when using hypermedia (since > developers (or at least the good ones!) will naturally ask 'how does API > versioning work with Hydra?')...? Good point. Actually we can version 2 things: the implementation and the semantics (for example an application specific vocab). Versioning the implementation might be needed for cache revalidation purposes, but I guess that can be solved different ways. Versioning vocabs is an interesting question I think. For example if non-backward compatible versions of a vocab use the same IRIs, then clients understanding the v1 vocab will break when they meet a service supporting the v2 vocab. What's your opinion about resource versioning?
Received on Friday, 19 September 2014 10:52:17 UTC