- From: Karol Szczepański <karol.szczepanski@gmail.com>
- Date: Thu, 26 May 2016 23:11:40 +0200
- To: Asbjørn Ulsberg <asbjorn@ulsberg.no>
- Cc: "Markus Lanthaler" <markus.lanthaler@gmx.net>, "Hydra" <public-hydra@w3.org>
Hi Asbjørn >> 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. If that's event possible to achieve. I'm just worried that temptation of pointing Hydra to one specific direction will make some other being dropped. >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. +10 Best Karol
Received on Saturday, 28 May 2016 14:00:14 UTC