Best Practice? Transparency of Entity Framework/Linq2sql in Business Layer

I'm into a little migration from traditional DataSets and of course continue go through BL. How do best I create a single class in BL that's acts like a transparent class, for data that are requested from application & not need to be managed开发者_开发百科 differently then it already is in DAL?

Is there some major violation in this idea?

---

Have a look at using POCOs with Entity Framework 4. The linked blog post is a really good starting point.