I recieved an email saying I could win a prize by just bloging about it... so here it is:
Now seriously, I'm not intimate with the product itself, nor have I done much WS developement in a long time. I have, however, done web services programming some time ago, and read a lot of info about it. and it seemed and still seems logical to me to first define the contract - i.e. the interface, and go from there to defining and coding the actual implementation. This seems the closest to OO design, where the internals don't matter as much as what is public.
I won't blabber to much about it, go and check it out, if you like it -
buy it keep it - it's free! (thanks for the reminder I missed that)