WSDL and Deem's Dime Dogfood :)
I'm presenting on WSE (Web Services Enhancements) at the Visual Studio/Windows Server 2003 launch in Seattle on Thursday, and while going through an internal Rough Draft my CTO Chris Brooks, brought up the question, but where does WSDL define DIME. My short answer was, "Hell if I know, it's out of band" and Chris said "that's not good enough." So, a little poking around led us to Mike Deem's DIME WSDL Extension roughspec/RFC. What's going on in this space? There's a cacophony of WS-KitchenSink specs out there with all their glorious interrelationships, and WSDL a tricky touch point. I know some folks have strong opinions about WSDL, but regardless, WSDL clearly, as XML is wont to do, can be twisted and turned to fit, but should it be? And until then should I just chalk DIME up as out-of-band literally and contractually? Or do I eat Deem's Dogfood?