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
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <melvincarvalho@gmail.com>) id 1WQSKE-0005HM-6h
for bitcoin-development@lists.sourceforge.net;
Thu, 20 Mar 2014 02:03:18 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.174 as permitted sender)
client-ip=209.85.217.174; envelope-from=melvincarvalho@gmail.com;
helo=mail-lb0-f174.google.com;
Received: from mail-lb0-f174.google.com ([209.85.217.174])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WQSKC-0000Xs-FH
for bitcoin-development@lists.sourceforge.net;
Thu, 20 Mar 2014 02:03:18 +0000
Received: by mail-lb0-f174.google.com with SMTP id u14so118642lbd.33
for <bitcoin-development@lists.sourceforge.net>;
Wed, 19 Mar 2014 19:03:09 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.190.135 with SMTP id gq7mr28043562lac.28.1395280989896;
Wed, 19 Mar 2014 19:03:09 -0700 (PDT)
Received: by 10.112.26.38 with HTTP; Wed, 19 Mar 2014 19:03:09 -0700 (PDT)
In-Reply-To: <c32ff09f8e9c7a6c94fb3d92ae5b0231.squirrel@fulvetta.riseup.net>
References: <CACvcBVrOgN+NSX7rKgq2aZtgi7r-MKsX=f36OcftnH1LeSPRow@mail.gmail.com>
<c32ff09f8e9c7a6c94fb3d92ae5b0231.squirrel@fulvetta.riseup.net>
Date: Thu, 20 Mar 2014 03:03:09 +0100
Message-ID: <CAKaEYhKcPGHwA+4K8QkSe-yjOna=eGJi3v4P0xmLHNW_H4i8Ew@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: Odinn Cyberguerrilla <odinn.cyberguerrilla@riseup.net>
Content-Type: multipart/alternative; boundary=001a11381b50c3c60b04f5002b4b
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
(melvincarvalho[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: 1WQSKC-0000Xs-FH
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [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: Thu, 20 Mar 2014 02:03:18 -0000
--001a11381b50c3c60b04f5002b4b
Content-Type: text/plain; charset=ISO-8859-1
On 20 March 2014 02:41, Odinn Cyberguerrilla <
odinn.cyberguerrilla@riseup.net> wrote:
> I wish to state that I fundamentally disagree with this proposal of use
> cases for W3C payments workshop. Please read my following explanation and
> then do what you will:
>
> At one time I was invited to join the Web Payments conference calls. I
> considered it and then declined due to the very CLAs that Brent mentioned
> in the message that started this thread.
>
> I was trying to remember the language that I objected to relating to the
> W3C CLA. Found it: https://web-payments.org/minutes/ As mentioned, I was
> offered to join these calls but I declined due to, in part, the following:
> Upon review of the page at web-payments.org, I noticed that it provides
> a means to connect with web payments group by teleconference. However,
> there is an agreement that the site would require me to accept merely to
> join the teleconference and collaborate with others in the web payments
> group. I would say "unfortunately," but in my case I will say
> fortunately, I don't agree with the required agreement as shown here at
> http://www.w3.org/community/about/agreements/cla/ which is shown as
> follows at https://web-payments.org/minutes/ "There are no costs
> associated with joining the group or limitations on who may join the
> teleconference as long as they agree to the Web Payments community "
>
> Some of the things I don't like about the proposed agreement /
> "requirement" are fundamental. At the core, it should be understood that
> collaborative efforts, or teleconferences involving innovators who strive
> to develop concepts for eventual development of a social good, for
> example, should not be subject to a "requirement" that anyone agree to a
> license in relation to their participation or contribution. Such
> "requirements" inhibit innovation and free thought. For example, the web
> payments group provides that in order for me to participate, I must first
> "agree to license my Essential Claims under the W3C CLA RF Licensing
> Requirements" and numerous other requirements.
>
> Although I was interested in some sort of collaboration with the Web
> Payments Community Group, these CLAs - lengthy, burdensome, and in my
> personal view, highly dubious and potentially restricting with respect to
> innovation and free thought - caused me to reconsider, and thus I will not
> be entering into web or telephone conferences or related collaborations
> with the W3C / Web Payments folks until such time as they remove these
> burdensome requirements which are applied merely to join a call.
>
Fair point, but you need to understand that all specs created by the W3C
are committed to be royalty free. That's why there's a CLA, but I can
totally see if you or your employer feels uncomfortable with that. You
might have the best possible interests, but not everyone may be as honest.
Personally, have participated as an unaffiliated volunteer and hobbyist at
the W3C for a few years, I've never seen an issue with this. In fact, I'm
really happy that they have a bullet proof intellectual property framework
that guarantees all my contributions will never be encumbered by patents or
be charged royalties for.
>
> > 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
> >
> ------------------------------------------------------------------------------
> > Learn Graph Databases - Download FREE O'Reilly Book
> > "Graph Databases" is the definitive new guide to graph databases and
> their
> > applications. Written by three acclaimed leaders in the field,
> > this first edition is now available. Download your free book today!
> >
> http://p.sf.net/sfu/13534_NeoTech_______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> >
>
>
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--001a11381b50c3c60b04f5002b4b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On 20 March 2014 02:41, Odinn Cyberguerrilla <span dir=3D"ltr"><=
<a href=3D"mailto:odinn.cyberguerrilla@riseup.net" target=3D"_blank">odinn.=
cyberguerrilla@riseup.net</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I wish to state that I fundamentally disagre=
e with this proposal of use<br>
cases for W3C payments workshop. =A0Please read my following explanation an=
d<br>
then do what you will:<br>
<br>
At one time I was invited to join the Web Payments conference calls. =A0I<b=
r>
considered it and then declined due to the very CLAs that Brent mentioned<b=
r>
in the message that started this thread.<br>
<br>
I was trying to remember the language that I objected to relating to the<br=
>
W3C CLA. =A0Found it: <a href=3D"https://web-payments.org/minutes/" target=
=3D"_blank">https://web-payments.org/minutes/</a> As mentioned, I was<br>
offered to join these calls but I declined due to, in part, the following:<=
br>
Upon review of =A0the page at =A0<a href=3D"http://web-payments.org" target=
=3D"_blank">web-payments.org</a>, I noticed that it provides<br>
a means to connect with web payments group by teleconference. =A0However,<b=
r>
there is an agreement that the site would require me to accept merely to<br=
>
join the teleconference and collaborate with others in the web payments<br>
group. =A0I would say "unfortunately," but in my case I will say<=
br>
fortunately, I don't agree with the required agreement as shown here at=
<br>
<a href=3D"http://www.w3.org/community/about/agreements/cla/" target=3D"_bl=
ank">http://www.w3.org/community/about/agreements/cla/</a> which is shown a=
s<br>
follows at <a href=3D"https://web-payments.org/minutes/" target=3D"_blank">=
https://web-payments.org/minutes/</a> "There are no costs<br>
associated with joining the group or limitations on who may join the<br>
teleconference as long as they agree to the Web Payments community "<b=
r>
<br>
Some of the things I don't like about the proposed agreement /<br>
"requirement" are fundamental. =A0At the core, it should be under=
stood that<br>
collaborative efforts, or teleconferences involving innovators who strive<b=
r>
to develop concepts for eventual development of a social good, for<br>
example, should not be subject to a "requirement" that anyone agr=
ee to a<br>
license in relation to their participation or contribution. =A0Such<br>
"requirements" inhibit innovation and free thought. =A0For exampl=
e, the web<br>
payments group provides that in order for me to participate, I must first<b=
r>
"agree to license my Essential Claims under the W3C CLA RF Licensing<b=
r>
Requirements" and numerous other requirements.<br>
<br>
Although I was interested in some sort of collaboration with the Web<br>
Payments Community Group, these CLAs - lengthy, burdensome, and in my<br>
personal view, highly dubious and potentially restricting with respect to<b=
r>
innovation and free thought - caused me to reconsider, and thus I will not<=
br>
be entering into web or telephone conferences or related collaborations<br>
with the W3C / Web Payments folks until such time as they remove these<br>
burdensome requirements which are applied merely to join a call.<br></block=
quote><div><br></div><div>Fair point, but you need to understand that all s=
pecs created by the W3C are committed to be royalty free.=A0 That's why=
there's a CLA, but I can totally see if you or your employer feels unc=
omfortable with that.=A0 You might have the best possible interests, but no=
t everyone may be as honest.<br>
<br></div><div>Personally, have participated as an unaffiliated volunteer a=
nd hobbyist at the W3C for a few years, I've never seen an issue with t=
his.=A0 In fact, I'm really happy that they have a bullet proof intelle=
ctual property framework that guarantees all my contributions will never be=
encumbered by patents or be charged royalties for.<br>
</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class=3D"h5"><br>
> Hello Bitcoiners,<br>
><br>
> I have been working on some use cases for the W3C payments workshop. I=
'd<br>
> like to include Bitcoin, but I might not have the time:<br>
><br>
> Here is what I have:<br>
><br>
> <a href=3D"https://www.w3.org/community/webpayments/wiki/WebPaymentsMo=
bileUseCases" target=3D"_blank">https://www.w3.org/community/webpayments/wi=
ki/WebPaymentsMobileUseCases</a><br>
><br>
> Which is editable with a w3c username and password. Just be a member o=
f<br>
> the<br>
> webpayments community group: <a href=3D"http://www.w3.org/community/we=
bpayments/" target=3D"_blank">http://www.w3.org/community/webpayments/</a><=
br>
><br>
> More formally you can submit a pull request to:<br>
><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>
> -------------<br>
><br>
> Due to discussions with others am attempting to apply the following<br=
>
> template:<br>
><br>
><br>
> Name: name of the solution<br>
> Use Cases: Key use cases for the solution<br>
> Regions and currencies: Any SDKs or APIs which are available to develo=
pers<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 cup 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 pers=
on<br>
> is<br>
> not signed up for the service)?<br>
> (6) buy product online<br>
> (7) resolve disputes?<br>
> (8) view transactions?<br>
> (9) secure the wallet<br>
> (10) etc.<br>
><br>
> Thanks for your time and have a great day!<br>
><br>
> -Brent Shambaugh<br>
</div></div>> ----------------------------------------------------------=
--------------------<br>
> Learn Graph Databases - Download FREE O'Reilly Book<br>
> "Graph Databases" is the definitive new guide to graph datab=
ases and their<br>
> applications. Written by three acclaimed leaders in the field,<br>
> this first edition is now available. Download your free book today!<br=
>
> <a href=3D"http://p.sf.net/sfu/13534_NeoTech__________________________=
_____________________" target=3D"_blank">http://p.sf.net/sfu/13534_NeoTech_=
______________________________________________</a><br>
> Bitcoin-development mailing list<br>
> <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-d=
evelopment@lists.sourceforge.net</a><br>
> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-develo=
pment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitco=
in-development</a><br>
><br>
<br>
<br>
<br>
---------------------------------------------------------------------------=
---<br>
Learn Graph Databases - Download FREE O'Reilly Book<br>
"Graph Databases" is the definitive new guide to graph databases =
and their<br>
applications. Written by three acclaimed leaders in the field,<br>
this first edition is now available. Download your free book today!<br>
<a href=3D"http://p.sf.net/sfu/13534_NeoTech" target=3D"_blank">http://p.sf=
.net/sfu/13534_NeoTech</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div></div>
--001a11381b50c3c60b04f5002b4b--
|