wsdl s:schema_WSDL和Deem's Dime Dogfood :)

wsdl s:schema

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?

我将在周四在西雅图举行的Visual Studio / Windows Server 2003发布会上介绍WSE(Web服务增强)，并且在通过内部草稿时，我的CTO Chris Brooks提出了问题，但是WSDL在哪里定义DIME 。 我的简短回答是：“如果我知道，那是不合时宜的”，克里斯说：“那还不够好。” 因此，经过一番摸索，我们找到了Mike Deem的DIME WSDL Extension粗糙文档/ RFC 。 在这个空间里发生了什么？ WS-KitchenSink规范之间存在各种光荣的相互关系，而WSDL是一个棘手的接触点。 我知道有些人对WSDL有很强的见解，但是不管怎么说，WSDL显然是XML所不能做的，它可以被扭曲并变成合适的形式，但是应该吗？ 在那之前，我是否应该按字面意思和合同方式将DIME视为带外内容？ 还是我吃Deem的Dogfood？

翻译自: https://www.hanselman.com/blog/wsdl-and-deems-dime-dogfood

wsdl s:schema