5 things every Web service developer should know

"It's a plus if you really care about interop, but I admit it's not feasible for most shops given the current tool situation."

How hard is it to use XMLSpy? I know that learning and mastering WSDL, XSD, and XML Namespaces isn't exactly the smallest learning curve in the world - but the investment in time and concentration pays off ten-fold. You can then objectively evaluate SOAP platforms to see how their "autogenerated" WSDL varies, shudder, and then proceed to design your WSDL first and generate your launguage bindings (or, if you've got really complex XSD, go hands on the XML).

I just keep hearing that the tooling will alleviate the complexity, but it is always a better thing to know the spec and understand what the tooling is buying you. Is it really such a bad thing to grit your teeth and learn WSDL?

I'm a fan of XML Spy. I don't use it for WSDL editing, but I use it near exclusively for XSLT and XSD editing. I'd use it for WSDL too, but I don't do much with web services at present.

6) The types of change the definition of entities in the schema can undergo as the service evolves and how to control the fallout of those changes.
7) An understanding of semantics and ontologies - since a schema is defining concepts shared between applications.

Some random links left as flagged in my blogreader that I’m too lazy to comment on right now: Web services-related stuff in The case against high-level components, Whither delivery assurance?; 5 things every Web service developer should know; Retail Tagging ; Contracts define agreement; some posts of general interest: Cocoa and the Emerging Software Market and in the continuing saga...