In my opinion, there&#39;s not necessary any payload format (json, xml, multipart). In keeping stuff KISS, everything we need is just an address in response + potentially some stuff like HTTP redirects (for providing additional compatibility for proposal of bitcoin URIs with &quot;amount&quot;, &quot;label&quot; and other parts). I don&#39;t see reason why we need some extra payload yet.<div>

<br></div><div>slush<br><div><br><div class="gmail_quote">On Mon, Dec 19, 2011 at 7:13 PM, Jordan Mack <span dir="ltr">&lt;<a href="mailto:jordanmack@parhelic.com">jordanmack@parhelic.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

If the idea is to &quot;KISS&quot;, and provide a method that is both quick and<br>
easy to implement for the average developer, then JSON is a stand out<br>
option. Using HTTP for the data interchange will make things difficult<br>
for a lot of developers if multipart responses are used. JSON will be<br>
greeted with open arms.<br>
<div class="im HOEnZb"><br></div></blockquote></div></div></div>