Cart
|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Challenge
 Didier, >In fact, I hope that W3C workgroup listen to this tread because they will learn something in the process. Hope they will use this as a use case. I see you are frsturated, but I'd like to reiterate that the use case you describe is *exactly* the one addressed by the W3C XForms Recommendation. Exactly. That's what an XForms client does -- it fetches an XML instance document to edit, and a data model for that instance, and a presentation layer, edits the document, and posts it back using POST or PUT. (XForms can do a few other tricks, but that's beside the point.) The data model uses XPath and XML Schema Part II (Datatypes), which are W3C recommendations, and can optionally use Part I (Strutures) as well. There are some people interested in ISO DSDL/Relax NG support, and I count myself among the interested parties. As for SOAP and XML-RPC and WEBDAV, the XForms specification allows for implementations to add other submission methods in an extensible way, and my guess is that future versions of XForms will codify something that people have decided works in that area. Leigh. -----Original Message----- From: Didier PH Martin [mailto:martind@n...] Sent: Thursday, November 06, 2003 6:44 AM To: 'Bill de hÓra' Cc: xml-dev@l... Subject: RE: Challenge Hi Bill, Bill said: I assume that whatever you all come up with, this document is coming back in a POST. Didier replies: Not necessarily, using xmlHTTP (available in both Mozilla and IE) we can send back the XML document and use a PUT HTTP method. Why did you assume that we would use a POST? Did you made the inference that we would use an HTML form? The requirement is that an XML document is to be returned to the server. Did you had in mind that we would use a SOAP call? Could be if the returned document is to be stored on a server having that kind of web service interface. Did you had in mind that the returned XML document is moved to the server with a POST? Could be if the server imposes that the document is returned through a POST. In any cases, the returned message would be through an HTTP POST or PUT (I doubt delete would do the job to update the document on the server). In the case of a POST the message payload could be packaged as SOAP or otherwise. In the case of PUT as sent though the initial GET but this time with the data content filled. UP to now, it is clear and obvious that using standard technologies it is not that obvious to simply get an XML document, fill it up and return it to the server. This is why it is so important to get at least a simple working example. In fact, I hope that W3C workgroup listen to this tread because they will learn something in the process. Hope they will use this as a use case. Cheers Didier PH Martin http://didier-martin.com 
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! 
Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||
