Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UV2SH-00012t-Gc for bitcoin-development@lists.sourceforge.net; Wed, 24 Apr 2013 16:22:01 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.170 as permitted sender) client-ip=209.85.217.170; envelope-from=melvincarvalho@gmail.com; helo=mail-lb0-f170.google.com; Received: from mail-lb0-f170.google.com ([209.85.217.170]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UV2SG-0004ga-0o for bitcoin-development@lists.sourceforge.net; Wed, 24 Apr 2013 16:22:01 +0000 Received: by mail-lb0-f170.google.com with SMTP id r10so1360725lbi.1 for ; Wed, 24 Apr 2013 09:21:53 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.145.230 with SMTP id sx6mr9764374lbb.49.1366820513042; Wed, 24 Apr 2013 09:21:53 -0700 (PDT) Received: by 10.112.143.38 with HTTP; Wed, 24 Apr 2013 09:21:52 -0700 (PDT) In-Reply-To: References: Date: Wed, 24 Apr 2013 18:21:52 +0200 Message-ID: From: Melvin Carvalho To: Mike Hearn Content-Type: multipart/alternative; boundary=047d7b3a7d9226d6f804db1db3ea 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: 1UV2SG-0004ga-0o Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] BIP21 bitcoin URIs and HTML5 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 16:22:01 -0000 --047d7b3a7d9226d6f804db1db3ea Content-Type: text/plain; charset=ISO-8859-1 On 24 April 2013 09:42, Mike Hearn wrote: > 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. > This is great news for bitcon, and the IANA application will be improved if there is evidence of it being used > > 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. > Not 100% sure how accurate this is, tho it may be the world view of some folks in WHATWG. WHATWG is not a major standards body tho. Work on improving the URL spec is always welcome, as it is the value proposition of the Web. > > > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > --047d7b3a7d9226d6f804db1db3ea Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On 24 April 2013 09:42, Mike Hearn <mike@plan99.net> w= rote:
HTML5 allows web apps to re= gister themselves for handling URI schemes, such as the bitcoin: URI that i= s already in use and being extended as part of the payment protocol.

The bad news is that for security reasons there is a whiteli= st of acceptable schemes in the spec:


The good news is that yesterday I talked to Hixie= about it and he added bitcoin to the whitelist:

<= a href=3D"http://html5.org/tools/web-apps-tracker?from=3D7849&to=3D7850= " target=3D"_blank">http://html5.org/tools/web-apps-tracker?from=3D7849&= ;to=3D7850

I'm currently finding out what the process is for b= rowser makers to notice the change (perhaps they watch the spec commit hist= ory and nothing needs to be done), but within a few months most users shoul= d have browsers that can accept bitcoin as a web-app handleable protocol sc= heme. I suppose IE10 users may be the laggards, but I guess we can live wit= h that for now.

This is great news for bitcon, and t= he IANA application will be improved if there is evidence of it being used<= br>
=A0

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 mar= k the old one as replaced, or can we just fix it in place given the relativ= ely exotic nature of most of the issues? Here's his feedback:


- BNF doesn&#= 39;t say what it's character set is (presumably it's Unicode)
=

=A0- "bitcoinparams" production doesn't define the separator,= so in theory the syntax is ...?label=3Dfoomessage=3Dfooother=3Dfoo (rather= than ...?label=3Dfoo&message=3Dfoo etc)

- 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>

- "pchar" is ref= erenced without definition.

- the "simpler" syntax is just wrong (it would result i= n bitcoin:address?amount=3D1?label=3DFOO rather than=A0bitcoin:address?amou= nt=3D1&label=3DFOO)

BTW the IETF URL specs= are being obsoleted by=A0http://url.spec.whatwg.org/, at least for Web purposes. In tha= t case matters.

Not 100% sure how accura= te this is, tho it may be the world view of some folks in WHATWG.=A0 WHATWG= is not a major standards body tho.=A0 Work on improving the URL spec is al= ways welcome, as it is the value proposition of the Web.
=A0


-----------------------------------------------------------------------= -------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service=
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_= ______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment


--047d7b3a7d9226d6f804db1db3ea--