- From: Melvin Carvalho <melvincarvalho@gmail.com>
- Date: Tue, 24 Jan 2012 13:40:37 +0100
- To: Kingsley Idehen <kidehen@openlinksw.com>
- Cc: public-webpayments@w3.org, "foaf-protocols@lists.foaf-project.org" <foaf-protocols@lists.foaf-project.org>, public-rww@w3.org
On 24 January 2012 13:19, Kingsley Idehen <kidehen@openlinksw.com> wrote: > On 1/24/12 12:11 AM, Manu Sporny wrote: >> >> Hi all, >> >> The modularization discussion of the PaySwarm specification has become >> much more of a distraction than I had anticipated. To address this, >> let's try splitting the spec along the lines of where we think we might >> end up. This will be a headache for the editors of the specifications, >> but will hopefully make understanding the key technologies a bit easier. >> >> The first thing that has been split out of the PaySwarm Web API >> specification is how we do public/private key management. The result is >> the first (incredibly rough!, pre-alpha!) draft of the Web Keys 1.0 >> specification: >> >> http://payswarm.com/specs/ED/web-keys/2012-01-23/ >> >> The PaySwarm specification will probably endure a few more splits over >> the next couple of weeks into the following specs: >> >> * Payments >> * Commerce >> * Payment Intents >> >> I think these splits are roughly along the lines of what Pelle was >> suggesting that we do. >> >> -- manu >> > Manu, > > Good move! +1 > > FYI to others. > > -- > > Regards, > > Kingsley Idehen > Founder& CEO > OpenLink Software > Company Web: http://www.openlinksw.com > Personal Weblog: http://www.openlinksw.com/blog/~kidehen > Twitter/Identi.ca handle: @kidehen > Google+ Profile: https://plus.google.com/112399767740508618350/about > LinkedIn Profile: http://www.linkedin.com/in/kidehen > > > > > >
Received on Tuesday, 24 January 2012 12:41:06 UTC