- From: Asbjørn Ulsberg <asbjorn@ulsberg.no>
- Date: Thu, 26 May 2016 22:53:37 +0200
- To: Karol Szczepański <karol.szczepanski@gmail.com>
- Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, Hydra <public-hydra@w3.org>
2016-05-26 22:26 GMT+02:00 Karol Szczepański <karol.szczepanski@gmail.com>: > It's not like nobody tried to apply Hydra to some working piece of code on > both server and client side, thus let's not jump into another extremae of > creating the "One and Only" Hydra compliant client. While I agree that it shouldn't -- and probably can't, nor won't -- exist only one Hydra client, I do think it's crucial for Hydra's success to provide one reference implementation that covers most, if not all of Hydra's functionality, so it's easy for server implementers to write Hydra-compliant APIs. On the opposite side, I think it's important to have a full-blown Hydra-compliant server API as well, so client implementers have something they can exercise their clients against. On top of this, there should be automated test suites that can be executed against both client and API implementations, so it's easy for implementers to figure out where their implementations are lacking. -- Asbjørn Ulsberg -=|=- asbjorn@ulsberg.no «He's a loathsome offensive brute, yet I can't look away»
Received on Thursday, 26 May 2016 20:54:05 UTC