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

Re: LDP would benefit from being RESTful

From: Martynas Jusevičius <martynas@graphity.org>
Date: Wed, 14 Nov 2012 21:58:35 +0200
Message-ID: <CAE35Vmxe2tgs+98o-8FxhrN-MJmx0cSDy4rs5Z5+nxSLFCJwqg@mail.gmail.com>
To: Erik Wilde <dret@berkeley.edu>
Cc: public-ldp@w3.org, Mark Baker <distobj@acm.org>
Erik,

the solution to your book problem is simple enough -- the book
webservice needs an explicit (RDF) description of the result of its
invocation.
RDF by itself is not actionable (you can follow the hyperlinks), but
with description of the service it can be. Again, HTML is not any more
hypermedia -- if you submit a form, you don't know it's a book you
will get, unless the textual description says so somewhere.

And you haven't answered the state machine part :) If you do, please
tell me if the given Bug example is consistent with HTTP, RDF/OWL, and
if you see how it circumvents any issues the LDP spec has.

Martynas

On Wed, Nov 14, 2012 at 9:39 PM, Erik Wilde <dret@berkeley.edu> wrote:
> hello martynas.
>
>
> On 2012-11-14 11:18 , Martynas Jusevičius wrote:
>>
>> How is RDF any less of a hypermedia format than HTML? If it has
>> URIs/URLs built-in, you can follow them.
>
>
> i am sorry, but RDF really isn't a hypermedia format, and there's little i
> can add to that. linked data sort of changes that a little, but simply says
> "everything is a link you can try to GET", so you still have no purposefully
> actionable links that can be represented in the model where you could say
> "if you POST a description of a book to this URI, you will get in your
> mailbox in a couple of days." hypermedia formats allow clients to
> purposefully navigate a set of interlinked resources, and they can choose
> the links that they need to accomplish their goals.
>
> cheers,
>
> dret.
Received on Wednesday, 14 November 2012 19:59:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 14 November 2012 19:59:03 GMT