W3C HTML JSON form submission
1–10 of 103 posts
Re: W3C HTML JSON form submission
#2They're still working on XForms after 10 years http://www.w3.org/MarkUp/Forms/
Re: W3C HTML JSON form submission
#3> wow[such][deep][3][much][power][!]
And there goes my interest for this submission. Don't use overused memes in a submission. Liking the idea though.
Re: W3C HTML JSON form submission
#4They're still working on XForms after 10 years http://www.w3.org/MarkUp/Forms/
Isn't that kind of like saying "They're still working on HTML after 23 years"? Technically you're right, but version 1.1 of XForms was completed and published over 5 years ago.
That said, XForms is dead AFAIK, and that's not a bad thing.
Re: W3C HTML JSON form submission
#5Guessing that it's interesting when using an uniform endpoint for both forms and js-driven requests.
Re: W3C HTML JSON form submission
#6Kind of nice, basically turns form submission into a bare-bones API call.
Re: W3C HTML JSON form submission
#7In fairness, you have to look at how standards get somewhere - this is an editor's draft which is a starting point of an idea rather than a done deal. Don't be surprised if the final product winds up being significantly different than this - even better, get involved in the conversation to make it what we need. That's not to pour cold water on it: It's good as it is, but there are changes which potentially help explain the magic of participating in form encoding and submission which may be better and allow more adaptation and experimentation over time.
Re: W3C HTML JSON form submission
#8Submitting files with this form encoding is of course going to have the base64 overhead, but otherwise this looks great!
Re: W3C HTML JSON form submission
#9Can we just get rid of HTML and replace it with JSON while we're at it?
Re: W3C HTML JSON form submission
#10It amazes me that we're now at the point of standardizing sticking array references inside strings and yet we're still not having a serious discussion about what comes after HTML.