Todd, The reality is that vendor implementation of standards such as XML schema in their toolkits are.... inconsistent. There was a major thread on this particular topic on the SOAP Builder list some time ago in which I, and some of the other folks on this list [Hiya Anne :-)] participated in. I've tried to put together a synopsis of that discussion here: SOAPBuilders Discussion Summary on Web Services Interoperability Issues (March 2005) http://www.securesoa.com/blog/PermaLink,guid,149f0037-8d96-4519-8a2d-e9e 76c5ffee4.aspx As to guidance and documents on schema design, a good starting point is to look at the document from Eve Maler [Sun] for the various schema design styles that are available to you such as Russian Doll, Salami Slice, Venetian Blind, Garden of Eden etc. You can find that document here: http://www.idealliance.org/papers/xml02/dx_xml02/papers/05-01-02/05-01-0 2.html#schema-style I've also come across some documents that provide pretty good and explicit guidance for XML Schema design when it comes to the web services. I have pointers to them here: Guidelines for XML Schema Design to Improve Web Services Interoperability http://www.securesoa.com/blog/PermaLink,guid,e15ab18d-6e1a-4c9c-ab92-8db d9103632a.aspx And as a practioner who deals with Interop, angle brackets and technology blinders :-) on a daily basis, the approach I follow for developing Interoperable web services is documented here: Schema-First/Contract-First/Top-Down Style of Development & Tools http://www.securesoa.com/blog/PermaLink,guid,a87cdfc9-d5d2-4a5c-91ff-369 a1f38d7cf.aspx Regards, - Anil
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Biske, Todd Sent: Wednesday, November 09, 2005 9:57 AM To: [email protected] Subject: [service-orientated-architecture] Best practices for XML Schema usage in Web Services A colleague and myself have been trying to bridge his world of XML schemas, coming from a database modeling background, and my world of Web Services, and it hasn't been easy. Where things break down are where we start to discuss mapping XML Schema back to a Java or C# class model. I'll admit that the problems go away if we implement web services using what I term a schema-oriented development environment, typically associated with the BPM space. It appears to me that there are approaches to XML Schema design that will make a mapping to a class model easy, and there are approaches that will make things difficult. I haven't seen any such list documented, however. A decision that will need to be made is whether or not I should expect developers to begin from a method that looks something like: XMLDocument myServiceCall(XMLDocument request) or whether it's realistic to map XML Schema types to a class hierarchy, letting developers work with something that will be a bit more familiar. Thoughts? Any pointers to some good guidance in this space? Thanks- Todd Biske Software Infrastructure Engineering A.G. Edwards Technology Group, Inc. V:(314) 955-6254 F:(314) 955-4055 E:[EMAIL PROTECTED] ------------------------ Yahoo! Groups Sponsor --------------------~--> Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life. http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
