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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1UUuLe-0008U4-OC
for bitcoin-development@lists.sourceforge.net;
Wed, 24 Apr 2013 07:42:38 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.169 as permitted sender)
client-ip=209.85.214.169; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f169.google.com;
Received: from mail-ob0-f169.google.com ([209.85.214.169])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UUuLd-00016u-Kd
for bitcoin-development@lists.sourceforge.net;
Wed, 24 Apr 2013 07:42:38 +0000
Received: by mail-ob0-f169.google.com with SMTP id tb18so1223908obb.28
for <bitcoin-development@lists.sourceforge.net>;
Wed, 24 Apr 2013 00:42:32 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.112.202 with SMTP id is10mr17403624obb.8.1366789352227;
Wed, 24 Apr 2013 00:42:32 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.167.169 with HTTP; Wed, 24 Apr 2013 00:42:32 -0700 (PDT)
Date: Wed, 24 Apr 2013 09:42:32 +0200
X-Google-Sender-Auth: Gxy8sE0__DJ9uT1UK8FOvOl2usk
Message-ID: <CANEZrP2OPU8cpvUJ0B8z00PPp6jOGCjQ1ipZ9mq8_LSLo4Rebg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=089e015369bed28bd704db1671bc
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1UUuLd-00016u-Kd
Subject: [Bitcoin-development] BIP21 bitcoin URIs and HTML5
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, 24 Apr 2013 07:42:38 -0000
--089e015369bed28bd704db1671bc
Content-Type: text/plain; charset=UTF-8
HTML5 allows web apps to register themselves for handling URI schemes, such
as the bitcoin: URI that is already in use and being extended as part of
the payment protocol.
The bad news is that for security reasons there is a whitelist of
acceptable schemes in the spec:
http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html#dom-navigator-registerprotocolhandler
The good news is that yesterday I talked to Hixie about it and he added
bitcoin to the whitelist:
http://html5.org/tools/web-apps-tracker?from=7849&to=7850
I'm currently finding out what the process is for browser makers to notice
the change (perhaps they watch the spec commit history and nothing needs to
be done), but within a few months most users should have browsers that can
accept bitcoin as a web-app handleable protocol scheme. I suppose IE10
users may be the laggards, but I guess we can live with that for now.
Ian pointed out some errors in the BIP21 spec. What's the process for
amending the BIP? Do we need to create a new one and mark the old one as
replaced, or can we just fix it in place given the relatively exotic nature
of most of the issues? Here's his feedback:
- BNF doesn't say what it's character set is (presumably it's Unicode)
- "bitcoinparams" production doesn't define the separator, so in theory
the syntax is ...?label=foomessage=fooother=foo (rather than
...?label=foo&message=foo etc)
- the syntax allows ?amount=FOO&amount=1.1 as far as I can tell, since
"otherparam" matches any name followed by any value, including "amount"
followed by a bogus value.
- "pchar" is referenced without definition.
- the "simpler" syntax is just wrong (it would result in
bitcoin:address?amount=1?label=FOO rather
than bitcoin:address?amount=1&label=FOO)
BTW the IETF URL specs are being obsoleted by http://url.spec.whatwg.org/,
at least for Web purposes. In that case matters.
--089e015369bed28bd704db1671bc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">HTML5 allows web apps to register themselves for handling =
URI schemes, such as the bitcoin: URI that is already in use and being exte=
nded as part of the payment protocol.<div><br></div><div>The bad news is th=
at for security reasons there is a whitelist of acceptable schemes in the s=
pec:</div>
<div><br></div><div><a href=3D"http://www.whatwg.org/specs/web-apps/current=
-work/multipage/timers.html#dom-navigator-registerprotocolhandler">http://w=
ww.whatwg.org/specs/web-apps/current-work/multipage/timers.html#dom-navigat=
or-registerprotocolhandler</a><br>
</div><div><br></div><div style>The good news is that yesterday I talked to=
Hixie about it and he added bitcoin to the whitelist:</div><div style><br>=
</div><div style><a href=3D"http://html5.org/tools/web-apps-tracker?from=3D=
7849&to=3D7850">http://html5.org/tools/web-apps-tracker?from=3D7849&=
;to=3D7850</a></div>
<div style><br></div><div style>I'm currently finding out what the proc=
ess is for browser makers to notice the change (perhaps they watch the spec=
commit history and nothing needs to be done), but within a few months most=
users should have browsers that can accept bitcoin as a web-app handleable=
protocol scheme. I suppose IE10 users may be the laggards, but I guess we =
can live with that for now.</div>
<div style><br></div><div style>Ian pointed out some errors in the BIP21 sp=
ec. What's the process for amending the BIP? Do we need to create a new=
one and mark the old one as replaced, or can we just fix it in place given=
the relatively exotic nature of most of the issues? Here's his feedbac=
k:</div>
<div style><br></div><div style><br></div><div style><div class=3D"gmail_ex=
tra">- BNF doesn't say what it's character set is (presumably it=
9;s Unicode)</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_=
extra">
=C2=A0- "bitcoinparams" production doesn't define the separat=
or, so in theory the syntax is ...?label=3Dfoomessage=3Dfooother=3Dfoo (rat=
her than ...?label=3Dfoo&message=3Dfoo etc)</div><div class=3D"gmail_ex=
tra"><br></div>
<div class=3D"gmail_extra">- the syntax allows ?amount=3DFOO&amount=3D1=
.1 as far as I can tell, since "otherparam" matches any name foll=
owed by any value, including "amount" followed by a bogus value.<=
/div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><span style=
=3D"font-family:arial,sans-serif;font-size:13px">- "pchar" is ref=
erenced without definition.</span><br style=3D"font-family:arial,sans-serif=
;font-size:13px">
<div class=3D"gmail_extra" style=3D"font-family:arial,sans-serif;font-size:=
13px"><br>- the "simpler" syntax is just wrong (it would result i=
n bitcoin:address?amount=3D1?label=3DFOO rather than=C2=A0bitcoin:address?a=
mount=3D1&label=3DFOO)</div>
<div style=3D"font-family:arial,sans-serif;font-size:13px"><br></div><div s=
tyle=3D"font-family:arial,sans-serif;font-size:13px">BTW the IETF URL specs=
are being obsoleted by=C2=A0<a href=3D"http://url.spec.whatwg.org/" target=
=3D"_blank">http://url.spec.whatwg.org/</a>, at least for Web purposes. In =
that case matters.</div>
<div><br></div></div></div></div>
--089e015369bed28bd704db1671bc--
|
