On 3/23/06, toydi <[EMAIL PROTECTED]> wrote: > Mark, I notice that form-based language in nature does not describe > the output/response details, contrasting with several others service > description language. I wonder what's the rational behind its design.
That's because the responses are self-descriptive. It would be possible to do both of course - be self-descriptive *and* provide some info up front - but the fact that it hasn't been done before for forms (AFAIK) is probably a pretty good indicator that the tradeoffs don't work in its favour, at least in the general case. I mean, the technique is commonly used in other scenarios where the benefits are clearer, e.g. <img src="foo.jpg" type="image/jpeg"> permits a client to avoid unnecessary image downloads for formats it doesn't recognize, albeit at the cost of the consistency since media type information isn't authoritative and may therefore be incorrect. Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca _______________________________________________ microformats-rest mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-rest
