From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Rti5H-00014h-3x for bitcoin-development@lists.sourceforge.net; Sat, 04 Feb 2012 16:03:27 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.161.175 as permitted sender) client-ip=209.85.161.175; envelope-from=g.rowe.froot@gmail.com; helo=mail-gx0-f175.google.com; Received: from mail-gx0-f175.google.com ([209.85.161.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1Rti5D-0004Fb-UF for bitcoin-development@lists.sourceforge.net; Sat, 04 Feb 2012 16:03:27 +0000 Received: by ggeq1 with SMTP id q1so3015901gge.34 for ; Sat, 04 Feb 2012 08:03:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.187.3 with SMTP id x3mr12843019yhm.50.1328371398575; Sat, 04 Feb 2012 08:03:18 -0800 (PST) Sender: g.rowe.froot@gmail.com Received: by 10.236.195.99 with HTTP; Sat, 4 Feb 2012 08:03:17 -0800 (PST) Received: by 10.236.195.99 with HTTP; Sat, 4 Feb 2012 08:03:17 -0800 (PST) In-Reply-To: <20120204140325.16110@gmx.net> 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> Date: Sat, 4 Feb 2012 16:03:17 +0000 X-Google-Sender-Auth: rmATmVj7reY4ItTw9PtSwqTnaKU Message-ID: From: Gary Rowe To: Bitcoin Development List Content-Type: multipart/alternative; boundary=20cf305b0a3a57865c04b8259128 X-Spam-Score: -0.5 (/) 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (g.rowe.froot[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Rti5D-0004Fb-UF Subject: Re: [Bitcoin-development] BIP 20 Rejected, process for BIP 21N 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, 04 Feb 2012 16:03:27 -0000 --20cf305b0a3a57865c04b8259128 Content-Type: text/plain; charset=UTF-8 Seems reasonable to me. On 4 Feb 2012 14:03, 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". > > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > > ------------------------------------------------------------------------------ > 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 > --20cf305b0a3a57865c04b8259128 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

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 =C2=A0transaction. This has use cases that go beyond QR codes.

If I am right, then I would say that naming it "message" is misle= ading. In fact, "message" suggests that a message will be sent to= someone (the recipient of the funds? a third party?), which is not the cas= e 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

---------------------------------------------------------------------------= ---
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-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment
--20cf305b0a3a57865c04b8259128--