Re: HTML JSON form data

Hi Larry,

Can you cite specific technical issues which you believe are higher
priority and a rubric for why that's true? Or can you cite data to suggest
that this complexity isn't already being borne by many in the form of
pervasive library code (e.g., I know we had a dojo.formToJson() method for
nearly identical functionality because it was so commonly requested and
Form serialization is welded-shut in the platform).

If anything, it seems the technical argument here should be that blessing
*any* encoding without describing the mechanism by which it works is
anti-extensibility and therefore robs all users of power and generality.

Regards

On Fri, May 30, 2014 at 12:06 AM, Larry Masinter <masinter@adobe.com> wrote:

>  This is a good example of adding new features without paying attention
> to fixing what’s already there in need of clean up.
>
> The result is an even more complex platform and more unreliability, not
> less.
>
>
>
>
>
> *From:* Larry Masinter
> *Sent:* Thursday, May 29, 2014 11:25 PM
> *To:* 'public-html@w3.org'
> *Subject:* Re: Extension specification proposal: JSON form submission
>
>
>
> Although form submission in JSON might have been nicer than what we have,
> I see no prospect of ever getting rid of either x-url-encoded or
> mulipart/form-data.   Before you put a lot of effort into adding something
> new that will just add to complexity and implementation burden, could you
> please give some serious attention to the mulipart/form-data spec?
>
>
>
> https://github.com/masinter/multipart-form-data
>
>
>
> Including test framework. Review, update, pull requests.
>
>
>
> Larry
>
> --
>
> http://larry.masinter.net
>
>
>