W3C home > Mailing lists > Public > public-ldp-wg@w3.org > November 2012

Re: ldp-ISSUE-38 (filtering, inlining): filtered representations and inlining [Linked Data Platform core]

From: Arnaud Le Hors <lehors@us.ibm.com>
Date: Mon, 19 Nov 2012 14:13:40 -0800
To: Roger Menday <Roger.Menday@uk.fujitsu.com>
Cc: "Wilde, Erik" <Erik.Wilde@emc.com>, Linked Data Platform Working Group <public-ldp-wg@w3.org>
Message-ID: <OF245DEF11.D293A32F-ONC1257ABB.0079B647-88257ABB.007A1ADA@us.ibm.com>
Roger Menday <Roger.Menday@uk.fujitsu.com> wrote on 11/19/2012 01:49:16 
PM:
> ...
> > REST would require you to expose this in a way that clients can 
construct
> > those URIs at runtime, just by interacting with the LDP server. since 
you
> > cannot assume any specifics about the back-end, all you could do is 
have a
> > framework for how servers can expose additional interaction 
affordances,
> > in this case probably through a URI template. and then there would be 
a
> > magical parameter that would be entirely opaque to LDP, that would be
> > exposed by the LDP service. we are currently just in the process of
> > designing such a "query template" media type
> 
> I would be interested in seeing that ... where is this design at 
themoment ? 
> 
> I think that something link driven must be possible. i.e. like on a 
> shopping site, where the facets change according to which other 
> facets are selected previously, etc etc ... I think that this kind 
> of mechanism can be copied, such that the query strings can be "built 
up". 

I was just about to ask: who's "we" in your sentence, Erik? This is 
certainly not we, the LDP WG. :-)

> 
> regards, 
> Roger
> 
> > (so that exposing query
> > capabilities becomes a little bit easier because there's a standard 
way of
> > doing it), but afaict, there is no such thing around at this point in 
time.
> > 
> > cheers,
> > 
> > dret.
> > 
> 

--
Arnaud  Le Hors - Software Standards Architect - IBM Software Group
Received on Monday, 19 November 2012 22:14:16 UTC

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