I agree with you. I posted the link because I found Steve's challenge interesting and with some merit.

The strength of web services is that I don't care how or where objects are implemented.

lnCanBucks = oCurrExchange.UStoCan(100.00)

This could be a VFP object, a COM object, a DCOM object or a web service. This is simply fantastic.

I can imagine web services that people would gladly pay bucks for
- currency conversion
- complex calculations (thinking of medical, academic or financial)
- medical lab results
- financial transactions like merchant accounts

>Compelling in what sense?
>IMO, the idea of publishing data on the web and fostering interoperability between disparate systems is a pretty compelling idea. Separating the chaff from the wheat, web services is simply a label, one devised by marketing chieftains. If .net does one thing, it makes the production of these sorts of components a bit easier. That too is a compelling thing; regardless of whatever it is called...
>
>IMO, FoxCentral gives a glimpse of what is possible. Check out xmethods.com. There, you will find many of web-services. You might be interested to see who makes the top of the list...
>
>
>IMO, the challenge is akin to finding a compelling use for the automobile; the day after it was invented. On a conceptual level, it is clear to see why the technology that underlies web services is a good thing. It is something that still needs to ripen. With that said, for me, the compelling and most interesting aspect of .Net is found in Windows Forms and the features that allow for easier interaction with the OS.