Re: HTML Form to semantic web proposal

> On 27 Nov 2015, at 10:54, Graham Klyne <gk@ninebynine.org> wrote:
> 
> I come to this without having a real grasp of the discussion context, but just in case it adds anything... (otherwise, pls ignore me)
> 
> FWIW, we wrestled with what I think may be some related issues for accessing provenance data for a resource (http://www.w3.org/TR/prov-aq/), which led (IMO) to a something of a multiplicity of access options with varying trade-offs.  In particular, adding link relations (a mechanism I generally favour) is not available to all users, so the group felt alternatives were required.
> 
> I guess my core question here would be:  how can parties who have no control over the served web form make their interpretation discoverable?

You can put an html page up, or return content that published the relation.
The Link relation ties into html headers, and more.

> 
> #g
> --
> 
> On 26/11/2015 18:53, 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> 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
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>

Received on Friday, 27 November 2015 13:52:31 UTC