- From: Dietrich Schulten <ds@escalon.de>
- Date: Sat, 24 Jan 2015 13:32:39 +0100
- To: public-hydra@w3.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Ruben, last year's program shows me that my first idea was not appropriate. I had the idea that we could have sort of a challenge to actually code a hydra client that can handle two independently created simple hydra apis to achieve the same thing, all built within one day. An experiment, not a research paper :) But now I see from last year that the format is a 30 min. talk. So I think what I could offer is my experience and lessons learned while building and using hydra-java. I'll try to come up with a suitable paper in time. Do I understand correctly, that a three-page "vision/demo/poster/breaking research" paper would do for the moment, as long as it outlines the lessons learned? Best regards, Dietrich Am 15.01.2015 um 10:26 schrieb Ruben Verborgh: > Hi Dietrich, > >> I have never been to that congress and I wonder if it makes >> sense to have a workshop in the sense of getting some working >> code. > > Working code is interesting as long as it illustrates a > (relatively) novel technique or method. For instance, a paper that > reminded me of Hydra, and also is based on “working code”, is this > one: > > Pragmatic Hypermedia: Creating a Generic, Self-Inflating API > Client for Production Use by Pete Gamache > http://ws-rest.org/2014/sites/default/files/wsrest2014_submission_6.pdf > > > It is based on code, both the concepts behind it transcend the > code itself. > > For inspiration in general, do check out last year's papers: > http://ws-rest.org/2014/program > >> What if I have in mind is to work together one day to solve a >> challenge that shows the power of hydra, like "use existing >> libraries to implement a client that interoperates with two >> different hydra apis/independently implement two simple apis >> with hydra" for something that is not covered by existing >> media-types, i.e. not a blog post. > > That seems very relevant! > >> Goal: prove what works well/identify weaknesses. > > And that is *exactly* what we are looking for: lessons learned. > >> Rest Fest has done something similar for alps a while ago. > > Yeah. The main difference is that WS-REST is at a scientific > conference; that doesn't mean your paper has to contain formulas > or anything ;-) it mostly means that we use a more > structured/method-driven approach. Browse through last year's > paper to have an idea. > > Best, > > Ruben > - -- Dietrich Schulten Escalon System-Entwicklung Bubenhalde 10 74199 Untergruppenbach -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iEYEARECAAYFAlTDkOcACgkQuKLNitGfiZNk1ACgvvJDoAegCVDAkalKpCvrvi7k sKQAn3mOI752PGE+J5xUl8U8QL2aaX4p =fs02 -----END PGP SIGNATURE-----
Received on Saturday, 24 January 2015 12:33:13 UTC