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

Re: forms, direction, query, etc

From: Henry Story <henry.story@bblfish.net>
Date: Tue, 20 Nov 2012 01:58:38 +0100
Cc: Linked Data Platform Working Group <public-ldp-wg@w3.org>
Message-Id: <F0F1D97D-0261-4483-A035-0915001156CD@bblfish.net>
To: Roger Menday <roger.menday@uk.fujitsu.com>
Thanks Roger.

My initial referral to SPARQL was to get us to think high level about what a Form is
about: it is a query of the server to the end user. The syntax of the answer (SPARQL 
or something else ) was not quite as important to this high level conceptual insight. 

From the e-mail you cite I think I ended up being clearest in
http://lists.w3.org/Archives/Public/public-ldp-wg/2012Nov/0165.html
on the relation between forms and SPARQL. You can see the parallel
very clearly:
<FORM action="p?" method="post">
 <P>
 page number:  <INPUT type="text" name="page"><BR>
 entries per page: <INPUT type="text" name="pageSz"><BR>
 <BUTTON name="Get answers" value="submit" type="submit"></BUTTON>
</FORM> 

So let's transform the above form into a SPARQL query

SELECT ?page ?pageSz 
TO <p>
WHERE {
  [] a PaginationSlice;
     :pageNumber ?page;
     :entriesPerPage ?pageSz .
}
So this clearly shows why it is related to Pagination in ISSUE-33 .
My thought that once one sees this, one may find this is just a way
to solve a huge number of problems that forms usually solve, but 
now with extra semantics.

There have been other attempts at doing forms in RDF. A quick search
led me to - but I think there have been others.
  http://www.markbaker.ca/2003/05/RDF-Forms/




On 19 Nov 2012, at 18:40, Roger Menday <roger.menday@uk.fujitsu.com> wrote:

> 
> Henry opened up some discussion at the end of our phone conference today, regarding his proposal about forms and query. 
> 
> I've got to say that I thought Henry's proposal [1] was really elegant.
> I also think that it is a solution for a problem that is very relevant to LDP. 
> 
> If it has a flaw, it that a client needs to be SPARQL aware - which I don't think will help uptake. I made my proposal on this topic at [2]. I'll freely admit that it does not have the elegance of Henry's use of SPARQL to drive interaction from the client, but, what it does have is simplicity! It is sort of like "duck-typed creation" .... it doesn't offer anything elaborate (repeated, options, etc.) at the moment. 
> 
> Roger
> 
> [1] http://lists.w3.org/Archives/Public/public-ldp-wg/2012Nov/0144.html
> [2] http://lists.w3.org/Archives/Public/public-ldp-wg/2012Oct/0274.html
> 

Social Web Architect
http://bblfish.net/




Received on Tuesday, 20 November 2012 00:59:12 UTC

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