- From: Dietrich Schulten <ds@escalon.de>
- Date: Sat, 27 Sep 2014 13:02:35 +0200
- To: public-hydra@w3.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 17.09.2014 20:06, schrieb Kev Kirkland: > > I think the solution you mention below does this (if I interpret > it correctly). That is we return a representation that has a single > Hydra operation and the single operation is to POST some > information using a SupportedClass? > In fact, that is one possibility. Mike Amundsen once identified exactly this as a possible way to tell a client what to do in the hypermedia-web group. Another is a rel the client looks for. The IANA rel 'next' might be a good candidate for a wizard BTW :) My interpretation of json-ld attributes having links as values is that they are a special case of relation types. The attribute names are always IRIs, if you resolve them. The attribute "event" on the schema.org class "Organization" can be interpreted as an extension rel: Link rel=http://schema.org/event href="http://api.example.com/events". Only, they are not registered with IANA, but published in another well-known place. So a generic client could also be parameterized to look for "event", then for "offers" etc. This means that clients follow sequences of rels. With the rel 'next' it could also follow without knowing exactly how many times. If a client should show a form, traverse to different ui states, or fill required attributes autonomously from its "memory" is up to the client. At least we found that we should not design the service for a special user interface representation. Best regards, Dietrich - -- Dietrich Schulten Escalon System-Entwicklung Bubenhalde 10 74199 Untergruppenbach -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iEYEARECAAYFAlQmmUsACgkQuKLNitGfiZPL7wCgmKc056/6J8pBTKCtZlXq4oNR pFIAmwWfTIuqkN8VaCIEXht4pFAkSc5y =PmBe -----END PGP SIGNATURE-----
Received on Saturday, 27 September 2014 11:03:29 UTC