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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <odinn.cyberguerrilla@riseup.net>) id 1WQRzZ-0004X4-FI
for bitcoin-development@lists.sourceforge.net;
Thu, 20 Mar 2014 01:41:57 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of riseup.net
designates 198.252.153.129 as permitted sender)
client-ip=198.252.153.129;
envelope-from=odinn.cyberguerrilla@riseup.net;
helo=mx1.riseup.net;
Received: from mx1.riseup.net ([198.252.153.129])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1WQRzY-000290-C6
for bitcoin-development@lists.sourceforge.net;
Thu, 20 Mar 2014 01:41:57 +0000
Received: from fulvetta.riseup.net (fulvetta-pn.riseup.net [10.0.1.75])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "*.riseup.net",
Issuer "Gandi Standard SSL CA" (not verified))
by mx1.riseup.net (Postfix) with ESMTPS id 534B34670E;
Wed, 19 Mar 2014 18:41:50 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
(Authenticated sender: odinn.cyberguerrilla@fulvetta.riseup.net)
with ESMTPSA id E740F1A8
Received: from localhost (127.0.0.1)
(SquirrelMail authenticated user odinn.cyberguerrilla)
by fulvetta.riseup.net with HTTP; Wed, 19 Mar 2014 18:41:50 -0700
Message-ID: <c32ff09f8e9c7a6c94fb3d92ae5b0231.squirrel@fulvetta.riseup.net>
In-Reply-To: <CACvcBVrOgN+NSX7rKgq2aZtgi7r-MKsX=f36OcftnH1LeSPRow@mail.gmail.com>
References: <CACvcBVrOgN+NSX7rKgq2aZtgi7r-MKsX=f36OcftnH1LeSPRow@mail.gmail.com>
Date: Wed, 19 Mar 2014 18:41:50 -0700
From: "Odinn Cyberguerrilla" <odinn.cyberguerrilla@riseup.net>
To: "Brent Shambaugh" <brent.shambaugh@gmail.com>
User-Agent: SquirrelMail/1.4.21
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: clamav-milter 0.98.1 at mx1
X-Virus-Status: Clean
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [198.252.153.129 listed in list.dnswl.org]
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay
lines
X-Headers-End: 1WQRzY-000290-C6
Cc: 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 01:41:57 -0000
I wish to state that I fundamentally disagree with this proposal of use
cases for W3C payments workshop. Please read my following explanation an=
d
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 no=
t
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.=EF=BB=BF
> 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 develop=
ers
>
> 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 perso=
n
> 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 th=
eir
> 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
>
|
