Re: The difference between PaySwarm and OpenTransact

SOAP and it's associated standards often known as WS-* created a very
complicated standard on top of HTTP.

It was filled with complex concepts, vocabularies etc and attempted to
reinvent everything to fit into it's large model about how the world should
be.

It was particularly ridiculed when they created a "SOAP Resource
Representation Header" spec:

http://www.w3.org/TR/2004/WD-soap12-rep-20040428/

Which was jokingly called HTTP over SOAP.

http://www.tbray.org/ongoing/When/200x/2004/05/01/SRRH

Rest on the other hand is web native and simple.

It's about resources and actions you perform on it.

OpenTransact uses the concept of Assets as the resources. Payment itself is
a simple restful action on an asset.

PaySwarm like SOAP builds a complex world view and eco system that requires
reinventing TLS, OAuth (but not really as you said yourself) and creates a
heavy conceptual model for developers and consumers a like to deal with.




On Thu, Jan 12, 2012 at 6:05 PM, David I. Lehn <dil@lehn.org> wrote:

> On Thu, Jan 12, 2012 at 5:44 PM, Pelle Braendgaard
> <pelle@stakeventures.com> wrote:
> > On Thu, Jan 12, 2012 at 3:26 PM, Dave Longley <
> dlongley@digitalbazaar.com>
> > wrote:
> >> PaySwarm only "encompasses one way of doing things" for what it is that
> it
> >> standardizes. PaySwarm enables interoperability between payment
> providers
> >> and facilitates online payment and commerce. It only standardizes what
> needs
> >> to be delegated in order for this to happen and gets out of your way for
> >> everything else. That is not a limitation, rather just the opposite.
> What
> >> PaySwarm does limit is only what it standardizes, which solves the
> >> challenges that anyone who wants to engage in open online commerce would
> >> otherwise need to solve themselves. I think it does so rather minimally,
> >> without being so basic that it ignores what I think are very important
> and
> >> long standing use cases for online commerce.
> >
> >
> > I beg to differ. It's SOAP vs Rest
> >
>
> Could you please explain what you mean with that comparison?  I think
> you used that before and I didn't quite understand what you were
> getting at.  Both standards seem to be using RESTish ideas.  Thanks.
>
> -dave
>



-- 
http://picomoney.com - Like money, just smaller
http://stakeventures.com - My blog about startups and agile banking