Re: GET should be encouraged, not deprecated, in XForms [was: Issue request for the TAG: XForms]

"David E. Cleary" wrote:
> 
> > Some of the most important forms users in the world will not move to
> > XForms if they do not support GET. This includes Google, Yahoo, eBay
> > etc. They understand why GET is important and use it appropriately.
> 
> Could you enlighten me as to why GET is important and appropriate for
> submitting forms as opposed to POST?

http://lists.w3.org/Archives/Public/www-forms/2002Jan/0119.html

>...
> The same reason anything gets deprecated. It has been superseded by
> something better suited for the task at hand. 

That's the problem. There is nothing in XForms that solves this problem
better.

> ... Now I'm no history major in
> regards to the development of HTTP, but if there was no POST in the
> beginning, then overloading GET the way it has been was certainly a valid
> way to go. 

No, it would not. GET is for GETting information. i.e. all articles
older than six months with the name "Cleary" in the newsgroup
"comp.text.sgml". What user interface would you like on that query? A
form!

POST and PUT are for POSTing and PUTting information. For logically
adding data to the server. They do something totally different.

>...
> BTW, XForms has deprecated the use of DTDs and uses XML Schema instead. Now
> DTDs were a key part of the XML 1.0 design and people built wonderful
> applications around them, so does that mean XForms should be required to use
> them?

You replaced DTDs with Schemas. What have you replaced GET with? How do
I do a safe, idempotent query that returns a URL that I can cut and
paste from a browser into an email or dictate to my mother over the
phone?

 Paul Prescod

Received on Wednesday, 23 January 2002 16:09:41 UTC