OpenId as an ad-hoc federator

[S. Sriram]

From: "Martin Atkins" <mart at degeneration.co.uk>

> This sounds a bit like the "OpenRPC" thing I was proposing a while back,
> though that wasn't really all that RESTy. The key is that the request
> must be "user accompanied", which is to say that at least part of the

I went through OpenRPC and the concept is the same, however could it
not be as simple as the following.

(I reworked the OpenRPC- How does it work? below)

RestOpenID
-------------

How does it work?

There are three players in a RestOpenID request:

The attending user - identified by an OpenID Identity.
The caller - The site requesting data
The target site - The site sending the data.

The flow goes a little something like this:

-User enters the  OpenID identity they want to "be" while attending this
transaction into the calling site. The latter might have already been
decided by a previous OpenID login to the site, or it could just be a
text box as in my demo.

-User submits request with REST-url from which to collect required
information.

-Caller redirects the user to send an HTTP GET request directly to the
Rest API url as follows:

http//targetsite.com/restapi/get_my_data_out
  ?openid=www.livejournal.com/users/myid
  &returl=http://caller.com/put_my_data_in

-Target site validates the OpenID with the user.

-Target site than redirects the user to the return url parameter providing
either the data requested or an error.


Thanks
S. Sriram