I don't think so. I've seen lots of pages that say "You'll need a WWW
client that understands forms to use this..." I think current practice
most certainly does include the notion of labelling forms-using pages
as such.
> Making
>forms a "separate document type" would grievously wound WWW as it now
>exists.
How so?
An HTTP client, for example, is requried to handle HTML. If we make
forms part of HTML, then all HTTP clients will have to grok forms. I
suggest that forms should be an optional feature. A client should
send:
Accept: application/html-form
to announce that it groks forms.
>If you don't see this, please look harder.
Ok. :-)
>Likewise for inlined images.
I misspoke on inlined images. There's nothing wrong with the IMG
element. But I think we need a way to combine image/gif data and
text/html data into one transaction. But that technique is not
ready for standardization yet. That's what I meant.
Dan