1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <brent.shambaugh@gmail.com>) id 1WQNxR-00045Q-RH
for bitcoin-development@lists.sourceforge.net;
Wed, 19 Mar 2014 21:23:29 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.170 as permitted sender)
client-ip=209.85.220.170;
envelope-from=brent.shambaugh@gmail.com;
helo=mail-vc0-f170.google.com;
Received: from mail-vc0-f170.google.com ([209.85.220.170])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WQNxQ-0007Z9-Tb
for bitcoin-development@lists.sourceforge.net;
Wed, 19 Mar 2014 21:23:29 +0000
Received: by mail-vc0-f170.google.com with SMTP id hu19so10125651vcb.1
for <bitcoin-development@lists.sourceforge.net>;
Wed, 19 Mar 2014 14:23:20 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.52.175.166 with SMTP id cb6mr26589710vdc.1.1395264200432;
Wed, 19 Mar 2014 14:23:20 -0700 (PDT)
Received: by 10.58.99.193 with HTTP; Wed, 19 Mar 2014 14:23:20 -0700 (PDT)
Date: Wed, 19 Mar 2014 16:23:20 -0500
Message-ID: <CACvcBVrOgN+NSX7rKgq2aZtgi7r-MKsX=f36OcftnH1LeSPRow@mail.gmail.com>
From: Brent Shambaugh <brent.shambaugh@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=bcaec50fdff308e5c904f4fc43ff
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(brent.shambaugh[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WQNxQ-0007Z9-Tb
Subject: [Bitcoin-development] Bitcoin for W3C Payments Workshop, March 24-25
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 19 Mar 2014 21:23:30 -0000
--bcaec50fdff308e5c904f4fc43ff
Content-Type: text/plain; charset=ISO-8859-1
Hello Bitcoiners,
I have been working on some use cases for the W3C payments workshop. I'd
like to include Bitcoin, but I might not have the time:
Here is what I have:
https://www.w3.org/community/webpayments/wiki/WebPaymentsMobileUseCases
Which is editable with a w3c username and password. Just be a member of the
webpayments community group: http://www.w3.org/community/webpayments/
More formally you can submit a pull request to:
https://github.com/w3c-webmob/payments-use-cases
-------------
Due to discussions with others am attempting to apply the following
template:
Name: name of the solution
Use Cases: Key use cases for the solution
Regions and currencies: Any SDKs or APIs which are available to developers
with the following things to consider (for use cases):
(1) add real money to the service
(2) buy a physical good in the real wold (e.g., a cup of coffee)
(3) pay for physical service (e.g., gym membership)?
(4) convert virtual money back into paper money
(5) transfer money from one person to another (even if the second person is
not signed up for the service)?
(6) buy product online
(7) resolve disputes?
(8) view transactions?
(9) secure the wallet
(10) etc.
Thanks for your time and have a great day!
-Brent Shambaugh
--bcaec50fdff308e5c904f4fc43ff
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div><div>Hello Bitcoiners,<br><br>I have been w=
orking on some use=20
cases for the W3C payments workshop. I'd like to include Bitcoin,=20
but I might not have the time:<br><br></div>Here is what I have:<br>
<br><a href=3D"https://www.w3.org/community/webpayments/wiki/WebPaymentsMob=
ileUseCases" target=3D"_blank">https://www.w3.org/community/webpayments/wik=
i/WebPaymentsMobileUseCases</a><br><br></div><div>Which is editable with a =
w3c username and password. Just be a member of the webpayments community gr=
oup: <a href=3D"http://www.w3.org/community/webpayments/" target=3D"_blank"=
>http://www.w3.org/community/webpayments/</a><br>
</div><div><br></div><div>More formally you can submit a pull request to:<b=
r><br><a href=3D"https://github.com/w3c-webmob/payments-use-cases" target=
=3D"_blank">https://github.com/w3c-webmob/payments-use-cases</a><br><br></d=
iv>
<div>-------------<br>
<br></div>Due to discussions with others am attempting to apply the followi=
ng template:<br><br><br>Name: name of the solution<br>Use Cases: Key use ca=
ses for the solution<br>Regions and currencies: Any SDKs or APIs which are =
available to developers<br>
<br>with the following things to consider (for use cases):<br>(1) add real =
money to the service<br>(2) buy a physical good in the real wold (e.g., a c=
up of coffee)<br>(3) pay for physical service (e.g., gym membership)?<br>
(4) convert virtual money back into paper money<br>(5) transfer money from =
one person to another (even if the second person is not signed up for the s=
ervice)?<br>(6) buy product online<br>(7) resolve disputes?<br>(8) view tra=
nsactions?<br>
(9) secure the wallet<br>(10) etc.<br><br></div>Thanks for your time and ha=
ve a great day!<br><br></div>-Brent Shambaugh<br></div>
--bcaec50fdff308e5c904f4fc43ff--
|
