- From: Pelle Braendgaard <pelle@stakeventures.com>
- Date: Wed, 11 Jan 2012 18:46:40 -0500
- To: opentransact@googlegroups.com
- Cc: Web Payments <public-webpayments@w3.org>
- Message-ID: <CAHtLsUWjB7t-5E3M1x6rreP0h4VfpRwUyLFDUB4aPCus=PiyTw@mail.gmail.com>
One of the most important things I have taken from this debate with the PaySwarm guys has been that we do need to explicitly show how various kinds of applications can be created using OpenTransact. So before I reply properly to the latest discussion I wanted to take the time out and properly explain a few use cases: So I have added this new Recipe's section to the OpenTransact site: http://www.opentransact.org/recipes/ There are detailed recipes for OpenTransact use in Crowd Funding: http://www.opentransact.org/recipes/crowdfunding.html and detailed example on how derivative assets such as what we are calling reserves can be used: http://www.opentransact.org/recipes/reserves.html I wil be adding examples for exchanges and subscriptions as well. Please provide me with feedback on errors, omissions and if this is a good format to show how it works. The idea with these recipes is that they provide practical examples of how you can do things. Conventions and Best Practices for OpenTransact. It shows how OpenTransact works together as a whole with other standards such as HTTP and OAuth 2.0. Some of the recipes, such as reserves may become more official specs in the future. Pelle -- http://picomoney.com - Like money, just smaller http://stakeventures.com - My blog about startups and agile banking
Received on Thursday, 12 January 2012 00:13:20 UTC