Abigail, I see your point. I guess mine is if he has a requirement to serialize to flat text why the heck would he not want to look at his options, the limitations of different methods, the complexity of the store -- how it effects all of the objects before he implements everything? Depending on how he implements his options for serialization become very open or very convoluted. If you need 1, take a heavy brick with you and 2, cross a road -- it makes no sense to decide how to cross the road (ignoring the core of bringing the heavy brick with you) cross the road then look back at the heavy brick on the other side wondering how you are going to get it to you. dealing with the storable issues as he decides how to implemnt his objects will save work and make for a more elegant solution.