Received-SPF: pass (sog-mx-4.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; 
From: Matt Corallo <bitcoin-list@bluematt.me>
To: bitcoin-development@lists.sourceforge.net
In-Reply-To: <CAKm8k+0V+LEBESkp18uhQR6CniLogobpxY_34YBqDM0VYcmzzw@mail.gmail.com>
References: <1328020046.70720.YahooMailNeo@web121002.mail.ne1.yahoo.com>
	<1328025899.2832.5.camel@BMThinkPad.lan.bluematt.me>
	<1328034145.2832.11.camel@BMThinkPad.lan.bluematt.me>
	<20120204140325.16110@gmx.net>
	<CAKm8k+0V+LEBESkp18uhQR6CniLogobpxY_34YBqDM0VYcmzzw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Sat, 04 Feb 2012 12:15:02 -0500
Message-ID: <1328375702.27827.3.camel@BMThinkPad.lan.bluematt.me>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [Bitcoin-development] BIP 20 Rejected, process for BIP 21N
Precedence: list

I changed the description of the message parameter to be a bit more
descriptive, however, I dont want to change the name of the parameter
because some clients have already implemented that and I really prefer
to make as minor of changes as possible to this BIP even if it is
officially only a Draft.  

Matt

On Sat, 2012-02-04 at 16:03 +0000, Gary Rowe wrote:
> Seems reasonable to me.
> 
> On 4 Feb 2012 14:03, <thomasV1@gmx.de> wrote:
>         Just another question concerning BIP21:
>         
>         On the wiki, the description of the "message" parameter reads:
>         "message that shown to the user after scanning the QR code"
>         
>         I believe that the purpose of this parameter is to contain a
>         description of the  transaction. This has use cases that go
>         beyond QR codes.
>         
>         If I am right, then I would say that naming it "message" is
>         misleading. In fact, "message" suggests that a message will be
>         sent to someone (the recipient of the funds? a third party?),
>         which is not the case here. That parameter should probably be
>         called "description".