The navigation property on the "one" side of the relationship would be a collection that could hold multiple instances of the entity on the "many"side of the relationship. It would not be a primary key. The navigation property on the entity on the "many" side would hold an instance of the entity on the "one" side. That would also not be a primary key. For more explanation, see the tutorials http://asp.net/entity-framework/tutorials