From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1RqwHc-0003ev-0F for bitcoin-development@lists.sourceforge.net; Sat, 28 Jan 2012 00:36:44 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bluematt.me designates 173.246.101.161 as permitted sender) client-ip=173.246.101.161; envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me; Received: from vps.bluematt.me ([173.246.101.161] helo=mail.bluematt.me) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1RqwHa-0000eQ-SH for bitcoin-development@lists.sourceforge.net; Sat, 28 Jan 2012 00:36:43 +0000 Received: from [21.87.101.196] (66-87-109-196.pools.spcsdns.net [66.87.109.196]) by mail.bluematt.me (Postfix) with ESMTPSA id 5B7F3FB6 for ; Sat, 28 Jan 2012 01:28:11 +0100 (CET) References: <1327704664.31621.YahooMailNeo@web121003.mail.ne1.yahoo.com> <201201271800.31819.luke@dashjr.org> User-Agent: K-9 Mail for Android In-Reply-To: <201201271800.31819.luke@dashjr.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----VI44AN7K9O8Q9QZXWUTX0TUNB0MOCW" From: bitcoin-list@bluematt.me Date: Fri, 27 Jan 2012 19:36:31 -0500 To: bitcoin-development@lists.sourceforge.net Message-ID: <05d62c81-ef50-4c43-8fa5-65592c8f54a4@email.android.com> X-Spam-Score: -1.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 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -1.1 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RqwHa-0000eQ-SH Subject: Re: [Bitcoin-development] BIP 0020: URI Scheme 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: Sat, 28 Jan 2012 00:36:44 -0000 ------VI44AN7K9O8Q9QZXWUTX0TUNB0MOCW Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable It was implemented in the waylaying client with the merge of Bitcoin-Qt f= or drag and drop, and just recently for system URI handling in https://gi= thub.com/bitcoin/bitcoin/commit/70f55355e29c8e45b607e782c5d76609d23cc858.= However the version on the wiki armed as BIP 20 has a ton of extraneous = crap in it's number encoding which is not implemented in Bitcoin-Qt since= it was explicitly voted against at the time the spec was being discussed= . If that stuff were removed, I would agree that it is final. Luke-Jr wrote: On Friday, January 27, 2012 5:51:04 PM Amir Taaki wrote: > BIP 0020 is the old URI scheme BIPisized. >=20 > ATM it is Draft status. It's been Final (even according to BIP 1 standards) since late January 20= 11.=20 The only change recently is assigning it a BIP number for formality. > I do not know enough about the discussion back last year to know whethe= r to > move it to Accepted status or not. My feelings are that having a > re-decision (even if it was accepted last year) is healthy since it mak= es > no sense to have a standard before a standardisation process existed. Once P2SH is deployed, it will probably make good sense to revisit the UR= I=20 Scheme for revision, and eventually move BIP 20 to Replaced/Superceded st= atus. _____________________________________________ Try before you buy =3D See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _____________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development ------VI44AN7K9O8Q9QZXWUTX0TUNB0MOCW Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable It was implemented in the waylaying client with = the merge of Bitcoin-Qt for drag and drop, and just recently for system U= RI handling in https://github.com/bitcoin/bitcoin/c= ommit/70f55355e29c8e45b607e782c5d76609d23cc858. However the version o= n the wiki armed as BIP 20 has a ton of extraneous crap in it's numbe= r encoding which is not implemented in Bitcoin-Qt since it was explicitly= voted against at the time the spec was being discussed. If that stuff we= re removed, I would agree that it is final.

Luke-Jr <luke@dashjr.org> wrote:
On Friday, January 27, 2012 5:51:04 PM Amir Taaki wrote:
=
> BIP 0020 is the old URI scheme BIPisized.
> 
> ATM i=
t is Draft status.

It's been Final (even according to BIP 1 st=
andards) since late January 2011. 
The only change recently is assig=
ning it a BIP number for formality.

> I do not know enough =
about the discussion back last year to know whether to
> move it =
to Accepted status or not. My feelings are that having a
> re-dec=
ision (even if it was accepted last year) is healthy since it makes
=
> no sense to have a standard before a standardisation process existed=
.

Once P2SH is deployed, it will probably make good sense to r=
evisit the URI 
Scheme for revision, and eventually move BIP 20 to R=
eplaced/Superceded status.


Try before you buy =3D =
See our experts in action!
The most
comprehensive online learning library for Microsoft developers
is ju=
st $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
=
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/lea=
rndevnow-dev2

Bitcoin-development mailing list
=
Bitcoin-development@lists.sourceforge.net
https://lists.sourcefo=
rge.net/lists/listinfo/bitcoin-development
------VI44AN7K9O8Q9QZXWUTX0TUNB0MOCW--