A couple of years ago, I wrote an article on ITWorld about how software may provide a way to improve financial regulation.
It appears that the SEC are heading in this direction for capturing the semantics of complex financial instruments...and doing it with Python to boot.
Featured Post
These days, I mostly post my tech musings on Linkedin. https://www.linkedin.com/in/seanmcgrath/
Saturday, April 24, 2010
Monday, April 05, 2010
Blog comment spam hits 100%
I stepped away from my machine for a couple of days and today I find 60+ comment spams for moderation. I have taken to using a "super quick scan" followed by "select all" and "delete" strategy.
Sigh.
Wednesday, March 24, 2010
Congrats to Timetric on their funding round
Timetric has announced completion of a funding round and congrats are in order. Timetric are in a very interesting space. I'll be watching it closely.
Saturday, March 13, 2010
Schematron is 10. My oh my! Don't they grow up fast?
I'm shocked to find out today that Schematron is in its second decade. Amazing how time flies. Congrats to Rick.
Tuesday, February 02, 2010
Friday, January 08, 2010
Wednesday, January 06, 2010
Push me, pull me...a PSB blast from the past
Jim Downing has kindly resurrected a doc I wrote some years ago for and Irish Government agency called Reach that is now no more. Reach's goal in life was to lay down an infrastructure to allow government agencies to integrate their IT systems and also to provide a platform on which new government services could be quickly created. It was called the PSB - Public Services Broker.
I did the initial design work and I used to call it an SOA architecture. However because that phrase is essentially meaningless I had better explain what and "SOA" means in my head and its simply this: the reliable, asynchronous exchange of business level messages using XML payloads. Tons of detail went behind that simple statement of course. It used to be all online but not so much now. Anyway, as soon as you have endpoints that need to communicate you have the question of choreography to address and that is what the Push/Pull doc was all about.
I did the initial design work and I used to call it an SOA architecture. However because that phrase is essentially meaningless I had better explain what and "SOA" means in my head and its simply this: the reliable, asynchronous exchange of business level messages using XML payloads. Tons of detail went behind that simple statement of course. It used to be all online but not so much now. Anyway, as soon as you have endpoints that need to communicate you have the question of choreography to address and that is what the Push/Pull doc was all about.
Subscribe to:
Posts (Atom)