- From: Mark Nottingham <mark.nottingham@bea.com>
- Date: Tue, 14 Jun 2005 16:20:56 +0200
- To: <hughw@wellstorm.com>
- Cc: "'Paul Downey'" <paul.downey@whatfettle.com>, <public-web-http-desc@w3.org>
I think we're talking about how people use the format here, rather than the format itself. Can someone show (e.g., with examples) how code generation vs. forms surfaces in the format itself? I have been assuming that I'll be using the format to inform the runtime behaviour of the application, and WADL (for example) seems to support this. Is there some what it doesn't? On Jun 14, 2005, at 3:48 PM, Hugh Winkler wrote: > >> On 14 Jun 2005, at 05:29, Hugh Winkler wrote: >> >>> >>>> >>>> If the service suddenly expects the client to send the credit card >>>> number using a different parameter name, >>> >>> No, that wouldn't break using forms. The form sends down the >>> parameter >>> name >>> to use for passing the credit card number. >> >> Er, I could use that argument for any self describing format >> including XML >> >> -- > > Yes, if you augment the XML with rules -- a forms description language > -- > instructing clients how to process the tags. > > > The point being that the "forms description" approach would be more > robust > against this kind of change, than the "code generation" approach. > > > > > > > > > > > > -- Mark Nottingham Principal Technologist Office of the CTO BEA Systems
Received on Tuesday, 14 June 2005 14:21:13 UTC