Here we go again! :)

Does it have to be "either/or"? Can't it be a different model?

I.e. like a VOIP client, who initiates the connection to a server and after that opens a port / listens to incoming connections as well. The bank would be the "client" to OBP (giving control over the initialisation to the bank) and after that waiting for incoming requests as well.

OBP could sort of forward-handshake connections from/to user side then and wouldn't have to store any sensitive information.

Does that make sense!?

cheers D.

some more! :)

The show must go on! :)

*D.

Please note: these are just ideas, sketches if you like... None of the colours, photos, text or anything really is set in stone. Just ideas I was trying out, I hope there will be many more too...

v1c



v2ba



v2bb



v2bc



v3
This hasn't any colour, it was just more about layout. Obviously, colour would come later :)



v4a



v4b



v5



Thanks, James

Hi Folks,

We had a nice meeting in Paris with Société Générale today :-)

For our meeting we prepared another demo. A couple of screen shots below:

(also trying a new logo)

There are two components so far:

1) A Scala / Lift application currently using MongoDB to store transaction data.

2) A Python importer that grabs (via Selenium) a csv file from our Postbank account, parses it and pushes it to the OBP Scala API.

There is some simple "mediating" / filtering to demonstrate the concept of showing different views of the data to different people.

We published the code under Apache 2.0 lisense here: :-)

https://github.com/OpenBankProject

It was pretty rushed to get it ready - so its "warts and all"!

Big thanks to Alex and Everett (and previously Stefan) who worked on this code.

cheers,

Simon.

Hi Folks. This profile is now public except for some (non technical) posts written by others.

update - basically i just tried to use my best judgement and ismail also had a look through.

http://www.bbc.co.uk/news/magazine-16535620

http://www.ebaytechblog.com/2011/11/30/announcing-ql-io/