It's in general not good practise to use a service as a tier.
Surely WCF is precicely that though; an abstract bridge between
(generally physical/horizontal) tiers For instance, a smart-client
using WCF to access data from a WCF service over (typically) http[s].
Perfectly normal and indeed the textbook use-case.
For specific scenarios, this does exist - but in quite controlled
scenarios - google for "LINQ to Amazon" for example; not WCF, but a
similar fundamental principle - but it takes a lot of plumbing code.
http://weblogs.asp.net/fmarguerie/ar...to-Amazon.aspx
In the more general sense, I know what the OP is asking for (something
akin to a data-context for a WCF interface), and unfortunately I
haven't seen anything that really fills that gap - but the biggest
barrier is that LINQ really works within a logical (vertical) tier
where you can just about get away with allowing ad-hoc (i.e. not
formally defined up-front) queries, since you are in the same column.
It doesn't work well accross physical (horizontal) tiers, where you
normally want to have well-defined interfaces. That said, the REST
offering in 3.5 may offer some interesting possibilities, since that
is a bit less formalised (allow for better composability); but a
double edged sword...
Marc