W3C home > Mailing lists > Public > public-ldp-wg@w3.org > March 2013

Re: ACTION-43 Draft use case for ordering

From: Richard Cyganiak <richard@cyganiak.de>
Date: Tue, 26 Mar 2013 08:59:23 +0000
Message-Id: <3E3F1331-F04B-46CB-B060-8FDF8A6FB943@cyganiak.de>
Cc: Steve Speicher <sspeiche@gmail.com>, "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
To: "Wilde, Erik" <Erik.Wilde@emc.com>
On 25 Mar 2013, at 22:54, "Wilde, Erik" <Erik.Wilde@emc.com> wrote:
> we cannot rely on client-side ordering,
> because ordering is not necessarily based on anything *in* the response. a
> service could very well support ordering based on information that is not
> exposed in the response.

That's true, but maybe not that critical, given that it's always easy for the server to add one more property to the container members to expose the value used for ordering.

> but the interesting question still remains: how
> do we expose these capabilities, so that clients can actually send a
> request that will result in the response as shown by richard?

There's two issues: how do clients request a particular sort order. And how do servers expose the sort order in a response. The current LDP spec doesn't address the first question. That's ok with me. It's a version one. It ought to answer the second question if we support paging, for the reasons Steve stated in the initial mail of this thread.

Best,
Richard




> 
> cheers,
> 
> dret.
> 
> 
Received on Tuesday, 26 March 2013 08:59:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:38 UTC