Closed Unassigned: Need support for Duplicate Class name over differing namespaces [1197]

I was hoping to model two sets with EF which share the same class name, but found this is not possible at the moment.

Consider the following two sets:
1. public DbSet<Postal.Address> Postal_Addresses {get; set; }
2. public DbSet<Email.Address> Email_Addresses {get; set; }

The namespace scopes the domain and meaning of the class, within the namespace code can nominate Address without conflict.

I desire the ability to extend OO .NET concepts through to my ORM of choice. It appears that somewhere along the line EF ignores the namespace, leading to the incidence of collision.

I can certainly get around this limitation, however employing such workarounds reduces the clarity of the code, particularly when the business domain doesn't reflect directly in code.

Your consideration of supporting the full namespace in future versions would be greatly appreciated.
Comments: Duplicate of http://entityframework.codeplex.com/workitem/483