From: bitcoin-list@bluematt•me
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP 0020: URI Scheme
Date: Fri, 27 Jan 2012 19:36:31 -0500 [thread overview]
Message-ID: <05d62c81-ef50-4c43-8fa5-65592c8f54a4@email.android.com> (raw)
In-Reply-To: <201201271800.31819.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1831 bytes --]
It was implemented in the waylaying client with the merge of Bitcoin-Qt for drag and drop, and just recently for system URI handling in https://github.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 <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 it is Draft status.
It's been Final (even according to BIP 1 standards) since late January 2011.
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 whether 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 makes
> no sense to have a standard before a standardisation process existed.
Once P2SH is deployed, it will probably make good sense to revisit the URI
Scheme for revision, and eventually move BIP 20 to Replaced/Superceded status.
_____________________________________________
Try before you buy = 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
[-- Attachment #2: Type: text/html, Size: 2412 bytes --]
next prev parent reply other threads:[~2012-01-28 0:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 22:51 Amir Taaki
2012-01-27 23:00 ` Luke-Jr
2012-01-28 0:36 ` bitcoin-list [this message]
2012-01-28 1:45 ` Luke-Jr
2012-01-28 2:12 ` bitcoin-list
2012-01-28 8:23 ` Wladimir
2012-01-28 16:32 ` Andreas Schildbach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=05d62c81-ef50-4c43-8fa5-65592c8f54a4@email.android.com \
--to=bitcoin-list@bluematt$(echo .)me \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox