DLinQ = LinQ for SQL
OK, it actually happened. We'll have two mapping technologies in .NET v.next.
LinQ for SQL, previously known as DLinQ is the 'simple' mapping technology.
LinQ for Entities, will be on top of the new ADO.NET Entity Framework, and will be the 'complex' (we could say 'real') mapping technology.
Now, does this make sense? How will someone decide to use one or the other?
I think Microsoft did this for internal politically correctness (they did not want to not to ship any of the frameworks) but I can't see why this is good for the .NET Framework as a whole.