I dunno -- the more I think about it, the more the idea isn't crazy. From a well-formatted Web Service, there's enough metadata to be able to build a UI (indeed, that's how one typically works with Web Services in the Microsoft stack). And Querki is flexible enough that building at least a crude mapping probably isn't that hard.

And having said yesterday that I don't know *why* we would use that, I've come up with two concrete Use Cases for it in the past 18 hours. So this might make it into the medium-term stack yet...