Open Web Payments initiative by PayPal

[Andreas Pizsa]

Praveen Alavilli, PM at PayPal X, has shared some slides about his
views on what could become an "Open Web Payments" standard stack. It's
based on open web standards such as Atom, Portable Contacts, and OAuth
2.0 for authorization / transaction approval (aka 'payment' :) ).

The slides are available at

http://www.slideshare.net/ppalavilli/open-web-payments

and there is also a Google group at http://groups.google.com/group/owp-api
and here's the blog post: http://whyidentity.blogspot.com/2010/07/open-web-payments.html

My first impression:

+ right direction, especially the OAuth payments authorization part
+ the Atom model has a transaction "funding type" attribute that
includes "Gold", which I feel I will have to comment on in the owp-api
group :)
+ not sure if Atom isn't a bit heavyweight compared to a JSON
representation, but that's probably a question of personal taste and
preference

Best,A.

[Melvin Carvalho]

Nice slides!

On 22 July 2010 09:23, Andreas Pizsa <hop...@gmail.com> wrote:

Praveen Alavilli, PM at PayPal X, has shared some slides about his
views on what could become an "Open Web Payments" standard stack. It's
based on open web standards such as Atom, Portable Contacts, and OAuth
2.0 for authorization / transaction approval (aka 'payment' :) ).

The slides are available at

http://www.slideshare.net/ppalavilli/open-web-payments

and there is also a Google group at http://groups.google.com/group/owp-api
and here's the blog post: http://whyidentity.blogspot.com/2010/07/open-web-payments.html

My first impression:

+ right direction, especially the OAuth payments authorization part

Prefer FOAF+SSL here
 

+ the Atom model has a transaction "funding type" attribute that

Atom is fine, but my idea has always been something called "NATO"

Netting and transactions ontology.

This will cater for a list of transaction (actually a tree) and realtime updates of balances.  RDF for the lightweight ontologies.
 

includes "Gold", which I feel I will have to comment on in the owp-api
group :)

Multi currency is fine.  Associate the currency with a URI or an ISO code literal.
 

+ not sure if Atom isn't a bit heavyweight compared to a JSON
representation, but that's probably a question of personal taste and
preference

Agreed.
 

Best,A.

--
You received this message because you are subscribed to the Google Groups "agile-banking" group.
To post to this group, send email to agile-...@googlegroups.com.
To unsubscribe from this group, send email to agile-bankin...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/agile-banking?hl=en.