Re: [xml-dev] Transformative Programming: Flow-based, functional, and mo

The Verb/Resource model of REST is not a simple tuple pair, unless you referring to PUT / GET parameterization which is probably a perfect example of why such interfaces are so error prone. �The rest (um, no pun intended) of HTTP carries with it headers and Mime types pointing to varying levels of formal specification as to the resource contents with varying success.

Peter Hunsberger

On Thu, Oct 17, 2013 at 7:35 PM, Uche Ogbuji <uche@ogbuji.net> wrote:

On Thu, Oct 17, 2013 at 4:35 PM, Peter Hunsberger <peter.hunsberger@gmail.com> wrote:

Hi Simon,

I'll buy into your view on REST, maybe a better fit is something like�Web Sockets? �However, I can't agree with you in regards to tighter�specs inside applications and looser between them. �Are you suggesting�that (for example) a Java method that has a single String as it's input�and output needs a full XSD or some other more formal spec? �I suspect�you're indulging in a bit of hyperbole in that, flexibility between�applications in what they can accept might simplify the world, but you�know as well as anyone that not everything can be mapped to name value�pairs or tuples and left at that?

I'm pretty sure I'm baffled by the above paragraph so this might not at all be relevant, but I will say that REST, and the Web itself pretty has loose specification between applications as its fundamental principle. The Verb/Resource model of REST is pretty much exactly the tuple pairs you seem to think cannot work.

--
Uche Ogbuji � � � � � � � � � � � � � � � � � � � http://uche.ogbuji.net
Founding Partner, Zepheira � � � � � � � � �http://zepheira.com
Author, Ndewo, Colorado � � � � � � � � � ��http://uche.ogbuji.net/ndewo/
Founding editor, Kin Poetry Journal � � �http://wearekin.org
Editor & Contributor, TNB � ��http://www.thenervousbreakdown.com/author/uogbuji/
http://copia.ogbuji.net� ��http://www.linkedin.com/in/ucheogbuji� ��http://twitter.com/uogbuji