Re: Non-trivial trading flows with schema.org

Hi,


Am 19. Februar 2015 17:07:05 schrieb Dietrich Schulten <ds@escalon.de>:

> Hi,
>
>
> Am 19. Februar 2015 11:41:39 schrieb Melvin Carvalho
> <melvincarvalho@gmail.com>:
>
> > On 19 February 2015 at 11:38, Dietrich Schulten <ds@escalon.de> wrote:
> >
> > > Hi,
> > >
> > > I have started to implement a "restbucks" coffee shop with hydra, hoping I
> > > could use schema.org.
> > >
> > > The results are not so encouraging so far, especially when it comes to
> > > interactions. On https://lists.w3.org/Archives/
> > > Public/public-vocabs/2015Feb/0092.html I have asked how it should work
> > > with schema:potentialActions, but I have similar problems with
> > > hydra:Operation. The necessary properties are simply not there, where I
> > > could attach my operations.
> > >
> > > Is anyone interested in discussing this here with the focus on
> > > hydra:operation?
> > >
> >
> > what are restbucks?
>
> A Starbucks coffee shop, only as a restful service. Originally conceived by
> Gregor Hohpe to discuss business interaction without db transactions,
> Webber picked up and showed how rest clients can use links not just for
> crud operations, but for application states.

Here is the link to the article:
http://www.infoq.com/articles/webber-rest-workflow

>
> >
> > I've been working with crypto currencies, REST and linked data for almost
> > 10 years now.  I'd never thought to use hydra : Operation, that's an
> > interesting idea.  Could you explain more?
>
> Not only give the client a link, but also tell it what to do with it.
> Options should always work, but a media type can hint the client what to
> send as a request body, what http method to use etc.
>
> I'll give an example later.

Example: http://tinyurl.com/p36rhv9

I would summarize hydra:Operation as a descriptor which wraps a restful 
method (usually http PUT POST DELETE) and adds information what to send as 
request body, furthermore it describes the ultimate goal of one or more 
http method executions (e.g. schema:OrderAction). The url for the operation 
is the @id of the subject which has the hydra:operation property.

A schema:Action can appear in an unfinished state, so it might span 
multiple http method calls, at least that is how I read them. That also 
makes it clear that the goal is not to re-introduce rpc by simply mapping a 
POST to a remote procedure call order().

>
> >
> >
> > >
> > > Best regards
> > > Dietrich
> > >
> > >
> > >
> > >
> > >