MIME-Version: 1.0
References: <CACUQsLKTHVE7pe=0-zuMTGZWbUaJFp5=CNZCQE0477B7LZRsbg@mail.gmail.com>
	<CAHGSxGuqf2vKOWtW-_hfdqfsH8a_QTaWBsrUViV8A39dk1KA6A@mail.gmail.com>
	<871627c9-8679-5f82-a76f-cec9ffa28379@c3d2.de>
In-Reply-To: <871627c9-8679-5f82-a76f-cec9ffa28379@c3d2.de>
From: Clark Moody <clark@clarkmoody.com>
Date: Thu, 18 Oct 2018 17:27:41 -0500
Message-ID: <CAHGSxGssNaVn_CAK252D_N8hzLFLnBFO8XPJLrCAHVw9+gCLWQ@mail.gmail.com>
To: vv01f@c3d2.de, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="000000000000243e9e0578884d7b"
Subject: Re: [bitcoin-dev] BIP for segwit compatibility URIs
Precedence: list

--000000000000243e9e0578884d7b
Content-Type: text/plain; charset="UTF-8"

I agree with spelling out the `address` field.

As for "value is either an address or an array of addresses", there is no
standard for specifying an array in a URI, and processing different
querystring schemes is application-specific. (see
https://stackoverflow.com/a/9547490)

Since those app-specific methods don't necessarily preserve order, which is
important here, the most compatible fallback is a delimiter-separated list
under one parameter. Most languages have library functions for splitting
strings on commas.


-Clark


On Thu, Oct 18, 2018 at 5:13 PM vv01f via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> I already pointed out a while ago that the separator could be the & and
> the returning value is either an address or an array of addresses.
> So no comma or other delimiter needed.
> also I would suggest to call the parameter `address` and not a shortcut
> for it as we are used to `message` and `amount` spelled out as well.
>
> On 18.10.2018 16:20, Clark Moody via bitcoin-dev wrote:
> > Since we don't know what sort of address changes will happen later on,
> you
> > could make this future-proof by passing a list of addresses to `addr`.
> >
> > The syntax is
> >
> > bitcoin:<address>[?addr=<address>[,<address>[,<address>]]]
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:tahoma,sans-serif;font-size:small;color:rgb(0,0,0)">I agree with s=
pelling out the `address` field.</div><div class=3D"gmail_default" style=3D=
"font-family:tahoma,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div>=
<div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif;font-si=
ze:small;color:rgb(0,0,0)">As for &quot;value is either an address or an ar=
ray of addresses&quot;, there is no standard for specifying an array in a U=
RI, and processing different querystring schemes is application-specific. (=
see <a href=3D"https://stackoverflow.com/a/9547490">https://stackoverflow.c=
om/a/9547490</a>)</div><div class=3D"gmail_default" style=3D"font-family:ta=
homa,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div><div class=3D"g=
mail_default" style=3D"font-family:tahoma,sans-serif;font-size:small;color:=
rgb(0,0,0)">Since those app-specific methods don&#39;t necessarily preserve=
 order, which is important here, the most compatible fallback is a delimite=
r-separated list under one parameter. Most languages have library functions=
 for splitting strings on commas.<br></div><div><div dir=3D"ltr" class=3D"g=
mail_signature"><div><br></div><div><br></div><div>-Clark</div><div></div><=
/div></div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">=
On Thu, Oct 18, 2018 at 5:13 PM vv01f via bitcoin-dev &lt;<a href=3D"mailto=
:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.o=
rg</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I already pointed=
 out a while ago that the separator could be the &amp; and<br>
the returning value is either an address or an array of addresses.<br>
So no comma or other delimiter needed.<br>
also I would suggest to call the parameter `address` and not a shortcut<br>
for it as we are used to `message` and `amount` spelled out as well.<br>
<br>
On 18.10.2018 16:20, Clark Moody via bitcoin-dev wrote:<br>
&gt; Since we don&#39;t know what sort of address changes will happen later=
 on, you<br>
&gt; could make this future-proof by passing a list of addresses to `addr`.=
<br>
&gt; <br>
&gt; The syntax is<br>
&gt; <br>
&gt; bitcoin:&lt;address&gt;[?addr=3D&lt;address&gt;[,&lt;address&gt;[,&lt;=
address&gt;]]]<br>
<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--000000000000243e9e0578884d7b--