We did an event the other day that was called something along the lines of;

"Building Rich Internet Applications with Visual Studio 2008 Service Pack 1"

as part of that, we spent some time talking about Silverlight V2 and some time talking about WPF as it stands in .NET Framework V3.5 Service Pack 1.

One of the pieces of feedback that I got ( I did the WPF part of this session ) was something along the lines of;

"What has WPF got to do with building Rich Internet Applications on Service Pack 1?"

perhaps I didn't do a very good job although ( trying to rebuild my ego here ) it was just one comment out of quite a lot.

So....I took that version of "WPF Airlines" that I ported the other day ( from here ) and repackaged it as an XBAP below;

XBAP Deployment of WPF Airlines

Now, here's some thoughts about this application;

1. It's Rich. Now, it's not perhaps the richest application that you've ever seen but this is WPF V3.5 Sp1 so it can be extremely rich if it wants to be. It just so happens that this sample isn't using all of WPF.
2. It's served from the Internet. It runs online only. It runs inside a browser. It runs inside a sandbox without any "Do you trust this application" style clicks.
3. It's an Application. Don't think there's any doubt about that although clearly it's just a sample with no calls off to back end web services.
4. I built it with Visual Studio 2008 Service Pack 1.

For me, this XBAP is a Rich, Internet Application. If it's not a Rich, Internet Application for you then I'd be interested in why it's not? Possibly the definition of Internet isn't how you think of Internet?