In the latest episode of my Microsoft Conversations series I talked with Pablo Castro about Astoria, a layer of middleware that makes data readable and writeable by means of a RESTful interface. Even if you don't know or care about the buzzwords, it's easy to show what Astoria does and to explain why it's interesting. One of the sample databases configured to work with the experimental version of Astoria is a subset of the Encarta encyclopedia. You don't have be a programmer or grok XML in order to appreciate the Astoria-enhanced version of Encarta.
A database with Astoria layered on top of it isn't a web application, but it's within shouting distance of being one, and you don't even have to shout very loudly.
I'm not even close to being an expert in the underlying data access technologies, including ADO.NET, the Entity Data Model, and LINQ, so parts of the discussion quite frankly went over my head. Nor am I yet familiar with the tooling that's required to wrap this kind of services layer around a plain data source. But I'm 100% clear that it's a good idea, and a great example of RESTful web services -- a book that Pablo Castro says is "required reading" for members of the Astoria team.