- From: Andrei Oprea <andrei.br92@gmail.com>
- Date: Thu, 2 May 2013 05:57:08 +0300
- To: public-webpayments@w3.org
- Message-ID: <CAHpZo2cXatjf4QSVOBXW9jstGRUWgB8Np9aB0AvWCh8-WCbw5g@mail.gmail.com>
Hi, Thanks, Dave, for the feedback. Indeed my application is in need of some clarifications. I have researched the subject more thoroughly the past week and also discussed with Francisco Jordano who told me more about the the Firefox Marketplace and Web Payments. The FF Marketplace is a great model, (but implies )if you are a developer and can get around to writing code. After going through the most common use cases for Web Payments, the ones that stand out such as simple payment links, independent distribution and crowdfunding cover a lot of people that might not be programmers. What I want for this project to achieve is an easy to use web interface, accessible from any device, that is capable or registering your asset with a Pay Swarm authority of your choosing with the terms and conditions you wish to apply for your asset. Depending on the type of content you are selling different templates for registering your asset would be made available and the website could act as an intermediary to publish your asset as listing for sale. The same can be said about licensing information After this action is completed the website would help you keep track of for asset, sales and also allow for modifications to be brought to the item such as updates or even removal from the listing. I see it as a layer of abstraction over the payswarm authority of your choosing (depending on price, additionals fees and such) and a mean to make content more easily profitable for creators. The website itself would not contain any listings therefore avoiding the possibility of a monopolistic approach. Micropayments, crowdfunding, independent distribution and pricing are some of the usecases I want to address first. I will update my application today to reflect this. Thanks, - Andrei
Received on Thursday, 2 May 2013 02:58:30 UTC