WCF - Separation of concerns....

So I am finally catching up with the times and really diving into WCF. As usual, I take nothing slow and dived headlong into a project that requires me to utilize clear separations. So having spent a long time building web services that use one basic file to do most everything, I now have a set of logical projects and am confused about how some of them fit:

Interface (IMyWeb)
Web Service (MyWeb) - Has the adds, updates, deletes, gets for user Interface (implements it)
Data contracts - Independent classes {School, Instructor, Course, Class} - feeds MyWeb for properties, no logic, no database access.

Here is where things get fuzzy for me:
MyWebEntities - One entity Class per data contract class that has a mirrored list of properties from the data contract classes.

• What is this supposed to do?
• Where does this fall into the scheme of a WCF Service?
• Should this contain any type of validation or logic?

MyWebLogic Project - One Logic Class for each Data Contract Class (or Entity Class?)

• This should be the layer that interacts with the DAL....Yes?
• If I am looking at this correctly, only the Data Contract OR Entity Class should be feeding or receiving data?

General questions:
1. Where/How should user validation happen in this layout/schema? It would appear that there should be a separate class/project (ugh!!) for security, but am not sure how it should be properly implemented.

Just as a reference, here are the articles I have been using:
Original tutorial: https://www.packtpub.com/books/conte...ice-real-world

Security Article: https://visualstudiomagazine.com/art...cf-4-apps.aspx

Tutorial: http://www.codeproject.com/Articles/...ive-a-Tutorial

Routing services article
http://www.codeproject.com/Articles/...or-Routing-Ser

Thank you in advance and hopefully I can get some help....Typing this out has been less insightful than it usually is! Thanks in advance!

shoreteknow