[uf-rest] REST on Rails plug-ins

[Dr. Ernie Prabhakar]

Hi Sixtus,

> Can you position your efforts regarding http://code.google.com/apis/ 
> gdata/overview.html ?

I am (based on limited information) a big fan of GData.  I liked the  
Atom Publishing Protocol, but was frustrated that it didn't have any  
query semantics.

The short answer is that we want to do with HTML/hAtom what they are  
doing with Atom.  And we're not too proud to borrow all their good  
ideas. :-)

http://microformats.org/wiki/rest#Atom-based_alternatives

- Ernie P.


On Apr 21, 2006, at 5:13 PM, sixtus at gmail.com wrote:

> Hello Ernie,
>
>
> very nice, thanks for the effort. As it is way past my bedtime,  
> just a quick question:
>
> Can you position your efforts regarding http://code.google.com/apis/ 
> gdata/overview.html ?
>
>
> Cheers,
>
> Hagen
>
> On 4/22/06, Dr. Ernie Prabhakar <drernie at opendarwin.org> wrote:
> Hi all,
>
> Since there's been a lot of interest and activity lately, I setup a
> brief conference call between the various people working on
> expressing REST in Ruby on Rails:
> * David Hansson
> * Dan Kubb
> * Charlie Savage
> * Peter Williams
> and hosted by myself and Rohit Khare (the godfather of
> microformats.org).
>
> My notes from that meeting have been fed into the [rest/rails] wiki
> page:
>
> http://microformats.org/wiki/rest/rails#Plug-ins
>
> The main accomplishments of the call were:
>
> a) Defining a coherent scheme for generating RESTful URLs from within
> Rails
>
> b) Understanding the different goals of the various plug-ins now in
> existence
>
> While I can't say that consensus (or my notes) were perfect,
> hopefully it helps provide a starting point for future discussion.
> I hope the others will jump in and correct me where needed.
>
> While we probably can't converge on a single controller architecture
> due to different conceptual goals (Rails-first vs. REST-first), the
> hope is that both (all?) plug-ins would use the same URL conventions
> and share common code for the other items, e.g.:
> * Conditional GET
> * Status Codes
> * Content Negotiation
> * Caching and Warning Headers
> * Authentication and OPTIONS
>
> The ultimate dream is the same -- making Rails a testbed for best-
> practice RESTful application design, while will both be useful in
> itself and an inspiration for others in this space.
>
> Thanks for everyone who participated, and I hope everyone feels free
> to add their own ideas and suggestions.
>
> RESTfully yours,
> -- Ernie Prabhakar
> uf-REST Moderator
>
> _______________________________________________
> microformats-rest mailing list
> microformats-rest at microformats.org
> http://microformats.org/mailman/listinfo/microformats-rest
>
>
>
> -- 
> Dissertations are a successful walk through a minefield --  
> summarizing them is not. - Roy Fielding
> _______________________________________________
> microformats-rest mailing list
> microformats-rest at microformats.org
> http://microformats.org/mailman/listinfo/microformats-rest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://microformats.org/discuss/mail/microformats-rest/attachments/20060505/afac849b/attachment.htm