Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmx.de
	designates 213.165.64.22 as permitted sender)
	client-ip=213.165.64.22; envelope-from=thomasV1@gmx.de;
	helo=mailout-de.gmx.net; 
Content-Type: text/plain; charset="utf-8"
Date: Sat, 04 Feb 2012 15:03:25 +0100
From: thomasV1@gmx.de
In-Reply-To: <1328034145.2832.11.camel@BMThinkPad.lan.bluematt.me>
Message-ID: <20120204140325.16110@gmx.net>
MIME-Version: 1.0
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>
To: bitcoin-development@lists.sourceforge.net
Content-Transfer-Encoding: 8bit
Subject: Re: [Bitcoin-development] BIP 20 Rejected, process for BIP 21N
Precedence: list

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

-- 
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de