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

Re: ldp-ISSUE-33 (pagination): how to structure functionality

From: Wilde, Erik <Erik.Wilde@emc.com>
Date: Mon, 12 Nov 2012 19:47:04 -0500
To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
CC: "ashok.malhotra@oracle.com" <ashok.malhotra@oracle.com>, Henry Story <henry.story@bblfish.net>
Message-ID: <CCC6D6B6.BE1D%erik.wilde@emc.com>
hello henry.

On 2012-11-12 13:33 , "Henry Story" <henry.story@bblfish.net> wrote:
>It is part of a GET form, not of a POST form.

that depends entirely on how your media type decides to use POST forms.
you can go both ways, and both ways are fine.

>>the crucial
>> difference to a generic query language is a that a form exposes a
>> service-specific way of what clients can ask for, and then on the
>>service
>> side can be translated into whatever actual query language the backend
>> happens to use.
>Forms are just a query language to the user with human readable but not
>machine
>readable semantics. Take an example from the HTTP 4 spec
>http://www.w3.org/TR/html4/interact/forms.html

i always cringe when people refer to forms as query language. unless you
have a form where you simply tunnel a query language ("enter your SQL
query here and we'll trust you that you don't do anything stupid and will
run it unsanitized against our database"), a form is a specific service
that probably will be translated into a query somewhere, but the form
itself is data model for a service-specific request. i guess my view of a
query language is that of a generic language, and forms are the opposite
of that.

><FORM action="http://somesite.com/prog/adduser" method="post">
>    <P>
>    First name: <INPUT type="text" name="firstname"><BR>
>    Last name: <INPUT type="text" name="lastname"><BR>
>    email: <INPUT type="text" name="email"><BR>
>    <INPUT type="radio" name="sex" value="Male"> Male<BR>
>    <INPUT type="radio" name="sex" value="Female"> Female<BR>
>    <BUTTON name="submit" value="submit" type="submit">
>    Send<IMG src="/icons/wow.gif" alt="wow"></BUTTON>
>    <BUTTON name="reset" type="reset">
>    Reset<IMG src="/icons/oops.gif" alt="oops"></BUTTON>
>    </P>
> </FORM>
>This is asking the user for his firstname, last name, email and sex.
>This could also have been written as
>SELECT ?firstname, ?lastname, ?email, ?sex
>WHERE {
>   <http://you.org/#me> foaf:fname ?firstname;
>             foaf:givenName ?lastname;
>             foaf:mbox ?email;
>             foaf:gender ?sex .
>}

these are entirely different things. one is the service surface, the other
is one possible service implementation. the form might run against a SQL
backend, or might run against a RDF backend and do all kind of data
mapping and data cleanup voodoo to make sure you get quality results.

cheers,

dret.
Received on Tuesday, 13 November 2012 00:47:49 UTC

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