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

forms for guiding interactions

From: Wilde, Erik <Erik.Wilde@emc.com>
Date: Tue, 13 Nov 2012 17:30:54 -0500
To: Henry Story <henry.story@bblfish.net>, "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
CC: "ashok.malhotra@oracle.com" <ashok.malhotra@oracle.com>
Message-ID: <CCC80878.BF4F%erik.wilde@emc.com>
hello henry.

On 2012-11-13 14:06 , "Henry Story" <henry.story@bblfish.net> wrote:
>This is getting off topic. But let me answer quickly

agreed, but i am still curious about that "let's query the client-side
database" approach...

> 1. the query is not asking for anybody's name, but for the name of the
>person
>    authenticated: in the example this was <http://you.org/#me> . So you
>don't 
>    need a huge address book. the server is asking for your name, just as
>it was 
>    in the html form.

address/contact forms can and very often do ask about all kinds of
contacts. "please enter your name", "please enter the name you want this
gift to be shipped to", "please tell us where you will stay when you
arrive". whatever. i'd still be interested how you'd design your "query
the client-side RDF store" approach around these kind of contextual
questions.

> 2. of course the client would also need access control rules on what can
>be shown. 
>    But why does that seem so difficult to imagine? We need them on the
>server. 
>    Clients and servers are interchangeable. They are jsut roles played
>in a 
>    communication flow: The web is peer to peer.

nope, interactions on the web are decidedly client/server.

cheers,

dret.
Received on Tuesday, 13 November 2012 22:31:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:42 UTC