- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Wed, 24 May 2006 12:31:40 -0700
- To: <www-ws-desc@w3.org>
- Message-ID: <37D0366A39A9044286B2783EB4C3C4E802B35560@RED-MSG-10.redmond.corp.microsoft.com>
I checked in a new version with the new Woden results, my stylesheet updated to support the soap binding extensions and the safety extension. (doesn't yet do the rpc extension). Naturally, when there was a question I chose my implementation as the baseline ;-). Woden results appear to me to suffer from several problems: 1) {safety} property is often missing. I sent an issue on whether this is a valid interpretation of the spec. 2) When message content model is #none, Woden emits an invalid <elementDeclaration ref="id-null"/> reference. 3) When a binding doesn't specify an interface, Wodwn emits an invalid <interface ref="id-null"/> reference. 4) Woden often omits {soap underlying protocol}, though this is a REQUIRED property in the spec. 5) Some element declaration components still appear to be missing. [ Jonathan Marsh ][ jmarsh@microsoft.com <mailto:jmarsh@microsoft.com> ][ http://spaces.msn.com/auburnmarshes <http://spaces.msn.com/auburnmarshes> ]
Received on Wednesday, 24 May 2006 19:32:53 UTC