Fill in: Atom is to RSS what ____ is to REST
I guess I need to write this post now (eventually) as I’m still seeing some basic concepts being mixed up. As the ‘domain model’ goes, we can do something like Atom over REST over HTTP, Atom/SOAP/HTTP, Atom/XMPP, or APP (statically linked Atom/HTTP)—I don’t know why only REST was mentioned in the post linked above.
Atom surely supplements WS-DeathStar, but it can hardly replace any of it. Atom is a content presentation protocol, and I don’t actually even know any web services standard which defines content presentation. Web services standards define service-access/consumption related metadata, not content. And as content is just one kind of a service, ie. a subset of it, you can use WS-* with Atom for eg. callbacks, authorization etc. If you want to transport content in some standard form—which I definitely recommend—Atom can suit you fine. It’s definitely and absolutely better than RSS; and this is not an opinion, thus ‘absolutely’. :)
Well, I’ll include the following stuff here as I’m too lazy to write a complete entry out of it. I just fail to understand why the RESTian folks got so excited over WADL? Weren’t the RESTful services supposed to work without interface descriptions? (Like, duh.) Doesn’t WADL make REST way too SOAP’y? WADL is exactly what WSDL is for SOAP, and the major criticism towards SOAP was due to the ‘rigid’ interface descriptions, namely WSDL.
And just as a sidenote, I personally happen to like C header files, WSDL’s, Java interfaces and all other kinds of interface descriptions, and I believe WADL is one of the best things happened to REST yet.
PS. I was thinking SOAP as an answer to the title. Agree?