W3C home > Mailing lists > Public > public-hydra@w3.org > July 2014

RE: Express "go to specific page" for a collection

From: Philipp Zins <pipo@senaeh.de>
Date: Tue, 8 Jul 2014 11:41:49 +0200
Message-ID: <CACkJGAuJf4kV31Ab3tnXRBs-xOEj+NmLyKvfdOhsaVJSCH+AXQ@mail.gmail.com>
To: public-hydra@w3.org
Hi Markus and Jindřich,

sorry for "double posting". It seems my first mail didn't arrived at my in-box
and Jindřich answer also, but I read it in the public web archive. I hope
from now everything works - I had trouble with w3c mailing lists before.

> Does your use case really require it?
I would say, yes. If you compare some GUI pagination patterns (see
https://gist.github.com/mislav/622561) you can see that roughly 50% allow
the user to jump to an arbitrary page.

What do you think about Jindřich comment with the anonymous anonymous

Some background: I'm mainly a frontend developer switching to the backend
here and there. As we try to move more development processes to the client
(for better iteration speeds, dynamic and fluid GUIs, etc.) we need a good
interface between server and client. We really like the idea of Hypermedia
APIs (instead of RPC-ish "REST" APIs) and I try to evaluate different
solutions. We currently favor JSON Hyper-Schema directly embedded in our
resources, but I would like to explore if we can move to
Hydra/JSON-LD completely in the next turn as it seems to be a more widely
used standard and because JSON-LD is supported by all major search engines.
But I don't want to loose the benefits of JSON Hyper-Schema.

Received on Tuesday, 8 July 2014 09:42:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:29:42 UTC