W3C home > Mailing lists > Public > public-webpayments@w3.org > November 2015

Re: Markup for payable HTML resources

From: Steven Rowat <steven_rowat@sunshine.net>
Date: Wed, 18 Nov 2015 08:12:19 -0800
To: public-webpayments@w3.org, Meinhard Benn <meinhard@satoshipay.io>
Message-ID: <564CA363.8020105@sunshine.net>
On 11/17/15 3:37 PM, Meinhard Benn wrote:
  > I am the founder of SatoshiPay and we are looking at making paying for
> web content as frictionless as possible for all parties involved.
> What's happening in the http://will.satoshipay.eu/ example is that

Fun example! Welcome. Congratulations on getting investor funding. 
I'll be interested in how your beta launch unfolds.

I agree with your premise that direct sale of digital content for 
micro amounts is a potential disruptor for world information flow 
(publishing of all kinds).

What occurs to me, in the context of this list and the W3C IG effort, 
and its associated Credentials effort, is that perhaps we've reached a 
parting of the ways.

Specifically, my thought:
Maybe the system that sells digital content on the web for 
micro-amounts will be so different from the one required for movements 
of large amounts of money that attempting to develop both together is 

In other words, what you're doing may be easier, you may have already 
done it, and the people in this list may be working on a substantially 
different problem.

Thoughts anyone?  Have I jumped to an unwarranted conclusion?

Steven Rowat

> top-up the JS bitcoin wallet connects to the SatoshiPay server via
> WebSocket, negotiates the smart contract and moves funds to a multi-sig
> bitcoin address. With each payment the contract gets adjusted and a
> payment certificate is issued to the client by the SatoshiPay server.
> This certificate (currently a pre-shared secret) is shown by the client
> to the content server, which then ships the content. At no point
> SatoshiPay ever holds control over funds. We are merely the broker.
> Now, while the payments work fine, there are a few issues with the
> markup above as it's neither flexible nor consistent. So that's my where
> my question starts. My current idea is to redesign as follows:
> <div
>    data-sp-type="text/html"
>    data-sp-url="/paid-content/1?spCert=%s"
>    data-sp-id="563cc11c8c823d110025e951"
>    data-sp-currency="XBT"
>    data-sp-price="0.00004"
>    data-sp-length="1170"
> Improvements:
>   - there is a vendor prefix
>   - different text types could be rendered and styled differently
>   - the position of the SatoshiPay payment cert in the content retrieval
>     URL can be controlled by the publisher
>   - different currencies are supported
>   - price denomination meets a standard
> A payable image could look like this:
> <img
>    data-sp-type="image/png"
>    data-sp-url="/paid-images/1?spCert=%s"
>    data-sp-id="abcdef"
>    data-sp-currency="XBT"
>    data-sp-price="0.00006"
>    height="600"
>    width="800"
> Video/audio tags and download links would follow a similar pattern.
> So, I was wondering, did you spend some time on thinking about a
> standard for this already? The only W3C resource I found is a retired
> draft from 1999: http://www.w3.org/TR/Micropayment-Markup/
> On https://www.w3.org/community/webpayments/ I see a lot of JSON, but no
> HTML markup.
> Other thoughts? Are we thinking the right direction here?
> Cheers and thanks for listening, Meinhard Benn.
Received on Wednesday, 18 November 2015 16:12:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:07:43 UTC