I'm working on a couple of .NET name spaces at the same time towards the goal of having a pretty nice game library. The way I have it organized is that I want a general name space that handles all the graphics stuff and then a separate one, probably within it's own game-centric assembly, that contains all of the objects and data defined specifically for the game. The idea is that I can use the graphics library for any game I want to work on but any avatar classes, AIs, or game rules that I develop should probably be specific to each individual game. The underlying map for the game is basically a tile map. As I was working on defining all the objects I'll need, I realized that there are arguments for putting a map class in either of these name spaces that I've discussed. So far, I'm leaning towards putting the map class within the game specific name space because it's sole purpose is not to manage graphics - graphics are only one part of the data the map will control for me. I'd like to hear other peoples' opinion on this to see if there's anything that I'm failing to take into considerations. Appreciate any input you have. So where would YOU put the map class if it were your project?

 ____________________________