Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.210.47 as permitted sender)
	client-ip=209.85.210.47; envelope-from=laanwj@gmail.com;
	helo=mail-pz0-f47.google.com; 
MIME-Version: 1.0
In-Reply-To: <759be3f8-ca4c-4e36-aac1-b3894dda450d@email.android.com>
References: <1327704664.31621.YahooMailNeo@web121003.mail.ne1.yahoo.com>
	<201201271800.31819.luke@dashjr.org>
	<05d62c81-ef50-4c43-8fa5-65592c8f54a4@email.android.com>
	<201201272045.10787.luke@dashjr.org>
	<759be3f8-ca4c-4e36-aac1-b3894dda450d@email.android.com>
Date: Sat, 28 Jan 2012 09:23:51 +0100
Message-ID: <CA+s+GJAtRO_PH1oWmT7KOMeDF2L-YvoWkanURYD=keepCaQ9VQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: bitcoin-list@bluematt.me
Content-Type: multipart/alternative; boundary=f46d041705ad522a1904b79255d1
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP 0020: URI Scheme
Precedence: list

--f46d041705ad522a1904b79255d1
Content-Type: text/plain; charset=UTF-8

I'd state it this way: a spec needs to be minimally complete

The subset implemented by bitcoin-qt allows description of *all* currently
desirable bitcoin transactions.

The rest of the spec is simply other ways to describe the same = redundancy

In case new transaction types are added, the spec obviously needs to be
extended. But not with a zillion ways to write "send XXX coins to YYY".

Anyway, that's my last word about it.

Wladimir

On Sat, Jan 28, 2012 at 3:12 AM, <bitcoin-list@bluematt.me> wrote:

>
>
> Luke-Jr <luke@dashjr.org> wrote:
>
> >On Friday, January 27, 2012 7:36:31 PM bitcoin-list@bluematt.me wrote:
> >> 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/70f55355e29c8e45b607e782c5d76609
> >> d23cc858.
> >
> >It's been implemented in many clients for nearly all 2011.
> >Bitcoin-Qt is just behind the pace. Not relevant.
> >
> >> 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.
> >
> >You mean 3 months *after* the spec had a consensus and multiple
> >implementations.
> I'm really not gonna reopen this debate.  You made a poll that was worded
> in the most biased way I could think of and still lost.  The multiple
> implementations were written but you and I know of no sites that actually
> had links to your version.
>
>
> ------------------------------------------------------------------------------
> 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
>

--f46d041705ad522a1904b79255d1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div><br></div>I&#39;d state it this way: a spec needs to be=C2=A0minimally=
=C2=A0complete<div><br></div><div>The subset implemented by bitcoin-qt allo=
ws description of *all* currently desirable bitcoin transactions.</div><div=
><br></div>
<div>The rest of the spec is simply other ways to describe the same =3D red=
undancy</div><div><br></div><div>In case new transaction types are added, t=
he spec obviously needs to be extended. But not with a zillion ways to writ=
e &quot;send XXX coins to YYY&quot;.</div>
<div><br></div><div>Anyway, that&#39;s my last word about it.</div><div><br=
></div><div>Wladimir<br><br><div class=3D"gmail_quote">On Sat, Jan 28, 2012=
 at 3:12 AM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-list@bluematt=
.me">bitcoin-list@bluematt.me</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
<br>
Luke-Jr &lt;<a href=3D"mailto:luke@dashjr.org">luke@dashjr.org</a>&gt; wrot=
e:<br>
<br>
&gt;On Friday, January 27, 2012 7:36:31 PM <a href=3D"mailto:bitcoin-list@b=
luematt.me">bitcoin-list@bluematt.me</a> wrote:<br>
&gt;&gt; It was implemented in the waylaying client with the merge of<br>
&gt;Bitcoin-Qt for<br>
&gt;&gt; drag and drop, and just recently for system URI handling in<br>
&gt;&gt;<br>
&gt;<a href=3D"https://github.com/bitcoin/bitcoin/commit/70f55355e29c8e45b6=
07e782c5d76609" target=3D"_blank">https://github.com/bitcoin/bitcoin/commit=
/70f55355e29c8e45b607e782c5d76609</a><br>
&gt;&gt; d23cc858.<br>
&gt;<br>
&gt;It&#39;s been implemented in many clients for nearly all 2011.<br>
&gt;Bitcoin-Qt is just behind the pace. Not relevant.<br>
&gt;<br>
&gt;&gt; However the version on the wiki armed as BIP 20 has a ton of<br>
&gt;extraneous crap<br>
&gt;&gt; in it&#39;s number encoding which is not implemented in Bitcoin-Qt=
 since<br>
&gt;it was<br>
&gt;&gt; explicitly voted against at the time the spec was being discussed.=
<br>
&gt;<br>
&gt;You mean 3 months *after* the spec had a consensus and multiple<br>
&gt;implementations.<br>
</div>I&#39;m really not gonna reopen this debate. =C2=A0You made a poll th=
at was worded in the most biased way I could think of and still lost. =C2=
=A0The multiple implementations were written but you and I know of no sites=
 that actually had links to your version.<br>

<div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
Try before you buy =3D See our experts in action!<br>
The most comprehensive online learning library for Microsoft developers<br>
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,<br=
>
Metro Style Apps, more. Free future releases when you subscribe now!<br>
<a href=3D"http://p.sf.net/sfu/learndevnow-dev2" target=3D"_blank">http://p=
.sf.net/sfu/learndevnow-dev2</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>

--f46d041705ad522a1904b79255d1--