W3C home > Mailing lists > Public > public-hydra@w3.org > March 2017

PR for Suggested client interface draft

From: Dietrich Schulten <ds@escalon.de>
Date: Sun, 26 Mar 2017 12:36:59 +0200
To: public-hydra@w3.org
Message-ID: <f87a0024-6b4d-ba47-c2b6-0ddf5ec3d2e7@escalon.de>
Hi,

I have sent a pull request for the suggested client api. The main point 
of my suggestion is that the hydra client should behave very much like 
the browser, meaning, it maintains the current application state in the 
current representation. The current representation has controls and the 
client allows to look at the controls, choose one and interact with it 
using the uniform interface of the API. It also has a back navigation, 
and it could even have bookmarks.

https://github.com/HydraCG/Specifications/pull/111

You can read the draft here:

https://github.com/dschulten/Specifications/blob/master/drafts/client-interface.md

Please give feedback on issue #111, not here.

One can imagine many different ways to interact with Hydra. This 
suggestion is an opinionated one, I know. Let's see if we can reach a 
consensus how a client should work.

The most difficult part for me is the interaction with Schema.org 
actions, I have no clear idea what the client should do with them. I 
have tried to add an example nevertheless. Please rip apart if necessary 
and replace by something better, maybe that helps me understand what 
Schema.org actions are all about :-)

Best

Dietrich
Received on Sunday, 26 March 2017 10:37:34 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 26 March 2017 10:37:35 UTC