Re: HTML Form to semantic web proposal

> On 27 Nov 2015, at 14:13, Martynas Jusevičius <martynas@graphity.org> wrote:
> 
> Well then you need a canonical mapping from www-encoded data to RDF before you query. CONSTRUCT could work on that, but it will not help you define it.
> 
> The only existing one I know is RDF/POST.

I don't agree that you need a canonical mapping from www-encoded data to rdf.

You can think of the attribute values as the response-set of a missing WHERE.
So you only actually need the CONSTRUCT part.

You do of course need the resource you are POSTing to, to return something that
points to the transormation. This could be done with a Link header such as

200 Ok
Link: <http://w3c.org/social/WebMention>; rel="urlencoded"

as explained in https://github.com/w3c-social/webmention/issues/11 <https://github.com/w3c-social/webmention/issues/11>



> 
> 
> 
> On Fri, 27 Nov 2015 at 14:53, henry.story@bblfish.net <mailto:henry.story@bblfish.net> <henry.story@bblfish.net <mailto:henry.story@bblfish.net>> wrote:
> 
> > On 27 Nov 2015, at 11:17, Martynas Jusevičius <martynas@graphity.org <mailto:martynas@graphity.org>> wrote:
> >
> > Where did you find the CONSTRUCT ... WITH query form though?
> 
> I just invented it, a quick first idea for people to get the gist.
> Clearly what would be needed would be also some way of having optional form attributes.
> 
> >
> > It could probably be just CONSTRUCT template with an empty WHERE {} on
> > which you apply the variable bindings.
> 
> I don't think that would work. We are actually just doing a construct on
> an result set. The parameter values in the www-encoded POSTed content
> can be thought of as a result set.
> 
> 
> 
> >
> > On Thu, Nov 26, 2015 at 7:53 PM, henry.story@bblfish.net <mailto:henry.story@bblfish.net>
> > <henry.story@bblfish.net <mailto:henry.story@bblfish.net>> wrote:
> >> That requires people getting people making such forms to learn RDF, which if
> >> you
> >> read the types of answers to issue 11 linked below, or if you interact with
> >> IndieWeb folks,
> >> you'll understand is unlikely.  What is less unlikely is that the server
> >> provide a link
> >> to an interpretation. The interpretation can then be made machine readable
> >> in the way
> >> proposed.
> >>
> >>
> >> On 26 Nov 2015, at 18:47, Martynas Jusevičius <martynas@graphity.org <mailto:martynas@graphity.org>> wrote:
> >>
> >> Can't you reuse RDF/POST for that?
> >> http://www.lsrn.org/semweb/rdfpost.html <http://www.lsrn.org/semweb/rdfpost.html>
> >>
> >> On Thu, 26 Nov 2015 at 19:38, henry.story@bblfish.net <mailto:henry.story@bblfish.net>
> >> <henry.story@bblfish.net <mailto:henry.story@bblfish.net>> wrote:
> >>>
> >>> Hi,
> >>>
> >>>   following a discussion with the IndieWeb folks on a pingback protocol,
> >>> where we are trying to satisfy the constraints that the IndieWeb folks
> >>> live
> >>> by - which is very close to the first generation of the Web - and yet who
> >>> want to work in a global web of data - the following requirement came
> >>> up: how can a resource make explicit its interpretation of web forms.
> >>>
> >>> I write this up here:
> >>>  https://github.com/w3c-social/webmention/issues/11 <https://github.com/w3c-social/webmention/issues/11>
> >>>
> >>> Essentially this would not entail very much other than creating a Link
> >>> realation
> >>> that could point to something like a document that would contain a mapping
> >>> that could look like this
> >>>
> >>> [[
> >>> @prefix foaf: <http://xmlns.com/foaf/0.1/ <http://xmlns.com/foaf/0.1/>>.
> >>> @prefix contact: <http://www.w3.org/2000/10/swap/pim/contact# <http://www.w3.org/2000/10/swap/pim/contact#>> .
> >>>
> >>> CONSTRUCT {
> >>> []  foaf:name ?name;
> >>>    foaf:age ?age;
> >>>    contact:home
> >>>            [ a contact:ContactLocation;
> >>>                contact:address [ contact:city ?city;
> >>>                                  contact:country ?country;
> >>>                                  contact:postalCode ?zip;
> >>>                                  contact:street ?street
> >>>                                ] .
> >>> } WITH ?name ?age ?city ?country ?zip ?street
> >>> ]]
> >>>
> >>> where ?name ?age ?city etc would be the values of the properties taken
> >>> from the
> >>> application/x-www-form-urlencoded content sent in a POST.
> >>>
> >>> This should not be that much work to specify I suppose, especially for the
> >>> SPARQL knowledgeable folks.
> >>>
> >>> Any feedback?
> >>>
> >>>        Henry
> >>>
> >>>
> >>>
> >>>
> >>
>