Tim Bray on SellsCon

Don Box's Spoutlet

Syndication

 
Tim calls out that the perceived dependency on XSD hasn't helped community adoption. The problem here is with perception as much as with practice. There are any number of ways to use our current platform (ASMX) without relying on XSD, and the same will be true for Indigo. Moreover, it's not by accident that we spec the WS-* using "exemplar-style" pseudo-schemas and provide XSD as non-normative backup.
 
A related (and interesting) thought experiment is to build a WSDL importer that ignored the wsdl:types/xs:schema element and just provided XmlReader or XmlElement support.  If you assume doc/lit, you could probably get away from processing the binding as well (especially now that WS-Addressing spec'ed how to put Action URI in portTypes where they belong).

Posted Oct 28 2004, 08:10 PM by don-box

Comments

Jon Fancey wrote re: Tim Bray on SellsCon
on 10-29-2004 4:14 AM
Hallelujah! I thought it was just me who's been thinking that WSDL doesn't really add any value when:

1) you're not bothered about XSD and ORM - ie you'll do the message processing yourself
2) you need a more dynamic/flexible binding mechanism than WSDL gives you

I'm glad to hear that Indigo won't be mandating using stuff that we don't always need. Will it make it equally easy NOT to use it though? - because asmx doesn't. WSDL seems to have gained most traction in the codegen'd proxy space with tooling but as we all heard (and agreed?) at the SellsCon last week, that experience isn't always great if constrained by XSD.
Aleksander Slominski wrote WSDL a la dynamic
on 11-21-2004 8:02 PM
I have done exactly this in Super Dynamic Invoker. You can access wsdl/types as XmlElement (my own API not .NET ...) and then if you prefer cast XsSchema view (use to dig sequence of elements for doc/literal bindings) or not - your choice ;-)
yaa wrote re: Tim Bray on SellsCon
on 01-14-2005 5:20 PM
I'm glad to hear that Indigo

Add a Comment

(required)  
(optional)
(required)  
Remember Me?